batteryCheck: add new battery threshold for arming (COM_ARM_BAT_MIN) #22175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
bkueng
approved these changes
Oct 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved Problem
Currently the battery checks make sure that arming is not possible when the SOC is below the warning threshold (BAT_LOW_THR). BAT_LOW_THR is though in the first place thought to be the in-flight battery level warning. For systems that require a lot of energy during takeoff (eg VTOLs) it is beneficial to have a separate, higher threshold to prevent arming.
Solution
Add new battery threshold for arming (new parameter COM_ARM_BAT_MIN).
Changelog Entry
For release notes: