TM 5-6350-275-24&P
Table 3-2. Primary Monitor Console DS Maintenance Troubleshooting - Continued
MALFUNCTION
TEST OR INSPECTION
CORRECTIVE ACTION
3. PMC CPU DOES NOT COMMUNICATE WITH INDIVIDUAL, MULTIPLE, OR STRING OF RADCS
(RADCS STATION NUMBERS 1 THROUGH 8 COMMON TO SAME POLLER MUX) (FO-2)
Step 1. Determine number of RADC stations that are not communicating with PMC CPU by reviewing the alarm
queue at the operator workstation or reviewing the event printer printout.
Step 2. On communications rack, locate MUX Module(s) that communicate with RADCs station(s) showing failure.
Step 3. Verify that MUX Module(s), RTU LEDs RTS, TX, CD, RX, and GW are flashing on and off.
If all RTU LEDs are not flashing on and off, replace MUX Module(s). (Para. 3-26)
If RX and GW RTU LEDs are still not flashing on and off, replace Line Interface Unit (LIU) (Para. 3-31)
supporting MUX Module(s) that indicate bad communications between RADC(s) and communications cabinet
MUX Module.
If an individual, multiple, or string of RADCs are still not communicating with PMC CPU, (refer to Table 3-3, Step
1).
If an individual, multiple, or string of RADCs are still not communicating with PMC CPU, notify supervisor for
coordination for telephone line testing.
4. PMC CPU DOES NOT SWITCH RESPONSIBILITY TO RSM UPON FAILURE (Figure 3-1 and FO-3)
Step 1. Verify that the RSM processor assembly begins polling the RADCs.
If RSM does not assume responsibility for the PMC CPU, replace the Data Communications Auto/Manual Switch
If RSM still does not assume responsibility for the PMC CPU, verify the 9600 baud modem at the PMC displays
If RSM still does not assume responsibility for the PMC, verify the 9600 baud modem at the RSM displays the
If PMC to RSM link is equipped with DAS Modules, verify indicator lights depict equipment synchronization.
If RSM still does not accept responsibility for the PMC, notify supervisor for coordination for telephone line
testing.
3-6