u-blox ZED-F9P Interface Description - Manual
Advance Information
• if the layers bitfield does not specify a layer to delete a value from
Notes:
• Any request for another UBX-CFG- message type (including UBX-CFG-VALSET and UBX-
CFG-VALGET) will cancel any started transaction, and no configuration is applied.
• This message can be sent with no keys to delete 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 is effectively deleted only once.
• Attempting to delete items that have not been set before, or that have already been
deleted, is considered a valid request
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x06 0x8C 4 + 4*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
deleted from (see
2
X1
-
transaction
-
Transaction action to be applied: (see
)
3
U1
-
reserved1
-
Start of repeated block (N times)
4 + 4*N
U4
-
keys
-
of the Configuration
Items to be deleted
End of repeated block
Bitfield layers
This graphic explains the bits of
layers
Name
Description
bbr
Delete configuration from the BBR layer
flash
Delete configuration from the Flash layer
Bitfield transaction
This graphic explains the bits of
transaction
UBX-18010854 - R04
Advance Information
Page 84 of 259
