Expose u-blox min elevation and min SNR parameters RTK Fix Improvements #25720
+41
−1
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.
Solved Problem
When using the u-Blox RTK F9P with the PX4-Autopilot, I found that it will get RTK Fix, but it often drops to other fix mode. I have been reading about this issue, and encountered the following artcles: https://mowerproject.com/2020/07/06/an-even-better-rtk-fix/ and https://discuss.cubepilot.org/t/here-does-not-hold-rtk-fixed-status-reliably-help-please/1056, which mentions that increasing the
CFG-NAVSPG-INFIL_MINCNO
from the default 10 to 15 deg, andCFG-NAVSPG-INFIL_MINELEV
from 6 dBHz to 35 dBHz ouputs a more reliable RTK Fix.Potentially fixes #21555 by improving the RTK fix reliability issue if there is no RTCM drop out but RTK fix changes to other fix mode, although this will not handle RTCM drop outs and it's a separate issue.
Solution
Note: This PR needs the GPS Driver submodule to be merged to main before merging this PR to main.