6-3
RF-5800H 150-WATT COMMUNICATION SYSTEM
TROUBLESHOOTING
Perform the following procedure to power up the RF-5800H 150-Watt Communication System and execute BIT:
a. If the system is vehicular skip this step and proceed directly to Step b On the RF-5051PS, check to
ensure that the power switch is set to the ON position.
b. ?On the RF-5833H-PA, check to ensure that switch CB1 is set to the ON (up) position.
c. Rotate the function switch to the Plain Text (PT) position. If the RF-5800H-MP does not power-up,
verify that the power source is on. If necessary proceed to Paragraph 6.2.3, Non-BIT Fault
Troubleshooting.
d. Press the OPT button.
e. If necessary, press the left/right arrow buttons to select the TEST field.
NOTE
While in TEST mode, the radio cannot receive or transmit.
f. Press the ENT button.
g. If necessary, press the left/right arrow buttons to select the ALL field.
h. Press the ENT button.
If the RF-5800H-MP displays a fault code on the Liquid Crystal Display (LCD) after completing the
BIT test, record the fault code and proceed to Paragraph 6.2.4, BIT Troubleshooting.
If the RF-5800H-MP displays no error message, try to operate the RF-5800H 150-Watt Communication
System in an attempt to generate a run-time fault. If a run-time fault is generated, refer to the non-BIT
troubleshooting procedures in Paragraph 6.2.3.
If a run-time fault cannot be generated and the RF-5800H 150-Watt Communication System is still not
operating properly, refer to the non-BIT troubleshooting procedures in Paragraph 6.2.3.
6.2.3 Non-BIT Troubleshooting
Table 6-1 is a list of the non-BIT fault symptoms. Next to the symptom is a reference to the recommended action
that should be taken. Perform the recommended actions one at a time in the order listed, testing the system after each
action is performed. Paragraph 2.5 provides the LRU removal and installation procedures. When the action column
refers to a TAP, proceed to the specified TAP in Paragraph 6.2.5.
If the actions do not correct the problem, proceed to the troubleshooting index in Paragraph 6.3.2.