Table of Contents
Chapter 5
Troubleshoot the iTRAK 5730 System
114
Fault Code Overview
The fault code tables are designed to help you determine the source of the fault
or exception. When a fault condition is detected, the motor section or mover
performs the appropriate fault action and the fault is added to a persistent
fault log (along with diagnostics data). If a fault condition is still active
following a Fault Reset service, the fault is again written to the fault log.
However, there can be a delay before the fault is posted again. In a Studio 5000
Logix Designer® application, this delay results as the AxisFault tag on the axis
being cleared until the fault is posted again. During this delay, the AxisState
tag continues to indicate that the axis is faulted. Use the AxisState tag on the
axis object only to determine if an axis is faulted.
Although software overtravel fault codes do not exist, software overtravel
detection for the AXIS_CIP_DRIVE axis type is determined in the Logix 5000™
controller. For more information, see Integrated Motion on the EtherNet/IP™
Network Reference Manual, publication MOTION-RM003.
The iTRAK 5730 maintains a fault log of the last 128 faults. The fault log
includes time stamps and is stored in persistent memory. However, the fault
log cannot be cleared on the module.
Table 15 - Fault Code Summary
(1) (2)
Fault Code Type
FLT Sxx
FLT Mxx
INIT FLT Sxx
INIT FLT Mxx
NODE FLTxx
NODE ALARM xx
INHIBIT Sxx
INHIBIT Mxx
ALARM Sxx
ALARM Mxx
SAFE FLTxx
(1) Sxx refers to Standard exceptions.
(2) Mxx refers to Manufacturer-specific exceptions.
Fault codes triggered by conditions that fall outside factory set limits are identified by FL
at the end of the display message. For example, FLT S07 – MTR OVERLOAD FL.
Fault codes triggered by conditions that fall outside user set limits are identified by UL at
the end of the display message. For example, FLT S08 – MTR OVERLOAD UL.
Rockwell Automation Publication 2198T-UM003A-EN-P - May 2020
Description
Standard runtime axis exceptions. The exception can apply to an individual axis or to all
axes.
Manufacturer-specific runtime axis exception. The exception can apply to an individual
axis or to all axes.
Exceptions that prevent normal operation and occur during the initialization process.
Exceptions that can prevent normal operation and apply to the entire module and affect
all axes.
Exceptions that can prevent normal operation, but do not result in any action other than
reporting the alarm to the controller.
Conditions that prevent normal operation and indicate the axis is prevented from being
enabled.
An underlying exception condition that does not result in any action other than reporting
the alarm to the controller.
Exception generated by a fault condition detected in the safety function.
Table of Contents
