u-blox ZED-F9T, RCB-F9T Integration Manual
ZED-F9T
u-blox F9 high accuracy timing module
Integration Manual
Abstract
This document describes the features and application of ZED-F9T, a multiband GNSS module offering nanosecond level timing accuracy.
www.u-blox.com
UBX-19005590 - R01
ZED-F9T-Integration Manual
Document Information
Title ZED-F9T
Subtitle u-blox F9 high accuracy timing module
Document type Integration Manual
Document number UBX-19005590
Revision and date R01 15-Mar-2019
Document status Advance Information
This document applies to the following products:
Product name Type number Firmware version PCN reference
ZED-F9T ZED-F9T-00B-00 TIM 2.00 N/A
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.
Copyright © 2019, u-blox AG.
u-blox is a registered trademark of u-blox Holding AG in the EU and other countries.
UBX-19005590 - R01
Page 2 of 80
Advance Information
ZED-F9T-Integration Manual
Contents
1 Integration manual structure............................................................................................ 6
2 System description............................................................................................................... 7
2.1 Overview.................................................................................................................................................... 7
2.1.1 Differential timing.......................................................................................................................... 7
2.2 Architecture..............................................................................................................................................7
2.2.1 Block diagram..................................................................................................................................8
3 Receiver functionality..........................................................................................................9
3.1 Receiver configuration........................................................................................................................... 9
3.1.1 Changing the receiver configuration..........................................................................................9
3.1.2 Default GNSS configuration.........................................................................................................9
3.1.3 Default interface settings..........................................................................................................10
3.1.4 Basic receiver configuration...................................................................................................... 10
3.1.5 Differential timing mode configuration...................................................................................12
3.1.6 Legacy configuration interface compatibility........................................................................ 15
3.1.7 Navigation configuration............................................................................................................ 15
3.2 Geofencing..............................................................................................................................................20
3.2.1 Introduction...................................................................................................................................20
3.2.2 Interface......................................................................................................................................... 21
3.2.3 Geofence state evaluation......................................................................................................... 21
3.2.4 Using the geofence pin state output...................................................................................... 21
3.3 Interfaces................................................................................................................................................21
3.3.1 UART interfaces........................................................................................................................... 23
3.3.2 SPI interface..................................................................................................................................23
3.3.3 USB interface................................................................................................................................23
3.3.4 D_SEL interface............................................................................................................................24
3.3.5 RESET_N interface...................................................................................................................... 24
3.3.6 SAFEBOOT_N interface..............................................................................................................24
3.3.7 TIMEPULSE interface..................................................................................................................25
3.3.8 Display data channel (DDC).......................................................................................................25
3.3.9 Antenna supervisor..................................................................................................................... 25
3.3.10 EXTINT......................................................................................................................................... 28
3.3.11 Communication ports............................................................................................................... 28
3.4 Multiple GNSS assistance (MGA)..................................................................................................... 33
3.4.1 AssistNow Online......................................................................................................................... 33
3.4.2 Host software............................................................................................................................... 34
3.4.3 AssistNow Online sequence...................................................................................................... 34
3.4.4 Flow control................................................................................................................................... 35
3.4.5 Authorization................................................................................................................................ 35
3.4.6 Service parameters......................................................................................................................35
3.4.7 Multiple servers............................................................................................................................37
3.5 Clocks and time.....................................................................................................................................37
3.5.1 Receiver local time.......................................................................................................................37
3.5.2 Navigation epochs....................................................................................................................... 37
3.5.3 iTOW timestamps........................................................................................................................38
UBX-19005590 - R01
Contents Page 3 of 80
Advance Information
ZED-F9T-Integration Manual
3.5.4 GNSS times...................................................................................................................................38
3.5.5 Time validity..................................................................................................................................39
3.5.6 UTC representation..................................................................................................................... 39
3.5.7 Leap seconds................................................................................................................................ 40
3.5.8 Real time clock............................................................................................................................. 40
3.5.9 Date.................................................................................................................................................40
3.6 Timing functionality............................................................................................................................. 41
3.6.1 Time pulse..................................................................................................................................... 41
3.6.2 Timemark.......................................................................................................................................45
3.7 Security (operating, monitoring and maintaining)........................................................................ 46
3.7.1 Receiver status monitoring....................................................................................................... 46
3.7.2 Spoofing detection / monitoring............................................................................................... 48
3.8 u-blox protocol feature descriptions................................................................................................ 48
3.8.1 Broadcast navigation data.........................................................................................................48
3.9 Forcing a receiver reset....................................................................................................................... 54
4 Design..................................................................................................................................... 56
4.1 Pin assignment......................................................................................................................................56
4.2 Power supply.......................................................................................................................................... 58
4.2.1 VCC: Main supply voltage.......................................................................................................... 58
4.2.2 V_BCKP: Backup supply voltage............................................................................................... 58
4.2.3 ZED-F9T power supply............................................................................................................... 59
4.3 ZED-F9T minimal design....................................................................................................................59
4.4 Antenna...................................................................................................................................................60
4.4.1 Antenna bias.................................................................................................................................61
4.5 EOS/ESD precautions.......................................................................................................................... 64
4.5.1 ESD protection measures.......................................................................................................... 64
4.5.2 EOS precautions...........................................................................................................................65
4.5.3 Safety precautions...................................................................................................................... 65
4.6 Electromagnetic interference on I/O lines.......................................................................................65
4.6.1 General notes on interference issues...................................................................................... 66
4.6.2 In-band interference mitigation................................................................................................ 66
4.6.3 Out-of-band interference........................................................................................................... 67
4.7 Layout......................................................................................................................................................67
4.7.1 Placement......................................................................................................................................67
4.7.2 Package footprint and solder mask......................................................................................... 67
4.7.3 Layout guidance........................................................................................................................... 67
4.8 Design guidance....................................................................................................................................69
4.8.1 General considerations............................................................................................................... 69
4.8.2 backup battery............................................................................................................................. 69
4.8.3 RF front-end circuit options...................................................................................................... 70
4.8.4 Antenna/ RF input....................................................................................................................... 70
4.8.5 Ground pads..................................................................................................................................71
4.8.6 Schematic design........................................................................................................................ 71
4.8.7 Layout design-in guideline......................................................................................................... 71
5 Product handling................................................................................................................. 72
5.1 ESD handling precautions.................................................................................................................. 72
5.2 Soldering.................................................................................................................................................72
5.3 Tapes....................................................................................................................................................... 75
5.4 Reels........................................................................................................................................................ 76
UBX-19005590 - R01
Contents Page 4 of 80
Advance Information
ZED-F9T-Integration Manual
5.5 Moisture sensitivity levels.................................................................................................................. 76
6 Appendix................................................................................................................................ 77
6.1 Glossary...................................................................................................................................................77
7 Related documents............................................................................................................ 78
8 Revision history................................................................................................................... 79
UBX-19005590 - R01
Contents Page 5 of 80
Advance Information
ZED-F9T-Integration Manual
1 Integration manual structure
This document provides a wealth of information to enable a successful design with the ZED-F9T
module. The manual is structured according to system, software and hardware aspects.
The first section, "System description" outlines the basics of the ZED-F9T timing receiver.
The following section "Receiver functionality" provides an exhaustive description of the receiver's
functionality. Beginning with the new configuration concept both existing and new users should read
this section to understand the new messages employed. Most of the following sub-sections should
be familiar to existing users of u-blox positioning products, however some changes are introduced
owing to the new configuration concept.
The sections from "Design" onwards addresses hardware options when designing the ZED-F9T
into a new product. This part gives power supply recommendations and provides guidance for
circuit design and PCB lay-out assistance. An antenna section provides design information and
recommendation for this important component. A final "Design guidance" section helps the
designer to check that crucial aspects of the design-in process have been carried out.
The final section addresses the major product handling concerns giving guidance on ESD
precautions, production soldering considerations and module delivery tape and reel information.
UBX-19005590 - R01
1 Integration
manual structure
Page 6 of 80
Advance Information
ZED-F9T-Integration Manual
2 System description
2.1 Overview
The ZED-F9T is a multi-band GNSS module offering 5 ns (1-sigma) timing accuracy with
unparalleled low power consumption.
The ZED-F9T incorporates the u-blox F9 multi-band platform in a small surface mount device with
a form factor of 22 x 17 mm.
2.1.1 Differential timing
The u-blox ZED-F9T high accuracy timing receiver takes local timing accuracy to the next level with
its differential timing mode.
In differential timing mode correction data is exchanged with other neighboring ZED-F9T timing
receivers via a communication network. In differential timing mode the ZED-F9T can operate either
as a master reference station, or as a slave station.
When ZED-F9T acts as a master reference timing station, it sends RTCM 3.3 differential corrections
to slave receivers.
When ZED-F9T acts as a slave receiver, it receives differential corrections RTCM 3.3 messages and
aligns its time pulse to the master reference station.
2.2 Architecture
The ZED-F9T module provides all the necessary RF and baseband processing to enable multi-band,
multi-constellation operation. The block diagram below shows the key functionality implemented in
the module.
UBX-19005590 - R01
2 System description Page 7 of 80
Advance Information
ZED-F9T-Integration Manual
2.2.1 Block diagram
Figure 1: ZED-F9T block diagram
An active antenna is mandatory with the ZED-F9T.
UBX-19005590 - R01
2 System description Page 8 of 80
Advance Information
ZED-F9T-Integration Manual
3 Receiver functionality
This section describes the ZED-F9T operational features and their configuration.
3.1 Receiver configuration
The ZED-F9T is fully configurable with UBX configuration interface keys. The configuration
database in the receiver's RAM holds the current configuration, which is used by the receiver
at run-time. It is constructed on start-up of the receiver from several sources of configuration.
The configuration interface and the available keys are described fully in the ZED-F9T Interface
Description [2].
A configuration setting stored in RAM remains effective until power-down or reset. If stored in
BBR (battery backed RAM), the setting will be used as long as the backup battery supply remains.
Configuration settings can be saved permanently in flash memory.
The configuration interface has changed from earlier u-blox positioning receivers.
There is some backwards compatibility however, users are strongly advised to adopt the
configuration interface described in this document. See legacy UBX-CFG message fields
reference section in the ZED-F9T Interface Description [2].
Configuration interface settings are held in a database consisting of separate configuration
items. An item is made up of a key ID and value pair. Related items are grouped together and
identified under a common group name: CFG-GROUP-ITEM; a convention used in u-center and
within this document. Within u-center, a configuration group is identified as "Group name" and the
configuration item is identified as the "item name" under the "Generation 9 Configuration View" "Advanced Configuration" view.
The UBX messages available to change or poll the configurations are the UBX-CFG-VALSET, UBXCFG-VALGET, and UBX-CFG-VALDEL messages. For more information about these messages and
the configuration keys see the configuration interface section in the ZED-F9T Interface Description
[2].
3.1.1 Changing the receiver configuration
All configuration messages, including legacy UBX-CFG messages, will result in a UBX-ACK-ACK
or UBX-ACK-NAK response. If several configuration messages are sent without waiting for this
response then the receiver may pause processing of input messages until processing of a previous
configuration message has been completed. When this happens a warning message "wait for cfg
ACK" will be sent to the host.
3.1.2 Default GNSS configuration
The ZED-F9T default GNSS configuration is set as follows:
• GPS: L1C/A, L2C
• GLONASS: L1OF, L2OF
• Galileo: E1B/C, E5b
• BeiDou: B1I, B2I
• QZSS: L1C/A, L2C
SBAS is also supported but not enabled in the default GNSS configuration. SBAS is not
recommended for timing applications.
For more information about default configuration, see the ZED-F9T Interface Description [2].
UBX-19005590 - R01
3 Receiver functionality Page 9 of 80
Advance Information
ZED-F9T-Integration Manual
3.1.3 Default interface settings
Interface Settings
UART1 output 38400 Baud, 8 bits, no parity bit, 1 stop bit. NMEA GGA, GLL, GSA, GSV, RMC, VTG, TXT (and no
UBX) messages are output by default.
UART1 input 38400 Baud, 8 bits, no parity bit, 1 stop bit. UBX, NMEA and RTCM 3.3 messages are enabled by
default.
UART2 output 38400 Baud, 8 bits, no parity bit, 1 stop bit. No host interface (UBX). Configured by default to
allow RTCM 3.3 as an output protocol. NMEA can also be configured as an output protocol.
UART2 input 38400 Baud, 8 bits, no parity bit, 1 stop bit. No Host interface support (UBX). RTCM 3.3 protocol
enabled by default
USB output NMEA GGA, GLL, GSA, GSV, RMC, VTG, TXT (and no UBX) messages are output by default.
USB input UBX, NMEA, RTCM 3.3 protocols enabled by default.
DDC
Fully compatible with the I2C 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.
SPI Allow communication to a host CPU, operated in slave mode only. Default messages activated as
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-F9T Integration Manual).
Table 1: Default interface settings
Refer to the u-blox ZED-F9T Interface Description [2] for information about further
settings.
By default the ZED-F9T outputs NMEA 4.10 messages that include satellite data for all GNSS bands
being received. This results in a higher-than-before 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.
3.1.4 Basic receiver configuration
This section summarizes the basic receiver configuration most commonly used.
3.1.4.1 Communication interface configuration
Several configuration groups allow operation mode configuration of the various communications
interfaces. These include parameters for the data framing, transfer rate and enabled input/output
protocols. See Communication ports section for details. The configuration groups available for each
interface are:
Interface Configuration groups
UART1 CFG-UART1-*, CFG-UART1INPROT-*, CFG-UART1OUTPROT-*
UART2 CFG-UART2-*, CFG-UART2INPROT-*, CFG-UART2OUTPROT-*
USB CFG-USB-*, CFG-USBINPROT-*, CFG-USBOUTPROT-*
I2C
CFG-I2C-*, CFG-I2CINPROT-*, CFG-I2COUTPROT-*
SPI CFG-SPI-*, CFG-SPIINPROT-*, CFG-SPIOUTPROT-*
Table 2: Default configurations
3.1.4.2 Message output configuration
The rate of NMEA and UBX protocol output messages are configurable.
If the rate configuration value is zero, then the corresponding message will not be output. Values
greater than zero indicate how often the message is output.
For periodic output messages the rate relates to the event the message is related to. For example,
the UBX-NAV-PVT (navigation position velocity and time solution) is related to the navigation epoch.
If the rate of this message is set to one (1), it will be output for every navigation epoch. If the rate
UBX-19005590 - R01
3 Receiver functionality Page 10 of 80
Advance Information
ZED-F9T-Integration Manual
is set to two (2), it will be output every other navigation epoch. The rates of the output messages
are individually configurable per communication interface. See the CFG-MSGOUT-* configuration
group.
Some messages, such as UBX-MON-VER, are not periodic and will only be output as the answer to
a poll request.
The UBX-INF-* information messages are non-periodic output messages that do not have a
message rate configuration. Instead they can be enabled for each communication interface via the
CFG-INFMSG-* configuration group.
All message output is additionally subject to the protocol configuration of the
communication interfaces. Messages of a given protocol will not be output until the protocol
is enabled for output on the interface (see previous section).
3.1.4.3 GNSS signal configuration
The GNSS constellations and bands are configurable with configuration keys. Each GNSS
constellation can be enabled or disabled independently. A GNSS constellation is considered to be
enabled when the constellation enable key is set and at least one of the constellation's band keys
are enabled.
ZED-F9T only supports certain combinations of constellations and bands. For all constellations,
both L1 and L2 bands must either be enabled or disabled. BeiDou B2 is the exception (can either
have BeiDou B1+B2 or B1-only). Unsupported combinations will be rejected with a UBX-ACK-NAK
and the warning: "invalid sig cfg" will be sent via UBX-INF and NMEA-TXT messages (if enabled).
The following table shows possible configuration key combinations for the GPS constellation.
Constellation key
CFG-SIGNAL-GPS_ENA
Band key
CFG-SIGNAL-GPS_L1CA_ENA
Band key
CFG-SIGNAL-GPS_L2C_ENA
Constellation
enabled?
false (0) false (0) false (0) no
false (0) false (0) true (1) no
false (0) true (1) false (0) no
false (0) true (1) true (1) no
true (1) false (0) false (0) no
true (1) false (0) true (1) Unsupported
combination
true (1) true (1) false (0) Unsupported
combination
true (1) true (1) true (1) yes
Table 3: Example of possible values of configuration items for the GPS constellation
3.1.4.4 Antenna supervisor configuration
This section describes the antenna supervisor configuration, its use and restrictions.
The antenna supervisor is used to control an active antenna. The configuration of the antenna
supervisor allows the following:
• Control voltage supply to the antenna, which allows the antenna supervisor to cut power to the
antenna in the event of a short circuit or optimize power to the antenna in power save mode.
• Detect a short circuit in the antenna and auto recover the antenna supply in such event.
• Detect an open antenna, which can be used to tell if the antenna has been disconnected.
See the table below, for a description of the configuration items related to the antenna supervisor
operation.
UBX-19005590 - R01
3 Receiver functionality Page 11 of 80
Advance Information
ZED-F9T-Integration Manual
Configuration item Description Comments
CFG-HW-ANT_CFG_VOLTCTRL Enable active antenna voltage control
CFG-HW-ANT_CFG_SHORTDET Enable short circuit detection
CFG-HW-ANT_CFG_SHORTDET_POL Short antenna detection polarity Set to 1 if the required logic polarity is
active-low (default)
CFG-HW-ANT_CFG_OPENDET Enable open circuit detection
CFG-HW-ANT_CFG_OPENDET_POL Open antenna detection polarity Set to 1 if the required logic polarity is
active-low (default)
CFG-HW-ANT_CFG_PWRDOWN Power down antenna supply if Short
Circuit is detected
CFG-HW-ANT_CFG_PWRDOWN_POL Power down antenna logic polarity Set to 1 if the required logic polarity is
active-high (default)
CFG-HW-ANT_CFG_RECOVER Enable auto recovery in the event of a
short circuit
To use this feature, short circuit
detection should be enabled. See CFGHW-ANT_CFG_SHORTDET
CFG-HW-ANT_SUP_SWITCH_PIN PIO-Pin (PIO number) used for switching
antenna supply
It is recommended that you use the
default PIO and assigned pin
CFG-HW-ANT_SUP_SHORT_PIN PIO-Pin (PIO number) used for detecting
a short in the antenna supply
It is recommended that you use the
default PIO and assigned pin
CFG-HW-ANT_SUP_OPEN_PIN PIO-Pin (PIO number) used for detecting
open/not connected antenna
It is recommended that you use the
default PIO and assigned pin
Table 4: Antenna supervisor configuration
It is possible to obtain the status of the antenna supervisor through the UBX-MON-RF message.
Moreover, any changes in the status of the antenna supervisor are reported to the host interface
in the form of notice messages. See the tables below for a description of the antenna state status
and the antenna power status.
Status Description
OFF Antenna is off
ON Antenna is on
DONTKNOW Antenna power status is not known
Table 5: Antenna power status
3.1.5 Differential timing mode configuration
In differential timing mode the ZED-F9T can operate either as a master reference station or as a
slave station. Using the RTCM3 protocol, the master sends timing corrections to the slave via a
communication link enabling the slave to compute its time relative to the master with high accuracy.
This section describes how to configure the ZED-F9T high accuracy timing receiver as a master
reference station and as slave station. The section begins with a note describing the RTCM protocol
and corresponding supported message types.
3.1.5.1 RTCM corrections
RTCM is a binary data protocol for communication of GNSS correction information. The ZED-F9T
high accuracy timing receiver supports RTCM as specified by RTCM 10403.3, Differential GNSS
(Global Navigation Satellite Systems) Services – Version 3 (October 7, 2016).
The RTCM specification is currently at version 3.3 and RTCM version 2 messages are not supported
by this standard. Users can download the standard from the RTCM website here.
To modify the RTCM input/output settings, see the configuration section in the u-blox ZED-F9T
Interface Description [2].
UBX-19005590 - R01
3 Receiver functionality Page 12 of 80
Advance Information
ZED-F9T-Integration Manual
3.1.5.2 List of supported RTCM input messages
Message Description
RTCM 1005 Stationary RTK reference station ARP
RTCM 1077 GPS MSM7
RTCM 1087 GLONASS MSM7
RTCM 1097 Galileo MSM7
RTCM 1127 BeiDou MSM7
RTCM 1230 GLONASS code-phase biases
RTCM 4072 Additional reference station information
Table 6: ZED-F9T supported input RTCM version 3.3 messages
3.1.5.3 List of supported RTCM output messages
Message Description
RTCM 1005 Stationary RTK reference station ARP
RTCM 1077 GPS MSM7
RTCM 1087 GLONASS MSM7
RTCM 1097 Galileo MSM7
RTCM 1127 BeiDou MSM7
RTCM 1230 GLONASS code-phase biases
RTCM 4072 Additional reference station information
Table 7: ZED-F9T supported output RTCM version 3.3 messages
3.1.5.4 Timing receiver position
Time mode is a special receiver mode where the position of the receiver is known and fixed and only
the time and frequency is calculated using all available satellites. This mode allows for maximum
time accuracy, for single-SV solutions, and also for using the receiver as a stationary reference
station.
In order to use time mode, the receiver's position must be known as exactly as possible. Errors in the
fixed position will translate into time errors depending on the satellite constellation.
The following procedures can be used to initialize the timing receiver position:
• Using built-in survey-in procedure to estimate the position.
• Entering coordinates independently generated or taken from an accurate position such as a
survey marker.
3.1.5.4.1 Survey-in
Survey-in is a procedure that is carried out prior to entering Time mode. It estimates the receiver
position by building a weighted mean of all valid 3D position solutions.
Two major parameters are required when configuring:
• A minimum observation time defines the minimum observation time independent of the
actual number of fixes used for the position estimate. Values can range from one day for high
accuracy requirements to a few minutes for coarse position determination.
• A 3D position standard deviation defines a limit on the spread of positions that contribute to
the calculated mean.
Survey-in ends when both requirements are successfully met. The Survey-in status can be queried
using the UBX-NAV-SVIN message.
The timing receiver should not be fed RTCM corrections while it is in survey-in mode.
UBX-19005590 - R01
3 Receiver functionality Page 13 of 80
Advance Information
ZED-F9T-Integration Manual
To configure a timing receiver into Survey-in mode (CFG-TMODE-MODE=SURVEY_IN), the following
items are required:
Configuration item Description
CFG-TMODE-MODE Receiver mode (disabled, survey-in or fixed)
CFG-TMODE-SVIN_MIN_DUR Survey-in minimum duration
CFG-TMODE-SVIN_ACC_LIMIT Survey-in position accuracy limit. The accuracy of given coordinates in 0.0001
meters (i.e. value 100 equals 1 cm)
Table 8: Configuration items used for setting a timing receiver into Survey-in mode
3.1.5.4.2 Fixed position
Here the timing receiver position coordinates are entered manually. Any error in the timing receiver
position will directly translate into timing errors.
To configure into Fixed mode (CFG-TMODE-MODE=FIXED), the following items are relevant:
Configuration item Description
CFG-TMODE-MODE Receiver mode (disabled or survey-in or fixed)
CFG-TMODE-POS_TYPE Determines whether the ARP position is given in ECEF or LAT/LON/HEIGHT
CFG-TMODE-ECEF_X ECEF X coordinate of the ARP position, coordinate in centimeters
CFG-TMODE-ECEF_Y ECEF Y coordinate of the ARP position, coordinate in centimeters
CFG-TMODE-ECEF_Z ECEF Z coordinate of the ARP position, coordinate in centimeters
CFG-TMODE-LAT Latitude of the ARP position, coordinate in 1e-7 degrees
CFG-TMODE-LON Longitude of the ARP position, coordinate in 1e-7 degrees
CFG-TMODE-HEIGHT Height of the ARP position, coordinate in centimeters
CFG-TMODE-ECEF_X_HP High-precision ECEF X coordinate of the ARP position, coordinate in 0.1 millimeters
CFG-TMODE-ECEF_Y_HP High-precision ECEF Y coordinate of the ARP position, coordinate in 0.1 millimeters
CFG-TMODE-ECEF_Z_HP High-precision ECEF Z coordinate of the ARP position, coordinate in 0.1 millimeters
CFG-TMODE-LAT_HP High-precision latitude of the ARP position, coordinate in 1e-9 degrees
CFG-TMODE-LON_HP High-precision longitude of the ARP position, coordinate in 1e-9 degrees
CFG-TMODE-HEIGHT_HP High-precision height of the ARP position, coordinate in 0.1 millimeters
CFG-TMODE-FIXED_POS_ACC Fixed position 3D accuracy estimate
Table 9: Configuration items used for setting a timing receiver into fixed mode
Once the receiver is set in fixed mode, select the position format to use: either LLH or ECEF with
optional high precision (mm) coordinates compared to the standard cm value.
For example, with CFG-TMODE-POS_TYPE=ECEF the timing receiver antenna position can be
entered to cm precision using CFG-TMODE-ECEF_X, CFG-TMODE-ECEF_Y, CFGTMODE-ECEF_Z.
For high precision (mm) coordinates use CFG-TMODEECEF_X_HP, CFG-TMODE-ECEF_Y_HP, CFGTMODE-ECEF_Z_HP. The same applies with corresponding coordinates used with CFG-TMODEPOS_TYPE=LLH.
If the timing receiver is moved during operation then new position coordinates must be
configured.
3.1.5.5 Master reference station
When the ZED-F9T high accuracy timing receiver acts as a master timing station, it sends RTCM
3.3 differential corrections to slave receivers. Corrections are generated after a timing fix calculation
in order to remove the master receiver's clock offset.
3.1.5.5.1 Master reference station: RTCM output configuration
At this point the timing receiver should report a TIME fix, not a 3D fix.
UBX-19005590 - R01
3 Receiver functionality Page 14 of 80
Advance Information
ZED-F9T-Integration Manual
The desired RTCM messages must be selected and configured on UART1 rate 1:
• RTCM 1005 Stationary RTK reference station ARP
• RTCM 1077 GPS MSM7
• RTCM 1088 GLONASS MSM7
• RTCM 1097 Galileo MSM7
• RTCM 1127 BeiDou MSM7
• RTCM 1230 GLONASS code-phase biases
• RTCM 4072 Additional reference station information
The configuration messages for these are shown in the Table 10.
The following configuration items output the recommended messages for a default satellite
constellation setting. Note that these are given for the UART1 interface:
Configuration item Description
CFG-UART1OUTPROT-NMEA CFG-UART1OUTPROT-NMEA to 0
CFG-UART1OUTPROT-RTCM3X CFG-UART1OUTPROT-RTCM3X to 1
CFG-UART1OUTPROT-UBX CFG-UART1OUTPROT-UBX to 0
CFG-MSGOUTRTCM_3X_TYPE1005_UART1
CFG-UART1OUTPROT-RTCM3X to 1
CFG-MSGOUTRTCM_3X_TYPE1077_UART1
Output rate of the RTCM-3X-TYPE1077 message on port UART1: RTCM GPS
MSM7
CFG-MSGOUTRTCM_3X_TYPE1087_UART1
Output rate of the RTCM-3X-TYPE1087 message on port UART1: RTCM GLONASS
MSM7
CFG-MSGOUTRTCM_3X_TYPE1097_UART1
Output rate of the RTCM-3X-TYPE1097 message on port UART1: RTCM Galileo
MSM7
CFG-MSGOUTRTCM_3X_TYPE1127_UART1
Output rate of the RTCM-3X-TYPE1127 message on port UART1: RTCM Additional
reference station information
CFG-MSGOUTRTCM_3X_TYPE1230_UART1
Output rate of the RTCM-3X-TYPE1230 message on port UART1: RTCM GLONASS
code-phase biases
CFG-MSGOUTRTCM_3X_TYPE4072_1_UART1
Output rate of the RTCM-3X-TYPE4072.1 message on port UART1: RTCM
Additional reference station information
Table 10: Configuration items used for setting a master reference station
3.1.5.6 Slave station
When the ZED-F9T acts as a slave receiver, it receives differential corrections RTCM 3.3 messages
from a master reference station and aligns its time pulse to it.
Connect the slave receiver to the reference server or to the NTRIP server. When the slave receives
the configured RTCM correction stream, it will automatically start using the corrections.
Reception of RTCM 4072.1 is required to start using differential correction data.
3.1.6 Legacy configuration interface compatibility
There is some backwards-compatibility for the legacy UBX-CFG configuration messages. It is
strongly recommended to adopt the new configuration interface, as the legacy configuration
messages support will be removed in the future.
See Legacy UBX-CFG Message Fields Reference section in the ZED-F9T Interface Description [2].
3.1.7 Navigation configuration
This section presents various configuration options related to the navigation engine. These options
can be configured through various configuration groups, such as CFG-NAVSPG-*, CFG-ODO-*, and
CFG-MOT-*.
UBX-19005590 - R01
3 Receiver functionality Page 15 of 80
Advance Information
ZED-F9T-Integration Manual
3.1.7.1 Platform settings
u-blox receivers support different dynamic platform models (see table below) to adjust the
navigation engine to the expected application environment. These platform settings can be
changed dynamically without performing a power cycle or reset. The settings improve the receiver's
interpretation of the measurements and thus provide a more accurate position output. Setting the
receiver to an unsuitable platform model for the given application environment is likely to result in
a loss of receiver performance and position accuracy.
The dynamic platform model can be configured through the CFG-NAVSPG-DYNMODEL
configuration item. The supported dynamic platform models and their details can be seen in Table
11 and Table 12 below.
Platform Description
Portable Applications with low acceleration, e.g. portable devices. Suitable for most situations.
Stationary Used in timing applications (antenna must be stationary) or other stationary applications.
Velocity restricted to 0 m/s. Zero dynamics assumed.
Pedestrian Applications with low acceleration and speed, e.g. how a pedestrian would move. Low
acceleration assumed.
Automotive Used for applications with equivalent dynamics to those of a passenger car. Low vertical
acceleration assumed.
At sea Recommended for applications at sea, with zero vertical velocity. Zero vertical velocity assumed.
Sea level assumed.
Airborne <1g Used for applications with a higher dynamic range and greater vertical acceleration than a
passenger car. No 2D position fixes supported.
Airborne <2g Recommended for typical airborne environments. No 2D position fixes supported.
Airborne <4g Only recommended for extremely dynamic environments. No 2D position fixes supported.
Wrist Only recommended for wrist worn applications. Receiver will filter out arm motion.
Table 11: Dynamic platform models
Platform Max altitude [m] Max horizontal
velocity [m/s]
Max vertical velocity
[m/s]
Sanity check type Max
position
deviation
Portable 12000 310 50 Altitude and velocity Medium
Stationary 9000 10 6 Altitude and velocity Small
Pedestrian 9000 30 20 Altitude and velocity Small
Automotive 6000 100 15 Altitude and velocity Medium
At sea 500 25 5 Altitude and velocity Medium
Airborne <1g 50000 100 100 Altitude Large
Airborne <2g 50000 250 100 Altitude Large
Airborne <4g 50000 500 100 Altitude Large
Wrist 9000 30 20 Altitude and velocity Medium
Table 12: Dynamic platform model details
Dynamic platforms designed for high acceleration systems (e.g. airborne <2g) can result in a higher
standard deviation in the reported position.
If a sanity check against a limit of the dynamic platform model fails, then the position solution
is invalidated. Table 12 above shows the types of sanity checks which are applied for a particular
dynamic platform model.
3.1.7.2 Navigation input filters
The navigation input filters in CFG-NAVSPG-* configuration group provide the input data of the
navigation engine.
UBX-19005590 - R01
3 Receiver functionality Page 16 of 80
Advance Information
ZED-F9T-Integration Manual
Configuration item Description
CFG-NAVSPG-FIXMODE By default, the receiver calculates a 3D position fix if possible but reverts to 2D
position if necessary (auto 2D/3D). The receiver can be forced to only calculate 2D (2D
only) or 3D (3D only) positions.
CFG-NAVSPG-CONSTR_ALT, CFGNAVSPG-CONSTR_ALTVAR
The fixed altitude is used if fixMode is set to 2D only. A variance greater than zero
must also be supplied.
CFG-NAVSPG-INFIL_MINELEV Minimum elevation of a satellite above the horizon in order to be used in the
navigation solution. Low elevation satellites may provide degraded accuracy, due to
the long signal path through the atmosphere.
CFG-NAVSPG-INFIL_NCNOTHRS,
CFG-NAVSPG-INFIL_CNOTHRS
A navigation solution will only be attempted if there are at least the given number of
SVs with signals at least as strong as the given threshold.
Table 13: Navigation input filter parameters
3.1.7.3 Navigation output filters
The result of a navigation solution is initially classified by the fix type (as detailed in the fixType
field of UBX-NAV-PVT message). This distinguishes between failures to obtain a fix at all ("No Fix")
and cases where a fix has been achieved, which are further subdivided into specific types of fixes
(e.g. 2D, 3D, dead reckoning).
The ZED-F9T firmware does not support the dead reckoning position fix type.
Where a fix has been achieved, a check is made to determine whether the fix should be classified as
valid or not. A fix is only valid if it passes the navigation output filters as defined in CFG-NAVSPGOUTFIL. In particular, both PDOP and accuracy values must lie below the respective limits.
Important: Users are recommended to check the gnssFixOK flag in the UBX-NAV-PVT or
the NMEA valid flag. Fixes not marked valid should not normally be used.
UBX-NAV-STATUS message also reports whether a fix is valid in the gpsFixOK flag. These
messages have only been retained for backwards compatibility and users are recommended to use
the UBX-NAV-PVT message.
3.1.7.3.1 Speed (3D) low-pass filter
The CFG-ODO-OUTLPVEL configuration item offers the possibility to activate a speed (3D) low-pass
filter. The output of the speed low-pass filter is published in the UBX-NAV-VELNED message (speed
field). The filtering level can be set via the CFG-ODO-VELLPGAIN configuration item and must be
comprised between 0 (heavy low-pass filtering) and 255 (weak low-pass filtering).
Strictly speaking, the internal filter gain is computed as a function of speed. Therefore,
the level as defined in the CFG-ODO-VELLPGAIN configuration item defines the nominal
filtering level for speeds below 5 m/s.
3.1.7.3.2 Course over ground low-pass filter
The CFG-ODO-OUTLPCOG configuration item offers the possibility to activate a course over ground
low-pass filter when the speed is below 8 m/s. The output of the course over ground (also named
heading of motion 2-D) low-pass filter is published in the UBX-NAV-PVT message (headMot field),
UBX-NAV-VELNED message (heading field), NMEA-RMC message (cog field) and NMEA-VTG
message (cogt field). The filtering level can be set via the CFG-ODO-COGLPGAIN configuration item
and must be comprised between 0 (heavy low-pass filtering) and 255 (weak low-pass filtering).
The filtering level as defined in the CFG-ODO-COGLPGAIN configuration item defines the
filter gain for speeds below 8 m/s. If the speed is higher than 8 m/s, no course over ground
low-pass filtering is performed.
3.1.7.3.3 Low-speed course over ground filter
The CFG-ODO-USE_COG activates this feature and the CFG-ODO-COGMAXSPEED, CFG-ODOCOGMAXPOSACC configuration items offer the possibility to configure a low-speed course over
ground filter (also named heading of motion 2D). This filter derives the course over ground from
UBX-19005590 - R01
3 Receiver functionality Page 17 of 80
Advance Information
ZED-F9T-Integration Manual
position at very low speed. The output of the low-speed course over ground filter is published in the
UBX-NAV-PVT message (headMot field), UBX-NAV-VELNED message (heading field), NMEA-RMC
message (cog field) and NMEA-VTG message (cogt field). If the low-speed course over ground filter
is not activated or inactive, then the course over ground is computed as described in section freezing
the course over ground.
3.1.7.4 Static hold
Static hold mode allows the navigation algorithms to decrease the noise in the position output when
the velocity is below a pre-defined "Static Hold Threshold". This reduces the position wander caused
by environmental factors such as multi-path and improves position accuracy especially in stationary
applications. By default, static hold mode is disabled.
If the speed drops below the defined "Static Hold Threshold", the static hold mode will be activated.
Once static hold mode has been entered, the position output is kept static and the velocity is set to
zero until there is evidence of movement again. Such evidence can be velocity, acceleration, changes
of the valid flag (e.g. position accuracy estimate exceeding the Position Accuracy Mask, see also
section Navigation Output Filters), position displacement, etc.
The CFG-MOT-GNSSDIST_THRS, configuration item additionally allows for configuration of
distance threshold. If the estimated position is farther away from the static hold position than this
threshold, static mode will be quit. The CFG-MOT-GNSSSPEED_THRS configuration item allows you
to set a speed that the static hold will release.
Figure 2: Position publication in static hold mode
UBX-19005590 - R01
3 Receiver functionality Page 18 of 80
Advance Information
ZED-F9T-Integration Manual
Figure 3: Flowchart of the static hold mode
3.1.7.5 Freezing the course over ground
If the low-speed course over ground filter is deactivated or inactive (see section low-speed course
over ground filter), the receiver derives the course over ground from the GNSS velocity information.
If the velocity cannot be calculated with sufficient accuracy (e.g., with bad signals) or if the absolute
speed value is very low (under 0.1 m/s) then the course over ground value becomes inaccurate too.
In this case the course over ground value is frozen, i.e. the previous value is kept and its accuracy
is degraded over time. These frozen values will not be output in the NMEA messages NMEA-RMC
and NMEA-VTG unless the NMEA protocol is explicitly configured to do so (see NMEA protocol
configuration).
UBX-19005590 - R01
3 Receiver functionality Page 19 of 80
Advance Information
ZED-F9T-Integration Manual
Figure 4: Flowchart of the course over ground freezing
3.1.7.6 Degraded navigation
Degraded navigation describes all navigation modes which use less than four satellite vehicles (SV).
3.1.7.6.1 2D navigation
If the receiver only has three SVs for calculating a position, the navigation algorithm uses a constant
altitude to compensate for the missing fourth SV. When a SV is lost after a successful 3D fix (min.
four SVs available), the altitude is kept constant at the last known value. This is called a 2D fix.
u-blox receivers do not calculate any navigation solution with less than three SVs.
3.2 Geofencing
3.2.1 Introduction
Figure 5: Geofence
The geofencing feature allows for the configuration of up to four circular areas (geofences) on the
Earth's surface. The receiver will then evaluate for each of these areas whether the current position
lies within the area or not and signal the state via UBX messaging and PIO toggling.
UBX-19005590 - R01
3 Receiver functionality Page 20 of 80
Advance Information
ZED-F9T-Integration Manual
3.2.2 Interface
Geofencing can be configured using the CFG-GEOFENCE-* configuration group. The geofence
evaluation is active whenever there is at least one geofence configured.
The current state of each geofence plus the combined state is output in UBX-NAV-GEOFENCE with
every navigation epoch.
Additionally the user can configure the receiver to output the combined geofence state on a physical
pin (assigned to a PIO being used for geofence state indication).
3.2.3 Geofence state evaluation
With every navigation epoch the receiver will evaluate the current solution's position versus the
configured geofences. There are three possible outcomes for each geofence:
•
Inside - The position is inside the geofence with the configured confidence level
•
Outside - The position lies outside of the geofence with the configured confidence level
•
Unknown - There is no valid position solution or the position uncertainty does not allow for
unambiguous state evaluation
The position solution uncertainty (standard deviation) is multiplied with the configured confidence
sigma level number and taken into account when evaluating the geofence state (red circle in figure
below).
Figure 6: Geofence states
The combined state for all geofences is evaluated as the combination (logical OR) of all geofences:
•
Inside - The position lies inside of at least one geofence
•
Outside - The position lies outside of all geofences
•
Unknown - All remaining states
3.2.4 Using the geofence pin state output
This feature can be used for example for waking up a sleeping host when a defined geofence
condition is reached. The receiver will toggle the assigned pin according to the combined geofence
state. Due to hardware restrictions, the unknown state will always be represented as HIGH. If the
receiver is in software backup or in a reset, the pin will go to HIGH accordingly. The meaning of the
LOW state can be configured using the CFG-GEOFENCE-PINPOL configuration item.
3.3 Interfaces
ZED-F9T provides UART1, SPI, DDC (I2C compatible) and USB interfaces for communication with
a host CPU. The interfaces are configured via the configuration interface which is described in the
ZED-F9T Interface Description [2].
It is important to isolate interface pins when VCC is removed. They can be allowed to float or
connected to a high impedance.
Some example isolation circuits are shown below.
UBX-19005590 - R01
3 Receiver functionality Page 21 of 80
Advance Information
ZED-F9T-Integration Manual
Figure 7: ZED-F9T output isolation
Figure 8: ZED-F9T input isolation
UBX-19005590 - R01
3 Receiver functionality Page 22 of 80
Advance Information
ZED-F9T-Integration Manual
Figure 9: ZED-F9T interface level translation
3.3.1 UART interfaces
ZED-F9T includes 2 UART ports.
UART1 can be used for host interface. It supports a configurable baud rate and protocol selection.
UART2 is available as an optional stand-alone RTCM interface. It should not be used as a host
interface.
The default baud rate is 38400 baud. To prevent buffering problems it is recommended not
to run at a lower baud rate than the default.
3.3.2 SPI interface
The ZED-F9T high accuracy timing receiver 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. The maximum
transfer rate using SPI is 125 kB/s and the maximum SPI clock frequency is 5.5 MHz.
3.3.3 USB interface
The USB interface is compatible with a USB version 2.0 FS (full speed, 12 Mb/s) interface.
USB suspend mode is not supported.
USB bus powered mode is not supported.
It is important to connect V_USB to ground when the USB interface is not used in an
application.
UBX-19005590 - R01
3 Receiver functionality Page 23 of 80
Advance Information
ZED-F9T-Integration Manual
There are additional hardware requirements if USB is designed in to be used:
In self powered mode the receiver is powered by its own power supply. V_USB is used to detect the
availability of the USB port, i.e. whether the receiver is connected to a USB host.
• Pin 38, V_USB needs to be powered by a separate LDO enabled by module VCC and supplied by
the USB host.
• A pull down resistor is required on the output of this V_USB LDO
• V_USB (pin 38) requires 1 µF and 100 nF capacitors mounted adjacent to the pin to ensure
correct V_USB voltage detection
• Apply USB_DM and USB_DP series resistors; typically 27 Ω
Figure 10: ZED-F9T V_USB supply
R11 = 100 k Ω is recommended
R4, R5 = 27 Ω is recommended
3.3.4 D_SEL interface
The D_SEL pin can be used to configure the functionality of pins 42 to 45. It is possible to configure
the pins as UART1 + I2C, or as SPI. See Table 14 below.
Pin No D_SEL == 0 D_SEL == 1
42 SPI_MISO UART1 TXD
43 SPI_MOSI UART1 RXD
44 SPI_CS_N
DDC/I2C SDA
45 SPI_CLK
DDC/I2C SCL
Table 14: D_SEL configuration
3.3.5 RESET_N interface
The ZED-F9T high accuracy timing receiver provides the ability to reset the receiver. The RESET_N
pin is an input-only pin with an internal pull-up resistor. Driving RESET_N low for at least 100 ms will
trigger a cold start.
The RESET_N pin will trigger a cold start and therefore should only be used as a recovery
option and not a Power On Reset.
3.3.6 SAFEBOOT_N interface
The ZED-F9T high accuracy timing receiver provides a SAFEBOOT_N pin that is used to command
the receiver into safe boot mode.
If this pin is low at power up, the receiver starts in safe boot mode and GNSS operation is disabled.
It can be used to recover from situations where the Flash has become corrupted and needs to be
restored.
UBX-19005590 - R01
3 Receiver functionality Page 24 of 80
Advance Information
Loading...