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
recorded. If a log entry is retrieved with a satellite count equal to the maximum this means that
value or more. The maximum count is 51.
• A horizontal accuracy estimate is recorded to give an indication of fix quality. This is an
approximate compressed representation of the accuracy as determined by the fix process. Any
accuracy less than 0.7 m will be recorded as 0.7 m and any value above 1 km will be recorded
as 1 km. Within these limits, the recorded accuracy will always be greater than the fix accuracy
number (by up to 40%).
• Heading to a precision of one degree.
• Odometer distance data (if odometer is enabled).
Figure 8: The states of the active logging subsystem
3.3.5 Retrieval
UBX-LOG-RETRIEVE starts the process which allows the receiver to output log entries. UBX-LOG-
INFO may be helpful to a host system in order to understand the current log status before retrieval
is started.
Once retrieval has started, one message will be output from the receiver for each log entry
requested. Sending any logging message to the receiver during retrieval will cause the retrieval to
stop before the message is processed.
To maximize the speed of transfer it is recommended that a high communications data rate is used
and GNSS processing is stopped during the transfer (see UBX-CFG-RST).
UBX-LOG-RETRIEVE can specify a start-entry index and entry-count. The maximum number of
entries that can be returned in response to a single UBX-LOG-RETRIEVE message is 256. If more
entries than this are required the message will need to be sent multiple times with different
startEntry indices. It might be useful to stop recording via CFG_LOGFILTER-RECORD_ENA while
retrieving log entries from a circular log to avoid deletion of the requested entries between the
request and transmission.
The receiver will send a UBX-LOG-RETRIEVEPOS message for each position fix log entry and a UBX-
LOG-RETRIEVESTRING message for each string log entry. If the odometer was enabled at the time a
position was logged, then a UBX-LOG-RETRIEVEPOSEXTRA will also be sent. Messages will be sent
in the order in which they were logged, so UBX-LOG-RETRIEVEPOS and UBX-LOG-RETRIEVESTRING
messages may be interspersed in the message stream.
UBX-19005590 - R05
3 Receiver functionality Page 24 of 87
C1-Public Early production information