5 Most Common Allen-Bradley PLC Faults and How to Fix Them

Allen-Bradley PLCs from Rockwell Automation are the most widely used controllers in North American manufacturing. CompactLogix and ControlLogix run everything from simple conveyor logic to complex batch processes. When they fault, the line stops. Here are the five faults you'll see most often and how to fix each one.

1. Fault 01 — Watchdog Timeout

The watchdog timer monitors how long the controller takes to complete one scan of your program. If the scan exceeds the configured limit, the controller faults to prevent unpredictable output behavior. This is the PLC equivalent of "your program is taking too long."

Fix: Open Task Properties in Studio 5000 and check the actual scan time vs. the watchdog setting. If the scan time legitimately needs to be longer, increase the watchdog timer. If the scan time spiked, look for a runaway loop or an instruction that's processing a large data set in a single scan.

2. Fault 16 — I/O Not Responding

This is the most common fault in any CompactLogix or ControlLogix system. It means one or more I/O modules lost communication with the controller. The faulted module's outputs go to their configured fault state (typically off).

Fix: Expand the I/O tree in Studio 5000 — the faulted module will have a red X. Reseat it firmly into the backplane. Check 24VDC power at the module. For remote I/O over EtherNet/IP, verify the network cable and switch port LEDs.

3. Fault 04 — Recoverable I/O Fault

Less severe than Fault 16, a recoverable I/O fault means a module reported an error but the controller keeps running. The data from that module may be stale, which can cause subtle logic errors downstream.

Fix: Check the specific module's fault code in the I/O tree. Common causes are firmware mismatches and momentary cable disconnections. The fault auto-clears when the module recovers, or you can clear it with a CLR Major Fault instruction.

4. Communication Timeout (Micro820)

The Micro820 and Micro850 are budget-friendly controllers used on smaller machines. A communication timeout means the controller lost contact with a Modbus TCP or RTU slave device. Unlike the CompactLogix, the Micro820 doesn't have an I/O tree — it uses MSG instructions for communication.

Fix: Ping the target device from a laptop. For Modbus RTU, check the RS-485 wiring: A to A, B to B, with 120Ω termination resistors at both ends of the bus. Verify baud rate and parity settings match.

5. User Program Error (Micro820)

A user program error means your ladder logic hit a runtime error — typically a division by zero or an array index out of bounds. The controller stops, and all outputs go to their fault state.

Fix: Connect with Connected Components Workbench (CCW) and check the fault log for the specific instruction address. Add guard logic before math operations (check for zero before dividing) and validate array indices before using them.