Rockwell Automation Logix5000 Controllers Major, Minor, and I/O Faults Programming Manual User Manual
Page 33
Major faults Chapter 1
Type
Code
Cause
Recovery Method
14
6
Safety partner firmware is incompatible.
Update the safety partner so that the firmware major and minor revision matches the
primary controller.
14
7
Safety task is inoperable.
This fault occurs when the safety logic is invalid. For example, a
mismatch in logix exists between the primary controller and
safety partner, a watchdog timeout occurred, or memory is
corrupt.
•
Clear the fault.
•
If a safety task signature exists, safety memory is re-initialized 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 to
allow the safety task to run.
14
8
Coordinated system time (CST) not found.
Clear the fault. Configure a device to be the CST master.
14
9
Safety partner nonrecoverable controller fault.
Clear the fault and download the program. If the fault persists, replace the safety
partner.
18
1
The CIP Motion drive has not initialized correctly.
To determine corrective action, see the CIP Initialization attribute for details about the
type of fault that occurred.
For more information about the CIP Initialization attribute, see th
ublicatio
18
2
The CIP Motion drive has not initialized correctly.
This fault is indicated when a manufacturer-specific
initialization fault has occurred.
To determine the corrective action, see the CIP Initialization Fault - Mfg attributes for
details about the fault that occurred.
For more information about the CIP Initialization Fault - Mfg attribute, see the
publicatio
18
3
The Physical Axis Fault bit is set, indicating a fault on the
physical axis.
To determine corrective action, see the CIP Axis Fault attributes for details about the
fault that occurred.
For more information about the CIP Axis Fault attributes, see the Integrated Motion on
t
ublicatio
18
4
The Physical Axis Fault bit is set, indicating a fault on the
physical axis.
This fault is indicated when a manufacturer-specific axis fault
has occurred.
To determine corrective action, see the CIP Axis Fault - Mfg attributes for details about
the fault that occurred.
For more information about the CIP Axis Fault -Mfg attributes, see th
publication
18
5
A motion fault occurred.
To determine corrective action, see the Motion Fault attribute and Motion Fault bits for
details about the fault that occurred.
For more information about the Motion Fault attribute and Motion Fault bits, see the
publicatio
18
6
A CIP Motion Drive fault has occurred.
Usually the fault affects all the axes associated with the
module and all of the associated axes are shut down.
Reconfigure the faulted motion module to correct the fault.
For more information about the Module Fault attribute and Module Fault bits, see the
publicatio
18
7
A motion group fault has occurred.
Usually the fault affects all of the axes associated with a motion
group.
Reconfigure the entire motion subsystem to correct the fault.
See the Group Fault attribute if details about the fault are needed.
18
8
A fault has occurred during the configuration of a CIP Motion
Drive.
Typically, this fault occurs after an attempt to update an axis
configuration attribute of a CIP Motion Drive was unsuccessful.
To determine the corrective action, see the Configuration Fault in the Attribute Error
Code and Attribute Error ID attributes associated with the motion or 1756-ENxT module.
Rockwell Automation Publication 1756-PM014G-EN-P – October 2014
33