[GPS] Fix GPS dynamic model setup for M10 GPS units#10199
Merged
Conversation
The old message probably works on M10 by accident, as it is not even mentioned in the manual anymore.
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
1 participant
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.
Another round of ublox updates.
Dynamic model was the last piece of code using deprecated APIs to setup configuration.
This config was probably failing on M10 gps.
Also update the gps_ublox_nav_hz to use the correct API for newer units.
The fact it worked with M10, using the obsolete APIs, seems to be an oversight, since the docs don't even mention it anymore.