Table of Contents
Advertisement
Bitfield flags
This graphic explains the bits of flags
Name
Description
0 when RTCM message received and passed CRC check, 1 when failed in which case refStation and msgType
crcFailed
might be corrupted and misleading
5.15.6 UBX-RXM-SFRBX (0x02 0x13)
5.15.6.1 Broadcast Navigation Data Subframe
UBX-RXM-SFRBX
Message
Broadcast Navigation Data Subframe
Description
Supported on:
Firmware
•
u-blox 9 with protocol version 27
Output
Type
This message reports a complete subframe of broadcast navigation data decoded from a
Comment
single signal. The number of data words reported in each message depends on the nature
of the signal.
Header
0xB5 0x62
Message Structure
Payload Contents:
Byte Offset
Number
Format
0
U1
1
U1
2
U1
3
U1
4
U1
5
U1
6
U1
7
U1
Start of repeated block (numWords times)
8 + 4*N
U4
End of repeated block
UBX-18010854 - R04
Class
ID
Length (Bytes)
0x02 0x13 8 + 4*numWords
Scaling
Name
-
gnssId
-
svId
-
reserved1
-
freqId
-
numWords
-
chn
-
version
-
reserved2
-
dwrd
Advance Information
u-blox ZED-F9P Interface Description - Manual
Unit
Description
-
GNSS identifier (see
-
Satellite identifier (see
-
Reserved
-
Only used for GLONASS: This is the frequency
slot + 7 (range from 0 to 13)
-
The number of data words contained in this
message (up to 10, for currently supported
signals)
-
The tracking channel number the message was
received on
-
Message version, (0x02 for this version)
-
Reserved
-
The data words
Payload
Checksum
CK_A CK_B
see below
Satellite
Numbering)
Satellite
Numbering)
Page 180 of 259
Advertisement
Table of Contents
