Download OEM6 Installation and Operation

Troubleshooting
Chapter 6
No data is being logged
See Section 2.5.3, CAN Bus, page 43, and Section 3.1,
Communications with the Receiver, page 47.
Random data is being output by the
receiver, or binary data is streaming
Check the baud rate on the receiver and in the
communication software. Refer to the SERIALCONFIG
log and FRESET command in the OEM6 Family
Firmware Manual. See also Section 2.5.3, CAN Bus,
page 43.
A command is not accepted by the
receiver
Check for correct spelling and command syntax.
See Section 3.1, Communications with the Receiver,
page 47 and refer to the FRESET command in the OEM6
Family Firmware Reference Manual.
Differential mode is not working
properly
See Section 3.3, Transmitting and Receiving
Corrections, page 49 and refer to the COMCONFIG log
in the OEM6 Family Firmware Reference Manual.
There appears to be a problem with
the receiver’s memory
Refer to the NVMRESTORE command in the OEM6
Family Firmware Reference Manual.
An environmental or memory
failure. The receiver temperature is
out of acceptable range or the
internal thermometer is not working
See the ENVIRONMENTAL sections in the tables of
Appendix B, Technical Specifications starting on
page 97. Move the receiver to within an acceptable
temperature range or increase the baud rate.
Overload and overrun problems.
Either the CPU or port buffers are
overloaded
Reduce the amount of logging or reduce the baud rate.
See also Section 3.1.1, Serial Port Default Settings,
page 47.
The receiver is indicating that an
invalid authorization code has been
used
Refer to the Version log, VALIDMODELS log and the
MODEL command in the OEM6 Family Firmware
Reference Manual.
The receiver is being affected by
jamming
Move the receiver away from any possible jamming
sources.
The receiver’s automatic gain
control (AGC) is not working
properly
See Section 2.3.2, Choosing a Coaxial Cable, page 30
and the jamming symptom in this table.
OEM6 Family Installation and Operation User Manual Rev 4
89