Swift Navigation Binary Protocol Specification v2.6.3
Swift Navigation Binary Protocol Specification v2.6.3
Contents
1 Overview 1
2 Message Framing Structure 2
3 NMEA-0183 2
4 Basic Formats and Payload Structure 3
5 Message Types 4
6 Stable Message Definitions 7
6.1 Ext Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Imu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.3 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.4 Mag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.5 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.6 Observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.7 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.8 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7 Draft Message Definitions 91
7.1 Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2 File IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.3 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.4 Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
7.5 Piksi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.6 Sbas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7.7 Ssr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.8 Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.9 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7.10 Vehicle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
1 Overview
The Swift Navigation Binary Protocol (SBP) is a fast, simple, and minimal binary protocol for commu-
nicating with Swift devices. It is the native binary protocol used by the Piksi GPS receiver to transmit
solutions, observations, status, and debugging messages, as well as receive messages from the host op-
erating system, such as differential corrections and the almanac. As such, it is an important interface
with your Piksi receiver and the primary integration method with other systems.
This document provides a specification of SBP framing and the payload structures of the messages
currently used with Swift devices. SBP client libraries in a variety of programming languages are available
at https://github.com/swift-nav/libsbp and support information for sbp is available at https:
//support.swiftnav.com/customer/en/portal/articles/2492810-swift-binary-protocol.
Table 2.0.1: Swift Binary Protocol message structure. N denotes a variable-length size.
3 NMEA-0183
Swift devices, such as the Piksi, also have limited support for the standard NMEA-0183 protocol.
Note that NMEA-0183 doesn’t define standardized message string equivalents for many important
SBP messages such as observations, baselines and ephemerides. For this reason it is strongly recom-
mended to use SBP for new development. NMEA-0183 output is provided primarily to support legacy
devices.
1 CCITT
16-bit CRC Implementation uses parameters used by XMODEM, i.e. the polynomial: x 16 +x 12 +x 5 +1. For more details, please see the
implementation at https://github.com/swift-nav/libsbp/blob/master/c/src/edc.c#L59. See also A Painless Guide to CRC Error Detection
Algorithms at http://www.ross.net/crc/download/crc˙v3.txt
Example Message
As an example, consider this framed series of bytes read from a serial port:
55 02 02 cc 04 14 70 3d d0 18 cf ef ff ff ef e8 ff ff f0 18 00 00 00 00 05 00 43 94
This byte array decodes into a MSG BASELINE ECEF (see pg. 16), which reports the baseline position
solution of the rover receiver relative to the base station receiver in Earth Centered Earth Fixed (ECEF)
coordinates. The segments of this byte array and its contents break down as follows:
5 Message Types
Packages define a logical collection of SBP messages. The contents and layout of messages in packages
marked stable are unlikely to change in the future. Draft messages will change with future development
and are detailed purely for informational purposes only. Many draft messages are implementation-defined,
and some collections, such as the acquisition package, are used for internal development.
Reports detection of an external event, the GPS time it occurred, which pin it was and whether it was
rising or falling.
Value Description
0 Low (falling edge)
2)
1.
le )
ew q
v
N e
er
im
es
Value Description
R
7 2 1 0
0 Unknown - don’t have nav solution
Field 6.1.1: Flags (flags) 1 Good (¡ 1 microsecond)
6.2 Imu
Inertial Measurement Unit (IMU) messages.
Raw data from the Inertial Measurement Unit, containing accelerometer and gyroscope readings. The
sense of the measurements are to be aligned with the indications on the device itself. Measurement
units, which are specific to the device hardware and settings, are communicated via the MSG IMU AUX
message.
Auxiliary data specific to a particular IMU. The ‘imu type‘ field will always be consistent but the rest of
the payload is device specific and depends on the value of ‘imu type‘.
Value Description
U
IM
7 0 0 Bosch BMI160
Field 6.2.1: IMU type (imu type) Table 6.2.3: IMU Type values (imu type[0:7])
Value Description
0 +/- 2g
1 +/- 4g
2 +/- 8g
4)
2.
3 +/- 16g
)
6.
.5
le
2
6.
ab
(T
le
ab
an
ge
R
an
er
R
et
om
pe
co
er
Value Description
os
el
cc
yr
G
6.3 Logging
Logging and debugging messages from the device.
This message contains a human-readable payload string from the device containing errors, warnings and
informational messages at ERROR, WARNING, DEBUG, INFO logging levels.
Value Description
0 EMERG
1 ALERT
2)
3.
6.
2 CRIT
le
b
3 ERROR
Ta
l(
4 WARN
ve
le
d
5 NOTICE
ng
ve
gi
er
6 INFO
es
Lo
R
7 3 2 0 7 DEBUG
Field 6.3.1: Logging level (level) Table 6.3.2: Logging level values (level[0:2])
This message provides the ability to forward messages over SBP. This may take the form of wrapping
up SBP messages received by Piksi for logging purposes or wrapping another protocol with SBP.
The source identifier indicates from what interface a forwarded stream derived. The protocol identifier
identifies what the expected protocol the forwarded msg contains. Protocol 0 represents SBP and the
remaining values are implementation defined.
6.4 Mag
Magnetometer (mag) messages.
6.5 Navigation
Geodetic navigation messages reporting GPS time, position, velocity, and baseline position solutions. For
position solutions, these messages define several different position solutions: single-point (SPP), RTK,
and pseudo-absolute position solutions.
The SPP is the standalone, absolute GPS position solution using only a single receiver. The RTK
solution is the differential GPS solution, which can use either a fixed/integer or floating carrier phase
ambiguity. The pseudo-absolute position solution uses a user-provided, well-surveyed base station position
(if available) and the RTK solution in tandem.
When the inertial navigation mode indicates that the IMU is used, all messages are reported in the
vehicle body frame as defined by device settings. By default, the vehicle body frame is configured to
be coincident with the antenna phase center. When there is no inertial navigation, the solution will be
reported at the phase center of the antenna. There is no inertial navigation capability on Piksi Multi or
Duro.
This message reports the GPS time, representing the time since the GPS epoch began on midnight
January 6, 1980 UTC. GPS time counts the weeks and seconds of the week. The weeks begin at the
Saturday/Sunday transition. GPS week 0 began at the beginning of the GPS time scale.
Within each week number, the GPS time of the week is between between 0 and 604800 seconds
(=60*60*24*7). Note that GPS time does not accumulate leap seconds, and as of now, has a small offset
from UTC. In a message stream, this message precedes a set of other navigation messages referenced
to the same time (but lacking the ns field) and indicates a more precise time of these messages.
Value Description
ce
ur
ed
0 None (invalid)
so
v
e
er
im
1 GNSS Solution
es
T
R
7 3 2 0 2 Propagated
Field 6.5.1: Status flags (reserved) (flags) Table 6.5.2: Time source values (flags[0:2])
This message reports the Universal Coordinated Time (UTC). Note the flags which indicate the source
of the UTC offset value and source of the time fix.
Value Description
0 None (invalid)
1 GNSS Solution
)
5. 5.5
.
le le 6
2 Propagated
4)
b
(T (Ta
6.
ce ce
ab
ur
d
off
ve
e
er
C
T
es
Value Description
T
U
R
7 5 43 2 0
0 Factory Default
1 Non Volatile Memory
Field 6.5.2: Indicates source and time validity (flags)
2 Decoded this Session
This dilution of precision (DOP) message describes the effect of navigation satellite geometry on po-
sitional measurement precision. The flags field indicated whether the DOP reported corresponds to
differential or SPP solution.
Value Description
7)
0 Invalid
5.
6.
le
ab
ve r fl
e
re
3 Float RTK
od
IM
m
er
4 Fixed RTK
es
A
x
Fi
R
7 6 3 2 0 5 Undefined
6 SBAS Position
Field 6.5.3: Indicates the position solution with which the
DOPS message corresponds (flags) Table 6.5.7: Fix mode values (flags[0:2])
The position solution message reports absolute Earth Centered Earth Fixed (ECEF) coordinates and the
status (single point vs pseudo-absolute RTK) of the position solution. If the rover receiver knows the
surveyed position of the base station and has an RTK solution, this reports a pseudo-absolute position
solution using the base station position and the rover’s RTK baseline vector. The full GPS time is given
by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
1 Single Point Position (SPP)
)
10
3 Float RTK
le
9) ab
4 Fixed RTK
T
6. e (
5 Dead Reckoning
d
ab Mo
5.
6 SBAS Position
(T on
le
ti
od iga
av
e
ed
tia
v
m
er
er
es
x
In
R
7 5 43 2 0
Value Description
Field 6.5.4: Status flags (flags) 0 None
1 INS used
The position solution message reports absolute Earth Centered Earth Fixed (ECEF) coordinates and the
status (single point vs pseudo-absolute RTK) of the position solution. The message also reports the
upper triangular portion of the 3x3 covariance matrix. If the receiver knows the surveyed position of
the base station and has an RTK solution, this reports a pseudo-absolute position solution using the
base station position and the rover’s RTK baseline vector. The full GPS time is given by the preceding
MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
1 Single Point Position (SPP)
)
3
3 Float RTK
le
12 ab
4 Fixed RTK
T
6. e (
5 Dead Reckoning
d
ab Mo
5.
6 SBAS Position
(T on
le
ti
od iga
av
e
In ed
tia
v
m
er
er
es
x
R
7 5 43 2 0
Value Description
Field 6.5.5: Status flags (flags) 0 None
1 INS used
This position solution message reports the absolute geodetic coordinates and the status (single point
vs pseudo-absolute RTK) of the position solution. If the rover receiver knows the surveyed position of
the base station and has an RTK solution, this reports a pseudo-absolute position solution using the
base station position and the rover’s RTK baseline vector. The full GPS time is given by the preceding
MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
1 Single Point Position (SPP)
)
16
3 Float RTK
le
15 ab
4 Fixed RTK
T
6. e (
5 Dead Reckoning
d
ab Mo
5.
6 SBAS Position
(T on
le
ti
od iga
av
e
In ed
tia
v
m
er
er
es
x
R
7 5 43 2 0
Value Description
Field 6.5.6: Status flags (flags) 0 None
1 INS used
This position solution message reports the absolute geodetic coordinates and the status (single point
vs pseudo-absolute RTK) of the position solution as well as the upper triangle of the 3x3 covariance
matrix. The position information and Fix Mode flags should follow the MSG POS LLH message. Since
the covariance matrix is computed in the local-level North, East, Down frame, the covariance terms
follow with that convention. Thus, covariances are reported against the ”downward” measurement and
care should be taken with the sign convention.
Value Description
0 Invalid
1 Single Point Position (SPP)
)
19
3 Float RTK
le
18 ab
4 Fixed RTK
T
6. e (
5 Dead Reckoning
d
ab Mo
5.
6 SBAS Position
(T on
le
ti
od iga
av
e
ed
tia
v
m
er
er
es
x
In
R
7 5 43 2 0
Value Description
Field 6.5.7: Status flags (flags) 0 None
1 INS used
This message reports the baseline solution in Earth Centered Earth Fixed (ECEF) coordinates. This
baseline is the relative vector distance from the base station to the rover receiver. The full GPS time is
given by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
)
21
1 Reserved
5.
6.
3 Float RTK
(T
e
d
4 Fixed RTK
od
ve
m
er
5 Reserved
es
x
Fi
R
7 3 2 0 6 Reserved
Field 6.5.8: Status flags (flags) Table 6.5.21: Fix mode values (flags[0:2])
This message reports the baseline solution in North East Down (NED) coordinates. This baseline is
the relative vector distance from the base station to the rover receiver, and NED coordinate system is
defined at the local WGS84 tangent plane centered at the base station position. The full GPS time is
given by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
)
23
1 Reserved
5.
6.
3 Float RTK
(T
e
d
4 Fixed RTK
od
ve
m
er
5 Reserved
es
x
Fi
R
7 3 2 0 6 Reserved
Field 6.5.9: Status flags (flags) Table 6.5.23: Fix mode values (flags[0:2])
This message reports the velocity in Earth Centered Earth Fixed (ECEF) coordinates. The full GPS time
is given by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
)
25 .26
5.
3 Dead Reckoning
6.
(
e
le
od
M
(T
ty ion
ci
er
S
es
IN
R
Value Description
7 5 43 2 0
0 None
Field 6.5.10: Status flags (flags) 1 INS used
This message reports the velocity in Earth Centered Earth Fixed (ECEF) coordinates. The full GPS time
is given by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
)
28 .29
5.
3 Dead Reckoning
6.
(
e
le
od
M
(T
ty ion
ci
e
S
es
IN
R
Value Description
7 5 43 2 0
0 None
Field 6.5.11: Status flags (flags) 1 INS used
This message reports the velocity in local North East Down (NED) coordinates. The NED coordinate
system is defined as the local WGS84 tangent plane centered at the current position. The full GPS time
is given by the preceding MSG GPS TIME with the matching time-of-week (tow).
Value Description
0 Invalid
)
31 .32
5.
3 Dead Reckoning
6.
(
e
le
od
M
(T
ty ion
ci
er
S
es
IN
R
Value Description
7 5 43 2 0
0 None
Field 6.5.12: Status flags (flags) 1 INS used
This message reports the velocity in local North East Down (NED) coordinates. The NED coordinate
system is defined as the local WGS84 tangent plane centered at the current position. The full GPS
time is given by the preceding MSG GPS TIME with the matching time-of-week (tow). This message is
similar to the MSG VEL NED, but it includes the upper triangular portion of the 3x3 covariance matrix.
Value Description
0 Invalid
)
34 .35
5.
3 Dead Reckoning
6.
(
e
le
od
M
(T
ty ion
ci
er
S
es
IN
R
Value Description
7 5 43 2 0
0 None
Field 6.5.13: Status flags (flags) 1 INS used
This message reports the velocity in the Vehicle Body Frame. By convention, the x-axis should point
out the nose of the vehicle and represent the forward direction, while as the y-axis should point out the
right hand side of the vehicle. Since this is a right handed system, z should point out the bottom of the
vehicle. The orientation and origin of the Vehicle Body Frame are specified via the device settings. The
full GPS time is given by the preceding MSG GPS TIME with the matching time-of-week (tow). This
message is only produced by inertial versions of Swift products and is not available from Piksi Multi or
Duro.
Value Description
0 Invalid
)
37 .38
5.
3 Dead Reckoning
6.
(
e
le
od
M
(T
ty ion
ci
er
S
es
IN
R
Value Description
7 5 43 2 0
0 None
Field 6.5.14: Status flags (flags) 1 INS used
This message reports the Age of the corrections used for the current Differential solution
6.6 Observation
Satellite observation messages from the device.
The GPS observations message reports all the raw pseudorange and carrier phase observations for the
satellites being tracked by the device. Carrier phase observation here is represented as a 40-bit fixed point
number with Q32.8 layout (i.e. 32-bits of whole cycles and 8-bits of fractional cycles). The observations
are be interoperable with 3rd party receivers and conform with typical RTCMv3 GNSS observations.
Value Description
0 Invalid pseudorange measurement
1 Valid pseudorange measurement and coarse TOW decoded
Value Description
0 Invalid carrier phase measurement
1 Valid carrier phase measurement
6. .3 )
le 6.6 6.4
6. )
Table 6.6.3: Carrier phase valid values (flags[1])
2)
ab le 6.
6)
(T ab ble
6.
lid (T a )
v a d ( T .5
6.
e ali ty .6
le
ng v ui 6
ab
ra se ig le
(T
b
do ha m a
Value Description
eu r p a (T
n
b
D rve usio
C lf-cer v
o d
a l
IM
H pp
7 6 4 3 2 1 0
Table 6.6.4: Half-cycle ambiguity values (flags[2])
Field 6.6.1: Measurement status flags. A bit field of flags
providing the status of this observation. If this field is 0 it
means only the Cn0 estimate for the signal is valid. (flags) Value Description
0 Invalid doppler measurement
1 Valid doppler measurement
Value Description
0 No exclusion
1 Measurement was excluded by SPP RAIM, use with care
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
7)
12 BDS2 B1
6.
6.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 6.6.2: Signal constellation, band and code (sid.code) Table 6.6.7: values (sid.code[0:7])
The base station position message is the position reported by the base station itself. It is used for
pseudo-absolute RTK positioning, and is required to be a high-accuracy surveyed location of the base
station. Any error here will result in an error in the pseudo-absolute position output.
The base station position message is the position reported by the base station itself in absolute Earth
Centered Earth Fixed coordinates. It is used for pseudo-absolute RTK positioning, and is required to
be a high-accuracy surveyed location of the base station. Any error here will result in an error in the
pseudo-absolute position output.
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GPS satel-
lite position, velocity, and clock offset. Please see the Navstar GPS Space Segment/Navigation user
interfaces (ICD-GPS-200, Table 20-III) for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
)
11
2 SBAS L1CA
6.
6.
3 GLO L1CA
le
ab
(T
4 GLO L2CA
7 0 5 GPS L1P
6 GPS L2P
Field 6.6.3: Signal constellation, band and code
(common.sid.code) Table 6.6.11: values (common.sid.code[0:7])
This observation message has been deprecated in favor of ephemeris message using floats for size reduc-
tion.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
13
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.4: Signal constellation, band and code
(common.sid.code) Table 6.6.13: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GPS satel-
lite position, velocity, and clock offset. Please see the Navstar GPS Space Segment/Navigation user
interfaces (ICD-GPS-200, Table 20-III) for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
15
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.5: Signal constellation, band and code
(common.sid.code) Table 6.6.15: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate QZSS satellite
position, velocity, and clock offset.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
17
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.6: Signal constellation, band and code
(common.sid.code) Table 6.6.17: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate BDS satellite
position, velocity, and clock offset. Please see the BeiDou Navigation Satellite System SIS-ICD Version
2.1, Table 5-9 for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
19
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.7: Signal constellation, band and code
(common.sid.code) Table 6.6.19: values (common.sid.code[0:7])
This observation message has been deprecated in favor of an ephemeris message with explicit source of
NAV data.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
21
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.8: Signal constellation, band and code
(common.sid.code) Table 6.6.21: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate Galileo satellite
position, velocity, and clock offset. Please see the Signal In Space ICD OS SIS ICD, Issue 1.3, December
2016 for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
23
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.9: Signal constellation, band and code
(common.sid.code) Table 6.6.23: values (common.sid.code[0:7])
Value Description
0 GPS L1CA
1 GPS L2CM
)
25
2 SBAS L1CA
6.
6.
3 GLO L1CA
le
ab
(T
4 GLO L2CA
7 0 5 GPS L1P
6 GPS L2P
Field 6.6.10: Signal constellation, band and code
(common.sid.code) Table 6.6.25: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GLO satellite
position, velocity, and clock offset. Please see the GLO ICD 5.1 ”Table 4.5 Characteristics of words of
immediate information (ephemeris parameters)” for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
)
27
2 SBAS L1CA
6.
6.
3 GLO L1CA
le
ab
(T
4 GLO L2CA
7 0 5 GPS L1P
6 GPS L2P
Field 6.6.11: Signal constellation, band and code
(common.sid.code) Table 6.6.27: values (common.sid.code[0:7])
This observation message has been deprecated in favor of ephemeris message using floats for size reduc-
tion.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
29
6 GPS L2P
6.
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.12: Signal constellation, band and code
(common.sid.code) Table 6.6.29: values (common.sid.code[0:7])
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
31
6 GPS L2P
6.
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.13: Signal constellation, band and code
(common.sid.code) Table 6.6.31: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GLO satellite
position, velocity, and clock offset. Please see the GLO ICD 5.1 ”Table 4.5 Characteristics of words of
immediate information (ephemeris parameters)” for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
33
6 GPS L2P
6.
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.14: Signal constellation, band and code
(common.sid.code) Table 6.6.33: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GLO satellite
position, velocity, and clock offset. Please see the GLO ICD 5.1 ”Table 4.5 Characteristics of words of
immediate information (ephemeris parameters)” for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
35
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.15: Signal constellation, band and code
(common.sid.code) Table 6.6.35: values (common.sid.code[0:7])
This observation message has been deprecated in favor of ephemeris message using floats for size reduc-
tion.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
37
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.16: Signal constellation, band and code
(common.sid.code) Table 6.6.37: values (common.sid.code[0:7])
The ephemeris message returns a set of satellite orbit parameters that is used to calculate GLO satellite
position, velocity, and clock offset. Please see the GLO ICD 5.1 ”Table 4.5 Characteristics of words of
immediate information (ephemeris parameters)” for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
39
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.17: Signal constellation, band and code
(common.sid.code) Table 6.6.39: values (common.sid.code[0:7])
The ionospheric parameters which allow the ”L1 only” or ”L2 only” user to utilize the ionospheric model
for computation of the ionospheric delay. Please see ICD-GPS-200 (Chapter 20.3.3.5.1.7) for more
details.
Value Description
0 GPS L1CA
1 GPS L2CM
5)
2 SBAS L1CA
4
6.
6.
3 GLO L1CA
le
ab
(T
4 GLO L2CA
7 0 5 GPS L1P
6 GPS L2P
Field 6.6.18: Signal constellation, band and code
(sid.code) Table 6.6.45: values (sid.code[0:7])
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
47
6 GPS L2P
6.
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.19: Signal constellation, band and code
(sid.code) Table 6.6.47: values (sid.code[0:7])
The almanac message returns a set of satellite orbit parameters. Almanac data is not very precise and is
considered valid for up to several months. Please see the Navstar GPS Space Segment/Navigation user
interfaces (ICD-GPS-200, Chapter 20.3.3.5.1.2 Almanac Data) for more details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
49
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.20: Signal constellation, band and code
(common.sid.code) Table 6.6.49: values (common.sid.code[0:7])
The almanac message returns a set of satellite orbit parameters. Almanac data is not very precise and
is considered valid for up to several months. Please see the GLO ICD 5.1 ”Chapter 4.5 Non-immediate
information and almanac” for details.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
51
6 GPS L2P
6.
6.
le
ab
12 BDS2 B1
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.21: Signal constellation, band and code
(common.sid.code) Table 6.6.51: values (common.sid.code[0:7])
The GLONASS L1/L2 Code-Phase biases allows to perform GPS+GLONASS integer ambiguity resolu-
tion for baselines with mixed receiver types (e.g. receiver of different manufacturers)
Azimuth and elevation angles of all the visible satellites that the device does have ephemeris or almanac
for.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
)
54
6 GPS L2P
6.
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.22: Signal constellation, band and code
(sid.code) Table 6.6.54: values (sid.code[0:7])
Value Description
0 Do not use signal
1 Valid signal
)
56
6. 7)
le 6.5
6.
ab 6. )
(Tble .58
ity Ta .6
lid ( e 6
Value Description
va ag bl
n fl a
io g (T
ct in g
re fix fla 0 Partial fixing unavailable
1 Partial fixing available
C rtia ing
x
or l
Pall fi
Fu
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
9)
6 GPS L2P
6 .5
6.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 6.6.24: Signal constellation, band and code
(sid.code) Table 6.6.59: values (sid.code[0:7])
6.7 Settings
Messages for reading, writing, and discovering device settings. Settings with a ”string” field have multiple
values in this field delimited with a null character (the c style null terminator). For instance, when querying
the ’firmware version’ setting in the ’system info’ section, the following array of characters needs to
be sent for the string field in MSG SETTINGS READ: ”system info\0firmware version\0”, where the
delimiting null characters are specified with the escape sequence ’\0’ and all quotation marks should be
omitted.
In the message descriptions below, the generic strings SECTION SETTING and SETTING are used
to refer to the two strings that comprise the identifier of an individual setting.In firmware version example
above, SECTION SETTING is the ’system info’, and the SETTING portion is ’firmware version’.
See the ”Software Settings Manual” on support.swiftnav.com for detailed documentation about all
settings and sections available for each Swift firmware version. Settings manuals are available for each
firmware version at the following link: Piksi Multi Specifications. The latest settings document is also
available at the following link: Latest settings document . See lastly settings.py , the open source python
command line utility for reading, writing, and saving settings in the piksi tools repository on github as a
helpful reference and example.
The save settings message persists the device’s current settings configuration to its onboard flash memory
file system.
The setting message writes the device configuration for a particular setting via A NULL-terminated and
NULL-delimited string with contents ”SECTION SETTING\0SETTING\0VALUE\0” where the ’\0’
escape sequence denotes the NULL character and where quotation marks are omitted. A device will only
process to this message when it is received from sender ID 0x42. An example string that could be sent
to a device is ”solution\0soln freq\010\0”.
Return the status of a write request with the new value of the setting. If the requested value is rejected,
the current value will be returned. The string field is a NULL-terminated and NULL-delimited string with
contents ”SECTION SETTING\0SETTING\0VALUE\0” where the ’\0’ escape sequence denotes the
NULL character and where quotation marks are omitted. An example string that could be sent from
device is ”solution\0soln freq\010\0”.
Value Description
0 Accepted; value updated
4)
7.
Field 6.7.1: Write status (status) Table 6.7.4: Write status values (status[0:1])
The setting message that reads the device configuration. The string field is a NULL-terminated and
NULL-delimited string with contents ”SECTION SETTING\0SETTING\0” where the ’\0’ escape se-
quence denotes the NULL character and where quotation marks are omitted. An example string that
could be sent to a device is ”solution\0soln freq\0”. A device will only respond to this message when it is
received from sender ID 0x42. A device should respond with a MSG SETTINGS READ RESP message
(msg id 0x00A5).
The setting message wich which the device responds after a MSG SETTING READ REQ is sent to de-
vice. The string field is a NULL-terminated and NULL-delimited string with contents ”SECTION SETTING\0SET
where the ’\0’ escape sequence denotes the NULL character and where quotation marks are omitted.
An example string that could be sent from device is ”solution\0soln freq\010\0”.
The settings message for iterating through the settings values. A device will respond to this message
with a ”MSG SETTINGS READ BY INDEX RESP”.
Table 6.7.7: MSG SETTINGS READ BY INDEX REQ 0x00A2 message structure
Table 6.7.8: MSG SETTINGS READ BY INDEX RESP 0x00A7 message structure
Table 6.7.9: MSG SETTINGS READ BY INDEX DONE 0x00A6 message structure
6.8 System
Standardized system messages from Swift Navigation devices.
The system start-up message is sent once on system start-up. It notifies the host or other attached
devices that the system has started and is now ready to respond to commands or configuration requests.
Value Description
rt
s ta
of
0 Power on
se
au
1 Software reset
C
8 0 2 Watchdog reset
Field 6.8.1: Cause of startup (cause) Table 6.8.2: Cause of startup values (cause[0:8])
Value Description
3)
8.
6.
0 Cold start
le
ab
(T
1 Warm start
8 0 2 Hot start
Field 6.8.2: Startup type (startup type) Table 6.8.3: values (startup type[0:8])
This message provides information about the receipt of Differential corrections. It is expected to be sent
with each receipt of a complete corrections packet.
Value Description
yp
lt
ia
nt
d
0 Invalid
ve
re
er
e
iff
1 Code Difference
es
D
R
7 4 3 0 2 RTK
Field 6.8.3: Status flags (flags) Table 6.8.5: Differential type values (flags[0:3])
The heartbeat message is sent periodically to inform the host or other attached devices that the system
is running. It is used to monitor system malfunctions. It also contains status flags that indicate to the
host the status of the system and whether it is operating correctly. Currently, the expected heartbeat
interval is 1 sec.
The system error flag is used to indicate that an error has occurred in the system. To determine the
source of the error, the remaining error flags should be inspected.
Value Description
0 System Healthy
1 An error has occurred
Value Description
0 System Healthy
1 An IO error has occurred
10 1)
r
be
be
le 6
7)
ab ble
nu
nu
8.
)
(T a
(T) .8.9
t (T
6.
n
n
io
io
le
ag .8 6
Value Description
or t
rs
rs
sh en
ab
Fl .8 le
ve
ve
a res
r 6 b
ro le Ta
ol
ol
nn p
0 System Healthy
oc
oc
Er b (
te na
Ta or
ot
ot
an en
em ( rr
pr
pr
st or E
or
or
rn a
Sy Er AP
aj
in
d
Sw d
te nal
ve
ve
m
IO ftN
r
Exter
er
er
P
es
SB
SB
Ex
31 30 29 24 23 16 15 8 7 3 2 1 0
Value Description
0 No external antenna detected
1 External antenna is present
The INS status message describes the state of the operation and initialization of the inertial navigation
system.
Value Description
0 Awaiting initialization
1 Dynamically aligning
2 Ready
3 GNSS Outage exceeds max duration
)
6
6
Value Description
od Fix ble
Ta
le
(
N or (
r
Er
rv
SS
1 GNSS fix
e
e
S
es
IN
M
G
R
31 8 7 4 3 2 0
Table 6.8.14: GNSS Fix values (flags[3])
Field 6.8.5: Status flags (flags)
Value Description
0 Reserved
1 IMU Data Error
2 INS License Error
3 IMU Calibration Data Error
This message describes the results from an attempted GPS signal acquisition search for a satellite PRN
over a code phase/carrier frequency range. It contains the parameters of the point in the acquisition
search space with the best carrier-to-noise (CN/0) ratio.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
2)
12 BDS2 B1
1.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.1.1: Signal constellation, band and code (sid.code) Table 7.1.2: values (sid.code[0:7])
The message describes all SV profiles during acquisition time. The message is used to debug and measure
the performance.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
4)
6 GPS L2P
1.
7.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 7.1.2: Signal constellation, band and code
(acq sv profile[N].sid.code) Table 7.1.4: values (acq sv profile[N].sid.code[0:7])
7.2 File IO
Messages for using device’s onboard flash filesystem functionality. This allows data to be stored per-
sistently in the device’s program flash with wear-levelling using a simple filesystem interface. The file
system interface (CFS) defines an abstract API for reading directories and for reading and writing files.
Note that some of these messages share the same message type ID for both the host request and the
device response.
The file read message reads a certain length (up to 255 bytes) from a given offset into a file, and returns
the data in a MSG FILEIO READ RESP message where the message length field indicates how many
bytes were succesfully read.The sequence number in the request will be returned in the response. If the
message is invalid, a followup MSG PRINT message will print ”Invalid fileio read message”. A device
will only respond to this message when it is received from sender ID 0x42.
The file read message reads a certain length (up to 255 bytes) from a given offset into a file, and returns
the data in a message where the message length field indicates how many bytes were succesfully read.
The sequence number in the response is preserved from the request.
The read directory message lists the files in a directory on the device’s onboard flash file sys-
tem. The offset parameter can be used to skip the first n elements of the file list. Returns a
MSG FILEIO READ DIR RESP message containing the directory listings as a NULL delimited list. The
listing is chunked over multiple SBP packets. The sequence number in the request will be returned in the
response. If message is invalid, a followup MSG PRINT message will print ”Invalid fileio read message”.
A device will only respond to this message when it is received from sender ID 0x42.
Table 7.2.3: MSG FILEIO READ DIR REQ 0x00A9 message structure
The read directory message lists the files in a directory on the device’s onboard flash file system. Message
contains the directory listings as a NULL delimited list. The listing is chunked over multiple SBP packets
and the end of the list is identified by an entry containing just the character 0xFF. The sequence number
in the response is preserved from the request.
Table 7.2.4: MSG FILEIO READ DIR RESP 0x00AA message structure
The file remove message deletes a file from the file system. If the message is invalid, a followup
MSG PRINT message will print ”Invalid fileio remove message”. A device will only process this message
when it is received from sender ID 0x42.
The file write message writes a certain length (up to 255 bytes) of data to a file at a given offset.
Returns a copy of the original MSG FILEIO WRITE RESP message to check integrity of the write.
The sequence number in the request will be returned in the response. If message is invalid, a followup
MSG PRINT message will print ”Invalid fileio write message”. A device will only process this message
when it is received from sender ID 0x42.
The file write message writes a certain length (up to 255 bytes) of data to a file at a given offset. The
message is a copy of the original MSG FILEIO WRITE REQ message to check integrity of the write.
The sequence number in the response is preserved from the request.
Requests advice on the optimal configuration for a FileIO transfer. Newer version of FileIO can support
greater throughput by supporting a large window of FileIO data that can be in-flight during read or write
operations.
The advice on the optimal configuration for a FileIO transfer. Newer version of FileIO can support
greater throughput by supporting a large window of FileIO data that can be in-flight during read or write
operations.
7.3 Linux
Linux state monitoring.
This message indicates the process state of the top 10 heaviest consumers of CPU on the system.
This message indicates the process state of the top 10 heaviest consumers of memory on the system.
Table 7.3.4: MSG LINUX PROCESS SOCKET COUNTS 0x7F03 message structure
Table 7.3.5: MSG LINUX PROCESS SOCKET QUEUES 0x7F04 message structure
7.4 Orientation
Orientation Messages
This message reports the baseline heading pointing from the base station to the rover relative to True
North. The full GPS time is given by the preceding MSG GPS TIME with the matching time-of-week
(tow). It is intended that time-matched RTK mode is used when the base station is moving.
Value Description
2)
4.
7.
0 Invalid
le
ab
1 Reserved
(T
e
d
m
er
3 Float RTK
es
x
Fi
R
7 3 2 0 4 Fixed RTK
Field 7.4.1: Status flags (flags) Table 7.4.2: Fix mode values (flags[0:2])
This message reports the quaternion vector describing the vehicle body frame’s orientation with respect
to a local-level NED frame. The components of the vector should sum to a unit vector assuming that the
LSB of each component as a value of 2ˆ-31. This message will only be available in future INS versions
of Swift Products and is not produced by Piksi Multi or Duro.
Value Description
ig
d
av
ve
N
er
0 Invalid
es
IN
R
7 3 2 0 1 Valid
Field 7.4.2: Status flags (flags) Table 7.4.4: INS Navigation mode values (flags[0:2])
This message reports the yaw, pitch, and roll angles of the vehicle body frame. The rotations should
applied intrinsically in the order yaw, pitch, and roll in order to rotate the from a frame aligned with
the local-level NED frame to the vehicle body frame. This message will only be available in future INS
versions of Swift Products and is not produced by Piksi Multi or Duro.
Value Description
ig
ed
av
N
v
er
0 Invalid
es
IN
R
7 3 2 0 1 Valid
Field 7.4.3: Status flags (flags) Table 7.4.6: INS Navigation mode values (flags[0:2])
This message reports the orientation rates in the vehicle body frame. The values represent the measure-
ments a strapped down gyroscope would make and are not equivalent to the time derivative of the Euler
angles. The orientation and origin of the user frame is specified via device settings. By convention, the
vehicle x-axis is expected to be aligned with the forward direction, while the vehicle y-axis is expected
to be aligned with the right direction, and the vehicle z-axis should be aligned with the down direction.
This message will only be available in future INS versions of Swift Products and is not produced by Piksi
Multi or Duro.
Value Description
ig
d
av
ve
N
er
0 Invalid
es
IN
R
7 2 2 0 1 Valid
Field 7.4.4: Status flags (flags) Table 7.4.8: INS Navigation mode values (flags[0:2])
7.5 Piksi
System health, configuration, and diagnostic messages specific to the Piksi L1 receiver, including a variety
of legacy messages that may no longer be used.
This is a legacy message for sending and loading a satellite alamanac onto the Piksi’s flash memory from
the host.
This message sets up timing functionality using a coarse GPS time estimate sent by the host.
This message from the host resets the Piksi back into the bootloader.
)
.4
5
7.
le
ab
(T
.
gs
in
tt
Value Description
se
d
t
ve
ul
er
a
ef
D
R
Field 7.5.1: Reset flags (flags) Table 7.5.4: Default settings. values (flags[0])
This message from the host resets the Piksi back into the bootloader.
This is an unused legacy message for result reporting from the CW interference channel on the SwiftNAP.
This message will be removed in a future release.
This is an unused legacy message from the host for starting the CW interference channel on the SwiftNAP.
This message will be removed in a future release.
This message resets either the DGNSS Kalman filters or Integer Ambiguity Resolution (IAR) process.
9)
5.
7.
le
ab
(T
t
se
re
to
ss
Value Description
e
oc
pr
ed
0 DGNSS filter
or
v
r
er
lte
1 IAR process
es
Fi
R
7 2 10 2 Inertial filter
Field 7.5.2: Filter flags (filter) Table 7.5.9: Filter or process to reset values (filter[0:1])
Deprecated
The thread usage message from the device reports real-time operating system (RTOS) thread usage
statistics for the named thread. The reported percentage values must be normalized.
The UART message reports data latency and throughput of the UART channels providing SBP I/O.
On the default Piksi configuration, UARTs A and B are used for telemetry radios, but can also be host
access ports for embedded hosts, or other interfaces in future. The reported percentage values must
be normalized. Observations latency and period can be used to assess the health of the differential
corrections link. Latency provides the timeliness of received base observations while the period indicates
their likelihood of transmission.
Deprecated
This message reports the state of the Integer Ambiguity Resolution (IAR) process, which resolves un-
known integer ambiguities from double-differenced carrier-phase measurements from satellite observa-
tions.
This message allows setting a mask to prevent a particular satellite from being used in various Piksi
subsystems.
Value Description
)
16
7. 7)
5.
0 Enabled
e .1
bl .5
Ta e 7
cq in
ve
A ck
er
a
es
Tr
Value Description
R
7 2 1 0
0 Enabled
Field 7.5.3: Mask of systems that should ignore this satellite. 1 Drop this PRN if currently tracking
(mask)
Table 7.5.17: Tracking channels values (mask[1])
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
)
18
12 BDS2 B1
5.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.5.4: Signal constellation, band and code (sid.code) Table 7.5.18: values (sid.code[0:7])
This message contains temperature and voltage level measurements from the processor’s monitoring
system and the RF frontend die temperature if available.
Request the recipient to execute an command. Output will be sent in MSG LOG messages, and the exit
code will be returned with MSG COMMAND RESP.
The response to MSG COMMAND REQ with the return code of the command. A return code of zero
indicates success.
Returns the standard output and standard error of the command requested by MSG COMMAND REQ.
The sequence number can be used to filter for filtering the correct command.
Request state of Piksi network interfaces. Output will be sent in MSG NETWORK STATE RESP
messages
The state of a network interface on the Piksi. Data is made to reflect output of ifaddrs struct returned
by getifaddrs in c.
If a cell modem is present on a piksi device, this message will be send periodically to update the host on
the status of the modem and its various parameters.
This message describes the gain of each channel in the receiver frontend. Each gain is encoded as a
non-dimensional percentage relative to the maximum range possible for the gain stage of the frontend.
By convention, each gain array has 8 entries and the index of the array corresponding to the index of the
rf channel in the frontend. A gain of 127 percent encodes that rf channel is not present in the hardware.
A negative value implies an error for the particular gain stage as reported by the frontend.
7.6 Sbas
SBAS data
This message is sent once per second per SBAS satellite. ME checks the parity of the data block and
sends only blocks that pass the check.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
2)
12 BDS2 B1
6.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.6.1: Signal constellation, band and code (sid.code) Table 7.6.2: values (sid.code[0:7])
7.7 Ssr
Precise State Space Representation (SSR) corrections format
The precise orbit and clock correction message is to be applied as a delta correction to broadcast
ephemeris and is typically an equivalent to the 1060 and 1066 RTCM message types
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
)
12 BDS2 B1
2
7.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.7.1: Signal constellation, band and code (sid.code) Table 7.7.2: values (sid.code[0:7])
The precise orbit and clock correction message is to be applied as a delta correction to broadcast
ephemeris and is typically an equivalent to the 1060 and 1066 RTCM message types
Table 7.7.3: MSG SSR ORBIT CLOCK DEP A 0x05DC message structure
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
)
12 BDS2 B1
4
7.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.7.2: Signal constellation, band and code (sid.code) Table 7.7.4: values (sid.code[0:7])
The precise code biases message is to be added to the pseudorange of the corresponding signal to get
corrected pseudorange. It is typically an equivalent to the 1059 and 1065 RTCM message types
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
6)
12 BDS2 B1
7.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.7.3: Signal constellation, band and code (sid.code) Table 7.7.6: values (sid.code[0:7])
The precise phase biases message contains the biases to be added to the carrier phase of the corresponding
signal to get corrected carrier phase measurement, as well as the satellite yaw angle to be applied to
compute the phase wind-up correction. It is typically an equivalent to the 1265 RTCM message types
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
8)
12 BDS2 B1
7.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.7.4: Signal constellation, band and code (sid.code) Table 7.7.8: values (sid.code[0:7])
The STEC per space vehicle, given as polynomial approximation for a given grid. This should be combined
with SSR-GriddedCorrection message to get the state space representation of the atmospheric delay.
7.8 Tracking
Satellite code and carrier-phase tracking messages from the device.
The tracking message returns a variable-length array of tracking channel states. It reports status and
carrier-to-noise density measurements for all tracked satellites.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
2)
12 BDS2 B1
8.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.8.1: Signal constellation, band and code (sid.code) Table 7.8.2: values (sid.code[0:7])
The tracking message returns a variable-length array of tracking channel states. It reports status and
carrier-to-noise density measurements for all tracked satellites.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
4)
6 GPS L2P
8.
7.
12 BDS2 B1
le
ab
(T
13 BDS2 B2
7 0 14 GAL E1B
20 GAL E7I
Field 7.8.2: Signal constellation, band and code
(mesid.code) Table 7.8.4: values (mesid.code[0:7])
When enabled, a tracking channel can output the correlations at each update interval.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
6)
12 BDS2 B1
8.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.8.3: Signal constellation, band and code (sid.code) Table 7.8.6: values (sid.code[0:7])
When enabled, a tracking channel can output the correlations at each update interval.
Value Description
0 GPS L1CA
1 GPS L2CM
2 SBAS L1CA
3 GLO L1CA
4 GLO L2CA
5 GPS L1P
6 GPS L2P
8)
12 BDS2 B1
8.
7.
13 BDS2 B2
le
ab
(T
14 GAL E1B
7 0 20 GAL E7I
Field 7.8.4: Signal constellation, band and code (sid.code) Table 7.8.8: values (sid.code[0:7])
7.9 User
Messages reserved for use by the user.
This message can contain any application specific user data up to a maximum length of 255 bytes per
message.
7.10 Vehicle
Messages from a vehicle.
Message representing the x component of vehicle velocity in the user frame at the odometry reference
point(s) specified by the user. The offset for the odometry reference point and the definition and origin
of the user frame are defined through the device settings interface. There are 4 possible user-defined
sources of this message which are labeled arbitrarily source 0 through 3.
Value Description
0 None (invalid)
1 GPS Solution (ms in week)
)
7. 0.3
2 Processor Time
)
.2
1
7.
10
(T ble
ce (Ta
le
e
er
Value Description
lo
im
es
R
7 5 43 2 0 0 Source 0
1 Source 1
Field 7.10.1: Status flags (flags) 2 Source 2
3 Source 3