NEO-D9S and ZED-F9 configuration
UBX- 22008160 - R02
ZED-F9 configurations
Page 9 of 17
C1-Public
3.3
Dynamic keys
ZED-F9 may require proper keys to decrypt a SPARTN data stream. Once the key or keys are
obtained from the correction service provider, the UBX-RXM-SPARTNKEY message needs to be
formatted and sent to the ZED-F9 receiver. The following is an example of a UBX-RXM-SPARTNKEY
construction for the PointPerfect service. For more details, read about UBX-RXM-SPARTNKEY in
the interface description [5].
The following shows a UBX-RXM-SPARTNKEY construction example for PointPerfect:
b5 62 02 36 00 2c
01
02 00 00
00
10
88 08 4d 82 04 00 00
10
88 08
ce 29 05 00
XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
de 77
☞
The keys are not stored in non-volatile memory and will be deleted on every module reset or restart.
In such cases, the keys need to be re-entered.
3.4
Functional check
Firstly, some initial functional checks are required to verify that ZED-F9 is operating correctly:
•
ZED-F9 communication has been established (e.g., via u-center) through UART1 or USB
•
The GNSS antenna is plugged in
•
The L-band and interface configurations have been sent, as well as the dynamic keys
•
The ZED-F9 UART2 has been connected to the NEO-D9S UART2
Then, the UBX-MON-COMMS message can be enabled to verify that UBX messages are received on
the ZED-F9 UART2, including UBX-RXM-PMP:
Figure 7: UBX-MON-COMMS message in u-center
