Specifications

Troubleshooting Resources 4–21
Solid OCP Pattern Display Reporting
Certain events cause a solid display of the OCP LEDs. The event and its resulting patterns
are described in Table 4–5.
Information related to the solid OCP patterns is automatically displayed on the
maintenance terminal (unless disabled via the FMU) using %FLL formatting, as detailed
in the following examples:
■●●●●●●
3F An invalid process ran during
initialization.
Replace controller.
Table 4–4 Flashing OCP Patterns (Continued)
Pattern OCP
Code
Error Repair Action
%FLL--HSG> --13-JAN-1999 04:39:45 (time not set)-- OCP Code: 38
Controller operation terminated.
%FLL--HSG> --13-JAN-1999 04:32:26 (time not set)-- OCP Code: 26
Memory module is missing.
Table 4–5 Solid OCP Patterns (Sheet 1 of 5)
Pattern OCP
Code
Error Repair Action
■❍❍❍❍❍❍
0 No program card detected or kill asserted
by other controller.
Controller unable to read program card.
Make sure that the program card is
properly seated while resetting the
controller. If the error persists, try the
card with another controller; or replace
the card. Otherwise, replace the
controller that reported the error.
❏❍❍❍❍❍❍
0 Catastrophic controller or power failure. Check power. If good, reset controller. If
problem persists, reseat controller
module and reset controller. If problem is
still evident, replace controller module.