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

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:
  • Verify AC control power is applied to the Kinetix 2000 system.
  • Call your Rockwell Automation sales representative to return module for repair.
-

Motor jumps when first enabled
Cause:
Motor wiring error, incorrect motor chosen, or digital I/O not working correctly (I/O power disconnected).

Remedy:
  • Check motor wiring.
  • Run Hookup test in RSLogix 5000 software.
  • Verify the proper motor is selected.
  • Verify connections and I/O power source.
E00

BusUndervoltage Fault
(Blown fuse)
Cause:
A blown fuse was detected on the inverter PCB.

Remedy:
  • Call your Rockwell Automation sales representative to return module for repair.
E04

MotorOvertemp Fault
Cause:
Motor thermal switch tripped due to high ambient motor temperature, excessive current, motor wiring error, or incorrect motor selection.

Remedy:
  • Operate within (not above) the continuous torque rating for the ambient temperature 40 °C (104 °F) maximum.
  • Lower ambient temperature, increase motor cooling.
  • Check motor wiring at MF connector on the IAM/AM.
  • Verify the proper motor has been selected.
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:
  • Verify continuity of motor power cable and connector.
  • Disconnect motor power cables; if motor is difficult to turn by hand, replace it.
  • Check for clogged vents or defective fan. Ensure cooling is not restricted.
  • Verify ambient temperature is not too high.
  • Operate within continuous power rating and reduce acceleration rates.
  • Remove all power/motor connections and perform continuity check on DC bus to U, V, W outputs.
E06

HardOvertravel Fault
Cause:
Axis moved beyond physical travel limits (positive/negative) or dedicated overtravel input is inactive.

Remedy:
  • Check wiring.
  • Verify motion profile.
  • Verify axis configuration in software.
E07

MotFeedbackFault
(Motor Feedback Loss)
Cause:
The feedback wiring is open, shorted, or missing.

Remedy:
  • Check motor encoder wiring.
  • Run Hookup test in RSLogix 5000 software.
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:
  • Verify voltage level of the incoming AC power.
  • Check AC power source for glitches or line drop.
  • Install an uninterruptible power supply (UPS) on your AC input.
  • Disable follower axis before removing power.
E10

DriveOvervoltage Fault
Cause:
The DC bus voltage is above its limit (over 410V for 230V system). Excessive regeneration of power.

Remedy:
  • Change the deceleration or motion profile.
  • Use a larger system (motor and Kinetix 2000 drive).
  • Install shunt module.
  • Verify input is within specifications.
E11

MotFeedbackFault
(Illegal Hall State)
Cause:
State of Hall feedback inputs is incorrect due to bad connections.

Remedy:
  • Verify the Hall wiring at the MF connector on the IAM/AM.
  • Verify 5V power supply to the encoder.
E16

Softovertravel Fault
Cause:
Axis position exceeded maximum software setting.

Remedy:
  • Verify motion profile.
  • Verify overtravel settings are appropriate.
E18

OverSpeedFault
Cause:
Motor speed has exceeded 150% of maximum rated speed.

Remedy:
  • Check cables for noise.
  • Check tuning.
E19

PositionErrorFault
(Follow Error)
Cause:
Position error limit was exceeded.

Remedy:
  • Increase the feed forward gain.
  • Increase following error limit or time.
  • Check position loop tuning.
  • Verify sizing of system.
  • Verify mechanical integrity of system within specification limits.
E20

MotFeedbackFault
(Mtr Fdbk AQB)
Cause:
Motor Encoder State Error; the motor encoder encountered an illegal transition.

Remedy:
  • Use shielded cables with twisted pair wires.
  • Route the feedback away from potential noise sources.
  • Check the system grounds.
  • Replace the motor/encoder.
E21

AuxFeedbackFault
Cause:
Communication was not established with an intelligent encoder.

Remedy:
  • Verify auxiliary encoder wiring.
E30

MotFeedbackFault
Cause:
Communication was not established with an intelligent encoder.

