liminfo

Allen-Bradley Fault Code Reference

Allen-Bradley PLC & drive fault code reference with causes and solutions

45 results

About Allen-Bradley Fault Code Reference

The Allen-Bradley Fault Code Reference is a free online lookup tool for automation engineers and PLC programmers working with Rockwell Automation equipment. It covers over 45 fault codes across five categories: Controller faults (Type 01/04 codes for ControlLogix and CompactLogix), EtherNet/IP and ControlNet communication errors (Type 03/06 codes), Kinetix servo drive motion faults (S01-S16), PowerFlex VFD faults (F002-F064), and I/O module diagnostics (Type 07 codes for 1769 and POINT I/O).

This reference is built for plant engineers, maintenance technicians, and system integrators who need rapid fault diagnosis during production downtime. It covers real-world scenarios including controller major faults (nonvolatile memory failure, firmware corruption, array subscript errors), EtherNet/IP connection timeouts and RPI mismatches, Kinetix following errors and encoder faults, PowerFlex overcurrent and electronic thermal trips, and I/O module configuration mismatches and wire-off diagnostics.

All data is loaded entirely in the browser with instant search and five-category filtering. The bilingual Korean-English interface serves international manufacturing teams. No login, software installation, or persistent internet connection is needed — the entire fault database works offline after page load.

Key Features

  • ControlLogix and CompactLogix controller fault codes (Type 01, Type 04) with resolution procedures
  • PowerFlex 520/525/527/750 VFD fault codes F002 through F064 with reset steps
  • Kinetix 5500/5700/6500 servo drive fault reference covering S01 through S16
  • EtherNet/IP and ControlNet communication fault troubleshooting (Type 03, Type 06)
  • I/O module diagnostic codes for 1769 CompactLogix and 1734 POINT I/O systems (Type 07)
  • Instant search by fault type/code (e.g. Type 04 Code 20), F-code (e.g. F012), or keyword
  • Bilingual Korean and English support for global automation teams
  • Offline-capable and mobile-responsive for factory floor troubleshooting

Frequently Asked Questions

What does Allen-Bradley fault Type 04 Code 16 mean?

Type 04 Code 16 is a Program Major fault indicating the controller encountered an unknown instruction during execution. This typically occurs when a program is incompletely downloaded, the firmware version does not support a particular instruction, or an Add-On Instruction (AOI) is missing. Resolve by re-downloading the program from Studio 5000, verifying firmware compatibility, and checking for missing AOIs.

How do I clear a ControlLogix major fault?

To clear a major fault: (1) Connect with Studio 5000 or RSLogix 5000, (2) Go to Controller Properties > General, (3) Click "Clear Major Fault", (4) Address the root cause shown in the fault code before switching to Run mode. You can also clear faults programmatically using GSV/SSV instructions on the FaultLog object. For Type 01 faults (nonrecoverable), a power cycle or firmware reinstall via ControlFLASH may be required.

How do I fix PowerFlex fault code F012 (HW overcurrent)?

PowerFlex F012 is a hardware overcurrent fault indicating the drive output current instantly exceeded the protection threshold. Causes include output short circuits, motor insulation breakdown, or ground faults. Diagnose by: (1) Measuring motor cable insulation resistance with a megger, (2) Checking motor phase-to-phase and phase-to-ground resistance, (3) Disconnecting the motor cable and testing the drive standalone, (4) Inspecting the drive IGBT module for damage, (5) Verifying motor cable length is within the allowable range.

What causes Kinetix servo fault S10 (following error)?

Kinetix S10 indicates the difference between commanded and actual position exceeded the configured tolerance. Common causes include mechanical jams or interference, insufficient servo tuning gains, aggressive acceleration/deceleration profiles, and encoder signal quality issues. Troubleshoot by manually checking the mechanism for binding, re-tuning axis parameters, moderating accel/decel rates, reviewing the Position Error Tolerance setting, and verifying encoder cable shielding.

How do I troubleshoot CompactLogix I/O faults (Type 07)?

For Type 07 I/O faults: (1) Check the physical module LEDs for error indication (red flashing), (2) Verify the module is properly seated in the backplane or base, (3) Confirm the module catalog number and series match the I/O tree configuration in Studio 5000, (4) Check if the module firmware version matches the project Electronic Keying settings, (5) For 24VDC field power loss (Code 10), measure voltage at the module field power terminals and verify the external power supply.

What does EtherNet/IP error Type 03 Code 16 mean?

Type 03 Code 16 indicates an I/O connection was lost to a remote device on the EtherNet/IP network. Causes include network cable faults, switch port failures, device power loss, or IP address conflicts. Troubleshoot by checking device power and status LEDs, inspecting network cables and switch ports, running ping tests, reviewing RPI values and connection settings in the I/O tree, and scanning for duplicate IP addresses on the network.

How do I resolve PowerFlex fault F007 (motor overload)?

PowerFlex F007 indicates the electronic thermal protection (I-squared-t) detected motor overheating from sustained overload. To resolve: (1) Verify the actual load current is within the motor rated current, (2) Ensure the Motor FLA (Full Load Amps) parameter correctly matches the motor nameplate, (3) Confirm Motor NP Amps matches the drive parameter settings, (4) Inspect motor cooling including fan and ventilation, (5) Reduce the mechanical load or consider upsizing the motor if it is undersized for the application.

How do I fix ControlNet fault Type 06 Code 01?

Type 06 Code 01 is a ControlNet connection fault indicating a scheduled connection failure. Causes include ControlNet module hardware failure or coaxial/fiber cable faults. To resolve: (1) Inspect ControlNet cable connections (coax or fiber), (2) Run diagnostics in RSNetWorx for ControlNet, (3) Reschedule the network, (4) Check the ControlNet module NTWK LED status, (5) Update module firmware and reschedule the network. For duplicate node addresses (Code 02), scan the network and change the conflicting node address via the rotary switch.