Manual
Table Of Contents
- Title
- Contents
- 1 Integration manual structure
- 2 System description
- 3 Receiver functionality
- 3.1 Receiver configuration
- 3.1.1 Changing the receiver configuration
- 3.1.2 Default GNSS configuration
- 3.1.3 Default interface settings
- 3.1.4 Basic receiver configuration
- 3.1.5 Differential timing mode configuration
- 3.1.6 Legacy configuration interface compatibility
- 3.1.7 Navigation configuration
- 3.2 Geofencing
- 3.3 Logging
- 3.4 Communication interfaces
- 3.5 Predefined PIOs
- 3.6 Antenna supervisor
- 3.7 Multiple GNSS assistance (MGA)
- 3.8 Clocks and time
- 3.9 Timing functionality
- 3.10 Security
- 3.11 u-blox protocol feature descriptions
- 3.12 Forcing a receiver reset
- 3.13 Firmware upload
- 3.1 Receiver configuration
- 4 Design
- 5 Product handling
- Appendix
- Related documents
- Revision history
- Contact
ZED-F9T-Integration manual
The UBX-LOG-FINDTIME message can be used to search a log for the index of the first entry less
than or equal to the given time. This index can then be used with the UBX-LOG-RETRIEVE message
to provide timebased retrieval of log entries.
3.3.6 Command message acknowledgment
Some log operations may take a long time to execute because of the time taken to write to flash
memory. The time for some operations may be unpredictable since the number and timing of
flash operations may vary. In order to allow host software to synchronize to these delays logging
messages will always produce a response. This will be UBX-ACK-NAK in case of error, otherwise UBX-
ACK-ACK unless there is some other defined response to the message.
It is possible to send a small number of logging commands without waiting for acknowledgment,
since there is a command queue, but this risks confusion between the acknowledgments for the
commands. Also a command queue overflow would result in commands being lost.
3.4 Communication interfaces
u-blox receivers are equipped with a communication interface which is multi-protocol capable. The
interface ports can be used to transmit GNSS measurements, monitor status information and
configure the receiver.
A protocol (e.g. UBX, NMEA) can be assigned to several ports simultaneously, each configured with
individual settings (e.g. baud rate, message rates, etc.). More than one protocol (e.g. UBX protocol
and NMEA) can be assigned to a single port (multi-protocol capability), which is particularly useful
for debugging purposes.
The ZED-F9T provides UART1, UART2, SPI, I2C and USB interfaces for communication with a
host CPU. The interfaces are configured via the configuration methods described in the ZED-F9T
interface description [2].
The following table shows the port numbers reported in the UBX-MON-COMMS messages.
Port no. UBX-MON-COMMS portId Electrical interface
0 0x0000 I2C
1 0x0100 UART1
2 0x0201 UART2
3 0x0300 USB
4 0x0400 SPI
Table 16: Port number assignment
It is important to isolate interface pins when VCC is removed. They can be allowed to float or
they can be connected to a high impedance.
Example isolation circuit is shown below.
UBX-19005590 - R05
3 Receiver functionality Page 25 of 87
C1-Public Early production information