Conversation
Bug fix to correct returning mm units of altitude to m.
Member
|
was it wrong before f000238#diff-befa46f2bd4efc7a67651a054834b31a6eee6aa04341559f93dd36b164087d82L248 then? |
bresch
requested changes
Jun 24, 2024
bresch
approved these changes
Jun 24, 2024
Contributor
Author
|
Cool! Thanks @bresch for looking into this. |
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
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
When sending CRSF telemetry, the GPS message provided an incorrect value for altitude [m]. This is because the existing PX4 code assumed the altitude_msl_m in the SensorGPS uORB message was in units of mm, instead of m.
Solution
Removed scaling of the altitude in the uORB message by 1000.
Changelog Entry
Bugfix for CRSF GPS telemetry
Test coverage
Tested with ELRS transmitter in the loop to confirm correct values.