"Studio 5000" is the umbrella; Logix Designer is the controller-programming app inside it (the old RSLogix 5000, renamed). Around it sit the controller families — ControlLogix, CompactLogix, GuardLogix — and the wider FactoryTalk world for HMI and data. Here's the map, plus a tool to pick the right controller.
They all run the same Logix engine and the same Studio 5000 — so your skills carry across the whole family. They differ in size, I/O style and whether they do safety. Answer the two questions and get a recommendation.
Because it's one engine and one toolset, you can prototype on a CompactLogix and scale to a ControlLogix without relearning anything — the program ports, you just re-target the controller and remap I/O. That portability across the family is the quiet superpower of the Logix platform.
CompactLogix, ControlLogix and GuardLogix share the Logix engine and Studio 5000; the Micro800 family is the exception — it uses the separate Connected Components Workbench. Want the full ladder, generation by generation? See the Logix Hardware Family deep dive.
That's the Rockwell stack end to end: design the logic in Logix Designer, visualise it in FactoryTalk View, connect it with Linx, and mine it with Historian — all speaking the same tag database you built in Track 02. You've now toured the whole Logix world.
A colleague mentions "RSLogix 5000." What's the modern name for that controller-programming application?