u-blox ZED-F9P Interface Description - Manual
Advance Information
• The update rate has a direct influence on the power consumption. The more fixes that
are required, the more CPU power and communication resources are required.
• For most applications a 1 Hz update rate would be sufficient.
• When using Power Save Mode, measurement and navigation rate can differ from the
values configured here.
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x06 0x08 6
see below
CK_A CK_B
Payload Contents:
Byte Offset
Number
Format
Scaling
Name
Unit
Description
0
U2
-
measRate
ms
The elapsed time between GNSS measurements,
which defines the rate, e.g. 100ms => 10Hz,
1000ms => 1Hz, 10000ms => 0.1Hz.
Measurement rate should be greater than or
equal to 25 ms.
2
U2
-
navRate
cycles
The ratio between the number of
measurements and the number of navigation
solutions, e.g. 5 means five measurements for
every navigation solution. Maximum value is
127.
4
U2
-
timeRef
-
The time system to which measurements are
aligned:
0: UTC time
1: GPS time
2: GLONASS time
3: BeiDou time
4: Galileo time
5.9.20 UBX-CFG-RINV (0x06 0x34)
5.9.20.1 Contents of Remote Inventory
Message
UBX-CFG-RINV
Description
Contents of Remote Inventory
Firmware
Supported on:
•
u-blox 9 with protocol version 27
Type
Get/Set
Comment
This message is deprecated in protocol versions greater than 23.01. Use
,
instead.
If
N
is greater than 30, the excess bytes are discarded.
See the
Legacy UBX Message Fields Reference
for the corresponding configuration item.
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x06 0x34 1 + 1*N
see below
CK_A CK_B
Payload Contents:
Byte Offset
Number
Format
Scaling
Name
Unit
Description
0
X1
-
flags
-
)
Start of repeated block (N times)
UBX-18010854 - R04
Advance Information
Page 75 of 259
