Added UART timestamp API for mavlink vision and GPS timing #8403
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
|
well.. that was quick! |
tridge
changed the title
|
ping @WickedShell, I've added use of this API for UBLOX as well |
|
Looks ok to me.. |
|
from a chat with @WickedShell it sounds like he would prefer more investigation and testing into the GPS changes so perhaps we should pop the last commit off before merging for now. |
this is used for mavlink vision time estimates
|
gps changes removed into a separate PR |
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 a API on our UART drivers for getting the timestamp of the last input bytes. This is then used for vision processing to constrain the latest possible time the message arrived, which makes the timestamping of vision messages more accurate.
pair-programmed with @peterbarker