-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Doing satpulsetool gps --gnss BDS on a NEO-F10N gets an error from the receiver.
What happens is:
- satpulse does a wildcard read of CFG-SIGNAL-* properties
- this includes s CFG-SIGNAL-BDS_B1_ENA
- satpulse infers that the the NEO-F10N supports BDS B1 (usually this is a safe inference: receivers don't have keys for signals they don't support)
- satpulse accordingly sends a message enabling BDS B1, B1C and B2A
- the receiver rejects this because it doesn't actually support BDS B1
I don't think there is any way to figure out what signals it does actually support without having hard-coded knowledge.
Maybe the best fix is #97
Metadata
Metadata
Assignees
Labels
No labels