Allen Bradley Kinetix 350 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 350 fault codes. Master CIP Motion diagnostics, troubleshoot E-codes via Studio 5000, and resolve Axis Faults.

Kinetix 350 Fault Codes Reference Table

Below is the complete list of error codes. The drive display typically scrolls the “E” followed by the code (e.g., E…0…5). Use this table to cross-reference the scrolling text with the Studio 5000 description.

Kinetix 350 Fault Codes Reference Table

Kinetix 350 Fault Codes Reference Table

Fault Code and Meaning Cause and Remedy
S 01
Axis enable input
Cause: Axis Enable Input is not active.

Remedy:
  • Check wiring and 24V source for drive ENABLE Input.
  • Disable enableInputChecking attribute by using a message instruction.
S 02
Motor not configured
Cause: Faulty intelligent encoder or incorrect motor file.

Remedy:
  • Cycle power or reset the drive.
  • Check that proper motor has been selected in Logix Designer Application.
  • Replace motor if faulting continues.
S 03
Feedback not configured
Cause: The associated feedback device has not been configured for use or the configuration does not match what is connected.

Remedy:
  • Verify feedback configuration matches connected device.
Sc05
Safe torque off
Cause: The safety function has disabled the power structure.

Remedy:
  • Apply 24V sources to safety circuit.
  • Use jumpers to bypass safety circuit.
F 02
Illegal Hall State
Cause: Improper connections.

Remedy:
  • Check wiring of S1, S2, and S3.
  • Check the power supply to the encoder.
F 03
Motor Overspeed
Cause: Motor speed has exceeded 125% of maximum rated speed.

Remedy:
  • Check motor wire phasing.
  • Check cables for noise.
  • Check tuning.
F 05
Motor Overtemperature
Cause: High motor ambient temperature and/or Excessive Current.

Remedy:
  • Check motor wiring at motor feedback (MF) connector.
  • Check TS+ and COM wiring.
  • Operate within (not above) the continuous torque rating for the ambient temperature.
  • Lower ambient temperature or increase motor cooling.
  • Verify that the proper motor has been selected.
F 07
Motor Thermal Protection
Cause: The machine duty cycle requires an RMS current that exceeds the continuous rating of the motor.

Remedy:
  • Change the command profile to reduce speed or increase time.
F 10
Inverter Overcurrent
Cause:
- Motor cables shorted.
- Motor winding shorted internally.
- Drive temperature too high.
- Loss of TTL signal.

Remedy:
  • Verify continuity of motor power cable and connector.
  • Disconnect motor power cables; check phase-to-phase is not open and phase-to-ground is open.
  • Check for clogged vents, defective fan, or insufficient space around unit.
  • Operate within continuous power rating.
  • Check AM+, AM-, BM+, and BM- signals.
F 11
Inverter Overtemperature
Cause: Drive fan failed, High cabinet ambient temperature, or Blocked airflow.

Remedy:
  • Replace the failed drive.
  • Check cabinet temperature (See specifications).
  • Change the command profile to reduce speed or increase time.
  • Check airflow and reroute cables away from drive system.
F 13
Inverter Thermal Protection
Cause: Machine duty cycle exceeds continuous rating OR Motor brake on.

Remedy:
  • Change the command profile to reduce speed or increase time.
  • Turn off motor brake.
F 33
Bus Undervoltage
Cause: DC bus voltage is below limits (460V system < 275V, 230V system < 137V, 120V system < 80V).

Remedy:
  • Verify the 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.
F 35
Bus Overvoltage
Cause: Excessive regeneration of power, external mechanical power source, or high AC line voltage.

Remedy:
  • Change the deceleration or motion profile.
  • Use a larger system (motor and drive).
  • Install shunt resistor.
F 43
Feedback Loss
Cause: The motor feedback wiring is open, shorted, or missing; OR Excessive noise on feedback signals.

Remedy:
  • Check motor encoder wiring.
  • Run Hookup test in RSLogix 5000 software.
  • Use shielded cables, route feedback away from potential noise sources.
  • Check system grounds, replace motor/encoder.
  • Verify Attribute #2703 (0=Lost, 1=Bad Hall, 2=Sin/Cos Limit, 3=Noise).
F 45
Feedback Serial Comms
Cause: Communication was not established with an intelligent encoder.

