Config Navmask #171
-
Hi everyone, I'm trying to configurate the NAVMASK of SV, and I get ACK-NAK from the Ublox receiver:
Just wondering what's wrong with my code. I'm using ZED-F9T |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
What firmware version are you running on the F9T? TIM 2.20 or TIM 2.24? I don't have an F9T to hand, but I've just tried the same on an F10T running firmware TIM 3.01 protocol 42.01 using a modified verson of the ubxpoller example, and I get an ACK-NAK with a mask of b"\x00", but a successful ACK-ACK with various other permissible values including b'\xff\xff\xff\xff\xff\xff\xaa\xaa' and b'\xff\xff\xff\xff\xff\xff\xff\xff' (the protocol default). I think the problem is simply that your mask is invalid - have a look at the Interface Manual for your firmware version - in particular Table 18 - for further details, or raise a query in the u-blox support forum. Starting handler threads. Press Ctrl-C to terminate...
<UBX(CFG-VALSET, version=0, ram=1, bbr=0, flash=0, action=0, reserved0=0, CFG_NAVMASK_SV_MASK_GAL=b'\x00')>
<UBX(ACK-NAK, clsID=CFG, msgID=CFG-VALSET)>
Stop signal set. Waiting for threads to complete...
Processing complete Starting handler threads. Press Ctrl-C to terminate...
<UBX(CFG-VALSET, version=0, ram=1, bbr=0, flash=0, action=0, reserved0=0, CFG_NAVMASK_SV_MASK_GAL=b'\xff\xff\xff\xff\xff\xff\xaa\xaa')>
<UBX(ACK-ACK, clsID=CFG, msgID=CFG-VALSET)>
Stop signal set. Waiting for threads to complete...
Processing complete Starting handler threads. Press Ctrl-C to terminate...
<UBX(CFG-VALSET, version=0, ram=1, bbr=0, flash=0, action=0, reserved0=0, CFG_NAVMASK_SV_MASK_GAL=b'\xff\xff\xff\xff\xff\xff\xff\xff')>
<UBX(ACK-ACK, clsID=CFG, msgID=CFG-VALSET)>
Stop signal set. Waiting for threads to complete...
Processing complete |
Beta Was this translation helpful? Give feedback.
-
Hi @semuadmin, Thank you for your answer. |
Beta Was this translation helpful? Give feedback.
Question for the u-blox forum I think... I suspect it would certainly be worth upgrading to the latest firmware version (which at time of writing is 2.24).