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. Meet them all.
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, one tool for CompactLogix, ControlLogix & GuardLogix. Prototype on a CompactLogix, scale to a ControlLogix, re-target and remap.
🔧 Connected Components Workbench — the separate tool for the Micro800 family. Different software, different file — don't expect a Micro850 to open in Studio 5000.
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) rides alongside the standard controllers.
Source : rockwellautomation.com
Skim the left panel for the plain-language version; dive into the right for the generations and a selection rule. Mind the one fork: most of the family shares Studio 5000, the Micro800 branch doesn't.
Allen-Bradley controllers climb a ladder — but mind one fork: most run the Logix engine in Studio 5000; the little Micro800 family doesn't.
Mental model: one family, two passports. CompactLogix / ControlLogix / GuardLogix share the Studio 5000 passport; Micro800 carries a different one (CCW).
The same Logix engine ports across CompactLogix → ControlLogix; Micro800 is the separate-toolchain exception.
Selection rule: tiny standalone machine → Micro800 (CCW). Machine / skid → CompactLogix. Plant area / big line / redundancy → ControlLogix. Any of them need safety → the GuardLogix variant.
Source : rockwellautomation.com
A machine ships with a Micro850. Which software do you open to program it?