Spektrum telemetry minor fix to address false Fastboot alerts on radios with latest update #9743
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
…xFF's to 0x00 to account for new fastbootUptime variable
mmosca
added a commit
that referenced
this pull request
Feb 22, 2024
JulianTiller
pushed a commit
to JulianTiller/inav
that referenced
this pull request
Oct 18, 2024
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.
Our recent radio update has an addition to the STRU_TELE_RPM telemetry packet type, which causes a telemetry alarm if the previous spare bytes were populated with 0xFF's instead of 0x00's.
This pull request adds the new variable (fastbootUptime) to the commented description of the struct, and changes the fill value to 0's.
I've tested this change on a REVO board
Same issue has been submitted and merged in betaflight.
betaflight/betaflight#13383