Examining the RXSTATUS Log

The RXSTATUS log provides detailed status information about your receiver and can be used to diagnose problems. Refer to the RXSTATUS log for details on this log and on how to read the receiver error word and status word. Table: Resolving a Receiver Error Word, Table: Resolving an Error in the Receiver Status Word and Table: Resolving an Error in the AUX1 Status Word have actions to take when your receiver has an error flag in these words. If you are not able to resolve the condition, contact Customer Support.

Resolving a Receiver Error Word
Bit Set	Action to Resolve
0-2	Issue a FRESET command (for bit 1, reload new firmware).
4	Contact Customer Support.
5	Check the VERSION log. The VERSION log will indicate "Invalid authcode". Upgrade the auth-code as described in Upgrading Using an Auth-Code.
6	Issue a FRESET command
7	See Power Supply Requirements for Receiver Cards Power Supply Requirements for the PwrPak7 Power Supply Requirements for the CPT7 Power Supply Requirements for the SMART7 Power Supply Requirements for the SMART2
8	Reserved
9	Check the temperature ranges in: OEM719 Electrical and Environmental Specifications OEM729 Electrical and Environmental Specifications OEM7600 Electrical and Environmental Specifications OEM7700 Electrical and Environmental Specifications OEM7720 Electrical and Environmental Specifications PwrPak7 Electrical and Environmental Specifications CPT7 Electrical and Environmental Specifications SMART7 Environmental and Electrical Specifications SMART2 Environmental and Electrical Specifications The operating temperatures are ambient air temperatures. The temperature sensors on the receiver PCB will reflect higher operating temperatures (refer to the HWMONITOR log). The PCB temperature sensors will trigger a receiver warning and receiver error at 100°C and 110°C respectively. The warning and error conditions are captured using the RXSTATUS log.
10	Possible hardware or environmental condition. If you cannot resolve the problem, contact Customer Support.
11	Possible hardware or environmental condition. If you cannot resolve the problem, contact Customer Support. Also, check the Auxiliary 2 Status word to determine which PLL is in error.
12-14	Reserved
15	Issue a FRESET command and power cycle the unit. If the bit is still present, contact Customer 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.
18-19	Reserved
20	SoftLoad is in progress. See Updating Using SoftLoad Commands.
21	You may be exceeding the receiver’s velocity limit. If so, reduce velocity. This error can only be cleared by resetting the receiver.
22	Reload firmware using WinLoad or the SoftLoad commands.
23-30	Reserved
31	Possible hardware failure. Contact Customer Support.

Resolving an Error in the Receiver Status Word
Bit Set	Action to Resolve
0	Check the Error Word in the RXSTATUS log. See also Table: Resolving a Receiver Error Word
1	Check the temperature ranges in OEM719 Electrical and Environmental Specifications OEM729 Electrical and Environmental Specifications OEM7600 Electrical and Environmental Specifications OEM7700 Electrical and Environmental Specifications OEM7720 Electrical and Environmental Specifications PwrPak7 Electrical and Environmental Specifications CPT7 Electrical and Environmental Specifications SMART2 Environmental and Electrical Specifications SMART7 Environmental and Electrical Specifications
2	See Power Supply Requirements for Receiver Cards Power Supply Requirements for the PwrPak7 Power Supply Requirements for the CPT7 Power Supply Requirements for the SMART7 Power Supply Requirements for the SMART2
3	See Selecting a GNSS Antenna, Choosing a Coaxial Cable, Connecting the Antenna to the Receiver Card, Antenna LNA Power For SMART Antennas, contact Customer Support
4
5
6
7	Check the CPU idle time. Check for unnecessary logging. Check for simultaneous use of functionality.
8	See Table: Serial Ports Supported Also, check the Auxiliary 2 Status word to determine which COM port has overrun its buffer.
9-11	Reserved
15	Check the Auxiliary 1 status word to determine which RF channels are jammed.
16-17	Reserved
18	When the receiver has tracked GNSS satellites long enough for a valid almanac to be received, this bit will be set to 0.
19	None. This bit only indicates if the receiver has calculated a position.
20	None. This bit is a status bit indicating if the receiver’s position has been manually fixed and does not represent a problem. Refer also to the FIX command.
21	None. This bit indicates if clock steering has been manually disabled. Refer also to the FRESET command.
22	None. This bit only indicates if the clock model is valid. Refer also to the FRESET command.
23	None. This bit indicates if the phase-lock-loop is locked when using an external oscillator. Refer also to the FRESET command.
24	Check the CPU idle time. Check for unnecessary logging. Check for simultaneous use of functionality.
25-26	None. These bits identify the receiver family. For OEM7 receivers, bit 25 is set to 1 and bit 26 is set to zero.
27	Interference Toolkit HDR mode status. When this bit is set to 1, Interference Toolkit HDR mode is enabled.
28	Digital filter status. When this bit is set to 1, an Interference Toolkit digital filter is enabled.
29	None. This bit indicates if any bits in the auxiliary 3 status word are set. The auxiliary 3 word provides status information and does not contain any new information on problems. Refer also to the FRESET command.
30	None. This bit indicates if any bits in the auxiliary 2 status word are set. The auxiliary 2 word provides status information and does not contain any new information on problems. Refer also to the FRESET command.
31	None. This bit indicates if any bits in the auxiliary 1 status word are set. The auxiliary 1 word provides status information and does not contain any new information on problems. Refer also to the FRESET command.