Novatel OEM6, User Manual

Page: 85 / 175

OEM6 Family Installation and Operation User Manual Rev 7 85
Chapter 7 Troubleshooting
There are simple ways to diagnose and resolve problems. In many cases, the issue can be resolved
within a few minutes, avoiding the inconvenience and loss of productivity that results from having to
return the receiver for repair. This chapter discusses troubleshooting issues and includes cross-
references to other sections of the manual that may help resolve problems.
If unsure of the symptoms or if the symptoms do not match any of those listed, use the RXSTATUS log to
check the receiver status and error words. See
Section 7.1, Examining the RXSTATUS Log, page 86 .
Try to resolve the problem using the troubleshooting guide in Table 9 , then try our Knowledge Base at
www.novatel.com/support/ . If you are still not able to resolve the problem, contact Customer Support on
Page 14 .
Table 9: Troubleshooting Based on Symptoms
Symptom Related Section
The receiver is not properly
powered
Check and replace a faulty power cable
See
2.4Power Supply Requirements on Page 24 for the OEM6 cards or
3.3.3FlexPak6 Alternative Power Source on Page 39
The receiver cannot establish
communication
Check and replace faulty serial cables and ports.
See
Section 4.7.2, CAN Bus, page 63 and
Section 5.6, Status LED, page 71 . Refer also to the COMCONFIG log in
the OEM6 Family Firmware Reference Manual (OM-20000129)
The receiver is not tracking
satellites
Ensure that you have an unobstructed view of the sky from horizon to
horizon.
Check the RXSTATUS error states. See
Section 7.1, Examining the
RXSTATUS Log, page 86 . If the receiver is in error mode, it does not track
Check for and replace a faulty antenna cable. See Section 2.3, Selecting
a GNSS Antenna, page 22 , Section 2.3.1, Choosing a Coaxial Cable,
page 23 , Section 2.3.3, Connecting the Antenna to the Receiver, page 24 .
No data is being logged
See Section 4.7.2, CAN Bus, page 63 and Section 4.1, Communications
with the Receiver, page 42
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 Reference Manual (OM-20000129). See also Section
4.7.2, CAN Bus, page 63
A command is not accepted by the
receiver
Check for correct spelling and command syntax.
See
Section 4.1, Communications with the Receiver, page 42 and refer to
the
FRESET
command in the OEM6 Family Firmware Reference Manual
(OM-20000129)
Differential mode is not working
properly
See Section 4.3, Transmitting and Receiving Corrections, page 47 and
refer to the COMCONFIG log in the OEM6 Family Firmware Reference
Manual (OM-20000129)
There appears to be a problem with
the receiver’s memory Refer to the
NVMRESTORE
command in the OEM6 Family Firmware
Reference Manual (OM-20000129)
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 all Appendices
specific to the product. Move the receiver to within an acceptable
temperature range