AP_Periph: Add MSP sensor output #15229
Closed
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
digitalentity
approved these changes
Sep 3, 2020
|
I'm getting 50Hz update rate on GPS which seems wrong. We should be waiting for a new GPS message and propagate it to CAN/MSP and not send dummy updates. Alternatively we can keep it as-is and de-dupe on AP/INAV side based on |
|
replaced by #15232 |
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.
This adds MSP sensor output to AP_Periph, allowing for a GPS to produce GPS, mag and baro data for both ArduPilot and INAV. Developed in collaboration with Konstantin from INAV
Only GPS tested to far
Matching PR in INAV: iNavFlight/inav#6090