u-blox ZED-F9P Interface Description - Manual
Advance Information
• See version 0 of
for simplified version of this message.
This message returns a UBX-ACK-NAK, cancels any started transaction, and no
configuration is applied:
• if any key within a transaction is unknown to the receiver FW
• if an invalid transaction state transition is requested
• if the layers bitfield changes within a transaction
• if the layers bitfield does not specify a layer to save a value to
This message returns a UBX-ACK-NAK, and no configuration is applied:
• if the requested configuration is not valid. While in a transaction context, only the last
message that requests to apply the transaction returns a NAK. The validity of a
configuration is checked only if the message requests to apply the configuration to the
RAM configuration layer. This also applies to a transaction-less request.
Notes:
• Any request for another UBX-CFG-message type (including UBX-CFG-VALDEL and UBX-
CFG-VALGET) will cancel any started transaction, and no configuration is applied.
• This message can be sent with no key/values to set for the purposes of managing the
transaction state transition.
• If a key is sent multiple times within the same message or within the same transaction,
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 1
1
X1
-
layers
-
The layers where the configuration should be
applied (see
)
2
U1
-
transaction
-
Transaction action to be applied (see
)
3
U1
-
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
UBX-18010854 - R04
Advance Information
Page 88 of 259
