Technical data

4–4 Troubleshooting
Troubleshooting Checklist
The following checklist provides a general procedure for diagnosing the controller
and its supporting modules. If you follow this checklist, you’ll be able to identify
many of the problems that occur in a typical installation. When you’ve identified the
problem, use Table 4–1 to confirm your diagnosis and fix the problem.
If your initial diagnosis points to several possible causes, use the tools described later
in this chapter to further refine your diagnosis. If the problem can’t be diagnosed
using the checklist and tools, call customer service for additional support.
To troubleshoot the controller and its supporting modules:
1. Check the power to the cabinet and its components. Are the cords properly
connected? Is the power within specifications?
2. Check the component cables. Are the bus cables to the controllers connected
properly? Are the ECB cables properly connected?
3. Check the program cards to ensure they’re fully seated.
4. Check the operator control panel and devices for LED codes. See “Flashing OCP
Pattern Display Reporting,” page 4-25, and “Solid OCP Pattern Display
Reporting,” page 4-27, to interpret the LED codes.
5. Connect a local terminal to the controller and check its configuration with the
following command:
SHOW THIS_CONTROLLER FULL
Ensure that the ACS version is correct and that pertinent patches have been
installed. Also, check the status of the cache module and its ECB.
In a dual redundant configuration, check the other controller with the following
command:
SHOW OTHER_CONTROLLER FULL
6. Using FMU, check for last failure or memory-system failure entries. Show these
codes and translate the last failure codes they contain. “Significant Event
Reporting,” page 4-24.