AP_GPS: Add driver option to allow GPS autobaud bypass and instead use configured SERIALx_BAUD #25488
+80
−28
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
* Adds ability to stop autobaud on all receivers Signed-off-by: Ryan Friedman <ryanfriedman5410+github@gmail.com>
Signed-off-by: Ryan Friedman <ryanfriedman5410+github@gmail.com>
Ryanf55
changed the title
Signed-off-by: Ryan Friedman <ryanfriedman5410+github@gmail.com>
Ryanf55
force-pushed
the
gps-bypass-autobaud-use-serial-manager-baud
branch
from
9f58821 to
80fed87
Compare
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 is a draft of allowing users to manually configure the baud rates. See #25449 for more context, which illustrated the need for a generic way to handle manual baud rates rather than driver-specific bits or params.
The goal of this work is to allow using any of the manual baud rates from SERIAL3_BAUD and bypass autodetection. With this feature, the correct driver is immediately instantiated, and more immune behavior to GPS power cycles triggering autobaud sequences.
Because the only way that SBF and SBF2 are differentiated is in their detection sequence, this probably shouldn't be used on those devices. Or, run the detect sequence for SBF/SBF2, but don't switch baud if the detect fails.