RCB-F9T - Integration manual
all of MIN_INTERVAL, TIME_THRS, SPEED_THRS or POSITION_THRS thresholds are exceeded. If a
threshold is set to zero it is ignored.
Position fixes are only recorded if a valid fix is obtained. Failed and invalid fixes are not recorded.
Position fixes are compressed to reduce the amount of flash space used. In order to improve the
compression, the fix values are rounded. This means that the values returned by the logging system
may differ slightly from those that are gathered in real time.
The recorded data for a fix comprises:
• The time and date of the fix recorded to a precision of one second.
• Latitude and longitude to a precision of one millionth of a degree. Depending on position on Earth
this is a precision in the order of 0.1 m.
• Altitude (height above mean sea level) to a precision of 0.1 m. Entries with an altitude lower than
-470 m (lower than the lowest point on earth) or higher than 20,000 m may not be recorded in
the log.
• Ground speed to a precision of 1 cm/s.
• The fix type (only successful fix types, since these are the only ones recorded).
• The number of satellites used in the fix is recorded, but there is a maximum count which can
be recorded. If the actual count exceeds this maximum count then the maximum count will be
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).
UBX-22004121 - R01
3 Receiver functionality
Page 24 of 64
C1-Public
Early production information