Remedy:
  • Verify motor selection.
  • Verify motor encoder wiring.
F 47
Feedback Self Test
Cause: Damage to feedback device.

Remedy:
  • Call Rockwell Automation sales representative to return the motor for repair.
F 50
Hardware Overtravel - Positive
Cause: Dedicated overtravel input is inactive.

Remedy:
  • Check wiring.
  • Verify motion profile.
  • Verify axis configuration in software.
F 51
Hardware Overtravel - Negative
Cause: Dedicated overtravel input is inactive.

Remedy:
  • Check wiring.
  • Verify motion profile.
  • Verify axis configuration in software.
F 54
Excessive Position Error
Cause: Partial loss of feedback signals, Improperly sized drive/motor, or Mechanical system out of specifications.

Remedy:
  • Check all wiring at the motor feedback (MF) connector.
  • Verify the sizing of the system.
  • Increase feed forward gain or following error limit.
  • Check position loop tuning.
  • Verify mechanical integrity of system.
  • Check motor power wiring.
F 55

Excessive Velocity Error
Cause:
  • Partial loss of feedback signals.
  • Improperly sized drive or motor.
  • Mechanical system out of specifications.

Remedy:
  • Check all wiring at motor feedback (MF) connector.
  • Increase velocity error limit or time.
  • Check velocity loop tuning.
  • Verify sizing of system.
  • Verify mechanical integrity of system within specification limits.
  • Check motor power wiring.
  • Reduce acceleration.
F 56

Overtorque Limit
Cause:
  • Overly aggressive motion profile.
  • Mechanical binding.
  • Mechanical system out of specifications.

Remedy:
  • Verify motion profile.
  • Verify that Overtorque settings are appropriate.
  • Verify sizing of system.
  • Verify torque offset.
  • Verify mechanical integrity of system within specification limits.
F 57

Undertorque Limit
Cause:
  • Improperly configured limit.
  • Improperly configured motion.
  • Improperly drive/motor sizing.
  • Mechanical system out of specifications.

Remedy:
  • Verify motion profile.
  • Verify that Overtorque settings are appropriate.
  • Verify sizing of system.
  • Verify mechanical integrity of system within specification limits.
F 61

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 the axis was enabled.

Remedy:
  • Check wiring of drive enable input.
  • Check 24V source.
  • Verify that Drive Enable hardware input is active whenever the drive is enabled through the software.
F 62

Controller Initiated Exception
Cause:
User configured software overtravel.

Remedy:
  • Move axis out of soft overtravel range.
  • Clear soft overtravel fault.
  • Check soft overtravel configuration.
  • Consult controller documentation.
Fc 02

Motor Voltage Mismatch
Cause:
Wrong motor has been connected to drive.

Remedy:
Connect appropriate motor to drive.
Fc 05

Motor Encoder Battery Loss
Cause:
Weak battery or poor battery connection.

Remedy:
  • Replace battery.
  • Check battery connection.
Fc 06

Motor Encoder Battery Low
Cause:
The battery voltage on a battery-backed motor encoder is low enough such that a power loss causes the absolute position to be lost.

Remedy:
(See Fc 05: Replace battery / Check connection).
Fc 14

Excessive Current Feedback Offset
Cause:
Current in one or more phases have been lost or remains below a preset level.

Remedy:
Replace the drive.
Fc 26

Runtime Drive Error
Cause:
The drive firmware encountered an unrecoverable runtime error.

Remedy:
  • Cycle control power.
  • Replace drive.
Ic 01

Boot Block Check Sum Fault
Cause:
Faulty intelligent encoder.

Remedy:
  • Cycle power or reset the drive.
  • Replace motor if faulting continues.
Ic 02

Motor Data Range Error
Cause:
Faulty intelligent encoder or incorrect motor file.

Remedy:
  • Cycle power or reset the drive.
  • Check validity of the motion database.
  • Replace motor if faulting continues.
Ic 03

Motor Feedback Communication Startup
Cause:
  • An incorrect motor has been selected or connected.
  • Faulty wiring.

Remedy:
  • Check motor selection.
  • Check motor encoder wiring.
Ic 06

Motor Absolute Startup Speed
Cause:
Mechanical movement of the machine has caused excessive rotation of the motor during powerup (>100 rpm).

Remedy:
Allow machine motion to stop before powerup.
L001

