Information in this document is subject to change without notice and does not represent a commitment on the part of NovAtel Inc. The information contained within this manual is believed to
be true and correct at the time of publication.
NovAtel is a registered trademarks of NovAtel Inc.
OEM7, OEM719, OEM729 and OEM7700 are trademarks of NovAtel Inc.
All other brand names are trademarks of their respective holders.
OEM6 to OEM7 Integration Guide2
Proprietary Notice2
Customer Support
NovAtel Knowledge Base6
Before Contacting Customer Support6
Contact Information6
Chapter 1New for OEM7
Chapter 2New for OEM7 – Firmware
2.1 Firmware Version Naming9
2.2 New for OEM7 – Commands9
2.2.1 Replaced Commands9
2.2.2 Revised Commands10
2.2.3 Deleted Commands13
2.2.4 New Commands13
2.2.5 CANCONFIG16
2.2.6 CCOMCONFIG18
2.2.7 COMCONTROL21
2.2.8 CONNECTIMU24
2.2.9 EXTERNALPVAS26
2.2.10 FORCEGLOL2CODE30
2.2.11 FORCEGPSL2CODE32
2.2.12 INSCALIBRATE34
2.2.13 INSSEED36
2.2.14 ITBANDPASSCONFIG38
2.2.15 ITFRONTENDMODE40
2.2.16 ITINTERFERENCEDETECT42
2.2.17 ITPROGFILTCONFIG44
2.2.18 ITSPECTRALANALYSIS46
2.2.19 J1939CONFIG50
2.2.20 NMEAFORMAT52
2.2.21 NVMUSERDATA55
2.2.22 PGNCONFIG56
2.2.23 PPPBASICCONVERGEDCRITERIA57
2.2.24 PPPDYNAMICSEED58
2.2.25 PPPRESET60
2.2.26 REFERENCESTATIONTIMEOUT61
2.2.27 RTKPORTMODE62
2.2.28 RTKRESET64
2.2.29 SAVEUSBCONFIG65
2.2.30 SETINSPROFILE66
2.2.31 SETINSROTATION67
2.2.32 SETINSTRANSLATION70
2.2.33 SETSEARCHTYPE73
2.2.34 USBCONFIG74
2.3 New for OEM7 – Logs76
2.3.1 Replaced Logs76
2.3.2 Revised Logs76
2.3.3 Deleted Logs79
OEM6 to OEM7 Integration Guide v13
OEM6 to OEM7 Integration Guide
2.3.4 New Logs80
2.3.5 HWMONITOR82
2.3.6 INSATTX86
2.3.7 INSCALSTATUS91
2.3.8 INSCONFIG93
2.3.9 INSSTDEV96
2.3.10 INSSTDEVS98
2.3.11 INSUPDATESTATUS100
2.3.12 ITBANDPASSBANK102
2.3.13 ITFILTTABLE104
2.3.14 ITPROGFILTBANK106
2.3.15 ITPSDFINAL109
2.3.16 J1939STATUS112
2.3.17 LBANDRAWFRAME114
2.3.18 MODELFEATURES116
2.3.19 RANGECMP4120
2.3.20 RTKASSISTSTATUS132
2.3.21 RXSTATUS134
2.3.22 SAFEMODESTATUS146
2.4 New for OEM7 – SPAN149
2.4.1 Translational Offsets149
2.4.2 Rotational Offsets149
2.4.3 INS Profiles150
2.4.4 INSSeed150
2.4.5 Multi-Line Body to Vehicle Calibration150
2.4.6 KVH1725 and KVH1750 Baud Rate Conversion151
2.4.7 INS Profiles152
2.4.8 Multi-Line Body to Vehicle Frame Rotation Calibration Routine153
2.4.9 INSSeed / Fast INS Initialization155
Saving155
Use at Boot-up155
Alignment Type: Bits 26-28156
NVM Seed Status: Bits 29-31156
Chapter 3New for OEM7 – Hardware
3.1 Physical changes157
3.1.1 Shielding157
3.1.2 Mounting157
3.1.3 Weight158
3.2 Electrical changes158
3.2.1 COM Port Data Rate158
3.2.2 Power Supply158
3.2.3 Input and Output lines159
3.2.4 LNA Power159
3.3 Environmental changes160
3.3.1 Thermal dissipation160
3.3.2 Vibration160
3.4 Interference160
3.4.1 Interference from Co-Located LNA161
3.5 Receiver Card Interface Examples163
3.5.1 EVENT_IN, EVENT_OUT and PPS Signal Protection163
3.5.2 Position Valid (PV) LED Driver165
3.5.3 Communication Ports166
3.5.4 CAN Controller Ports167
3.5.5 USB Interface168
OEM6 to OEM7 Integration Guide v14
OEM6 to OEM7 Integration Guide
3.5.6 Ethernet Port170
Chapter 4Receiver Technical Specifications
4.1 OEM719 Technical Specifications174
4.1.1 OEM719 Performance Specifications175
4.1.2 OEM719 Mechanical Specifications177
4.1.3 OEM719 Electrical and Environmental Specifications184
4.1.4 OEM719 Data Communication Specifications186
4.1.5 OEM719 Strobe Specifications188
4.1.6 OEM719 Interface Connector190
4.2 OEM729 Technical Specifications194
4.2.1 OEM729 Performance Specifications195
4.2.2 OEM729 Mechanical Specifications197
4.2.3 OEM729 Electrical and Environmental Specifications200
4.2.4 OEM729 Data Communication Specifications202
4.2.5 OEM729 Strobe Specifications204
4.2.6 OEM729 Interface Connectors206
4.3 OEM7700 Technical Specifications214
4.3.1 OEM7700 Performance Specifications215
4.3.2 OEM7700 Mechanical Specifications217
4.3.3 OEM7700 Electrical and Environmental Specifications220
4.3.4 OEM7700 Data Communication Specifications222
4.3.5 OEM7700 Strobe Specifications224
4.3.6 OEM7700 Interface Connector226
OEM6 to OEM7 Integration Guide v15
Customer Support
Customer Support
NovAtel Knowledge Base
If you have a technical issue, visit the NovAtel Support page at www.novatel.com/support.
Through the Support page, you can contact Customer Support, find papers and tutorials or download current manuals and the latest firmware.
Before Contacting Customer Support
Before you contact NovAtel Customer Support about a software problem, perform the following
steps:
If logging data over an RS-232 serial cable, ensure that the configured baud rate can support the data bandwidth (see SERIALCONFIG command). NovAtel recommends a min-
imum suggested baud rate of 115200 bps.
1.
Log the following data to a file on your computer for 15 minutes:
RXSTATUSB once
RAWEPHEMB onchanged
GLORAWEPHEMB onchanged
BESTPOSB ontime 1
RANGEB ontime 1
RXCONFIGA once
VERSIONA once
For SPAN systems, include the following logs in the file created on your computer:
RAWIMUSXB onnew
INSUPDATESTATUSB onnew
INSPVAXB ontime 1
INSCONFIGA once
2.
Send the data file to NovAtel Customer Support: support@novatel.com
3.
You can also issue a FRESET command to the receiver to clear any unknown settings.
The FRESET command will erase all user settings. You should know your configuration
(by requesting the RXCONFIGA log) and be able to reconfigure the receiver before you
send the FRESET command.
If you are having a hardware problem, send a list of the troubleshooting steps taken and the results.
Contact Information
Log a support request with NovAtel Customer Support using one of the following methods:
Log a Case and Search Knowledge:
OEM6 to OEM7 Integration Guide v16
Customer Support
Website: www.novatel.com/support
Log a Case, Search Knowledge and View Your Case History: (login access required)
Web Portal: https://novatelsupport.force.com/community/login
E-mail:
support@novatel.com
Telephone:
U.S. and Canada:1-800-NOVATEL (1-800-668-2835)
International:+1-403-295-4900
OEM6 to OEM7 Integration Guide v17
Chapter 1New for OEM7
When upgrading from an OEM6 receiver to an OEM7 receiver, there are several hardware and
software differences that must be accounted for in the system design.
These differences are described in the following chapters:
l
New for OEM7 – Firmware on page9
l
New for OEM7 – Hardware on page157
l
Receiver Technical Specifications on page173
OEM6 to OEM7 Integration Guide v18
Chapter 2New for OEM7 – Firmware
This chapter describes the new commands, logs, features and functionality available on OEM7
receivers.
2.1Firmware Version Naming
For information about the fields in the firmware version, refer to the VERSION log.
2.2New for OEM7 – Commands
The following sections describe the command changes between OEM6 and OEM7.
2.2.1Replaced Commands
The following table lists the OEM6 commands that have been obsoleted and the commands that
replace them in OEM7.
Table 1: Replaced Commands in OEM7
OEM6OEM7
ASSIGNLBANDUse the existing ASSIGNLBANDBEAM command
ASSIGNLBAND2Use the existing ASSIGNLBANDBEAM command
BASEANTENNAMODEL
COMUse the existing SERIALCONFIG command
Use the existing BASEANTENNAPCO command andBASEANTENNAPCV command
OEM6 to OEM7 Integration Guide v19
Chapter 2 New for OEM7 – Firmware
OEM6OEM7
COMCONFIG
EXTHDGOFFSETUse the new SETINSROTATION command (see page 67)
GIMBALSPANROTATIONUse the new SETINSROTATION command (see page 67)
INSWHEELUPDATEUse the existing SETINSUPDATE command
INSZUPTCONTROLUse the existing SETINSUPDATE command
LEVERARMCALIBRATEUse the new INSCALIBRATE command (see page 34)
PDPVELOCITYOUTUse the existing BESTVELTYPE command
RVBCALIBRATEUse the new INSCALIBRATE command (see page 34)
SETGIMBALORIENTATIONUse the new SETINSROTATION command (see page 67)
SETIMUORIENTATIONUse the new SETINSROTATION command (see page 67)
SETIMUTOANTOFFSETUse the new SETINSTRANSLATION command (see page 70)
SETIMUTOANTOFFSET2Use the new SETINSTRANSLATION command (see page 70)
SETIMUTOEXTOFFSETUse the new SETINSTRANSLATION command (see page 70)
SETIMUTOGIMBALOFFSETUse the new SETINSTRANSLATION command (see page 70)
Use the existing SERIALCONFIG command, INTERFACEMODE
command and ECHO command
SETINSOFFSETUse the new SETINSTRANSLATION command (see page 70)
SETINITATTITUDEUse the existing SETINITAZIMUTH command
VEHICLEBODYROTATIONUse the new SETINSROTATION command (see page 67)
Use the new SETINSROTATION command on page67 andSETINSTRANSLATION command on page70
The existing SETINSROTATION command (Message ID1796) has been
renamed SETINSROTATION_LEGACY, but retains the Message IDof
1796.
A new SETINSROTATION command (see page 67) (Message ID1921)
has been added. This new command has enhanced capability and is the
recommend command to use.
Use the new SETINSROTATION command on page67 andSETINSTRANSLATION command on page70
2.2.2Revised Commands
Revised commands are listed in the following table.
OEM6 to OEM7 Integration Guide v110
Chapter 2 New for OEM7 – Firmware
Table 2: Revised Commands in OEM7
OEM6OEM7
3V3 option removed
ANTENNAPOWER
ASSIGN,
ASSIGNALL,
LOCKOUT,
SBASCONTROL,
The OEM7 tracks SBAS PRNs 120-158 and 183-187.
The OEM6 tracked 120-138 and 183-187
TRACKSV,
UNLOCKOUT
If a short circuit or other problem causes an overload of the current supplied to the antenna, the receiver hardware shuts down
the power supplied to the antenna. To restore power, power
cycle the receiver. The Receiver Status word, available in the
RXSTATUS log (see page 134), provides more information
about the cause of the problem.
ASSIGNLBANDBEAM
AUTH
COMCONTROL
This command now supports multiple L-Band channels.
The Frequency field is entered only in Hz.
New options were added for the State parameter
ASCIIBinaryDescription
ERASE_
TABLE
CLEAN_
TABLE
7
8Remove all invalid auth codes from the system
Erase all auth codes from the system. Requires a
special auth code to prevent against accidental
erasing
Special auth code for the ERASE_TABLE case:
PW5W2B,WW5TM9,WW2PCZ,WW3M4H,WW4HPG,ERASE_AUTH
Special auth code for the CLEAN_TABLE case:
4DR69H,G369W8,34MNJJ,5NHXCJ,GW7C75,CLEAN_AUTH
The COM ports available have changed to reflect the OEM7 receivers.
See the COMCONTROL command on page21
OEM6 to OEM7 Integration Guide v111
Chapter 2 New for OEM7 – Firmware
OEM6OEM7
Added the EPSON G320 IMU.
Removed the Litef LCI-1 IMU.
CONNECTIMU
ETHCONFIG
EXTERNALPVAS
FRESET
INTERFACEMODE
For the IMU Type parameter, the ASCII values for IMU no longer use the
"IMU_" prefix. However, the legacy ASCIIvalues that contain the "IMU_"
prefix are still supported. The binary IMU type values have not changed.
See the CONNECTIMU command on page24
Ethernet interface hardware now automatically connects properly to the
other physical device
The format of several of the options in this command have been changed
from Double to Float.
See the EXTERNALPVAS command on page26
Added new FRESET targets.
BinaryASCIIDescription
10USERDATA
Resets the user data saved using the
NVMUSERDATA command
82USBCONFIGResets the stored USB port settings
Added new Interface Mode options:
BinaryASCIIDescription
NovAtel binary message with a minimal
49NOVATELMINBINARY
header.
Only available for CCOM ports.
The default settings for a command can not be checked by logging that
command. A command must be sent to the receiver before logging the
command will produce valid values. Refer to the command description in
this documentation for the default values.
The optional parameters Period, Offset and Hold are only used when the
LOG
Trigger is ONTIME. Previous versions of the firmware accepted (but ignored)
non-zero values for Period and Offset even if the Trigger was not ONTIME.
The firmware on OEM7 receivers will reject such commands and return an
error.
It is especially important that these values are zero when entering a LOG
command in Binary or ASCII format.
POSAVE“state” field no longer optional; default ON. A value must now be entered
SETINITAZIMUTH
OEM6 to OEM7 Integration Guide v112
The range for the standard deviation parameter has changed to 1 to 25
degrees.
Chapter 2 New for OEM7 – Firmware
2.2.3Deleted Commands
The OEM6 commands that are not supported in OEM7 are listed in the following table.
Table 3: Deleted Commands in OEM7
OEM6OEM7
APPLYVEHICLEBODYROTATIONobsolete
ASSIGNLBANDobsolete
ASSIGNLBAND2obsolete
DGPSEPHEMDELAYobsolete
OMNIUSEGLONASSobsolete
PDPVELOCITYOUTobsolete
RTKCOMMANDobsolete
RTKELEVMASKobsolete
SETCANNAMEobsolete
SETRTCM16obsolete
SETRTCM36obsolete
SETRTCMRXVERSIONobsolete
SETRTCMTXVERSIONobsolete
SETWHEELSOURCEobsolete
2.2.4New Commands
The following table lists the commands added in OEM7.
Table 4: New Commands in OEM7
OEM7Description
CANCONFIG
CCOMCONFIG
Configures the CAN port parameters
See the CANCONFIG command on page16
Binds a CAN port to a J1939 node configures the CAN protocol
used by the port.
See the CCOMCONFIG command on page18
INSCALIBRATE
OEM6 to OEM7 Integration Guide v113
Initiates the calibration of INS offsets
See the INSCALIBRATE command on page34
Chapter 2 New for OEM7 – Firmware
OEM7Description
INSSEED
Enables or disables saving and restoring the last known SPAN
solution
See the INSSEED command on page36
ITBANDPASSCONFIG
ITFRONTENDMODE
ITINTERFERENCEDETECT
ITPROGFILTCONFIG
ITSPECTRALANALYSIS
J1939CONFIG
NMEAFORMAT
NVMUSERDATA
Configures a bandpass filter on the receiver
See the ITBANDPASSCONFIG command on page38
Configures the front end mode for each RF path
See the ITFRONTENDMODE command on page40
Enables and configures interference detection
See the ITINTERFERENCEDETECT command on page42
Configures filtering on the receiver
See the ITPROGFILTCONFIG command on page44
Enables and configures spectral analysis on the receiver
See the ITSPECTRALANALYSIS command on page46
Configures the CAN J1939 network-level parameters
See the J1939CONFIG command on page50
Customizes the NMEA output
See the NMEAFORMAT command on page52
Writes the data provided to NVM
See the NVMUSERDATA command on page55
PGNCONFIG
PPPBASICCONVERGEDCRITERIA
PPPDYNAMICSEED
PPPRESET
Configures the PGNs of the proprietary NMEA 2000 fast-packet
messages
See the PGNCONFIG command on page56
Sets the convergence threshold for lower accuracy PPP
solutions.
See the PPPBASICCONVERGEDCRITERIA command on
page57
Seed the PPP filter in any platform motion state
See the PPPDYNAMICSEED command on page58
Resets the PPPfilter.
See the PPPRESET command on page60
OEM6 to OEM7 Integration Guide v114
Chapter 2 New for OEM7 – Firmware
OEM7Description
REFERENCESTATIONTIMEOUT
RTKPORTMODE
RTKRESET
SAVEUSBCONFIG
SETINSPROFILE
SETINSROTATION
SETINSTRANSLATION
Sets a timeout for removing previously stored base stations
See the REFERENCESTATIONTIMEOUT command on page61
Assigns a port on the rover receiver for the RTK and ALIGN
information being received
See the RTKPORTMODE command on page62
Resets the RTK filter.
See the RTKRESET command on page64
Saves the USB port configuration.
See the SAVEUSBCONFIG command on page65
Set the filter behavior to optimize the output for a specific
environment
See the SETINSPROFILE command on page66
Specifies the rotational offsets between the IMU frame and
other reference frames, such as the vehicle frame or an ALIGN
baseline
see the SETINSROTATION command on page67
Specifies the translational offsets between the IMU frame and
other reference frames, including GNSS antennas or the desired
output frame
SETSEARCHTYPE
USBCONFIG
See the SETINSTRANSLATION command on page70
Specifies the search type used by the receiver for signal
acquisition.
See the SETSEARCHTYPE command on page73
Configures the operating mode and speed of the USBport.
See the USBCONFIG command on page74
OEM6 to OEM7 Integration Guide v115
Chapter 2 New for OEM7 – Firmware
2.2.5CANCONFIG
Configure CAN ports
Platform:OEM729, OEM719, OEM7700
Use the CANCONFIG command to configure the hardware parameters of the CAN ports.
Message ID: 884
Abbreviated ASCII Syntax:
CANCONFIG port switch [speed]
Factory Default:
CANCONFIG CAN1 OFF 250K
CANCONFIG CAN2 OFF 250K
ASCII Example:
CANCONFIG CAN1 OFF 500K
FieldField Type
1
2port
3switch
4speed
CANCONFIG
header
The CAN port must be set to OFF (using CANCONFIG <port> OFF) before the port speed
can be changed.
ASCII
Value
--
CAN11
CAN22
ON1
OFF0
See Table 5: CANPort Speed below
Binary
Value
Table 5: CAN Port Speed
DescriptionFormat
Command header. See
Messages for more
information.
Physical CAN port IDEnum4H
Sets the port to be On or
Off the CAN bus
Physical CANport speed
(bits per second)
(default = 250K
-H0
Enum4H+4
Enum4H+8
Binary
Bytes
Binary
Offset
ASCII ValueBinary Value
10K0
20K1
OEM6 to OEM7 Integration Guide v116
Chapter 2 New for OEM7 – Firmware
ASCII ValueBinary Value
50K2
100K3
125K4
250K5
500K6
1M7
OEM6 to OEM7 Integration Guide v117
Chapter 2 New for OEM7 – Firmware
2.2.6CCOMCONFIG
Configure the CAN COM port
Platform:OEM729, OEM719, OEM7700
Bind a CAN communication port to a J1939 node (see J1939CONFIG command on page50) and
specify the CAN protocol, PGN, priority and address for messages transmitted and received over
the CCOM port.
Message ID: 1902
Abbreviated ASCII Syntax:
CCOMCONFIG port node protocol [pgn [priority [address]]]
Factory Default:
CCOMCONFIG ccom1 node1 1939 61184 7 fe
CCOMCONFIG ccom2 node2 J1939 61184 7 fe
CCOMCONFIG ccom3 node1 J1939 126720 7 fe
CCOMCONFIG ccom4 none none 0 0 0
CCOMCONFIG ccom5 none none 0 0 0
CCOMCONFIG ccom6 none none 0 0 0
ASCII Example :
ccomconfig ccom1 j1939 1792 6 1b
FieldField Type
1
2port
CCOMCONFIG
Header
ASCII
Value
--
CCOM138
CCOM239
CCOM340
CCOM441
CCOM542
Binary
Value
DescriptionFormat
Command header. See
Messages for more
information.
Name of CCOM portEnum4H
-H0
Binary
Bytes
Binary
Offset
CCOM643
NODE11
3node
NODE22
OEM6 to OEM7 Integration Guide v118
The J1939 node to use.
This binds a CCOM port to
the CAN NAME/address
associated with the node.
Enum4H+4
Chapter 2 New for OEM7 – Firmware
FieldField Type
ASCII
Value
See Table 6:
4protocol
CAN Protocol on
the next page
5pgn0 - 131071
6priority0-7
Binary
Value
DescriptionFormat
CAN transport protocol to
use
Any valid PGN as defined
by the J1939 protocol.
All messages transmitted
over this CCOM port will
contain this PGN value.
Only messages with this
PGN will be received on
this CCOM port
Note: This value is
ignored if the protocol is
NMEA2000.
Default CAN message
priority for transmitted
messages. (Priority 0 is
the highest priority)
Note: This value is
ignored if the protocol is
NMEA2000 or ISO15765.
Binary
Bytes
Binary
Offset
Enum4H+8
Ulong4H+12
Uchar1H+16
7address00 – FF
00 – FD:
Transmit and receive
messages to/from this
address only
FE:
Transmit and receive
message to/from the
address of the first
message received
FF:
Broadcast messages and
receive messages from
all addresses.
Note: This value is
ignored if the protocol is
NMEA2000 or ISO15765.
Hex1H+17
OEM6 to OEM7 Integration Guide v119
Chapter 2 New for OEM7 – Firmware
BinaryASCIIDescription
2J1939J1939 single packet
3NMEA2000NMEA2000 (single packet, multi-packet, fast packet)
4ISO15765ISO 15765-2 transport protocol
5ISO11783ISO 11783 transport protocol
Table 6: CAN Protocol
OEM6 to OEM7 Integration Guide v120
Chapter 2 New for OEM7 – Firmware
2.2.7COMCONTROL
Controls the serial port hardware control lines
Platform:OEM729, OEM719, OEM7700
This command is used to control the hardware control lines of the serial communication (COM)
ports. The TOGGLEPPS mode of this command is typically used to supply a timing signal to a
host PC computer by using the RTS and DTR lines. The accuracy of controlling the COM control
signals is better than 900 ms. The other modes are typically used to control custom peripheral
devices.
1.
If handshaking is disabled, any of these modes can be used without affecting regular
serial communications through the selected COM port. However, if handshaking is
enabled, it may conflict with handshaking of the selected COM port, causing unexpected results.
2.
The PULSEPPSLOW control type cannot be issued for a TX signal.
3.
Only PULSEPPSHIGH, FORCEHIGH and FORCELOW control types can be used for a TX
signal.
A break condition remains in effect until it is cleared. To clear a break condition on AUX:
COMCONTROL COM1 TX DEFAULT
OEM6 to OEM7 Integration Guide v121
Chapter 2 New for OEM7 – Firmware
or
COMCONTROL COM1 TX FORCEHIGH
Field
Field
Type
COM
1
CONTROL
header
2port
3signal
ASCII Value
Binary
Value
--
COM11
COM22
COM33
COM419
COM531
RTS0
TX2
DescriptionFormat
Binary
Bytes
Binary
Command header.
See Messages for
-H0
more information.
Serial port to control.Enum4H
COM signal to control.
The controllable COM
signals are RTS, DTR
and TX. (Default =
RTS)
Enum4H+4DTR1
See also Table 7: Tx,
DTR and RTS
Availability on the
next page
Offset
OEM6 to OEM7 Integration Guide v122
Chapter 2 New for OEM7 – Firmware
Field
Field
Type
4control
ASCII Value
Binary
DEFAULT0
FORCEHIGH1
FORCELOW2
TOGGLE3
TOGGLEPPS4
Value
DescriptionFormat
Disables this
command and returns
the COM signal to its
default state (Default)
Immediately forces
the signal high
Immediately forces
the signal low
Immediately toggles
the current sate of the
signal
Toggles the state of
the selected signal
within 900 μs after
each 1PPS event. The
state change of the
signal lags the 1PPS
by an average value
of 450 μs. The delay
of each pulse varies
by a uniformly
random amount less
than 900 μs
Binary
Bytes
Binary
Offset
Enum4H+8
Pulses the line low at
PULSEPPSLOW5
a 1PPS event and to
high 1 ms after it. Not
for TX
Pulses the line high
PULSEPPSHIGH6
for 1 ms at the time
of a 1PPS event
Table 7: Tx, DTR and RTS Availability
Tx Available OnDTR Available OnRTS Available On
OEM719COM1, COM2N/AN/A
OEM729COM1, COM2, COM3N/ACOM1 and COM2
OEM7700COM1, COM2, COM3, COM4, COM5N/ACOM1 and COM2
OEM6 to OEM7 Integration Guide v123
Chapter 2 New for OEM7 – Firmware
2.2.8CONNECTIMU
Connects an IMU to a Port
Platform:OEM729, OEM719, OEM7700
Use this command to specify the type of IMU connected to the receiver and the receiver port
used by the IMU.
Message ID: 1428
Abbreviated ASCII Syntax:
CONNECTIMU IMUPort IMUType
Abbreviated ASCII Example:
CONNECTIMU COM2 LN200
FieldField Type
1
2IMUPort
CONNECTIMU
header
1
3IMUType
SPI, COM4 and COM5 are available only on the OEM7700.
ASCII
Value
Binary
Value
Description
Command header. See
--
Messages for more
information.
COM11IMU Port is COM port 1
COM22IMU Port is COM port 2
COM33IMU Port is COM port 3
SPI7
IMUPort is the SPIport
(OEM7700 only)
COM419IMUPort is COM port 4
COM531IMU Port is COM port 5
See Table 8: IMUType on the next
IMU TypeEnum4H+4
page
Binary
Format
Binary
Bytes
Binary
-H0
Enum4H
Offset
1
The IMU-ISA-100C, IMU-FSAS, IMU-HG1900, IMU-LN200, IMU-µIMU, IMU-CPT and IMU-KVH1750 use RS-422
protocol and must be connected to a receiver port that is configured to use RS-422. Refer to the OEM7 Installation
and Operation User Manual (OM-20000168) for information about which receiver ports support RS-422 and
instructions for enabling RS-422.
OEM6 to OEM7 Integration Guide v124
Chapter 2 New for OEM7 – Firmware
BinaryASCIIDescription
0UNKNOWNUnknown IMU type (default)
1HG1700_AG11Honeywell HG1700 AG11
4HG1700_AG17Honeywell HG1700 AG17
5HG1900_CA29Honeywell HG1900 CA29
8LN200Litton LN-200
11HG1700_AG58Honeywell HG1700 AG58
12HG1700_AG62Honeywell HG1700 AG62
13IMAR_FSASiMAR iIMU-FSAS
16KVH_COTSKVH IMU-CPT
20HG1930_AA99Honeywell HG1930 AA99
26ISA100CNorthrop Grumman Litef ISA-100C
Table 8: IMU Type
27HG1900_CA50Honeywell HG1900 CA50
28HG1930_CA50Honeywell HG1930 CA50
31ADIS16488Analog Devices ADIS16488
32STIM300Sensonor STIM300
33KVH_1750KVH1750 IMU
34ISA100Northrop Grumman Litef ISA-100
41EPSON_G320Epson G320
45KVH-1725KVH1725 IMU
52LITEF_MICROIMULitef µIMU
The IMU Type field also supports the legacy ASCIIvalues that contain the "IMU_" prefix.
For example, LN200 or IMU_LN200.
Values not shown in this table are reserved.
OEM6 to OEM7 Integration Guide v125
Chapter 2 New for OEM7 – Firmware
2.2.9EXTERNALPVAS
Enter PVA Update
Platform:OEM729, OEM719, OEM7700
This command should only be used by advanced users of GNSS/INS.
The standard deviations entered using this command must be representative of actual
input error.
The EXTERNALPVAS command uses a short header if the command is entered in ASCII
or Binary.
This command allows a user to provide full position, velocity and attitude updates, in any combination, to the INS. The user can also provide height or attitude only updates, along with Zero
Velocity Updates (ZUPTs). These position and velocity updates are entered in local level frame
or ECEF.
The default input frame is ECEF. Updates are entered in ECEF unless Local Level is specified using the OptionsMask parameter.
Command header. See
Messages for more
information.
Binary
Format
-H0
Binary
Bytes
Binary
Offset
OEM6 to OEM7 Integration Guide v126
Chapter 2 New for OEM7 – Firmware
FieldField Type
2Position1
3Position2
4Position3
5Velocity1
6Velocity2
7Velocity3
ASCII
Value
Binary
Value
Description
Latitude in degrees or
ECEF X-coordinate in
metres
Longitude in degrees or
ECEF Y-coordinate in
metres
Height or ECEF Zcoordinate in metres
North velocity or velocity
along the X-axis in
metres/second
East velocity or velocity
along the Y-axis in
metres/second
Up velocity or velocity
along the Z-axis in
metres/second
Binary
Format
Binary
Bytes
Binary
Offset
Double8H
Double8H+8
Double8H+16
Float4H+24
Float4H+28
Float4H+32
8Attitude1
9Attitude2
10Attitude3
11PosStdDev1
12PosStdDev2
13PosStdDev3
14VelStdDev1
15VelStdDev2
Roll in local level in
degrees
Pitch in local level in
degrees
Azimuth in local level in
degrees
Position1 standard
deviation in metres
Position2 standard
deviation in metres
Position3 standard
deviation in metres
Velocity1 standard
deviation in
metres/second
Velocity2 standard
deviation in
metres/second
Float4H+36
Float4H+40
Float4H+44
Float4H+48
Float4H+52
Float4H+56
Float4H+60
Float4H+64
OEM6 to OEM7 Integration Guide v127
Chapter 2 New for OEM7 – Firmware
FieldField Type
16VelStdDev3
17AttStdDev1
18AttStdDev2
19AttStdDev3
20UpdateMask
ASCII
Value
Binary
Value
Description
Velocity3 standard
deviation in
metres/second
Attitude1 standard
deviation in degrees
Attitude2 standard
deviation in degrees
Attitude3 standard
deviation in degrees
This mask selects which
updates are applied.
Setting a bit applies the
update and more than
one update can be
applied at one time.
See Table 9:
EXTERNALPVAS Updates
Mask below.
Binary
Format
Binary
Bytes
Binary
Offset
Float4H+68
Float4H+72
Float4H+76
Float4H+80
HEX
Ulong
4H+84
This mask selects the
21OptionsMask
update options. See
Table 10:
EXTERNALPVAS Options
HEX
Ulong
4H+88
Mask on the next page.
Table 9: EXTERNALPVAS Updates Mask
BitMaskDescription
00x00001Reserved
10x00002Reserved
20x00004ZUPT Update. No fields required in the EXTERNALPVAS command for this update.
30x00008Reserved
40x00010Reserved
External Position Update.
50x00020
This update is entered using Position1 to Position3 in the EXTERNALPVAS
command.
OEM6 to OEM7 Integration Guide v128
Chapter 2 New for OEM7 – Firmware
BitMaskDescription
60x00040Reserved
70x00080Reserved
80x00100Reserved
90x00200Reserved
100x00400Reserved
110x00800Reserved
120x01000Reserved
130x02000Reserved
External Velocity Update.
140x04000
This update is entered using Velocity1 to Velocity3 in the EXTERNALPVAS
command.
External Attitude Update.
150x08000
This update is entered using Attitude1 to Attitude3 in the EXTERNALPVAS
command.
160x10000
170x20000
External Heading Update.
This update is entered using Attitude3 in the EXTERNALPVAS command.
External Height Update.
This update is entered using Position3 in the EXTERNALPVAS command.
If both the External Position Update and External Height Update bits are set, only the
External Position Update will be applied.
If both the External Attitude Update and External Heading Update bits are set, only the
External Attitude Update will be applied.
Table 10: EXTERNALPVAS Options Mask
BitMaskDescription
If this bit is set, the position and velocity input frame is set to local level.
00x1
If cleared, the input frame is ECEF.
If this bit is set, the heading update is set relative.
10x2
If cleared, the heading update is absolute.
OEM6 to OEM7 Integration Guide v129
Chapter 2 New for OEM7 – Firmware
2.2.10FORCEGLOL2CODE
Forces receiver to track GLONASS satellite L2 P or L2 C/A code
Platform:OEM729, OEM719, OEM7700
This command is used to force the receiver to track GLONASS satellite L2 P-code or L2 C/A code.
This command has no effect if the channel configuration contains both GLONASS L2 P and L2 C/A
channels.
Message ID: 1217
Abbreviated ASCII Syntax:
FORCEGLOL2CODE L2type
Factory Default:
FORCEGLOL2CODE default
ASCII Example:
FORCEGLOL2CODE p
Field
1
2L2type
The following table lists which L2 signal is tracked based on the channel configuration and the
setting used for the L2type parameter.
Field
Type
FORCEGLO
L2CODE
header
ASCII
Value
--
See Table 11:
GLONASS L2 Code
Type below
BinaryASCIIDescription
1PL2 P-code or L2 Precise code
2CL2 C/A code or L2 Coarse/Acquisition code
3DEFAULTSet to channel default
Binary
Value
Command header. See
Messages for more
information.
GLONASS L2 code typeEnum4H
Table 11: GLONASS L2 Code Type
DescriptionFormat
-H0
Binary
Bytes
Binary
Offset
OEM6 to OEM7 Integration Guide v130
Loading...
+ 207 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.