NavCom SF-3050 Rev.I User Manual
Page 48
SF-3050 GNSS Product User Guide
– Rev I
29
independently calculated based on an actual GNSS position measurement, as opposed to
an extrapolation/ interpolation between 1Hz measurements.
The throughput capacity of the ports is limited by the Baud rate and the
byte size and number of messages output.
1
Dependent on software bundle options
2
Port dependent, refer to Communications Ports for details.
NCT Binary Proprietary Data
The sensor can output proprietary raw data containing information including (but not
limited to):
Satellite Ephemeris (EPHEM1B)
Satellite Almanac (ALM1B)
Raw Pseudorange Measurements (MEAS1B)
Position, Height, & Time (PVT1B)
Velocity & Heading (PVT1B)
Signal to Noise (CHNLSTATUS1B)
Channel Status (CHNLSTATUS1B)
Correction Data (mirror data; RTKSTATUS1B)
Event/Marker (EVENTLATCHA)
Measurement Quality (PVT1B and PSEUDORANGESTATSB)
These data can be integrated in real-time positioning applications or post-processed
against any number of software applications designed to handle NCT or RINEX raw data.
The Sapphire Technical Reference Manual,
available on NavCom’s Web site, describes
the attributes of each of the input/output records (see Related Documents in the fore-
matter).
NMEA-0183 Data
The SF-3050 is capable of outputting several standard NMEA-0183 data strings (see
Related Standards in the fore-matter) and several proprietary data strings. All data are
headed with $GN, except for MLA, which is headed with $GL. All header formats are
accepted (e.g., $GP, $GL). Proprietary data strings are denoted with a $PNCT header.
The Sapphire Technical Reference Manual provides additional controls for heading types
and message lengths for some NMEA messages. NMEA data complies with v.4.1 of the
standard in SF-3050 v.3.0.16 or later.
Standard
ALM
– GPS Almanac Data
DTM
– Datum Reference
GBS
– GNSS Satellite Fault Detection
GFA
– GNSS Fix Accuracy and Integrity