SEPTENTRIO PolaRx5TR, Reference Manual

Page: 18 / 512

1 How To...
1.2 Understand the Output of the Receiver
The receiver outputs proprietary and standardized messages. Each proprietary message be-
gins with a two-character identifier, which identifies the message type.
Proprietary messages First two
characters
ASCII command replies and command error notification
$R
ASCII transmissions (e.g. periodic output of the status screen), termi-
nated by a prompt. Two sub-types are defined:
•
$TD
: ASCII display generated by the receiver;
•
$TE
: event notification (e.g. receiver is shutting down).
$T
Formatted information blocks (e.g. formal command description)
$-
SNMP’ binary command replies (Septentrio proprietary)
$&
Proprietary binary data (SBF)
$@
1.2.1 Proprietary Binary Output (SBF)
The binary messages conform to the SBF definition. The data are arranged in SBF blocks
identified by block IDs. All the blocks begin with the SBF identifier
$@
. Please refer to section 4
for a description of the SBF format.
The benefit of SBF is completeness. This format should be your first choice if you wish to
receive detailed information from the receiver.
The list of supported SBF messages can be found in appendix A
SBF Converter, provided in the RxTools package is an intuitive GUI which allows SBF conver-
sion into e.g. RINEX, KML, GPX or ASCII.
1.2.2 BINEX
The list of supported BINEX messages can be found in appendix B
Section 1.4 explains how to stream BINEX records, and section 1.19 explains how to log BINEX
files on the internal disk.
1.2.3 NMEA
The receiver can generate a set of approved NMEA sentences, which conform to the NMEA
Standard (version 3.01
(1)
and version 4.10
(2)
are supported). The benefit of the NMEA format
(1)
NMEA 0183, Standard for Interfacing Marine Electronic Devices, Version 3.01, National Marine Electronics
Association, 2002
(2)
NMEA 0183, Standard for Interfacing Marine Electronic Devices, Version 4.10, National Marine Electronics
Association, 2012
18