Allen Bradley Kinetix 300 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 300 fault codes. Troubleshoot E-codes, Web Interface connection issues, Indexing errors, and Safety trips.

Kinetix 300 Fault Codes Reference Table

Kinetix 300 Fault Codes Reference Table

Kinetix 300 Fault Codes Reference Table

Fault Code and Meaning Cause and Remedy
-

Status indicator not displaying any messages
Cause: No AC power or back-up power. Internal power supply malfunction.

Remedy:
  • Verify AC power or back-up power is applied to the Kinetix 300 drive.
  • Call your Allen-Bradley representative.
-

Motor jumps when first enabled
Cause: Motor wiring error. Incorrect motor chosen.

Remedy:
  • Check motor wiring.
  • Verify that the proper motor is selected.
E04

Motor overtemperature
Cause: Motor thermostat trips due to: High motor ambient temperature or Excessive current. Motor wiring error. 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.
  • Verify that the proper motor has been selected.
E06

Hardware overtravel
Cause: Dedicated overtravel input is inactive.

Remedy:
  • Check wiring.
  • Verify motion profile.
E07

Feedback lost
Cause: The feedback wiring is open, shorted, or missing.

Remedy:
  • Check motor encoder wiring.
  • Make sure that the motor is recognized from drive's Web-based configuration motor screen.
E09

Bus undervoltage
Cause: Low AC line/AC power input.

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.
E10

Bus overvoltage
Cause: Excessive regeneration of power (motor driven by external source). Excessive AC input voltage.

Remedy:
  • Change the deceleration or motion profile.
  • Use a larger system (motor and Kinetix 300 drive).
  • Use a resistive shunt (verify wiring if connected).
  • Verify that input is within specifications.
E11

Illegal Hall state
Cause: Incorrect phasing. Bad connections.

Remedy:
  • Check the Hall phasing.
  • Verify the Hall wiring.
  • Verify 5V power supply to the encoder.
E12

Home search failed
Cause: Home sensor and/or marker is outside the overtravel limits.

Remedy:
  • Check wiring.
  • Reposition the overtravel limits or sensor.
E14

Ethernet I/O connection lost
Cause: Ethernet I/O Connection lost.

Remedy:
  • Check wiring and Ethernet cables and routing.
  • Check controller program to be sure that I/O is scanned at correct RPI rate.
E16

Software overtravel
Cause: Programmed overtravel limit has been exceeded.

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

Overspeed fault
Cause: Motor speed has exceeded 125% of maximum rated speed.

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

Excess position error
Cause: Position error limit was exceeded.

Remedy:
  • Increase following error limit or time.
  • Check position loop tuning.
E23

Drive Thermal Protection
Cause: The internal filter algorithm protecting the drive from overheating has tripped.

Remedy:
  • Reduce acceleration rates.
  • Reduce duty cycle (ON/OFF) of commanded motion.
  • Increase time permitted for motion.
  • Use larger Kinetix 300 drive and motor.
  • Check tuning.
E26

Index parameter out of range
Cause: Parameters that are specified in the index table are beyond system capabilities.

Remedy:
  • Verify index parameters, such as position and velocity.
E27

Absolute move fault
Cause: Initiated move without being homed.

Remedy:
  • When using an absolute encoder home the axis before attempting an absolute move.
E30

Encoder communication fault
Cause: Communication was not established with an intelligent encoder.

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

Encoder data
Cause: Encoder data is corrupted.

Remedy:
  • Replace the motor/encoder.
E39

Safe Torque Off while enabled
Cause: The safety circuit was opened while drive was enabled or while attempting to enable.

Remedy:
  • Check safety circuit.
E43

Drive enable input
Cause: An attempt was made to enable the axis through software while the Drive Enable hardware input was inactive. The Drive Enable input transitioned from active to inactive while axis was enabled.

Remedy:
  • Verify that Drive Enable hardware input is active whenever the drive is enabled through software.
E44

Controller changed to PROG mode
Cause: Program downloaded or turned key on logix controller to program position.

Remedy:
  • Place controller back in RUN mode, clear faults.
E67

Operating system failed
Cause: Hardware or configuration failure.

Remedy:
  • Cycle power.
  • Check configuration settings to be sure that drive tags setting are valid.
  • Check your program to ensure that there are not explicit messages to internal drive variables that have been noted as unpublished or reserved.
E70

Memory module error
Cause: Bad memory module.

Remedy:
  • Replace memory module.
E72

