Most Allen-Bradley PLC Faults Aren't Program Faults: A ControlLogix Field Checklist

Most Allen-Bradley PLC "failures" are not the PLC's fault. If your ControlLogix or CompactLogix is randomly faulting, losing memory, or triggering an unexpected shutdown, the cause is usually something you can find with a multimeter and five minutes of inspection: a bad probe technique, a dead backup battery, or a surge protector that's the wrong type or in the wrong place. In my opinion, checking these three things should happen before you ever open Studio 5000 to trace program logic.

About the Author: Why I Built This Checklist

I'm a control systems technician. I've handled Allen-Bradley PLC service and repair orders for six years. I've personally made and documented 14 significant mistakes, totaling roughly $23,000 in wasted budget. Now I maintain our team's pre-power checklist to keep those mistakes from happening twice.

In my first year (2017), I made the classic mistake: I swapped a ControlLogix processor because the program looked corrupted. It turned out the battery had failed, the memory was lost, and the actual CPU was fine. The processor was returned under warranty, but the embarrassment stuck with me. I've never fully understood why the battery flag didn't get my attention sooner.

We've done maybe 200 service calls since then. Maybe 180, I'd have to check the system. The pattern is consistent enough that I can tell you where to look first.

Use Micro Leads for Multimeter Probing on Dense I/O Cards

On a 1756 ControlLogix I/O card, the terminal screws are close together. I once used a standard multimeter probe to check a 24V signal and accidentally bridged the output to the adjacent pin. The result was a blown analog input card—I want to say it was a 1756-IF8, but I'm mixing it up with the other project. It cost $890 and a 45-minute line stoppage. That's when I bought a set of micro leads for multimeter.

A set of micro leads for multimeter—the sharp, needle-point probes—costs around $15. I didn't understand why anyone would buy them until I paid for that card. Put another way: $15 is the cheapest insurance you'll ever buy for a dense terminal block. Honestly, I'm not sure why they're not standard issue in every electrical kit. My best guess is that the tool seems like a specialty item until a big failure makes it essential.

One note on technique: don't use a micro lead as a wedge between the wire and the terminal. The needle tip can pierce insulation if you push too hard. Touch the bare conductor or the terminal test point with a light hand. I learned that the expensive way too.

Battery Charger and Maintainer: For the Backup Path, Not the CPU Battery

This point confuses a lot of people. The 1756-BA2 lithium battery inside a ControlLogix CPU is not rechargeable. Do not connect a battery charger to it. If you're searching for a "battery charger and maintainer," it's probably because you have a DC-UPS or a station battery that keeps the rack alive during a brownout. That system does need a charger and maintainer.

A proper industrial battery charger and maintainer is often a small DIN-rail module with a float charge output and temperature compensation. It's not a generic car battery trickle charger. In an industrial panel, its job is to keep the DC-UPS battery at full charge so the PLC doesn't see a voltage sag.

In September 2022, I chased a phantom fault on a CompactLogix 5380 for two days. It looked fine on my screen. The fault history said "power supply disrupted," but the supply read 24VDC and the program was unchanged. The real problem was the backup battery at 9V—the battery charger and maintainer had been wired to the wrong terminals, so it was never actually maintaining anything. $450 in labor, straight to the trash. That's when I learned to verify the entire battery path before touching the code.

Here's what I do now:

• De-energize the 24V control supply.
• Measure the backup battery voltage with the load disconnected.
• Verify the charger/maintainer output is within the battery manufacturer's float voltage spec.
• Reconnect and measure at the PLC power connector—not just at the charger.

Per FTC advertising guidelines, I'd also be careful about claims on battery backup products. A charger that says "maintains all batteries" isn't necessarily suitable for your sealed lead-acid or lithium iron phosphate bank. Look for documented specs, not marketing language.

Type 1 vs Type 2 Surge Protector: Know the Line Side

Type 1 vs Type 2 surge protector is not a ranking. It's a location and application difference. Per UL 1449, a Type 1 SPD is intended for installation on the line side of the service disconnect—typically the main service entrance. A Type 2 SPD goes on the load side, usually in a subpanel or machine panel.

That line-side distinction matters more than most people think. I once saw an electrician install a Type 2 SPD at a service entrance because the label said 200kA. An upstream surge destroyed it, and the transient traveled into the building, taking out two analog cards and a 1756-ENBT module. The replacement order was over $3,200. If they'd used the correct Type 1 unit, a chunk of that damage might have been avoided.

Think of it like the federal mailbox rule (18 U.S.C. § 1708): only USPS-authorized mail may be placed in a residential mailbox. The penalty for violating that rule can be up to $5,000. A surge protector in the wrong location can cost far more than that—it can cost you the PLC rack.

Here's a boundary condition: if your facility is in a lightning-prone area or you have long exposed cable runs, you might need Type 1 at the service and Type 2 at the PLC panel. The choice isn't either/or. Honestly, I'm not sure why so many generic panel specs skip a site-specific surge risk assessment. My best guess is that distributors default to Type 2 because it's the most common stock item, but that's not always the right technical answer.

Why PLC Allen-Bradley Programming Is the Last Place to Look

When a machine faults, the natural impulse is to open the code and start tracing. But with ControlLogix, CompactLogix, and Micro850 systems, the PLC is usually recording what happened before it faulted. The fault history and the power supply diagnostics are the fastest way to narrow down the cause.

If you're asking about a "PLC Allen Bradley ControlLogix" fault that doesn't produce any error message, start with the battery and the backup power path. If the fault history shows a power supply disruption, don't look at the ladder logic—look at the supply. If it shows a battery flag, don't re-download the program—replace the battery.

The most frustrating part of PLC troubleshooting is that the same power issues recur. You'd think a clean 24VDC supply and proper grounding would be standard in every panel, but it isn't. I'm not saying the program is never the issue. I'm saying it's rarely the first issue worth pulling apart.

The Pre-Power Checklist

1. Measure 24VDC at the I/O terminal block using micro leads for multimeter probes.
2. De-energize and verify the backup battery voltage against the CPU manufacturer's specification.
3. Confirm the surge protector Type 1 vs Type 2 and its location relative to the service disconnect.
4. Test the battery charger and maintainer by checking float voltage and, if possible, performing a safe power-dip simulation.
5. Read the fault history in Studio 5000 (or Connected Components Workbench for Micro800) before changing any logic.
6. Only after the hardware and power path are verified, open the program.

This list isn't a replacement for a proper OEM startup procedure. It's a filter. It catches the environmental failures that masquerade as software bugs.

Where This Checklist Doesn't Apply

This approach won't fix a processor that has been physically damaged by a direct lightning hit, a failed firmware update, or a manufacturing defect. If the fault points to a specific module, you still need to do a physical swap and follow change management after the hardware is verified.

I've never fully understood why some checklists stop after "replace the bad module" without asking "why did that module die?" Maybe that's because the answer is often something we don't want to hear, like a persistent wiring problem or a surge event we didn't record. But that's exactly why I keep the pre-power checklist visible.

If you're reading this because you have a "dead" Allen-Bradley PLC, do yourself a favor: measure the battery, check the SPD, and grab those micro leads before you re-download the program. Five minutes of verification beats five days of correction.