68 Rockwell Automation Publication 1756-RM012B-EN-P - April 2018
Chapter 7 Monitor Status and Handle Faults
View Faults
The Recent Faults dialog box on the Major Faults tab of the Controller
Properties dialog box contains two subtabs, one for standard faults and one for
safety faults.
The status display on the controller also shows fault codes with a brief status
message. See more information on status indicators, see:
• ControlLogix 5580 and GuardLogix 5580 Controllers User Manual,
publication 1756-UM543
• CompactLogix 5380 and Compact GuardLogix 5380 User Manual,
publication 5069-UM001
Fault Codes
Table 4 shows the fault codes specific to GuardLogix 5580 and Compact
GuardLogix 5380 controllers. The type and code correspond to the type and
code that is displayed on the Major Faults tab of the Controller Properties
dialog box and in the PROGRAM object, MAJORFAULTRECORD (or
MINORFAULTRECORD) attribute.
The Logix5000 Controllers Major and Minor Faults Programming Manual,
publication 1756-PM014
, contains descriptions of the fault codes common to
Logix controllers.
Safety Partner Fault
The safety partner has an OK status indicator.
If the SIL configuration is set to SIL 2, and a Safety Partner is installed in the
slot next the Safety Primary, these actions occur:
• On the Safety Partner, the OK status indicator flashes red.
• The controller logs a Type 14, Code 12 minor fault that indicates that
the controller is configured for SIL 2, and a Safety Partner is present.
• The Studio 5000 Logix Designer application refuses to download a
SIL 2 application.
Table 4 - Major Safety Faults (Type 14)
Code Cause Status Corrective Action
01
Task watchdog expired. User task has not completed in a
specified period. A program error caused an infinite loop, the
program is too complex to execute as quickly as specified, or
higher priority or background tasks are keeping this task from
finishing.
Nonrecoverable Clear the fault.
If a safety task signature exists, safety memory is reinitialized and the safety
task begins executing.
If a safety task signature does not exist, you must redownload the program so
the safety task can run.
If the application allows, increase the watchdog time.
02 An error exists in a routine of the safety task. Recoverable Correct the error in the user-program logic.
07 Safety task is inoperable.
This fault occurs when the safety logic is invalid or not
present.
Nonrecoverable Clear the fault.
If a safety task signature exists, safety memory is reinitialized via the safety task
signature and the safety task begins executing.
If a safety task signature does not exist, you must download the program again
so the safety task can run.
To Next Page
Loading...
Need help?
General
