Skip to content

Conversation

@reimerix
Copy link
Contributor

@reimerix reimerix commented Jul 20, 2020

This PR adds the MSG_GNSS_TIME_OFFSET to the SBP protocol. It contains the offset between a local time (unique to the sender ID emitting the messages) and the GNSS time scale.

Copy link
Contributor

@GuillaumeDec GuillaumeDec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍
Was there any other extra autocheck / autotest for c or rust that was left untracked? (just checking, as i missed a couple when creating the leader msg..)

Copy link
Contributor

@lloydmaza lloydmaza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me overall, however I may have missed a discussion addressing the situation in which multiple sensors in the same stream require GNSS time offsets. I didn't see any fields in the message itself which would identify any associated messages to which the offset applies - perhaps it's the intent of the flags field for a future date?

@reimerix
Copy link
Contributor Author

@lloydmaza If a device has multiple sensors connected, it should be using the same clock to timestamp them. I don't think we would need more than one time offset by sender. If a device happens to timestamp different sensors with different clocks, it could also send out these messages with different sender ids.

@GuillaumeDec No other untracked files 🙂

@reimerix reimerix merged commit ffb9e01 into master Jul 21, 2020
@reimerix reimerix deleted the reimerix/hs-56/add-time-offset-message branch July 21, 2020 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants