u-blox ZED-F9P ZED-F9P FW 1.00 HPG 1.32 User Guide

: June 9, 2024
: u-blox

Table of Contents

u-blox ZED-F9P ZED-F9P FW 1.00 HPG 1.32
General information
Message interface
Improvements
Known limitations
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

u-blox ZED-F9P ZED-F9P FW 1.00 HPG 1.32

Abstract
This document contains general information, interface changes and firmware changes (features, improvements), along with known limitations for ZED-F9P FW 1.00 HPG 1.32.

General information

Scope
This Release Note applies to ZED-F9P with Firmware 1.00 HPG 1.32.

The document covers the changes in the ZED-F9P firmware compared to firmware version FW 1.00
HPG 1.30. Please refer to u-blox ZED-F9P Release Note FW 1.00 HPG 1.30 for a full description.

Released firmware image

Table 1: Released firmware image for u-blox ZED-F9P

u-blox-ZED-F9P-ZED-F9P-FW-1.00-HPG-1.32-1

Related software
It is recommended to use u-center GNSS evaluation software version 22.05 (or later) with the released product.

Message interface

UBX
ZED-F9P FW 1.00 HPG 1.32 supports UBX protocol version 27.31.
NMEA
ZED-F9P FW 1.00 HPG 1.32 supports up to NMEA protocol version 4.11.
Five NMEA standards are supported. The default NMEA version is 4.11, and, alternatively, versions
4.10, 4.0, 2.3, and 2.1 can be enabled.
RTCM
ZED-F9P FW 1.00 HPG 1.32 supports up to RTCM3 standard version 3.3.
SPARTN
ZED-F9P FW 1.00 HPG 1.32 supports up to SPARTN protocol version 2.0.1.
Interface changes

New

Modified

u-blox-ZED-F9P-ZED-F9P-FW-1.00-HPG-1.32-3

Removed

Improvements

Increased receiver robustness in southern hemisphere when SPARTN input is provided
When QZSS L1S is enabled, QZSS L1C/A reports now correct ‘Half cycle validity’ information in UBX-RXM-RAWX
UBX-RXM-SPARTNKEY can be polled on all ports, not only on UART1
UBX-RXM-SPARTNKEY can be send at any time to overwrite previously saved keys, without needing a system restart or without needing to wait for previously saved keys to expire
SPARTN IP stream decryption robustness improvements to ensure decryption is performed only on valid data verified fully as a SPARTN frame

Known limitations

A receiver moving at very slow speed (less than 10 cm/s) does not update the heading information in UBX-NAV-PVT. The velocity vectors can be used reliably.
Geofence status pin must not be re-assigned to another pin • If the receiver is configured to output RTCM messages on several ports, the ports must have
the same RTCM configuration, otherwise the MSM multiple message bit might not be set correctly
Time pulse can only be synced to GNSS. Configuration items and relevant flag cannot be set to false (CFG-TP-SYNC_GNSS_TP1, UBX-CFG-TP5)
If the receiver is configured to GLONASS only operation, it cannot get a PPP-RTK fix when using SPARTN corrections
Static hold mode is unreliable at navigation rates larger than 1 Hz
Incorrect SBAS pseudo range value corresponding to 4 ms shift may be reported in UBX-RXMSFRBX messages. This can be detected by monitoring the halfCyc flag in UBX-RXM-RAWX.
Lower navigation rate achievable compared to previous firmware; performance figures available in related Data sheet document
UART2 may report different UBX-INF-ERROR messages than the ones reported on the other interfaces
UBX-RXM-COR message does not get output for SPARTN protocol corrections, while the configuration item CFG-SPARTN-USE_SOURCE is set to LBAND
UBX-RXM-COR and UBX-RXM-SPARTN messages do not get output for encrypted SPARTN protocol corrections, while the configuration item CFG-SPARTN-USE_SOURCE is set to IP and no valid key is available in UBX-RXM-SPARTNKEY
Encrypted SPARTN protocol corrections received on UART2 are not reported as SPARTN input in UBX-MON-COMMS and UBX-MON-MSGPP, while the configuration item CFG-SPARTNUSE_ SOURCE is set to IP and no valid key is available in UBX-RXM-SPARTNKEY.

u-blox or third parties may hold intellectual property rights in the products, names, logos and designs included in this
document. Copying, reproduction, modification or disclosure to third parties of this document or any part thereof is only
permitted with the express written permission of u-blox.

The information contained herein is provided “as is” and u-blox assumes no liability for its use. No warranty, either express
or implied, is given, including but not limited to, with respect to the accuracy, correctness, reliability and fitness for a
particular purpose of the information. This document may be revised by u-blox at any time without notice. For the most recent
documents, visit www.u-blox.com.

UBX-22004887 – R01
C1-Public