Current consumption alarm in OSD element #4715
Merged
Conversation
This file contains hidden or 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
giacomo892
reviewed
May 17, 2019
nmaggioni
force-pushed
the
nm_current_consumption_alarm
branch
5 times, most recently
from
754f62e to
81adc61
Compare
nmaggioni
force-pushed
the
nm_current_consumption_alarm
branch
from
81adc61 to
5b48025
Compare
nmaggioni
changed the title
shellixyz
approved these changes
May 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Blinking alarm for Amps consumption, can be useful when running Li-Ion. The threshold is specified in full Amperes, I don't think that more precision is needed at this stage.
Partially solves #4666. Alters the MSP payload for the configurator.