NovAtel OEM / SPAN
The following describes the options available for this converter:
Perform pre-processing checks
If enabled, data is scanned after conversion to correct potential issues. See Pre-processing Checks for more information.
Decode RANGE_1/RANGECMP_1 log
This is applicable to SAASM receivers and to those logging data from both the primary and secondary antenna when using a dual antenna ALIGN system.
Enable this option to decode the RANGE_1B or RANGECMP_1B log to GPB. Please note, only RANGE_1B or RANGECMP_1B should be requested (not both).
Verbose messaging mode
Displays additional warning messages.
Create separate file for each MARKNTIME record
Enabling this option decodes the event marks from multiple inputs into separate station files.
Show receiver status event warnings
Displays any receiver status event warnings output by the receiver. These messages can be helpful for determining the cause of data logging anomalies.
Write GPB gaps to summary
Displays a summary of any data gaps in the GPB file. For this feature to report a gap, the epochs must be missing from the GPB file. If epochs exist in the GPB file, but do not contain any measurements, they will not be counted as gaps.
Create trajectory files for supported records
This option generates a separate FP file for each supported position record that is logged. The files can be loaded into a Waypoint project or used to compare against the post-processed solution.
Ignore clock model status for MARKNTIME records
Decode MARKNTIME records regardless of clock model status. This option may be useful for indoor surveys with no GNSS.
L2C phase correction
The default L2C correction for NovAtel receivers is 0.25 cycles. This value will be written to the GPB header and applied prior to processing. Correctly applying the L2C offset is required to correctly resolve carrier phase integer ambiguities in differential processing.
Static/Kinematic Mode
This option controls how the static/kinematic flags are set in the final GPB file. Auto will set the entire file static or kinematic according to the detected processing environment.
SPAN/IMU and Distance Measurement Instrument (DMI)
These options are only for users of NovAtel’s SPAN Technology and is only available in Inertial Explorer.
Logging data
See the SPAN Data Logging for Inertial Explorer application note (available at SPAN Data Logging for Inertial Explorer) for detailed instructions and examples for data logging.
Table: Records Supported for NovAtel OEM/SPAN contains a full list of supported records, both for GNSS only and GNSS+INS (NovAtel SPAN) applications. Below are suggestions on how to request these logs from your NovAtel receiver
or SPAN system.
Records Supported for NovAtel OEM/SPAN
|
VERSIONB (ID #37)
|
Version information for all components of a system
|
Optional
|
|
RANGEB (ID #43)
|
Measurements (expanded)
|
One of these records is required. Do not request more than one as duplicate measurements will result.
|
|
RANGEB_1
|
Measurements (expanded)
|
|
RANGECMPB (ID #140)
|
Measurements (compressed)
|
|
RANGECMP2B (ID #1273)
|
Measurements (compressed)
|
|
RAWEPHEMB (ID #41)
|
GPS Ephemeris
|
Required
|
|
GLOEPHEMERISB (ID #723)
|
GLONASS Ephemeris
|
Required if logging GLONASS data
|
|
BDSEPHEMERISB (ID #1696)
|
BeiDou Ephemeris
|
Required if logging BeiDou data
|
|
GALEPHEMERISB (ID# 1122)
GALINAVEPHEMERISB (ID# 1309)
GALFNAVEPHEMERISB (ID# 1310)
|
Galileo Ephemeris
|
Required if logging Galileo data
|
|
QZSSEPHEMERISB (ID# 1336)
|
QZSS Ephemeris
|
Required if logging QZSS data
|
|
BESTPOSB (ID #42)
RTKPOSB (ID #141)
OMNIHPPOSB (ID #495)
PSRPOSB (ID #47)
|
Position
|
Only required for comparison of real time trajectory to post-processed
|
|
MARKTIMEB (ID #231)
|
Event Mark Time
|
Written to STA file
|
|
MARKnTIMEB (ID #1130, 616, 1075, 1076)
TAGGEDMARKnPVAB (ID #1258, 1259, 1327, 1328)
|
Event Mark Time
|
Written to STA file
|
|
IONUTCB (ID #8)
|
Ionospheric Parameters
|
Optional.
If present will be written to EPP file. This will be applied in single frequency processing but ignored in dual frequency processing.
|
|
RAWIMUSB (ID #325)
RAWIMUSXB (ID #1462)
|
IMU Measurements
|
SPAN users only.
RAWIMUSXB is recommended.
Only one of these is required, do not log both as duplicate measurements will result.
|
|
BESTLEVERARMB (ID #674)
|
IMU to GNSS Lever Arm
|
SPAN users only.
IMUTOANTOFFSETSB is recommended as both primary and (if applicable) secondary lever arms are logged.
Lever arms must be set first through the SETIMUTOANTOFFSET and SETIMUTOANTOFFSET2 commands.
|
|
BESTLEVERARM2B (#1256)
|
IMU to secondary lever arm
|
|
IMUTOANTOFFSETSB (ID #1270)
|
Primary and secondary lever arms
|
|
BESTGPSPOSB (ID #423)
BESTGNSSPOSB (ID# 1429)
IMURATEPVAB (ID #1778)
IMURATEPVASB (ID #1305)
INSPVAB (ID #507)
INSPVASB (ID #508)
INSPOSB (ID #265)
INSPOSSB (ID #321)
|
Position, velocity and attitude
|
Optional for SPAN users only.
Can be used to compare real time and post-processed solutions.
|
|
SETIMUTYPE (ID #569)
|
IMU Type
|
Optional for SPAN users only.
Recommended if RAWIMUSB is logged, not needed if RAWIMUSXB is logged.
|
|
VEHICLEBODYROTATION (ID #642)
|
Angular offset between vehicle frame and SPAN frame
|
SPAN users only.
Allows vehicle body rotation to be automatically read by Inertial Explorer.
|
|
MARKnPVAB (ID #1067, 1068, 1118, 1119)
|
Event Mark Time
|
Written to STA file
|
|
HEADINGB (ID #971)
HEADING2B (ID #1335)
|
Heading from dual antenna
|
Written to HMR file.
the HEADINGB log has been deprecated and replaced with HEADING2B.
|
|
SITEDEFB (ID #153)
|
Site definitions
|
|
|
TIMEDWHEELDATAB (ID #622)
|
Odometer Measurements
|
SPAN users only.
Written to DMR file.
|
|
WHEELSIZEB (ID #646)
|
Circumference of Wheel
|
SPAN users only.
Written to DMR file.
|
|
RAWDMIB (ID #2269)
|
Odometer Measurements
|
Only applicable to SPAN firmware 7.07 and newer.
Written to DMR file.
|
|
DMICONFIGB (ID #2270)
|
DMI Operation Configuration
|
Only applicable to SPAN firmware 7.07 and newer.
Required if logging RAWDMI.
Velocity input is not currently supported.
|
