Deep dive · the Allen-Bradley controller family

The Logix hardware family

Allen-Bradley controllers climb a clear ladder: Micro800 for small standalone machines, CompactLogix for machines and skids, ControlLogix for big lines. Most run the same Logix engine in Studio 5000, but one branch doesn't. This page covers each of them.

🧱 Micro800 → ControlLogix🛡️ GuardLogix
01 · Two toolchains

Mind the software split

CompactLogix, ControlLogix and GuardLogix all run the same Logix engine and are programmed in Studio 5000 Logix Designer, so a program ports across the family. The Micro800 family is the exception: it's programmed in the separate, free Connected Components Workbench (CCW), not Studio 5000.

🧩 Studio 5000 Logix Designer: one engine and one tool for CompactLogix, ControlLogix & GuardLogix. Prototype on a CompactLogix, then scale to a ControlLogix by re-targeting the controller and remapping the I/O.

🔧 Connected Components Workbench is the separate tool for the Micro800 family. It is different software with a different file, so don't expect a Micro850 to open in Studio 5000.

02 · Choose your controller

The Logix ladder

The ladder runs from a Micro800 on a small machine to a ControlLogix running a plant area. Tap a model to match it to a job. The safety variant (GuardLogix / Compact GuardLogix) sits alongside the standard controllers.

🪜 choose your controller↑ more capacity

Source : rockwellautomation.com

03 · New here, or going deep?

Two tracks up the Logix ladder

Skim the left panel for the plain-language version, or read the right one for the generations and a selection rule. Mind the one fork: most of the family shares Studio 5000, but the Micro800 branch doesn't.

🌱 New to this? Beginner

Allen-Bradley controllers climb a ladder, with one fork to watch: most run the Logix engine in Studio 5000, and the little Micro800 family doesn't.

  • Small standalone machines → Micro800 (Micro810/820/850/870), programmed in the free Connected Components Workbench.
  • Machines and skids → CompactLogix; big lines and process → ControlLogix, both programmed in Studio 5000.
  • Need safety? GuardLogix (and Compact GuardLogix) add a safety engine right alongside.

Mental model: one family, two passports. CompactLogix / ControlLogix / GuardLogix share the Studio 5000 passport; Micro800 carries a different one (CCW).

⚙️ Go deeper Advanced

The same Logix engine ports across CompactLogix → ControlLogix; Micro800 is the separate-toolchain exception.

  • Micro: Micro810/820/850/870, programmed in CCW, not Studio 5000.
  • CompactLogix: 5370 / 5380 / 5390 / 5480, compact and often a single box.
  • ControlLogix: 5570 / 5580 / 5590, large 1756 chassis with redundancy options.
  • GuardLogix = the safety variant of Logix (Compact GuardLogix on the CompactLogix side).

Selection rule: tiny standalone machine → Micro800 (CCW). Machine / skid → CompactLogix. Plant area / big line / redundancy → ControlLogix. Any of them need safety → the GuardLogix variant.

🧩
Picture it
The Logix family is one ladder you re-target up and down; Micro800 is a different ladder leaning on the same wall. It looks similar, but it is a separate climb with a separate tool.
⏱️
Pick the right controller in 10 seconds
1Small standalone machine, lowest cost? → Micro800 (program in CCW).
2A machine or skid? → CompactLogix (5380 is the modern default).
3A plant area, big line, or redundancy? → ControlLogix (5580 / 5590). Add GuardLogix for safety.
⚠️
Common mistake
Buying a Micro850 and expecting to open it in Studio 5000. The Micro800 family lives in Connected Components Workbench, which is a different tool with a different file.

Source : rockwellautomation.com

04 · Check yourself

One quick question

A machine ships with a Micro850. Which software do you open to program it?