u-blox ZED-F9P Interface Description - Manual
Advance Information
• if the requested configuration is not valid. The validity of a configuration is checked only
if the message requests to apply the configuration to the RAM configuration layer.
Notes:
• If a key is sent multiple times within the same message, then the value eventually being
applied is the last sent.
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x06 0x8A 4 + 1*N
see below
CK_A CK_B
Payload Contents:
Byte Offset
Number
Format
Scaling
Name
Unit
Description
0
U1
-
version
-
Message version, set to 0
1
X1
-
layers
-
The layers where the configuration should be
applied (see
)
2
U1[2]
-
reserved1
-
Start of repeated block (N times)
4 + 1*N
U1
-
cfgData
-
End of repeated block
Bitfield layers
This graphic explains the bits of
layers
Name
Description
ram
Update configuration in the RAM layer
bbr
Update configuration in the BBR layer
flash
Update configuration in the Flash layer
5.9.27.2 Sets values corresponding to provided key-value pairs within a transaction
Message
UBX-CFG-VALSET
Description
Sets values corresponding to provided key-value pairs within a transaction
Firmware
Supported on:
•
u-blox 9 with protocol version 27
Type
Set
Comment
Overview:
• This message is used to set a configuration by providing configuration data (a list of key
and value pairs), which identify the configuration parameters to change, and their new
values.
• This message is limited to containing a maximum of 64 key-value pairs.
• This message can be used multiple times with the result being managed within a
transaction. Within a transaction there is no limit on the number key-value pairs; a
transaction is effectively limited to the number of known keys.
• See
for details.
UBX-18010854 - R04
Advance Information
Page 87 of 259
