ADR Sign Convention used in NovAtel GPS Receivers and RINEX Almanac Injection Procedure Amperage vs Voltage ASCII to binary log conversion example Can carbon fiber be used as an antenna cover? Can the GPGGA positions be output with more decimal places? Destination IP Should be Set in ICOMCONFIG if Setting up UDP Connection Difference Between Message Latency and Time Accuracy DL-4 DL-V script Example Do GPS-700 series antennas have a defined "North point"? GNSS-750 MTBF GNSS Ephemerides and Almanacs GNSS Frequencies and Signals GPS Receiver and SPAN SDLC card synchronization GPS Tracking Performance on Aircraft (Power Supply Issues) How does RTKANTENNA work? How Electrical Overstress damage is caused How often does Averaging Filter in POSAVE Command get Applied? How to Connect to PwrPak7 How to Determine the Channel in an ASSIGN Command How to extract 85-bit string from GLORAWFRAME log How to identify my PwrPak7 How to Recover Abbreviated ASCII Logs from Raw Data How to Use PASSCOM to Redirect Data HxGN SmartNet on NovAtel receivers In what frame is CORRIMUDATAS output in OEM6? ITK and Dual Antenna Receivers Maximum Cable Length vs. Data Rate MIC Mating Connectors MSM 6 and MSM 7 Issue MTBF Specifications for GPS-700 Series New ALIGN Message Lengths OEM4 and OEMV Reporting 1994 (Week Roll Over) OEM615 MTBF OEM628 MTBF OEM6 Dev Kit weight OEMStar API Specifcations OEMStar MTBF OEMV1-DF MTBF OEMV-2 & OEMV-2G MTBF OEMV Auth Codes for 3.907 ProPak6 FTP ProPak6 - USB Drive File Format Recommended Alignment Procedures Recommended Logs for Post Processing Regarding Absolute and Relative Antenna Calibrations Regarding standard deviations used in RBV Calibration Remaining memory on OEM638/ProPak6 Reporting a Stolen Receiver RTK Quality Mode, Extra Safe Mode SBAS Position Mode Sending Batch File and Logging Binary Data in Real Term SPAN-CPT Commonly Asked Questions SPAN-CPT Power specifications SPAN Troubleshooting logs Understanding IMU Data Gaps: Causes and Mitigation Strategies Updating SMART6 firmware from 6.230 or 6.231 to 6.510 (or later) USB Not Supported in WinLoad Software Using RTCM ephemeris data to speed up Time To First Fix (TTFF) WGS84 to ETRS89 datum transformations What Ionospheric Correction will SETIONOTYPE AUTO use? What is a EURO card? What is the Difference Between Active and Passive Serial Connection in CDU/Connect? What is the Effect of Bad Lever Arms in the GNSS/INS Filter? What is the Maximum Accepted Latency in ALIGN? What would cause speed (Field 8) in GPRMC to remain constant for some amount of time? Why am I seeing Two Kinds of HEADING2 Logs when Using two PP6Ds in Relative INS? Why Can't I disable RXSTATUSEVENTA permanently? Why is there no decoding information on the CAN PGNs? Why is the standard deviation of the BESTPOS log larger than the spec on the data sheet? Support Search

SBAS Position Mode

A receiver can compute a more accurate position by using Satellite Based Augmentation System (SBAS) corrections.  These corrections allow a receiver to mitigate clock, orbital, and ionospheric errors.

Hexagon | NovAtel receivers can be configured to compute an SBAS position by using the SBASCONTROL command.  By default, the receiver does not track SBAS satellites or use SBAS corrections.

When using the SBASCONTROL command, the receiver can be configured to use the SBAS system for the current region (if one is available), or the system of a user’s choosing.  In 7.08.00, the supported systems are WAAS, EGNOS, MSAS, and GAGAN.  Here are example commands with descriptions:

  • SBASCONTROL ENABLE - Automatically determines the satellite system to use and prevents the receiver from using satellites outside of the service area
  • SBASCONTROL ENABLE WAAS - Uses only corrections from WAAS satellites
  • SBASCONTROL ENABLE EGNOS - Uses only corrections from EGNOS satellites

In addition to the currently supported systems, the receiver can also be configured to use unsupported newer systems with the SBASCONTROL command.  An example is BDSBAS.  For example:

  • SBASCONTROL ENABLE 130 - Uses only corrections from PRN 130

Here are the PRN assignments for each SBAS system In the October 2020 version, these systems are included, although some are not currently operational:

  • ASAL (Algeria)
  • BDSBAS (China)
  • EGNOS (Europe)
  • GAGAN (India)
  • KASS (Korea)
  • MSAS (Japan)
  • NSAS (Nigeria)
  • QZSS (Japan)
  • SDCM (Russia)
  • SPAN (Australia and New Zealand)
  • WAAS (United States)

With SBASCONTROL, the receiver can also be configured to use corrections from a satellite even if it is in test mode (by default it does not use satellites in test mode).  For example, this command could be used if PRN 130 is in test mode:

  • SBASCONTROL ENABLE 130 ZEROTOTWO

In the BESTPOS log, the receiver reports the position type.  All SBAS positions are reported as “WAAS”, regardless of which SBAS system is used.  The SBAS satellite is reported in the stn id.

For instance, in this log the receiver is using corrections from PRN 131, which is WAAS. 

<BESTPOS COM1 0 65.0 FINESTEERING 2135 163825.000 02000000 cdba 16407
<     SOL_COMPUTED WAAS 51.15043942726 -114.03068830774 1100.1247
-17.0000 WGS84 0.6922 0.6044 1.4372 "131" 4.000 0.000 39 11 11 11 00 06 00 03
 

At this time, SBAS corrections are not broadcast for all GNSS constellations.  To compute even more accurate positions, it is recommended to use RTK or PPP.