Allen-Bradley PLC FAQ: Buying, Software, Manuals, and Market Share Questions

I've handled Allen-Bradley PLC orders and technical support for eight years now. In that time I've made - and written down - fourteen genuine mistakes, totaling roughly $18,000 in wrong parts, restocking fees, and last-minute freight. That file of embarrassments became our team's ordering checklist, and the answers below are the lessons from it, in the order customers actually ask them.

Here is what this article covers:

• What an Allen-Bradley PLC actually is
• Micro800 vs. CompactLogix vs. ControlLogix: which one to buy
• The software you need (and one common mix-up)
• Allen-Bradley PLC-5 manual and legacy support
• Siemens vs. Allen-Bradley market share in Mexico
• Backorders and whether rush shipping is really worth it
• The firmware question people ask too late

What is an Allen-Bradley PLC?

An Allen-Bradley PLC is a programmable logic controller sold under the Allen-Bradley brand, which is part of Rockwell Automation. The name has been around for more than a century - Allen-Bradley's roots go back to Milwaukee in 1903 - and Rockwell Automation acquired the company in 1985. A PLC, in plain terms, is a hardened industrial computer. It reads inputs such as push buttons, limit switches, proximity sensors, and analog instruments, runs a program in a continuous loop, and turns outputs on or off based on that logic.

When someone says 'Allen-Bradley PLC,' they usually mean one of three current families. Micro800 covers small, low-cost controllers. CompactLogix handles mid-size machines and production cells. ControlLogix is the high-end platform for large systems, redundancy, and complex process or motion control. Two older families, PLC-5 and SLC 500, still run in thousands of plants even though they are discontinued.

Which Allen-Bradley PLC should I choose?

Most of the requests I see ask for 'an Allen-Bradley PLC' without naming a family. That matters more than people think, because the family decides your programming software, network options, spare parts stock, and the skills your maintenance team needs.

If the machine is small and standalone, the Micro800 line is worth a look. It programs in Connected Components Workbench, which is free. But free software isn't free training: if your plant already standardizes on Studio 5000, choosing a Micro800 forces your electricians to learn a second environment. I've watched customers burn more money on that learning curve than they saved on the controller.

CompactLogix controllers, especially the 5380 series with 5069 I/O, sit in the middle: a strong instruction set, EtherNet/IP, motion options, and a less punishing price than ControlLogix. ControlLogix is what we suggest when the job needs redundant processors, high availability, or lots of distributed I/O.

The rule I use now is simple: don't buy the cheapest family, and don't buy the most powerful one. Buy the platform the people on site can support on a Tuesday afternoon. That rule would have saved me from a very awkward phone call early on.

What software do I need for an Allen-Bradley PLC?

This causes more confusion than it should, because the Allen-Bradley families do not share one programming package:

• Micro800: Connected Components Workbench (CCW), free
• CompactLogix and ControlLogix: Studio 5000 Logix Designer (formerly RSLogix 5000)
• SLC 500 and MicroLogix: RSLogix 500
• PLC-5: RSLogix 5

Wait - one correction. SLC 500 and MicroLogix are legacy products now; Rockwell has been phasing them out for years. Plants still run them, which is exactly why RSLogix 500 still appears on maintenance department PCs.

There is also a version rule that catches people: your Studio 5000 release has to support the controller's firmware revision. An older version of Studio simply will not connect to a newer controller. We get 'cannot find controller' calls that turn out to be nothing more than a version mismatch.

Is the PLC-5 still supported, and where can I find the Allen-Bradley PLC-5 manual?

The PLC-5 family - the 1785 controllers - has been discontinued for a long time. But 'discontinued' is not the same as 'gone.' We still see PLC-5s running mixers, packaging lines, and material handling systems built in the 1990s.

The manual itself is still easy to get. Rockwell Automation keeps legacy documentation free in its literature library at literature.rockwellautomation.com. Search for '1785' and look for the 1785-UM user manual series. I want to say that is the right publication prefix, but don't quote me on it; searching 'PLC-5 manual' will put it on the screen faster than I can remember numbers.

The harder question is whether to keep that old system running or migrate it. The trap is migration cost. When I first quoted a PLC-5 to ControlLogix migration, I priced the processor, chassis, and software, and forgot that the plant's remote racks were 1771 I/O. The surprise was not the new controller's price. It was the conversion modules and rewiring needed to make old remote I/O talk to the new system.

PLC market share: Siemens vs. Allen-Bradley in Mexico

People ask this one all the time, and the honest answer is that it depends on who is counting. Market share studies measure shipments, revenue, or installed base, and the rankings shift depending on the region and industry. Any vendor or engineer who gives you one permanent number is simplifying.

What I can tell you from the plants and distributors we support in Mexico: plants built to U.S. OEM standards, especially in food and beverage and automotive components, are heavily Allen-Bradley. Plants that arrived with European machinery, particularly German packaging and machine tool lines, are often Siemens. Both brands have a large installed base, strong local distributors, and capable support people in Mexico.

So the practical answer is less exciting than the argument. Choose the platform that matches the plant's existing standards, the OEM's specification, and local spare parts availability. In a market as competitive as Mexico, the installed base in your own plant matters more than the global pie chart.

Why is my Allen-Bradley part on backorder, and is rush shipping worth it?

After the semiconductor shortages of 2021 to 2023, a lot of distributors stopped promising firm dates. Nobody wanted to be the one who said 'two weeks' and then called back with eight. Some of that caution is still visible in quotes, especially for legacy modules and controllers with long production runs.

So should you pay the expedite premium? My answer is: ask what an unplanned day of downtime costs first. In March 2024, we paid roughly $430 in freight to fly a single 1756-EN2T module to a food plant. The customer's shutdown window was measured in hours; their line was worth thousands of dollars per hour while running. That $430 was the cheapest part of the week.

What you are really buying with a rush charge is certainty. Not speed for its own sake, but a confirmed date you can plan around. A quote that ends in 'probably' is not a quote. In an emergency, the cheapest option with an unconfirmed ship date is the most expensive thing on the table.

Rush shipping is not about going faster. It is about having a date you can trust.

Why do two Allen-Bradley modules with the same catalog number act differently?

This is the question nobody asks until 2 a.m.: firmware revisions.

Every networked Allen-Bradley module leaves the factory with firmware on it. A module built in 2018 and a module built in 2024 can have the same catalog number but different firmware revisions. In Studio 5000, the controller expects a specific major revision. If the replacement module's revision does not match, the slot can show a fault or refuse to connect even though the hardware is perfectly fine.

I learned this the expensive way. We skipped the firmware check on a spare module because we were rushing, and 'it's basically the same part.' It was the one time it mattered. The customer installed the module, the processor would not establish a connection, and a 15-minute swap turned into a $900 after-hours troubleshooting call. The module was not defective. Its firmware was simply older than what the controller required.

Now our checklist has a firmware revision field at the top, checked before any module ships. So glad we added it. Last month it caught a spare that had been sitting on a shelf for two years. One minute of checking saved someone else from repeating my $900 lesson.