North America's most installed controller and its most misread diagnostic tool
Rockwell Automation holds an estimated 36 percent of the North American PLC market (IHS Markit). Allen-Bradley ControlLogix and CompactLogix controllers are the most widely deployed in US discrete and hybrid manufacturing. The Fault log in Studio 5000 Logix Designer — accessible online via Controller Properties / General — is the primary diagnostic resource. It shows time-stamped major and minor fault entries with fault type and code. Major faults halt program execution. Without reading this log first, diagnosis is guesswork.
If your team is also dealing with electric motor faults or compressor shutdowns, the same principle applies: read the diagnostic log before touching anything. The controller is telling you what happened. The question is whether your team knows how to read it.
Major fault type 4 — when the I/O stops talking
An I/O fault stops program execution when a configured module does not respond within its communication window. The specific code identifies the slot and chassis location. Before assuming module failure, check the module status LEDs. A module with no LEDs lit indicates a power issue — specifically the 24VDC field power supply — rather than a module failure. Rockwell's Integrated Architecture Best Practices guide recommends this as the mandatory first check.
Major fault type 7 — the servo axis that will not cooperate
Motion faults occur on axes controlled through Kinetix servo drives. The sub-code identifies the axis and fault category. Rockwell Knowledgebase article 40283 documents the complete motion fault code library. Fault code 07 within motion indicates a position error fault — the axis did not reach commanded position within the allowed following error window. Common causes: mechanical binding on the axis, a servo loop tuned too tightly for the mechanical system, or a load change that has altered servo response characteristics since the last tuning session.
Minor fault type 3 — the program fault that is actually a process fault
Type 3 minor faults are generated by program conditions: divide by zero, indirect addressing outside array bounds, data type mismatches. In production controllers running unchanged programs, type 3 faults typically indicate a process variable moving outside its expected range — a calculation valid under normal conditions becomes invalid under an exceptional process condition. The Rockwell support database reports type 3 as the most common minor fault category in installed ControlLogix systems.
The intermittent fault that clears on power cycle but comes back
A fault that clears on restart and then reappears after a period of operation is the most diagnostically challenging category. In Allen-Bradley systems this is most commonly caused by network communication issues on EtherNet/IP I/O — a cable with marginal shielding that passes at low network load but fails under production load — or by a module with marginal internal voltage that functions after a reset but degrades during warming. The Controller Diagnostics counters under Controller Properties / Advanced record cumulative communication error counts. Accumulating error counts on a chassis or module are grounds for replacement even when the module is not currently faulted.
Intermittent faults are where a CMMS with good resolution notes pays for itself. If the last three times this fault appeared, the resolution was the same — a specific cable in a specific conduit — that pattern should be in the work order history. YAFEX surfaces exactly that kind of pattern from your plant's own data. Talk to us about making your Allen-Bradley fault history searchable for your whole maintenance team.
Ready to put this into practice?