-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use periodic messages on M10SPG #57
Open
AngusJull
wants to merge
21
commits into
main
Choose a base branch
from
m10spg-pvt-message
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Added configuration for the platform model, which will prevent gps data from being discarded during flight, and increased the mesasurement rate to roughly 3Hz
It seems that using the hypothetical limit on update rate for NAV-PVT causes problems with messages after about 10 have been recieved. This might be a problem with periodic/polled messages. Also fixed the config key, and moved some definitions
Premade messages shouldn't be neccessary with a periodic messaging system, and will just take up space
Filled in a couple functions and changed how valset works to better support these functions
Added some todo messages for future changes, and updated the main function to use the new periodic message interface
- Now sending and recieving a UBXFrame so information about lengths of messages and types are not lost upon return, also allows return error codes - Using send_valset in the enable_periodic function, reducing duplicated code and adding an actual check to the configuration - Updated the premade headers and added a way to check if a message is of a specified type, these headers may be useful for assembling a rarely polled message in the future
Closes #45 - this is a good start on periodic message reception. |
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.
Periodic messages offer a number of benefits over regular polling
Also made a couple other changes