Chapter 3, About troubleshooting – Rockwell Automation AADvance Controller Troubleshooting and Maintenance Manual User Manual

Page 23

Advertising
background image


Document: 553634
(ICSTT-RM406F_EN_P) Issue: 089:

3-1

Troubleshooting covers system faults, module and channel faults, termination assemblies and field fault.
The corrective troubleshooting and maintenance regime is founded on a series of automatic diagnostic
systems, fault warning through module status indicators (LEDs) or reported to the application through
the Workbench and a principle of repair by replacement. All modules are replaceable.

In a safety critical redundant configuration remove only one module at a time unless a system

shutdown is planned.

In This Chapter

Prerequisites for Troubleshooting ................................................................. 3-1
Recovery Mode and How it Affects Controller Operation ..................... 3-2
Internal Diagnostics ................................
............................................................ 3-2
Actions of the Diagnostic Systems ................................................................. 3-3
Latching and Non-Latching Faults ................................
................................... 3-3
Common Fault Alarm ........................................................................................ 3-4
Fault Indications ................................
.................................................................. 3-4
Fault Reporting Reference Information ......................................................... 3-8
Understanding the State Variable (<tagname>.STA) ............................... 3-15
View Module Firmware Versions .................................................................. 3-17

Prerequisites for Troubleshooting

The troubleshooting procedures described in this manual make the premise that the System
Healthy
alarm is connected to a variable in the AADvance Workbench and the alarm can be used as a
starting point for activities or, the processor module has defaulted to the Recovery Mode because of a
critical firmware failure.

The fault finding procedures make the following assumptions:

Chapter 3

About Troubleshooting

Advertising