u-blox ZED-F9P Interface Description - Manual
Advance Information
CFG-GEOFENCE continued
Byte Offset
Number
Format
Scaling
Name
Unit
Description
7
U1[1]
-
reserved2
-
Start of repeated block (numFences times)
8 + 12*N
I4
1e-7
lat
deg
Latitude of the geofence circle center
12 + 12*N
I4
1e-7
lon
deg
Longitude of the geofence circle center
16 + 12*N
U4
1e-2
radius
m
Radius of the geofence circle
End of repeated block
5.9.8 UBX-CFG-GNSS (0x06 0x3E)
5.9.8.1 GNSS system configuration
Message
UBX-CFG-GNSS
Description
GNSS system configuration
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.
See the
Legacy UBX Message Fields Reference
for the corresponding configuration item.
Gets or sets the GNSS system channel sharing configuration.
If the receiver is sent a valid new configuration, it will respond with a
message and immediately change to the new configuration. Otherwise the receiver will
reject the request, by issuing a
and continuing operation with the previous
configuration.
Configuration requirements:
• It is necessary for at least one major GNSS to be enabled, after applying the new
configuration to the current one.
• It is also required that at least 4 tracking channels are available to each enabled major
GNSS, i.e.
maxTrkCh
must have a minimum value of 4 for each enabled major GNSS.
• The number of tracking channels in use must not exceed the number of tracking
channels available in hardware, and the sum of all reserved tracking channels needs to
be less than or equal to the number of tracking channels in use.
Notes:
• To avoid cross-correlation issues, it is recommended that GPS and QZSS are always both
enabled or both disabled.
• Polling this message returns the configuration of all supported GNSS, whether enabled
or not; it may also include GNSS unsupported by the particular product, but in such
cases the enable flag will always be unset.
• See section
for a description of the GNSS IDs available.
• Configuration specific to the GNSS system can be done via other messages (e.g.
UBX-
CFG-SBAS
).
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x06 0x3E 4 + 8*numConfigBlocks
see below
CK_A CK_B
Payload Contents:
UBX-18010854 - R04
Advance Information
Page 46 of 259