User`s guide

Interpreting Screen Displays
4–12 MS-4900, Rev. A
Examining
System
Messages
You can examine system messages to get an indication of receiver activity over a
span of time. The IDR V1000 stores up to three user messages and three system
messages in memory, each of which reflects an event in the receiver’s operation. For
example, the initial system message when the receiver is first powered on indicates it
is not locked to a carrier. As soon as the receiver acquires a lock on the carrier, the
system stores that message. Each message is time-stamped, based on the time set in
the Set Features/Local Time screen.
User messages are rare occurrences. They are sent by the network operator to
individual receivers. New messages replace the earliest ones if the message buffer is
full.
You can scroll through the messages using the arrow buttons. Pressing SELECT on
a displayed message deletes it. Pressing CANCEL returns you to the previous screen
level.
Error and
Warning
Messages
The following table lists messages that could indicate a hardware problem within the
IDR V1000. If you see any of these messages:
1. Make a note of the message
2. Disconnect the IDR V1000 power, then re-connect it to clear and reset the
receiver.
3. Contact support personnel if the same message reoccurs.
NOTE: The first message you always see when IDR V1000 power is turned on is
“Self-Test in Progress.” You should not see this message at any other time
during normal operation.
Table 4-9. Error Messages
Message: Means:
Code ROM Check
should be 38 was C8
Error occurred reading program memory during self-test
RAM Memory Check @xxxxx
should be 00 was 20
Error occurred while writing a data pattern in RAM during
self-test
RAM Address Check @xxxxx
should be FE was FB
Error occurred writing address in RAM during self-test
Interrupt check Error causing spurious interrupts
Input Queue Overflow Input to the IDR V1000 cannot be processed fast enough
to keep up with data received
EEPROM Check X
Call Technical Support
EEPROM Check X
Attempting S/N Recovery Failure in non-volatile memory.
Configuration Reset X
EEPROM Check X
Return for Service
Failed TDD RAM Failure in time-division demultiplexer RAM