This data sheet describes the ZED-F9P high precision module with multiband GNSS receiver. The module provides multi-band RTK with fast
convergence times, reliable performance and easy integration of RTK
for fast time-to-market. It has a high update rate for highly dynamic
applications and centimeter accuracy in a small and energy-efficient
module.
www.u-blox.com
UBX-17051259 - R08
ZED-F9P-Data sheet
Document information
TitleZED-F9P
Subtitleu-blox F9 high precision GNSS module
Document typeData sheet
Document numberUBX-17051259
Revision and dateR0804-Jun-2020
Document statusEarly production information
Product statusCorresponding content status
In development /
prototype
Engineering sampleAdvance informationData based on early testing. Revised and supplementary data will be
Initial productionEarly production informationData from product verification. Revised and supplementary data may be
Mass production /
End of life
Objective specificationTarget values. Revised and supplementary data will be published later.
published later.
published later.
Production informationDocument contains the final product specification.
u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs
described herein may in whole or in part be subject to intellectual property rights. Reproduction, use, modification or
disclosure to third parties of this document or any part thereof without the express permission of u-blox is strictly prohibited.
The information contained herein is provided "as is" and u-blox assumes no liability for the use of the information. No warranty,
either express or implied, is given with respect to, including but not limited 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. For most recent documents,
please visit www.u blox.com.
5.4 USB interface.........................................................................................................................................17
The ZED-F9P positioning module features the u-blox F9 receiver platform, which provides multiband GNSS to high volume industrial applications. The ZED-F9P has integrated u-blox multiband RTK technology for centimeter level accuracy. The module enables precise navigation and
automation of moving machinery in industrial and consumer grade products in a compact surface
mounted form factor.
The ZED-F9P includes moving base support, allowing both base and rover to move while computing
a centimeter-level accurate position between them. Moving base is ideal for UAV applications where
the UAV is programmed to follow its owner or to land on a moving platform. It is also well suited to
attitude sensing applications where both base and rover modules are mounted on the same moving
platform and the relative position is used to derive attitude information for the vehicle or tool.
1.2 Performance
ParameterSpecification
Receiver typeMulti-band GNSS high precision receiver
Accuracy of time pulse signal
Frequency of time pulse signal
Operational limits
Velocity accuracy
Dynamic heading accuracy
1
2
2
RMS
99%
Dynamics
Altitude
Velocity
30 ns
60 ns
0.25 Hz to 10 MHz
(configurable)
≤ 4 g
50,000 m
500 m/s
0.05 m/s
0.3 deg
3
GNSS
4
Acquisition
Nav. update
rate
Convergence
6
time
Table 1: ZED-F9P performance in different GNSS modes
1
Assuming Airborne 4 g platform
2
50% @ 30 m/s for dynamic operation
3
GPS used in combination with QZSS and SBAS
4
Commanded starts. All satellites at -130 dBm. Measured at room temperature.
5
Dependent on the speed and latency of the aiding data connection, commanded starts
6
Depends on atmospheric conditions, baseline length, GNSS antenna, multipath conditions, satellite visibility and
geometry
Table 4: ZED-F9P moving base RTK performance in different GNSS modes
Figure 1: ZED-F9P moving base RTK heading accuracy versus baseline length
In a moving base application, and especially when the antennas are mounted on the same
platform, it is recommended to use identical antennas. Furthermore it is recommended
7
24 hours static
8
Measured using 1 km baseline and patch antennas with good ground planes. Does not account for possible antenna
phase center offset errors. ppm limited to baselines up to 20 km
9
Demonstrated with a good external LNA. Measured at room temperature.
UBX-17051259 - R08
Early production information
1 Functional descriptionPage 5 of 24
ZED-F9P-Data sheet
these antennas are mounted with identical orientation, as this will minimize effects of phase
center variation.
1.3 Supported GNSS constellations
The ZED-F9P GNSS modules are concurrent GNSS receivers that can receive and track multiple
GNSS constellations. Owing to the multi-band RF front-end architecture, all four major GNSS
constellations (GPS, GLONASS, Galileo and BeiDou) plus SBAS and QZSS satellites can be received
concurrently. All satellites in view can be processed to provide an RTK navigation solution when used
with correction data. If power consumption is a key factor, the receiver can be configured for a subset of GNSS constellations.
The QZSS system shares the same L1 and L2 frequency bands as GPS and can always be processed
in conjunction with GPS.
To take advantage of multi-band signal reception, dedicated hardware preparation must be
made during the design-in phase. See the ZED-F9P Integration manual [1] for u-blox design
recommendations.
The ZED-F9P supports the GNSS and their signals as shown in Table 5.
GPSGLONASSGalileo
L1C/A (1575.42 MHz)L1OF (1602 MHz + k*562.5
kHz, k = –7,..., 5, 6)
L2C (1227.60 MHz)L2OF (1246 MHz + k*437.5
kHz, k = –7,..., 5, 6)
Table 5: Supported GNSS and signals on ZED-F9P
E1-B/C (1575.42 MHz)B1I (1561.098 MHz)
E5b (1207.140 MHz)B2I (1207.140 MHz)
BeiDou
The following GNSS assistance services can be activated on ZED-F9P:
The Quasi-zenith satellite system (QZSS) is a regional navigation satellite system that transmits
additional L1 C/A and L2C signals for the Pacific region covering Japan and Australia. The ZEDF9P high precision receiver is able to receive and track these signals concurrently with GPS L1 C/A
and L2C signals, resulting in better availability especially under challenging signal conditions, e.g.
in urban canyons.
The ZED-F9P is also able to receive the QZSS L1S signal in order to use the SLAS (Sub-meter
Level Augmentation Service) which is an augmentation technology that provides correction data for
pseudoranges. Ground monitoring stations positioned in Japan calculate independent corrections
for each visible satellite and broadcast this data to the user via QZSS satellites. The correction
stream is transmitted on the L1 frequency (1575.42 MHz).
UBX-17051259 - R08
Early production information
1 Functional descriptionPage 6 of 24
ZED-F9P-Data sheet
QZSS can be enabled only if GPS operation is also configured.
1.4.2 Satellite based augmentation system (SBAS)
The ZED-F9P high precision receiver supports SBAS (including WAAS in the US, EGNOS in Europe,
MSAS in Japan and GAGAN in India) to deliver improved location accuracy within the regions
covered. However, the additional inter-standard time calibration step used during SBAS reception
results in degraded time accuracy overall.
1.4.3 Differential GNSS (DGNSS)
When operating in RTK mode, RTCM version 3 messages are required and the module supports
DGNSS according to RTCM 10403.3.
A ZED-F9P operating in rover mode can decode the following RTCM 3.3 messages:
Message typeDescription
RTCM 1001L1-only GPS RTK observables
RTCM 1002Extended L1-only GPS RTK observables
RTCM 1003L1/L2 GPS RTK observables
RTCM 1004Extended L1/L2 GPS RTK observables
RTCM 1005Stationary RTK reference station ARP
RTCM 1006Stationary RTK reference station ARP with antenna height
RTCM 1007Antenna descriptor
RTCM 1009L1-only GLONASS RTK observables
RTCM 1010Extended L1-only GLONASS RTK observables
RTCM 1011L1/L2 GLONASS RTK observables
RTCM 1012Extended L1/L2 GLONASS RTK observables
RTCM 1033Receiver and antenna description
RTCM 1074GPS MSM4
RTCM 1075GPS MSM5
RTCM 1077GPS MSM7
RTCM 1084GLONASS MSM4
RTCM 1085GLONASS MSM5
RTCM 1087GLONASS MSM7
RTCM 1094Galileo MSM4
RTCM 1095Galileo MSM5
RTCM 1097Galileo MSM7
RTCM 1124BeiDou MSM4
RTCM 1125BeiDou MSM5
RTCM 1127BeiDou MSM7
RTCM 1230GLONASS code-phase biases
RTCM 4072.0Reference station PVT (u-blox proprietary RTCM Message)
Table 7: Supported input RTCM 3.3 messages
A ZED-F9P operating as a base station can generate the following RTCM 3.3 output messages:
Message typeDescription
RTCM 1005Stationary RTK reference station ARP
UBX-17051259 - R08
Early production information
1 Functional descriptionPage 7 of 24
ZED-F9P-Data sheet
Message typeDescription
RTCM 1074GPS MSM4
RTCM 1077GPS MSM7
RTCM 1084GLONASS MSM4
RTCM 1087GLONASS MSM7
RTCM 1094Galileo MSM4
RTCM 1097Galileo MSM7
RTCM 1124BeiDou MSM4
RTCM 1127BeiDou MSM7
RTCM 1230GLONASS code-phase biases
RTCM 4072.0Reference station PVT (u-blox proprietary RTCM Message)
RTCM 4072.1Additional reference station information (u-blox proprietary RTCM Message)
Table 8: Supported output RTCM 3.3 messages
1.5 Broadcast navigation data and satellite signal
measurements
The ZED-F9P can output all the GNSS broadcast data upon reception from tracked satellites. This
includes all the supported GNSS signals plus the augmentation services QZSS and SBAS. The UBXRXM-SFRBX message is used for this information. The receiver also makes available the tracked
satellite signal information, i.e. raw code phase and Doppler measurements, in a form aligned to the
Radio Resource LCS Protocol (RRLP) [3]. For the UBX-RXM-SFRBX message specification, see the
u-blox ZED-F9P Interface description [2].
1.5.1 Carrier-phase measurements
The ZED-F9P modules provide raw carrier phase data for all supported signals, along with
pseudorange, Doppler and measurement quality information. The data contained in the UBX-RXMRAWX message follows the conventions of a multi-GNSS RINEX 3 observation file. For the UBXRXM-RAWX message specification, see the u-blox ZED-F9P Interface description [2].
Raw measurement data are available once the receiver has established data bit
synchronization and time-of-week.
1.6 Supported protocols
The ZED-F9P supports the following protocols:
ProtocolType
UBXInput/output, binary, u-blox proprietary
NMEA up to 4.11Input/output, ASCII
RTCM 3.3Input/output, binary
Table 9: Supported protocols
For specification of the protocols, see the u-blox ZED-F9P Interface description [2].
UBX-17051259 - R08
Early production information
1 Functional descriptionPage 8 of 24
2 System description
2.1 Block diagram
ZED-F9P-Data sheet
Figure 2: ZED-F9P block diagram
An active antenna is mandatory with the ZED-F9P. See the ZED-F9P Integration manual [1].
UBX-17051259 - R08
Early production information
2 System descriptionPage 9 of 24
ZED-F9P-Data sheet
3 Pin definition
3.1 Pin assignment
The pin assignment of the ZED-F9P module is shown in Figure 3. The defined configuration of the
PIOs is listed in Table 10.
For detailed information on pin functions and characteristics, see the u-blox ZED-F9P Integration
manual [1].
The ZED-F9P is an LGA package with the I/O on the outside edge and central ground pads.
Figure 3: ZED-F9P pin assignment
Pin NoNameI/ODescription
1GND-Ground
2RF_INIRF input
3GND-Ground
4ANT_DETECTIActive antenna detect - default active high
5ANT_OFFOExternal LNA disable - default active high
6ANT_SHORT_NIActive antenna short detect - default active low
7VCC_RFOVoltage for external LNA
8Reserved-Reserved
9Reserved-Reserved
UBX-17051259 - R08
Early production information
3 Pin definitionPage 10 of 24
ZED-F9P-Data sheet
Pin NoNameI/ODescription
10Reserved-Reserved
11Reserved-Reserved
12GND-Ground
13Reserved-Reserved
14GND-Ground
15Reserved-Reserved
16Reserved-Reserved
17Reserved-Reserved
18Reserved-Reserved
19GEOFENCE_STATOGeofence status, user defined
20RTK_STATORTK status: 0 (RTK fixed), Blinking (receiving and using RTCM corrections), 1
21Reserved-Reserved
22Reserved-Reserved
23Reserved-Reserved
24Reserved-Reserved
25Reserved-Reserved
26RXD2ICorrection UART input
27TXD2OCorrection UART output
28Reserved-Reserved
29Reserved-Reserved
30Reserved-Reserved
31Reserved-Reserved
32GND-Ground
33VCCIVoltage supply
34VCCIVoltage supply
35Reserved-Reserved
36V_BCKPIBackup supply voltage
37GND-Ground
38V_USBIUSB supply
39USB_DMI/OUSB data
40USB_DPI/OUSB data
41GND-Ground
42TXD / SPI_MISOOHost UART output if D_SEL = 1(or open). SPI_MISO if D_SEL = 0
43RXD / SPI_MOSIIHost UART input if D_SEL = 1(or open). SPI_MOSI if D_SEL = 0
44SDA / SPI_CS_NI/OI2C Data if D_SEL = 1 (or open). SPI Chip Select if D_SEL = 0
45SCL / SPI_CLKI/OI2C Clock if D_SEL = 1(or open). SPI Clock if D_SEL = 0
46TX_READYOTX_Buffer full and ready for TX of data
47D_SELIInterface select for pins 42-45
48GND-Ground
49RESET_NIRESET_N
50SAFEBOOT_NISAFEBOOT_N (for future service, updates and reconfiguration, leave OPEN)
51EXTINTIExternal Interrupt Pin
52Reserved-Reserved
(otherwise)
UBX-17051259 - R08
Early production information
3 Pin definitionPage 11 of 24
Pin NoNameI/ODescription
53TIMEPULSEOTime pulse
54Reserved-Reserved
Table 10: ZED-F9P pin assignment
ZED-F9P-Data sheet
UBX-17051259 - R08
Early production information
3 Pin definitionPage 12 of 24
ZED-F9P-Data sheet
4 Electrical specification
The limiting values given are in accordance with the Absolute Maximum Rating System
(IEC 134). Stress above one or more of the limiting values may cause permanent damage
to the device. These are stress ratings only. Operation of the device at these or at any other
conditions above those given below is not implied. Exposure to limiting values for extended
periods may affect device reliability.
Where application information is given, it is advisory only and does not form part of the
specification.
4.1 Absolute maximum ratings
ParameterSymbolConditionMinMaxUnits
Power supply voltageVCC-0.53.6V
Backup battery voltageV_BCKP-0.53.6V
Input pin voltageVinVCC ≤ 3.1 V-0.5VCC + 0.5V
VCC > 3.1 V-0.53.6V
VCC_RF output currentICC_RF100mA
Supply voltage USBV_USB–0.53.6V
USB signalsUSB_DN,
USB_DP
Input power at RF_INPrfinsource impedance =
50Ω, continuous wave
Storage temperatureTstg-40+85°C
Table 11: Absolute maximum ratings
-0.5V_USB + 0.5 V
10dBm
The product is not protected against overvoltage or reversed voltages. Voltage spikes
exceeding the power supply voltage specification, given in the table above, must be limited
to values within the specified boundaries by using appropriate protection diodes.
4.2 Operating conditions
All specifications are at an ambient temperature of 25 °C. Extreme operating temperatures
can significantly impact the specification values. Applications operating near the
temperature limits should be tested to ensure the specification.
ParameterSymbolMinTypicalMaxUnitsCondition
Power supply voltageVCC2.73.03.6V
Backup battery voltageV_BCKP1.653.6V
Backup battery currentI_BCKP36µAV_BCKP = 3 V,
SW backup currentI_SWBCKP1.4mA
Input pin voltage rangeVin0VCCV
Digital IO pin low level input voltageVil0.4V
Digital IO pin high level input voltage Vih0.8 * VCCV
Digital IO pin low level output voltage Vol0.4VIol = 2 mA
Digital IO pin high level output voltage VohVCC – 0.4VIoh = 2 mA
DC current through any digital I/O pin
(except supplies)
VCC_RF voltageVCC_RFVCC - 0.1V
Ipin5mA
VCC = 0 V
UBX-17051259 - R08
Early production information
4 Electrical specificationPage 13 of 24
ZED-F9P-Data sheet
ParameterSymbolMinTypicalMaxUnitsCondition
VCC_RF output currentICC_RF50mA
Receiver chain noise figure
External gain (at RF_IN)Ext_gain1750dB
Operating temperatureTopr-40+2585°C
Table 12: Operating conditions
10
NFtot9.5dB
Operation beyond the specified operating conditions can affect device reliability.
4.3 Indicative power requirements
Table 13 lists examples of the total system supply current including RF and baseband section for
a possible application.
Values in Table 13 are provided for customer information only, as an example of typical
current requirements. Values are characterized on samples with using a command cold
start. Actual power requirements can vary depending on FW version used, external circuitry,
number of SVs tracked, signal strength, type and time of start, duration, and conditions of
test.
SymbolParameterConditionsGPS+GLO
I
PEAK
11
I
VCC
I
supply
Table 13: Currents to calculate the indicative power requirements
Peak currentAcquisition130120mA
VCC currentAcquisition9075mA
11
Supply currentTracking8568mA
+GAL+BDS
All values in Table 13 are measured at 25 °C ambient temperature.
GPSUnit
10
Only valid for the GPS
11
Simulated GNSS signal
UBX-17051259 - R08
Early production information
4 Electrical specificationPage 14 of 24
ZED-F9P-Data sheet
5 Communications interfaces
There are several communications interfaces including UART, SPI, I2C12 and USB.
All the inputs have internal pull-up resistors in normal operation and can be left open if not used.
All the PIOs are supplied by VCC, therefore all the voltage levels of the PIO pins are related to VCC
supply voltage.
5.1 UART interface
There are two UART interfaces: UART1 and UART2. They operate from a speed of 9600 baud, up to
and including 921600 baud.
Hardware flow control is not supported.
UART1 is enabled by default if D_SEL = 1 or unconnected.
5.2 SPI interface
The ZED-F9P has an SPI slave interface that can be selected by setting D_SEL = 0. The SPI
slave interface is shared with UART1. The SPI pins available are: SPI_MISO (TXD), SPI_MOSI
(RXD), SPI_CS_N, SPI_CLK. The SPI interface is designed to allow communication to a host CPU.
The interface can be operated in slave mode only. Note that SPI is not available in the default
configuration because its pins are shared with the UART and I2C interfaces. The maximum transfer
rate using SPI is 125 kB/s and the maximum SPI clock frequency is 5.5 MHz.
This section provides SPI timing values for the ZED-F9P slave operation. The following tables
present timing values under different capacitive loading conditions. Default SPI configuration is
CPOL = 0 and CPHA = 0.
Timings 1 - 12 are not specified here as those are depending on SPI master. Timings A - E
are specified for SPI slave.
12
I2C is a registered trademark of Philips/NXP
UBX-17051259 - R08
Early production information
5 Communications
interfaces
Page 15 of 24
Timing value at 2 pF loadMin (ns)Max (ns)
"A" - MISO data valid time (CS)1438
"B" - MISO data valid time (SCK) weak driver mode2138
"C" - MISO data hold time114130
"D" - MISO rise/fall time, weak driver mode14
"E" - MISO data disable lag time2032
Table 14: ZED-F9P SPI timings at 2pF load
Timing value at 20 pF loadMin (ns)Max (ns)
"A" - MISO data valid time (CS)1952
"B" - MISO data valid time (SCK) weak driver mode2551
"C" - MISO data hold time117137
"D" - MISO rise/fall time, weak driver mode616
"E" - MISO data disable lag time2032
Table 15: ZED-F9P SPI timings at 20pF load
Timing value at 60 pF loadMin (ns)Max (ns)
"A" - MISO data valid time (CS)2979
"B" - MISO data valid time (SCK) weak driver mode3578
"C" - MISO data hold time122152
"D" - MISO rise/fall time, weak driver mode1541
"E" - MISO data disable lag time2032
Table 16: ZED-F9P SPI timings at 60pF load
ZED-F9P-Data sheet
5.3 Slave I2C interface
An I2C compliant interface is available for communication with an external host CPU. The interface
can be operated in slave mode only. It is fully compatible with Fast-Mode of the I2C industry
standard. Since the maximum SCL clock frequency is 400 kHz, the maximum bit rate is 400 kbit/
s. The interface stretches the clock when slowed down while serving interrupts, therefore the real
bit rates may be slightly lower.
The I2C interface is only available with the UART default mode. If the SPI interface is
selected by using D_SEL = 0, the I2C interface is not available.
UBX-17051259 - R08
Early production information
5 Communications
interfaces
Page 16 of 24
ZED-F9P-Data sheet
Figure 5: ZED-F9P high precision receiver I2C slave specification
SymbolParameterMin (Standard /
Fast-mode)
f
SCL
t
HD;STA
t
LOW
t
HIGH
t
SU;STA
t
HD;DAT
t
SU;DAT
t
r
t
f
t
SU;STO
t
BUF
SCL clock frequency0400kHz
Hold time (repeated) START condition4.0/1-µs
Low period of the SCL clock5/2-µs
High period of the SCL clock4.0/1-µs
Set-up time for a repeated START condition5/1-µs
Data hold time0/0-µs
Data set-up time250/100ns
Rise time of both SDA and SCL signals-1000/300 (for C = 400pF)ns
Fall time of both SDA and SCL signals-300/300 (for C = 400pF)ns
Set-up time for STOP condition4.0/1-µs
Bus free time between a STOP and START
5/2-µs
condition
t
VD;DAT
t
VD;ACK
V
nL
V
nH
Data valid time-4/1µs
Data valid acknowledge time-4/1µs
Noise margin at the low level0.1 VCC-V
Noise margin at the high level0.2 VCC-V
Table 17: ZED-F9P I2C slave timings and specifications
MaxUnit
5.4 USB interface
A USB interface, which is compatible to USB version 2.0 FS (Full Speed, 12 Mbit/s), can be used for
communication to a host. The V_USB pin supplies the USB interface.
UBX-17051259 - R08
Early production information
5 Communications
interfaces
Page 17 of 24
ZED-F9P-Data sheet
5.5 Default interface settings
InterfaceSettings
UART1 output
UART1 input
UART2 output
UART2 input
USBDefault messages activated as in UART1. Input/output protocols available as in UART1.
I2C
SPIAllow communication to a host CPU, operated in slave mode only. Default messages activated as
Table 18: Default interface settings
38400 baud, 8 bits, no parity bit, 1 stop bit.
NMEA protocol is enabled by default and GGA, GLL, GSA, GSV, RMC, VTG, TXT messages are
output by default.
UBX and RTCM 3.3 protocols are enabled by default but no output messages are enabled by
default.
38400 baud, 8 bits, no parity bit, 1 stop bit.
UBX, NMEA and RTCM 3.3 input protocols are enabled by default.
38400 baud, 8 bits, no parity bit, 1 stop bit.
UBX protocol cannot be enabled.
RTCM 3.3 protocol is enabled by default but no output messages are enabled by default.
NMEA protocol is disabled by default.
38400 baud, 8 bits, no parity bit, 1 stop bit.
UBX protocol cannot be enabled and will not receive UBX input messages.
RTCM 3.3 protocol is enabled by default.
NMEA protocol is disabled by default.
Fully compatible with the I2C13 industry standard, available for communication with an external
host CPU or u-blox cellular modules, operated in slave mode only. Default messages activated as
in UART1. Input/output protocols available as in UART1. Maximum bit rate 400 kb/s.
in UART1. Input/output protocols available as in UART1. SPI is not available unless D_SEL pin is
set to low (see section D_SEL interface in ZED-F9P Integration manual [1]).
Refer to the u-blox ZED-F9P Interface description [2] for information about further
settings.
By default the ZED-F9P outputs NMEA 4.10 messages that include satellite data for all
GNSS bands being received. This results in a high NMEA load output for each navigation
period. Make sure the UART1 baud rate being used is sufficient for the selected navigation
rate and the number of GNSS signals being received.
13
I2C is a registered trademark of Philips/NXP
UBX-17051259 - R08
Early production information
5 Communications
interfaces
Page 18 of 24
6 Mechanical specification
ZED-F9P-Data sheet
Figure 6: ZED-F9P mechanical drawing
UBX-17051259 - R08
Early production information
6 Mechanical specificationPage 19 of 24
ZED-F9P-Data sheet
7 Reliability tests and approvals
ZED-F9P modules are based on AEC-Q100 qualified GNSS chips.
Tests for product family qualifications are according to ISO 16750 "Road vehicles – environmental
conditions and testing for electrical and electronic equipment”, and appropriate standards.
7.1 Approvals
The ZED-F9P is designed to in compliance with the essential requirements and other relevant
provisions of Radio Equipment Directive (RED) 2014/53/EU.
The ZED-F9P complies with the Directive 2011/65/EU (EU RoHS 2) and its amendment Directive
(EU) 2015/863 (EU RoHS 3).
Declaration of Conformity (DoC) is available on the u-blox website.
UBX-17051259 - R08
Early production information
7 Reliability tests
and approvals
Page 20 of 24
ZED-F9P-Data sheet
8 Labeling and ordering information
This section provides information about product labeling and ordering. For information about
product handling and soldering see the ZED-F9P Integration manual [1].
8.1 Product labeling
The labeling of the ZED-F9P modules provides product information and revision information. For
more information contact u-blox sales.
8.2 Explanation of product codes
Three different product code formats are used. The Product name is used in documentation such
as this data sheet and identifies all u-blox products, independent of packaging and quality grade.
The Ordering code includes options and quality, while the Type number includes the hardware and
firmware versions. Table 19 below details these three different formats.
FormatStructureCode for this product
Product namePPP-TGVZED-F9P
Ordering codePPP-TGV-NNQZED-F9P-02B
Type numberPPP-TGV-NNQ-XXZED-F9P-02B-00
Table 19: Product code formats
The parts of the product code are explained in Table 20.
CodeMeaningExample
PPPProduct familyZED
TGPlatformF9 = u-blox F9
VVariantP = High precision
NNQOption / Quality gradeNN: Option [00...99]
Q: Grade, A = Automotive, B = Professional
XXProduct detailDescribes hardware and firmware versions
Table 20: Part identification code
8.3 Ordering codes
Ordering codeProductRemark
ZED-F9P-02BZED-F9PProduct shipped with the latest firmware
ZED-F9P-01BZED-F9PProduct shipped with firmware FW 1.00 HPG
Table 21: Product ordering codes
Product changes affecting form, fit or function are documented by u-blox. For a list of
Product Change Notifications (PCNs) see our website at: https://www.u-blox.com/en/