Drive temperature too high
Cause: The heatsink temperature sensor has detected an overtemperature condition due to improper airflow or environmental temperature.

Remedy:
  • Check for clogged vents or defective fan.
  • Make sure that cooling is not restricted by insufficient space around the unit.
  • Check ambient temperature in enclosure.
  • Reduce acceleration rates. Reduce duty cycle (ON/OFF). Increase time permitted for motion.
E74

Drive has exceeded peak current limit
Cause: Motor cables shorted. Motor winding shorted internally. Machine duty cycle requires RMS current exceeding rating. Operation above continuous power/env rating. Short circuit or failed component.

Remedy:
  • Verify continuity of motor power cables and connector.
  • Disconnect motor power cables. If motor is hard to turn by hand, replace it.
  • Change the command profile to reduce speed or increase time.
  • Verify ambient temperature. Operate within ratings. Reduce acceleration rates.
  • Perform continuity check from DC bus to U, V, W outputs. If continuity exists, check for wire fibers or send drive for repair.
E76

Blank memory module
Cause: A Blank MEM module has been inserted into the drive.

Remedy:
  • Push and hold the drive's enter key until the drive shows "bUSY". This formats the module.
E91

User watchdog has timed out
Cause: Ladder program error.

Remedy:
  • Not writing to WatchDogKick Tag frequently enough to help prevent timeout.
  • Watchdog timeout period set to too low a value. Increase timeout period or change controller application.
E92

Bad battery
Cause: Tamagawa absolute feedback battery voltage low or missing. Battery error at startup.

Remedy:
  • Replace battery.
E93

Motion set-up parameters calculation error
Cause: Motion set-up parameters calculate an acceleration value above or below the drive capability.

Remedy:
  • Check indexing profiles or motion set-up profiles.
  • Increase or decrease acceleration profile.
  • Increase or decrease permitted time for motion.
E94

Motor or motor feedback cable
Cause: Motor or feedback device malfunction. Grounding instructions not followed.

Remedy:
  • Check motor power/feedback wiring.
  • Replace motor or encoder.
  • Verify grounding.
  • Route feedback cables away from noise sources.
  • See System Design for Control of Electric Noise Reference Manual.
E95

Wrong Indexing Mode
Cause: Index Type or ReferenceSource not supported in configured Linear/Rotary Unwind mode.

Remedy:
  • Change the Index Type or ReferenceSource to values that are supported by selecting Linear or Rotary Unwind mode.
  

How to Read Kinetix 300 Faults

Diagnostics on the Kinetix 300 are unique because the primary tool is the drive’s built-in web server. Here is how to access diagnostic data in 2026:

  • The Status Display: The 4-digit LED display on the front face provides the immediate error code (E-Code) and the drive state (e.g., “Run”, “Stby”).
  • Web Interface (MotionView OnBoard):
    • Type the drive’s IP address into your web browser (Edge, Chrome, or Firefox).
    • Navigate to the Diagnostics tab.
    • This view shows the “Fault Log,” active system status, and the status of Digital Inputs/Outputs which are critical for indexing logic.
  • Module Status LEDs: The “MOD” and “NET” LEDs indicate Ethernet health. If the “NET” LED is flashing red, the drive has timed out from the PLC (Check the “E05” or “E06” codes).

Frequently Asked Questions (FAQ)

Q: How do I reset a Kinetix 300 fault?

A: You can reset the drive using:

  • EtherNet/IP: Toggle the “Fault Reset” bit in the output assembly from the PLC.
  • Digital Input: Trigger the input configured as “Drive Enable” or “Reset” (configurable via the Web Interface).
  • Web Interface: Click the “Clear Faults” button on the Diagnostics page.

Q: What does the “E05 IP Address” error mean?

A: This is a network configuration error. It usually means the rotary switches on the drive are set to a value (001-254) that conflicts with a static IP assigned in software, or the drive expects a DHCP server that isn’t present.

  • For a Static IP: Set rotary switches to 000.
  • For a Private Network IP (192.168.1.xxx): Set switches to the last octet (e.g., 015).

Q: Is the Kinetix 300 a “CIP Motion” drive?

A: No. This is a common misconception. The Kinetix 300 connects to ControlLogix/CompactLogix via EtherNet/IP, but it uses Explicit Messaging or I/O Assemblies to trigger internal indexes. You cannot use the “Motion Axis Move” (MAM) instructions in Studio 5000 like you would with a Kinetix 350 or 5500.

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