Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Multiple low battery thresholds #3561

Closed
faceEater opened this issue Jan 28, 2016 · 4 comments
Closed

Feature request: Multiple low battery thresholds #3561

faceEater opened this issue Jan 28, 2016 · 4 comments

Comments

@faceEater
Copy link

It would be convenient to have an option to sound the beeper to allow the pilot to take manual action at some voltage above that which triggers the battery failsafe. I don't want my copter to RTL/LAND every time it gets low on battery due to the risk of colliding with an obstacle while trying to do so, but it would be good if it could do so if its battery reached a "critical" level, after having started beeping when the battery was "low" (for example, this would be useful if I couldn't hear the beeper, or it were broken/unplugged). The possibility to make the failsafe choose LAND instead of RTL if it is too far from home would also be a nice touch.

@kosmikkosmik
Copy link

Maybe a better way is to incorporate distance and RTL speed into warning indicator instead. I've implemented similar feature in my fork of MinimOSD - show remaining flight time given battery %, current draw, distance to home and RTL speed settings.

@magicrub
Copy link
Contributor

Does this PR satisfy this issue? #5000

@WickedShell
Copy link
Contributor

It doesn't satisfy it for copter. It was a plane only, but it does pave the way for copter to be an easy addition.

@WickedShell
Copy link
Contributor

#7213 provides two stage battery failsafes, which you could configure low to be no action, which will still emit a warning message as well as set the battery warning bit to warn the user, then set the critical action to land. Closing this as we have more then enough issues open tracking this same feature set. (This is at least the 4th by my count)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants