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
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| S 01 Axis enable input |
Cause: Axis Enable Input is not active.
Remedy:
|
| S 02 Motor not configured |
Cause: Faulty intelligent encoder or incorrect motor file.
Remedy:
|
| 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:
|
| Sc05 Safe torque off |
Cause: The safety function has disabled the power structure.
Remedy:
|
| F 02 Illegal Hall State |
Cause: Improper connections.
Remedy:
|
| F 03 Motor Overspeed |
Cause: Motor speed has exceeded 125% of maximum rated speed.
Remedy:
|
| F 05 Motor Overtemperature |
Cause: High motor ambient temperature and/or Excessive Current.
Remedy:
|
| F 07 Motor Thermal Protection |
Cause: The machine duty cycle requires an RMS current that exceeds the continuous rating of the motor.
Remedy:
|
| F 10 Inverter Overcurrent |
Cause:
- Motor cables shorted. - Motor winding shorted internally. - Drive temperature too high. - Loss of TTL signal. Remedy:
|
| F 11 Inverter Overtemperature |
Cause: Drive fan failed, High cabinet ambient temperature, or Blocked airflow.
Remedy:
|
| F 13 Inverter Thermal Protection |
Cause: Machine duty cycle exceeds continuous rating OR Motor brake on.
Remedy:
|
| F 33 Bus Undervoltage |
Cause: DC bus voltage is below limits (460V system < 275V, 230V system < 137V, 120V system < 80V).
Remedy:
|
| F 35 Bus Overvoltage |
Cause: Excessive regeneration of power, external mechanical power source, or high AC line voltage.
Remedy:
|
| F 43 Feedback Loss |
Cause: The motor feedback wiring is open, shorted, or missing; OR Excessive noise on feedback signals.
Remedy:
|
| F 45 Feedback Serial Comms |
Cause: Communication was not established with an intelligent encoder.
Remedy:
|
| F 47 Feedback Self Test |
Cause: Damage to feedback device.
Remedy:
|
| F 50 Hardware Overtravel - Positive |
Cause: Dedicated overtravel input is inactive.
Remedy:
|
| F 51 Hardware Overtravel - Negative |
Cause: Dedicated overtravel input is inactive.
Remedy:
|
| F 54 Excessive Position Error |
Cause: Partial loss of feedback signals, Improperly sized drive/motor, or Mechanical system out of specifications.
Remedy:
|
| F 55 Excessive Velocity Error |
Cause:
Remedy:
|
| F 56 Overtorque Limit |
Cause:
Remedy:
|
| F 57 Undertorque Limit |
Cause:
Remedy:
|
| F 61 Drive Enable Input |
Cause:
Remedy:
|
| F 62 Controller Initiated Exception |
Cause: User configured software overtravel. Remedy:
|
| 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:
|
| 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:
|
| Ic 01 Boot Block Check Sum Fault |
Cause: Faulty intelligent encoder. Remedy:
|
| Ic 02 Motor Data Range Error |
Cause: Faulty intelligent encoder or incorrect motor file. Remedy:
|
| Ic 03 Motor Feedback Communication Startup |
Cause:
Remedy:
|
| 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:
Remedy: Unrecoverable error during POST. Contact Rockwell Automation technical support to return the drive for repair. |
| nF 01 Control Update Fault |
Cause:
Remedy:
|
| nF 02 Processor Watchdog Fault |
Cause: The watchdog-circuit monitoring processor operation detected a problem. Remedy:
|
| nF 03 Hardware Fault |
Cause:
Remedy:
|
| nF 04 Data Format Error |
Cause: Faulty memory component (Data format error discovered in controller-to-drive message). Remedy:
|
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
Post a Comment