Remedy:
  • Verify motor selection.
  • Verify the motor supports automatic identification.
  • Verify motor encoder wiring.
E34

GroundShortFault
Cause:
Excessive ground current detected due to:
- Wiring error.
- Motor internal ground short.
- Internal malfunction.
- Grounded control power terminal (230V systems).

Remedy:
  • Check motor and input power wiring.
  • Replace motor.
  • Disconnect motor power cable from drive and enable drive with current limit set to 0. If fault clears, wiring or motor is the issue. If fault remains, call sales rep.
  • Remove ground from control power input / add isolation transformer.
E35

DriveUndervoltage Fault
(Pre-charge Fault)
Cause:
Converter pre-charge cycle failed due to low AC input voltage or internal malfunction.

Remedy:
  • Check input AC voltage on all phases.
  • Call your sales representative.
E36

DriveOvertemp Fault
Cause:
Converter thermal switch tripped; excessive heat exists in the power circuitry.

Remedy:
  • Reduce acceleration rates.
  • Reduce duty cycle (ON/OFF) of commanded motion.
  • Increase time permitted for motion.
  • Use larger Kinetix 2000 converter.
  • Check for clogged vents or defective fan.
E37

PowerPhaseLoss Fault
Cause:
One or more phases of input AC power missing, or axis enabled when main power removed.

Remedy:
  • Check input AC voltage on all phases.
  • Disable axis before removing power.
E38

SERCOSFault
(Ring Flt)
Cause:
Cable disconnected; SERCOS ring not active after being active.

Remedy:
  • Check that fiber-optic cable is present and connected properly.
E39

DriveHardFault
(Self Sense Flt)
Cause:
Self-sensing Commutation Startup Error; motion required was obstructed.

Remedy:
  • Verify there are no impediments to motion at startup (hard limits).
  • Increase self-sensing current if high friction/load exists.
  • Check motor or encoder wiring using wiring diagnostics.
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:
  • Disable the Drive Enable Input fault.
  • Verify that Drive Enable hardware input is active whenever the drive is enabled through software.
E50

SERCOSFault
(Same ADDR)
Cause:
Duplicate node address detected on SERCOS ring.

Remedy:
  • Verify that each SERCOS drive is assigned a unique node address.
E54

DriveHardFault
(Ifbk HW Fault)
Cause:
Current feedback hardware fault detected.

Remedy:
  • Replace the module.
E60

DriveHardFault
(Unknown Axis)
Cause:
Illegal ID bits detected.

Remedy:
  • Replace the module.
E61

AuxFeedbackFault
(Aux Fdbk AQB)
Cause:
Auxiliary Encoder State Error; illegal transition encountered.

Remedy:
  • Use shielded cables with twisted pair wires.
  • Route the feedback away from potential noise sources.
  • Check the system grounds.
  • Replace the motor/encoder.
E62

AuxFeedbackFault
(Aux Fdbk Loss)
Cause:
The feedback wiring is open, shorted, or missing.

Remedy:
  • Check the motor feedback cable connectors/wiring to the IAM/AM and motor.
E63

AuxFeedbackNoise
Cause:
Noise on auxiliary feedback cable. Recommended grounding instructions not followed.

Remedy:
  • Verify grounding.
  • Route feedback cable away from noise sources.
E64

MotorFeedbackNoise
Cause:
Noise on motor feedback cable.

Remedy:
  • Refer to System Design for Control of Electrical Noise Reference Manual, publication GMC-RM001.
E65

No Fault Message
(Hookup Fault)
Cause:
Hookup procedure failed due to motor or feedback device malfunction.

Remedy:
  • Check motor power/feedback wiring.
  • Refer to on-screen message for resolution.
E66

No Fault Message
(Atune Flt)
Cause:
Autotune procedure failed due to motor or feedback device malfunction.

Remedy:
  • Check motor power/feedback wiring.
  • Refer to on-screen message for resolution.
  • Perform Hookup in RSLogix 5000 software.
  • Consult RSLogix 5000 help screen.
E67
DriveHardFault (Task init)

