Allen Bradley Kinetix 5700 Servo Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| FLT S02 – MTR COMMUTATION Motor Commutation Fault | Cause: An illegal state transition of the motor hall-commutation feedback signals has been detected. Remedy:
|
| FLT S03 – MTR OVERSPEED FL – 0 Motor Overspeed Factory Limit Fault | Cause: Motor speed has exceeded 125% of its maximum speed. Remedy:
|
| FLT S03 – MTR OVERSPEED FL – 1 Motor Overspeed Factory Limit Fault | Cause: The output frequency has exceeded 590 Hz. Remedy:
|
| FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault | Cause: Motor speed has exceeded motor overspeed user limit. Remedy:
|
| FLT S05 – MTR OVERTEMP FL nn Motor Overtemperature Factory Limit Fault | Cause: Calculations based on the motor thermistor indicate that the motor factory temperature limit has been exceeded. Sub-code (nn): 01: Motor Thermostat or Thermistor 02: Encoder Temperature Sensor Remedy:
|
| FLT S07 – MTR OVERLOAD FL Motor Thermal Overload Factory Limit Fault | Cause: The motor thermal model has exceeded its factory set thermal capacity limit. Remedy:
|
| FLT S08 – MTR OVERLOAD UL Motor Thermal Overload User Limit Fault | Cause: The motor thermal model has exceeded the thermal capacity limit given by Motor Thermal Overload User Limit. Remedy:
|
| FLT S09 – MTR PHASE LOSS Motor Phase Loss | Cause: Torque Prove function detected motor current below a limit set by Torque Prove Current Limit. Remedy:
|
| FLT S10 – INV OVERCURRENT Inverter Overcurrent Fault | Cause: Inverter current has exceeded the instantaneous current limit (determined by hardware). Remedy:
|
| FLT S11 – INV OVERTEMP FL Inverter Overtemperature Factory Limit Fault | Cause: The measured inverter temperature has exceeded the factory set temperature limit. Remedy:
|
| FLT S13 – INV OVERLOAD FL Inverter Thermal Overload Factory Limit Fault | Cause: The thermal capacity of the inverter has exceeded the factory set limit. Remedy:
|
| FLT S14 – INV OVERLOAD UL Inverter Thermal Overload User Limit Fault | Cause: The thermal capacity of the inverter has exceeded the user set limit given by the inverter Thermal Overload User Limit. Remedy:
|
| FLT S15 – CONV OVERCURRENT Converter Overcurrent Fault | Cause: The measured converter current has exceeded the factory set current limit. Remedy:
|
| FLT S16 – GROUND CURRENT Ground Current Factory Limit Fault | Cause: The sensing circuitry in the power stage has detected excessive ground current. Remedy:
|
| FLT S18 – CONV OVERTEMP FL Converter OverTemp Factory Limit Fault | Cause: The measured converter temperature has exceeded the factory set temperature limit. Remedy:
|
| FLT S20 – CONV OVERLOAD FL Converter Thermal Overload Factory Limit Fault | Cause: The converter thermal model indicates that the temperature has exceeded the factory set capacity rating of 110%. Remedy:
|
| FLT S21 – CONV OVERLOAD UL Converter Thermal Overload User Limit Fault | Cause: The converter thermal model indicates that the temperature has exceeded the limit given by the Converter Thermal Overload User Limit. Remedy:
|
| FLT S22 – AC POWER LOSS AC Power Loss Fault | Cause: All three AC input phases are detected as absent when any one of the inverters connected to a converter is in the enabled state. Remedy:
|
| FLT S23 – AC PHASE LOSS AC Single Phase Loss Fault | Cause: A single AC input phase was lost. Remedy:
|
| FLT S25 – CONV PRECHARGE FAILURE Precharge Failure Fault | Cause: The pre-charge circuit monitoring algorithm detected that the DC bus did not reach a factory set voltage level after charging for a period of time. Remedy:
|
| FLT S27 – BUS REG OVERTEMP FL Bus Regulator Overtemperature Factory Limit Fault | Cause: The digital input assigned to the shunt thermal switch OK is asserted LOW. Remedy:
|
| FLT S29 – BUS REG OVERLOAD FL Bus Regulator Thermal Overload Factory Limit Fault | Cause: The shunt thermal model has exceeded its factory set thermal capacity limit. Remedy:
|
| FLT S30 – BUS REG OVERLOAD UL Bus Regulator Thermal Overload User Limit Fault | Cause: The shunt thermal model has exceeded the thermal capacity limit given by Bus Regulator Thermal Overload User Limit. Remedy:
|
| FLT S31 – BUS REG FAILURE Bus Regulator Failure | Cause: The shunt circuit has detected that the shunt resistor is shorted. Remedy:
|
| FLT S32 – BUS CAPACITOR MODULE FAILURE Bus Capacitor Module Failure | Cause: The digital input assigned to capacitor module OK is asserted LOW. Remedy:
|
| FLT S33 – BUS UNDERVOLT FL Bus Undervoltage Factory Limit Fault | Cause: DC Bus voltage level is below the factory set limit. Remedy:
|
| FLT S34 – BUS UNDERVOLT UL Bus Undervoltage User Limit Fault | Cause: DC Bus voltage level is below the user set limit as given by Bus Undervoltage User Limit. For iTRAK power supply, this refers to the output (IDC) power busses. Remedy:
|
| FLT S35 – BUS OVERVOLT FL Bus Overvoltage Factory Limit Fault | Cause: DC Bus voltage level is above the factory set limit. For iTRAK power supply, this refers to the input or output iTRAK power busses. Remedy:
|
| FLT S37 – BUS POWER LOSS Bus Power Loss Fault | Cause: The DC-bus voltage level is below the bus power loss threshold for more than 50 ms. Remedy:
|
| FLT S38 – FUSE BLOWN nn Bus Power Fuse Blown Fault | Cause: The internal DC-bus power fuse is blown. Sub-code (nn): 00: Non user-replaceable fuse 01: User replaceable fuse (iTRAK power supply only) Remedy:
|
| FLT S40 – BUS POWER SHARING FAULT Bus Power Sharing Fault | Cause: A power supply or RPS sharing DC-bus power with this module (power supply or drive) has requested that this module stop consuming power from the DC-bus. Remedy:
|
| FLT S41 – MTR AQB STATE FL Feedback Signal Noise FL | Cause: The number of illegal state transitions of the motor AQB encoder feedback signals has exceeded a factory limit. Remedy:
|
| FLT S43 – FDBK LOSS FL Feedback Signal Loss FL | Cause: The detected voltage levels of the A/B channel signals from the feedback device are below the Feedback Signal Loss factory limit. Remedy:
|
| FLT S44 – FDBK LOSS UL Feedback Signal Loss UL | Cause: The associated fault/alarm sub-code indicates which of the supported feedback channels is reporting this fault/alarm. Remedy:
|
| FLT S45 – FDBK COMM FL Motor Feedback Data Loss Factory Limit Fault | Cause: The number of consecutive missed or corrupted serial data packets, or invalid position feedback values from the intelligent feedback device has exceeded a factory set limit. Remedy:
|
| FLT S46 – FDBK COMM UL Motor Feedback Data Loss User Limit Fault | Cause: The number of consecutive missed or corrupted serial data packets from the intelligent feedback device has exceeded a user set limit. Remedy:
|
| FLT S47 – FDBK DEVICE FAILURE nn Motor Feedback Device Failure Fault (DSL or Hiperface feedback) | Cause: The feedback device has detected an internal error (DSL or Hiperface). (Refer to manual for specific nn sub-code definitions including Acceleration Overflow, Tracking Filter Error, Counter Error, Sync Error, etc.) Remedy:
|
| FLT S49 – BRAKE SLIP FLT Brake Slip Exception | Cause: Motor displacement exceeded the brake slip tolerance while the mechanical brake was engaged. Remedy:
|
| FLT S50 – POS HW OTRAVEL Hardware Overtravel – Positive | Cause: The axis has moved beyond the digital input travel limit in the positive direction. Remedy:
|
| FLT S51 – NEG HW OTRAVEL Hardware Overtravel – Negative | Cause: The axis has moved beyond the digital input travel limit in the negative direction. Remedy:
|
| FLT S54 – POSN ERROR Excessive Position Error Fault | Cause: The position error of the position control loop has exceeded the value given by Position Error Tolerance for a time period given by Position Error Tolerance Time. Remedy:
|
| FLT S55 – VEL ERROR Excessive Velocity Error Fault | Cause: The velocity error of the velocity control loop has exceeded the value given by Velocity Error Tolerance for a time period given by Velocity Error Tolerance Time. Remedy:
|
| FLT S56 – OVERTORQUE LIMIT Overtorque Limit Fault | Cause: Motor torque has risen above user defined maximum torque level given by Overtorque Limit for a time period given by Overtorque Limit Time. Remedy:
|
| FLT S57 – UNDERTORQUE LIMIT Undertorque Limit Fault | Cause: Motor torque has dropped below user defined minimum torque level given by Undertorque Limit for a time period given by Undertorque Limit Time. Remedy:
|
| FLT S61 – ENABLE INPUT Enable Input Deactivated | Cause: The hardware enable input was deactivated while the drive was enabled. Remedy:
|
| FLT M02 – MOTOR VOLTAGE Motor Voltage Mismatch Fault | Cause: The configured voltage of the drive is greater than the motor rated voltage. For example, a 400V-class drive with a 200V-class motor. Remedy: Set the drive voltage to a lower value or replace motor with voltage rating that matches the drive. |
| FLT M07 – FEEDBACK INCREMENTAL COUNT ERROR FAULT Feedback Incremental Count Error | Cause: The periodic check of the incremental encoder position against the absolute encoder position or Hall edges (when available) indicates they are out of tolerance. Remedy: Verify the motor feedback wiring is correct and not open/shorted/missing, use shielded cables, route feedback away from potential noise sources, check system grounds, replace motor/encoder. |
| FLT M12 – POWER CYCLE FL Converter Precharge Overload Factory Limit Fault | Cause: The thermal model for the precharge resistor detected that precharge capacity exceeded the factory limit. Remedy:
|
| FLT M26 – RUNTIME ERROR Runtime Error | Cause: The drive firmware encountered an unrecoverable runtime error. Remedy:
|
| FLT M28 – SAFETY COMM Safety Module Communication Error | Cause: Communication with the safety hardware within the drive has failed. Remedy:
|
| INIT FLT M01 – ENCODER DATA Smart Encoder Data Corruption | Cause: The data stored in the encoder has a checksum error. Remedy:
|
| INIT FLT M02 – MTR DATA RANGE nn Motor Data Range Error | Cause: A motor data attribute stored in the encoder is out of range (See sub-codes 01-16 in manual). Remedy:
|
| INIT FLT M03 – MTR ENC STARTUP Motor Feedback Communication Startup | Cause: Communication with the encoder could not be established. Remedy:
|
| INIT FLT M06 – MOTOR ABSOLUTE STARTUP SPEED Feedback Absolute Startup Speed | Cause: The absolute encoder was not able to accurately determine the position after powerup due to speed greater than 100 rpm. Remedy: Make sure the motor shaft is not moving during power-up. |
| INIT FLT M14 – SAFETY FIRMWARE Invalid Safety Firmware | Cause: The loaded Safety firmware is not compatible with the drive firmware. Remedy:
|
| INIT FLT M20 – UNKNOWN MODULE Unknown Module Fault | Cause: The product code of the power board is invalid. Remedy:
|
| INIT FLT M21 – FACTORY CONFIG Factory Configuration Error | Cause: Factory configuration data is missing or invalid. Remedy:
|
| INHIBIT S01 – ENABLE INPUT Axis Enable Input Fault – Start Inhibit | Cause: When Enable Input Checking is enabled, the drive displays Axis Enable Input start inhibit when it detects the enable input is inactive and while the axis is in Starting/Running/Testing/Hold sub-state of Stopped state. Remedy:
|
| INHIBIT S02 – MOTOR NOT CONFIG Motor Not Configured | Cause: The associated motor has not been properly configured for use. Remedy: Verify motor configuration in the Logix Designer application. |
| INHIBIT S03 – FEEDBACK NOT CONFIGURED Feedback Not Configured | Cause: The feedback has not been properly configured for use. Remedy: Verify feedback configuration in the Logix Designer application. |
| INHIBIT S04 – COMMUTATION NOT CONFIGURED Commutation Not Configured – Standard Start Inhibit | Cause: Associated permanent magnet motor commutation has not been configured for use. Remedy: Verify that the proper motor feedback commutation alignment has been selected. |
| INHIBIT M02 – MOTOR FEEDBACK REQURIED Motor Feedback Required | Cause: Selected Motor Control mode cannot run without a valid feedback selection. Remedy: Verify that the proper motor feedback type has been selected. |
| INHIBIT M04 – PROVING CONFIG Torque Prove Configuration – Mfg Specific Start Inhibit | Cause: When Torque Proving configuration is enabled, control mode, feedback mode, motor feedback type, and motor option configuration must be set properly. Remedy:
|
| INHIBIT M05 – SAFE TORQUE OFF Start Inhibit – Safe Torque Off | Cause: The safety function has disabled the power structure. Remedy:
|
| NODE FLT 01 – LATE CTRL UPDATE Control Connection Update Fault | Cause: Several consecutive updates from the controller have been lost. Remedy:
|
| NODE FLT 02 – PROC WATCHDOG nn Processor Watchdog Fault | Cause: The processor on the power board or control board failed to update in a certain amount of time. Remedy:
|
| NODE FLT 03 – HARDWARE 00 Hardware Fault -PwrIF | Cause: Communication with the power board could not be established. Remedy:
|
| NODE FLT 03 – HARDWARE 02 Hardware Fault – DSL | Cause: Communication with the encoder could not be established. Remedy:
|
| NODE FLT 03 – HARDWARE 03 DSL Internal Hardware Fault | Cause: A DSL hardware error internal to the drive was detected. Remedy:
|
| NODE FLT 03 – HARDWARE 04 Hardware Fault – Board Compatibility | Cause: The control and power boards are incompatible. Remedy: Return drive for repair if fault continues. |
| NODE FLT 05 – CLOCK SKEW FLT Clock Skew Fault | Cause: The controller time and the drive’s system time are not the same. Remedy:
|
| NODE FLT 06 – LOST CTRL CONN Lost Controller Connection Fault | Cause: Communication with the controller has been lost. Remedy:
|
| NODE FLT 07 – CLOCK SYNC Clock Sync Fault | Cause: Drive’s local clock has lost synchronization with controller’s clock and was not able to resynchronize within allotted time. Remedy:
|
| NODE FLT 09 – DUPLICATE IP ADDRESS Duplicate IP Address Fault | Cause: Several consecutive updates from the controller have been lost (or IP conflict detected). Remedy: Select an IP address not already in use on the network. |
| NODE ALARM 01 – LATE CTRL UPDATE Control Connection Update Alarm | Cause: Updates from the controller have been late. Remedy:
|
| NODE ALARM 03 – CLOCK JITTER Clock Jitter Alarm | Cause: The sync variance has exceeded the sync threshold while the device is running in sync mode. Remedy:
|
| NODE ALARM 04 – CLOCK SKEW ALARM Clock Skew Alarm | Cause: The controller time and the drive’s time are not the same. Remedy:
|
| NODE ALARM 05 – CLOCK SYNC ALARM Clock Sync Alarm | Cause: Drive’s local clock has lost synchronization with controller’s clock for a short time during synchronous operation. Remedy:
|