Ubx Binary Protocol - u-blox ANTARIS 4 System Integration Manual

Note The voltage range for VDDUSB is specified from
specificat ion for VCC.

4.4.3 UBX Binary Protocol

T he u-blox GPS Receivers
asynchron ous RS232 or USB
•
Compa ct. 8 Bit binary
•
Checksum protected,
•
M odu lar, using a 2-stag
Note UBX protocol of
optimized to communicate with u-center AE software to get the best performance and optimal
debugging.
®
The ANTARIS 4 receiver features a
serial ports.
1. The RTCM, NMEA or UBX protocol can be enabled or disabled for a given USART port.
2. Messages can be enabled or disabled for each enabled protocol on each port.
For further information please refer to ANTARIS
4.4.3.1 UBX Packet Structure
A basic UBX packet looks as follows:
Figure 70: UBX Protocol Framing
•
Every message starts
•
A 1 Byte Class Field follows.
•
A 1 Byte ID Field defines the message that is to follow
•
A 2 Byte Length Field is following. Length is defined as being the length of the payload, only.
include Sync Chars, Length Field, Class, ID or CRC fields. The number format of the length field is an
unsigned 16-Bit integer in Little Endian Format.
•
The Payload is a variable length field.
•
CK_A and CK_B is a 16 Bit checksum whose calculation is defined below.
GPS Modules - System Integration Manual (SIM) (incl. Reference Design)
GPS.G4-MS4-05007-A1
use a u -blox propri
po rts. This proprietary
data is u sed
using a low-overhead
e M ess age Identifier
fer s a greater flexibility and more p
two-stage I/O message and protocol selection procedure for the available
with 2 Bytes: 0xB5 0x62
The Class defines the basic subset of the message
3.0V to 3.6V, which differs slightly from the
etary protocol to tr ansmit GPS data
protocol has th e following key featu
checksum algorit hm
(Cla ss- and Messag e ID)
owerful messages than N EA protocol. It'
®
4 GPS Protocol Specifications [9].
your position is our focus
to a hos t computer using
res:
M
It does not
Receiver Description
Page 82
s