Operating system failed
Cause: Software initialization fault detected due to hardware failure.

Remedy:
  • Cycle power.
  • If fault persists, replace module.
E68
DriveHardFault (SCANport Comm)

DPI communication failed
Cause: The DPI device or cable is faulty.

Remedy:
  • Check DPI connections.
E69
DriveHardFault (Objects Init)

Non-volatile memory is corrupt due to control board hardware failure.
Cause: Control board hardware failure.

Remedy:
  • Load default parameters, save to non-volatile memory, and recycle power or reset the drive.
E70
DriveHardFault (NV Mem Init)

Non-volatile memory is corrupt due to control board software error.
Cause: Control board software error.

Remedy:
  • Load default parameters, save to non-volatile memory, and recycle power or reset the drive.
E71
DriveHardFault (Memory Init)

RAM or Flash memory validation failure
Cause: Validation failure during initialization.

Remedy:
  • Cycle power.
  • If fault persists, replace module.
E72
DriveOvertemp Fault (Drive Overtemp)

Inverter thermal switch tripped
Cause:
  • The fan on the IAM or an AM failed.
  • The cabinet ambient temperature is above rating.
  • The machine duty cycle requires an RMS current exceeding the continuous rating of the controller.
  • The airflow access to the Kinetix 2000 system is limited or blocked.

Remedy:
  • Replace the failed module.
  • Check the cabinet temperature.
  • Change the command profile to reduce speed or increase time.
  • Check airflow and re-route cables away from the Kinetix 2000 system.
E73
Communicate (Backplane Comm)

Power rail CAN communications failed
Cause:
  • Power rail connection shorted or open.
  • Module not mounted properly.

Remedy:
  • Check module for proper mount.
  • Check power rail and module for foreign objects.
E74
DriveOvercurrent Fault (Bus OverCurrent)

DC link current exceeds rating
Cause:
  • Motor or transmission malfunction.
  • IAM not properly sized.

Remedy:
  • Check for proper motor sizing.
  • Check/replace transmission device.
  • Check/replace motor.
  • Check for proper IAM sizing.
  • Install larger kW rated IAM.
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:
  • Use a properly sized shunt or modify duty cycle of the application.
  • System uses internal shunt and requires external shunt for additional capacity.
E76
DriveHardFault (CAN Init)

DPI hardware initialization fault detected
Cause: Control board hardware failure.

Remedy:
  • Reset System.
  • If fault persists, replace system module.
E78
DriveHardFault (SERCOS Init)

Control hardware fault detected
Cause: Control hardware fault detected.

Remedy:
  • Cycle power.
  • If fault persists, replace module.
E79
DriveOvervoltage Fault (Shunt Module Flt)

Shunt module fault
Cause:
  • Shunt module temperature fault LED indicator is steady red.
  • Shunt module shunt fault LED indicator is steady red.
  • Module missing from power rail.

Remedy:
  • Refer to Temperature Fault LED Indicator (page 141).
  • Refer to Shunt Fault LED Indicator (page 141).
  • Install missing module on power rail.
  • Fill empty slot with slot filler module.
E80
DriveHardFault (CPLD Flt)

Control hardware fault detected
Cause: Control hardware fault.

Remedy:
  • Replace module.
E81
DriveHardFault (Common Bus Flt)

Follower IAM detected ac input power being applied
Cause: Follower IAM detected AC input power.

Remedy:
  • Remove ac input power connections from follower IAM.
E90
DriveHardFault (Pre-charge Timeout Flt)

Pre-charge resistor power exceeds the resistor rating
Cause: Pre-charge resistor power exceeds the resistor rating.

Remedy:
  • Allow resistor to cool.
All others
RESERVED
Cause: Unknown / Reserved error.

Remedy:
  • Call your local Rockwell Automation sales representative.

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

Popular posts from this blog

3210 DC bus overvoltage fault in lenze i550 drive

7180 Motor overcurrent fault in lenze i550 drive

FF06 Motor overspeed fault in lenze i550 drive