Identity block corrupted
Cause:
Unrecoverable error while starting the drive.

Remedy:
Reload the firmware and restart the drive. If message repeats, contact Rockwell Automation technical support.
L002

Firmware file load failed
Cause:
Unrecoverable error while starting the drive.

Remedy:
Reload the firmware and restart the drive. If message repeats, contact Rockwell Automation technical support.
L004

Firmware not programmed (drive is new)
Cause:
Drive is new or memory wiped.

Remedy:
Reload the firmware and restart the drive.
L008

DSP load operation failed
Cause:
Unrecoverable error while starting the drive.

Remedy:
Reload the firmware and restart the drive. If message repeats, contact Rockwell Automation technical support.
P001 - P007

POST (Power-on Self Test) Failure
Cause:
  • P001: SDRAM test failed
  • P002: FPGA load operation failed
  • P004: DPRAM Test failed
  • P005: DSP I/F to DPram - no DSP response
  • P006: I/F to DPram failed
  • P007: Firmware file md5 test failure

Remedy:
Unrecoverable error during POST. Contact Rockwell Automation technical support to return the drive for repair.
nF 01

Control Update Fault
Cause:
  • Excessive network traffic.
  • Noisy environment.

Remedy:
  • Remove unnecessary network devices from the motion network.
  • Change the network topology so that fewer devices share common paths.
  • Use faster/higher performance network equipment.
  • Isolate signal wiring from power wiring.
  • Use shielded cables.
  • Add snubbers to power devices.
nF 02

Processor Watchdog Fault
Cause:
The watchdog-circuit monitoring processor operation detected a problem.

Remedy:
  • Recycle control power or reset the drive.
  • Replace the control module if the problem persists.
nF 03

Hardware Fault
Cause:
  • The drive has an internal hardware problem.
  • Faulty memory component (Nonvolatile write failure).

Remedy:
  • Recycle control power or reset the drive.
  • Replace the drive if problem persists.
nF 04

Data Format Error
Cause:
Faulty memory component (Data format error discovered in controller-to-drive message).

Remedy:
  • Recycle control power or reset the drive.
  • Replace the control module if problem persists.
 

How to Read Kinetix 350 Faults

Because the Kinetix 350 is a CIP Motion drive, diagnostics are best performed using the Rockwell automation software suite rather than the physical hardware alone. Here is the standard procedure for 2026:

  • Studio 5000 Logix Designer: This is your primary tool.
    • Go to the Controller Organizer and find the Axis associated with the drive.
    • Right-click the Axis and select Properties > Faults & Alarms.
    • This screen provides the full text description of the fault (e.g., “Position Error” or “Feedback Noise”) and often suggests the cause.
  • Module Info Tab: In the I/O configuration tree, double-click the Kinetix 350 module. The “Connection” tab will tell you if the drive is “Running,” “Faulted,” or “Connecting.” If it says “Time Out,” the PLC cannot see the drive on the network.
  • Physical Display: The front LED display will scroll the fault code. Use this for a quick check if you do not have a laptop connected (e.g., “Code 05” usually indicates an IP address conflict or wait state).

Frequently Asked Questions (FAQ)

Q: How do I reset a Kinetix 350 fault?

A: Since the Kinetix 350 is controlled by the PLC, you cannot reset faults via the drive keypad. You must use the Motion Axis Fault Reset (MAFR) instruction in your ladder logic.

  • Trigger the MAFR instruction referencing the specific Axis tag.
  • After resetting, you often need to re-enable the drive using the Motion Servo On (MSO) instruction.

Q: What is the difference between Kinetix 300 and 350?

A: This is a critical distinction:

  • Kinetix 300: An “Indexing” drive. It stores moves internally and is configured via a Web Browser. The PLC triggers these moves via I/O or explicit messages.
  • Kinetix 350: A “CIP Motion” drive. It has no internal move storage; the PLC calculates the motion path in real-time. It is configured entirely inside Studio 5000.

Q: Why is the drive scrolling “E05”?

A: “E05” generally relates to IP address configuration. The drive is waiting to receive an IP address or has a conflict.

  • Check the rotary switches. If set to 000, it is waiting for a DHCP server (BootP).
  • If set to 001-254, it is trying to use that as the last octet of `192.168.1.xxx`. Ensure no other device on the network has the same address.

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