Fix F9P GNSS config keys broken by F10N support commit#184
Open
mattbnz wants to merge 1 commit into
Open
Conversation
The F10N support commit (e730cb3) changed the F9P BDS B2I key from 0x0e to 0x0f and added F10-only key 0x10310028 (BDS_B2A). The F9P NACKs the entire VALSET due to the unrecognized key, crashing ubxtool. https://claude.ai/code/session_01E9A3S4UwqgCZfo7i865ayL
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
2 participants
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.
Hi Bert,
I recently upgraded galmon and my ZED-F9P stopped working:
I fed the logs and the repo to Claude to debug and it came up the attached commit and rationale:
I have rebuilt with the patch to restore the v9 VALSET and that correctly makes my station (no 135) report again, so it seems Claude is not entirely hallucinating, I also cross-checked against https://content.u-blox.com/sites/default/files/documents/u-blox-F9-HPG-1.51_InterfaceDescription_UBXDOC-963802114-13124.pdf p286 which only contains the 0x0e key (no 0x0f or 0x28 which are only present in the https://content.u-blox.com/sites/default/files/documents/u-blox-F10-SPG-6.00_InterfaceDescription_UBX-23002975.pdf)
So given those docs, my now working receiver and the original commit also not appearing to intending to modify F9P setup per its description I'm pretty confident I'm not sending you slop... but I wrote/debug none of this myself either :)