u-blox ZED-F9P, Interface Description

Page: 135 / 267

u-blox ZED-F9P Interface Description - Manual
Advance Information
5.13 UBX-MON (0x0A)
Monitoring Messages: i.e. Communication Status, CPU Load, Stack Usage, Task Status.
Messages in the MON class are used to report the receiver status, such as CPU load, stack usage, I/O subsystem
statistics etc.
5.13.1 UBX-MON-COMMS (0x0A 0x36)
5.13.1.1 Comm port information
Message
UBX-MON-COMMS
Description
Comm port information
Firmware
Supported on:
•
u-blox 9 with protocol version 27
Type
Periodic/Polled
Comment
Consolidated communications information for all ports. The size of the message is
determined by the number of ports that are in use on the receiver. A port is only included if
communication, either send or receive, has been initiated on that port.
Header Class ID Length (Bytes) Payload Checksum
Message Structure
0xB5 0x62 0x0A 0x36 8 + 40*nPorts
see below
CK_A CK_B
Payload Contents:
Byte Offset Number
Format
Scaling Name Unit Description
0 U1 -
version
- Message version (0x00 for this version)
1 U1 -
nPorts
- Number of ports included
2 X1 -
txErrors
- tx error bitmask (see graphic below )
3 U1[1] -
reserved1
- Reserved
4 U1[4] -
protIds
The identifiers of the protocols reported in the
msgs array. 0: UBX, 1: NMEA, 2: RTCM2, 5:
RTCM3, 256: No protocol reported.
Start of repeated block (nPorts times)
8 + 40*N U2 -
portId
- Unique identifier for the port. See Serial
Communications Port Description for details.
10 + 40*N U2 -
txPending
bytes Number of bytes pending in transmitter buffer
12 + 40*N U4 -
txBytes
bytes Number of bytes ever sent
16 + 40*N U1 -
txUsage
% Maximum usage transmitter buffer during the
last sysmon period
17 + 40*N U1 -
txPeakUsage
% Maximum usage transmitter buffer
18 + 40*N U2 -
rxPending
bytes Number of bytes in receiver buffer
20 + 40*N U4 -
rxBytes
bytes Number of bytes ever received
24 + 40*N U1 -
rxUsage
% Maximum usage receiver buffer during the last
sysmon period
25 + 40*N U1 -
rxPeakUsage
% Maximum usage receiver buffer
26 + 40*N U2 -
overrunErrs
- Number of 100ms timeslots with overrun errors
28 + 40*N U2[4] -
msgs
msg Number of successfully parsed messages for
each protocol. The reported protocols are
identified through the protIds field.
36 + 40*N U1[8] -
reserved2
- Reserved
44 + 40*N U4 -
skipped
bytes Number of skipped bytes
UBX-18010854 - R04 Advance Information Page 127 of 259