Allen Bradley Kinetix 2000 Drive Fault Codes List
Complete guide to Allen Bradley Kinetix 2000 fault codes. Troubleshoot E-codes on IAM/AM modules, Sercos ring faults (E38), and Axis errors using Studio 5000.
Kinetix 2000 Fault Codes Reference Table
Below is the complete list of error codes. These codes flash on the 7-segment LED display of the specific IAM or AM module that is faulted. The display typically cycles through “E” followed by the 2-digit code (e.g., E…3…8).
Kinetix 2000 Fault Codes Reference Table
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| - Power (PWR) indicator not ON |
Cause: No AC power or auxiliary logic power, or internal power supply malfunction. Remedy:
|
| - Motor jumps when first enabled |
Cause: Motor wiring error, incorrect motor chosen, or digital I/O not working correctly (I/O power disconnected). Remedy:
|
| E00 BusUndervoltage Fault (Blown fuse) |
Cause: A blown fuse was detected on the inverter PCB. Remedy:
|
| E04 MotorOvertemp Fault |
Cause: Motor thermal switch tripped due to high ambient motor temperature, excessive current, motor wiring error, or incorrect motor selection. Remedy:
|
| E05 DriveOvercurrent Fault (Power Fault) |
Cause: Self-protection of the Intelligent Power Module (IPM) due to: - Motor cables shorted. - Motor winding shorted internally. - Drive temperature too high. - Operation above continuous power rating. - Short circuit/failed component. Remedy:
|
| E06 HardOvertravel Fault |
Cause: Axis moved beyond physical travel limits (positive/negative) or dedicated overtravel input is inactive. Remedy:
|
| E07 MotFeedbackFault (Motor Feedback Loss) |
Cause: The feedback wiring is open, shorted, or missing. Remedy:
|
| E09 BusUndervoltage Fault |
Cause: DC bus voltage is below its limit (below 137V for 230V system) or fell below limit while an axis on the follower power rail was enabled. Remedy:
|
| E10 DriveOvervoltage Fault |
Cause: The DC bus voltage is above its limit (over 410V for 230V system). Excessive regeneration of power. Remedy:
|
| E11 MotFeedbackFault (Illegal Hall State) |
Cause: State of Hall feedback inputs is incorrect due to bad connections. Remedy:
|
| E16 Softovertravel Fault |
Cause: Axis position exceeded maximum software setting. Remedy:
|
| E18 OverSpeedFault |
Cause: Motor speed has exceeded 150% of maximum rated speed. Remedy:
|
| E19 PositionErrorFault (Follow Error) |
Cause: Position error limit was exceeded. Remedy:
|
| E20 MotFeedbackFault (Mtr Fdbk AQB) |
Cause: Motor Encoder State Error; the motor encoder encountered an illegal transition. Remedy:
|
| E21 AuxFeedbackFault |
Cause: Communication was not established with an intelligent encoder. Remedy:
|
| E30 MotFeedbackFault |
Cause: Communication was not established with an intelligent encoder. Remedy:
|
| E34 GroundShortFault |
Cause: Excessive ground current detected due to: - Wiring error. - Motor internal ground short. - Internal malfunction. - Grounded control power terminal (230V systems). Remedy:
|
| E35 DriveUndervoltage Fault (Pre-charge Fault) |
Cause: Converter pre-charge cycle failed due to low AC input voltage or internal malfunction. Remedy:
|
| E36 DriveOvertemp Fault |
Cause: Converter thermal switch tripped; excessive heat exists in the power circuitry. Remedy:
|
| E37 PowerPhaseLoss Fault |
Cause: One or more phases of input AC power missing, or axis enabled when main power removed. Remedy:
|
| E38 SERCOSFault (Ring Flt) |
Cause: Cable disconnected; SERCOS ring not active after being active. Remedy:
|
| E39 DriveHardFault (Self Sense Flt) |
Cause: Self-sensing Commutation Startup Error; motion required was obstructed. Remedy:
|
| E43 DriveEnableInput Fault |
Cause: Missing Drive Enable Input Signal. Attempt to enable axis via software while hardware input was inactive, or input transitioned to inactive while enabled. Remedy:
|
| E50 SERCOSFault (Same ADDR) |
Cause: Duplicate node address detected on SERCOS ring. Remedy:
|
| E54 DriveHardFault (Ifbk HW Fault) |
Cause: Current feedback hardware fault detected. Remedy:
|
| E60 DriveHardFault (Unknown Axis) |
Cause: Illegal ID bits detected. Remedy:
|
| E61 AuxFeedbackFault (Aux Fdbk AQB) |
Cause: Auxiliary Encoder State Error; illegal transition encountered. Remedy:
|
| E62 AuxFeedbackFault (Aux Fdbk Loss) |
Cause: The feedback wiring is open, shorted, or missing. Remedy:
|
| E63 AuxFeedbackNoise |
Cause: Noise on auxiliary feedback cable. Recommended grounding instructions not followed. Remedy:
|
| E64 MotorFeedbackNoise |
Cause: Noise on motor feedback cable. Remedy:
|
| E65 No Fault Message (Hookup Fault) |
Cause: Hookup procedure failed due to motor or feedback device malfunction. Remedy:
|
| E66 No Fault Message (Atune Flt) |
Cause: Autotune procedure failed due to motor or feedback device malfunction. Remedy:
|
| E67 DriveHardFault (Task init) Operating system failed |
Cause: Software initialization fault detected due to hardware failure.
Remedy:
|
| E68 DriveHardFault (SCANport Comm) DPI communication failed |
Cause: The DPI device or cable is faulty.
Remedy:
|
| E69 DriveHardFault (Objects Init) Non-volatile memory is corrupt due to control board hardware failure. |
Cause: Control board hardware failure.
Remedy:
|
| E70 DriveHardFault (NV Mem Init) Non-volatile memory is corrupt due to control board software error. |
Cause: Control board software error.
Remedy:
|
| E71 DriveHardFault (Memory Init) RAM or Flash memory validation failure |
Cause: Validation failure during initialization.
Remedy:
|
| E72 DriveOvertemp Fault (Drive Overtemp) Inverter thermal switch tripped |
Cause:
Remedy:
|
| E73 Communicate (Backplane Comm) Power rail CAN communications failed |
Cause:
Remedy:
|
| E74 DriveOvercurrent Fault (Bus OverCurrent) DC link current exceeds rating |
Cause:
Remedy:
|
| E75 DriveOvervoltage Fault (Shunt Time Out) The IAM, AM, or SM has exceeded its shunt resistor continuous rating |
Cause: Exceeded shunt resistor continuous rating.
Remedy:
|
| E76 DriveHardFault (CAN Init) DPI hardware initialization fault detected |
Cause: Control board hardware failure.
Remedy:
|
| E78 DriveHardFault (SERCOS Init) Control hardware fault detected |
Cause: Control hardware fault detected.
Remedy:
|
| E79 DriveOvervoltage Fault (Shunt Module Flt) Shunt module fault |
Cause:
Remedy:
|
| E80 DriveHardFault (CPLD Flt) Control hardware fault detected |
Cause: Control hardware fault.
Remedy:
|
| E81 DriveHardFault (Common Bus Flt) Follower IAM detected ac input power being applied |
Cause: Follower IAM detected AC input power.
Remedy:
|
| E90 DriveHardFault (Pre-charge Timeout Flt) Pre-charge resistor power exceeds the resistor rating |
Cause: Pre-charge resistor power exceeds the resistor rating.
Remedy:
|
| All others RESERVED |
Cause: Unknown / Reserved error.
Remedy:
|
How to Read Kinetix 2000 Faults
Diagnostics on the Kinetix 2000 involve a combination of hardware inspection and software analysis. Here is the standard procedure for 2026:
- The 7-Segment Display: Each module (IAM and AM) has its own display.
- Status: A scrolling “4” indicates the drive is enabled and running. A flashing “0” indicates standby/stopped.
- Faults: A flashing “E” followed by numbers indicates a fault. If the IAM has the fault, the entire rail may stop. If an AM has the fault, only that axis (and potentially the IAM) will stop.
- Sercos Diagnostics (Studio 5000):
- Go to the Motion Group or the specific Axis in the controller organizer.
- Right-click the Axis and select Properties > Faults.
- If you see “Sercos Ring Fault,” check the 1756-MxxSE or 1768-M04SE module status to see which node (drive) broke the fiber optic ring.
- LED Status Indicators:
- COMM LED (Green/Red): Indicates the status of the Sercos fiber ring. Flashing red suggests a break or loose cable.
- BUS LED: Indicates the DC Bus status. Flashing Green is normal (Pre-charge); Solid Green is Bus Up.
Frequently Asked Questions (FAQ)
Q: How do I reset a Kinetix 2000 fault?
A: Most faults are reset via the PLC logic:
- Use the Motion Axis Fault Reset (MAFR) instruction in Studio 5000, targeting the specific axis.
- For “Hard Faults” (like E38 or E80), you may need to cycle the 24V Control Power to the IAM module.
- Note: Pressing buttons on the drive itself does not reset Sercos faults.
Q: What does “E38 Sercos Ring Fault” mean?
A: This is the most common communication error. It means the fiber optic light signal was lost.
- Check the Tx and Rx fiber cables for tight bends or breaks.
- Ensure the “Transmitter Power” (High/Low) switch on the drive matches the cable length (Set to “Low” for short patch cables in the cabinet).
- Verify the Node Address rotary switches match the configuration in the Logix project.
Q: Why is the drive showing “E90 Pre-charge Timeout”?
A: This indicates the DC Bus failed to charge up within the expected time.
- This often happens if you have too many Axis Modules (AM) connected to a single IAM, exceeding the capacitance limit.
- It can also indicate a failed internal resistor in the IAM module or a drop in the incoming AC voltage.
Comments
Post a Comment