Rockwell Automation Logix5000 Controllers Major, Minor, and I/O Faults Programming Manual - Manual (Page 32)

Chapter 1 Major faults
Type Code Cause Recovery Method
11 7 Synchronous connection incurred a failure. Try these steps:
•
First, run Motion Axis Fault Reset.
• If that does not work, pull the servo module out and plug it back in.
• If this does not work, replace the servo module.
11 8 Servo module has detected a serious hardware fault. Replace the module.
11 9 Configuration fault has occurred.
The motion module or drive rejected the update of one of the
axis attributes. See the AttributeErrorCode or AttributeErrorID axis tags to identify which attribute was
rejected and why.
11 10 Motor fault has occurred. See the DriveFaults axis tag for more information.
11 11 Motor thermal fault has occurred. See the DriveFaults axis tag for more information.
11 12 Drive thermal fault has occurred. See the DriveFaults axis tag for more information.
11 13 SERCOS ring fault has occurred. Verify the integrity of the SERCOS fiber-optic ring network and the devices on it.
11 14 Drive enable input fault has occurred. Re-enable the drive enable input and clear the fault.
11 15 Drive phase loss fault has occurred. Restore full power connection to the drive and clear the fault.
11 16 Drive guard fault has occurred. See the GuardFaults axis tag for more information.
11 32 The motion task has experienced an overlap. The group’s course update rate is too high to maintain correct operation. Clear the group
fault tag, raise the group’s update rate, and then clear the major fault.
12 32 A disqualified secondary controller cycled power and no
partner chassis or controller was found upon powerup. Verify the following items.
•
A partner chassis is connected.
• Power is applied to both redundant chassis.
• Partner controllers have the same:
− Catalog number
− Slot number
− Firmware revision
12 33 An unpartnered controller has been identified in the new
primary chassis after a switchover.
Either:
•
Remove the unpartnered controller and troubleshoot the cause of the switch over.
• Add a partner controller to the secondary chassis, troubleshoot the cause of the
switch over, and synchronize the system.
12 34 Just after a switchover occurs, the keyswitch positions of the
primary and secondary controllers are mismatched.
The old primary controller is in Program mode and the new
primary controller is in Run mode.
Either:
•
Change the keyswitches from Run to Program to Run mode twice to clear the fault.
• Use the Logix Designer application to go online with the controllers. Then clear the
faults and change the mode on both controllers to Run.
14 1 Safety 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 run
as quickly as specified, a higher priority task is keeping this task
from finishing, or the safety partner has been removed. • Clear the fault.
• If a safety task signature exists, safety memory is re-initialized and the safety task
begins executing.
• If a safety task signature does not exist, you must re-download the program to allow
the safety task to run.
• Reinsert the safety partner, if it was removed.
14 2 An error exists in a routine of the safety task. Correct the error in the user-program logic.
14 3 Safety partner is missing. Install a compatible safety partner.
14 4 Safety partner is unavailable. Install a compatible safety partner.
14 5 Safety partner hardware is incompatible. Install a compatible safety partner.
32 Rockwell Automation Publication 1756-PM014G-EN-P – October 2014