Examining The Rxstatus Log; Resolving A Receiver Error Word - Novatel OEM6 Series User Manual

Hide thumbs Also See for OEM6 Series:
Table of Contents

Advertisement

Chapter 7
Overload and overrun problems.
Either the CPU or port buffers are
overloaded
The receiver is indicating that an
invalid authorization code has been
used
The receiver is being affected by
jamming
The receiver's Automatic Gain
Control (AGC) is not working
properly
7.1

Examining the RXSTATUS Log

The RXSTATUS log provides detailed status information about your receiver and can be used to
diagnose problems. Refer to the
on this log and on how to read the receiver error word and status word. Table 10, Resolving a Receiver
Error Word on page 86 and Table 11, Resolving an Error in the Receiver Status Word on page 87 on
pages 86 to 87 have actions to take when your receiver has an error flag in either of these words. If you
are not able to resolve the condition, contact Customer Support on Page 14 .
Bit Set
0-2
Issue a FRESET command (for bit 1, reload new firmware)
4
Contact Customer Support on Page 14
Check the VERSION log. The VERSION log will indicate "Invalid authcode". Upgrade the auth-code
5
as described in 8.5Upgrading Using the AUTH Command on Page 99
6
Issue a FRESET command
7
See Section 2.4, Power Supply Requirements, page 24
8
Reserved
Check temperature ranges in the ENVIRONMENTAL table sections of all Appendices specific to the
9
product
Possible hardware or environmental condition. If you cannot resolve the problem, contact Customer
10-12
Support on Page 14
13-14
Reserved
Issue a FRESET command and power cycle the unit. If the bit is still present, contact Customer
15
Support
16
Monitor CPU idle time. Reduce number of logs or the rate of data logging
17
Ensure that the version log is consistent with the hardware
20
SoftLoad is in progress. See Section 8.4, Updating Using SoftLoad Commands, page 93
You may be exceeding the receiver's velocity limit. If so, reduce velocity. This error can only be
21
cleared by resetting the receiver
22
Reload firmware using WinLoad or the SoftLoad commands
31
Possible hardware failure. Contact Customer Support on Page 14
86
Reduce the amount of logging or increase the baud rate. See also Table
3, OEM6 Card Default Serial Port Configurations on page 31
Refer to the VERSON or VALIDMODELS logs and the MODEL or AUTH
commands in the
OEM6 Family Firmware Reference Manual
(OM-20000129)
Move the receiver away from any possible jamming sources
See Section 2.3.1, Choosing a Coaxial Cable, page 23 and the jamming
symptom in this table
OEM6 Family Firmware Reference Manual
Table 10: Resolving a Receiver Error Word
Action to Resolve
OEM6 Family Installation and Operation User Manual Rev 7
Troubleshooting
(OM-20000129) for details

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Oem615Oem617dOem628Oem638

Table of Contents