Deep dive · the Modicon controller family

The Modicon Family

Schneider runs two distinct controller lines — and two distinct engineering tools. Machine controllers on EcoStruxure Machine Expert, process PACs on EcoStruxure Control Expert. Meet both ladders and keep them straight.

🟢 Machine line🔵 Process line
01 · Two lines, two tools

Mind the platform split

This is the one thing not to mix up. The compact M2xx machine controllers are programmed in EcoStruxure Machine Expert (CODESYS-based). The modular M340/M580 process PACs are programmed in EcoStruxure Control Expert — a completely separate tool. Same vendor, two worlds.

🟢 Machine line — M221 · M241 · M251 · M262. Compact logic & motion controllers for OEM machines. Tool: EcoStruxure Machine Expert (CODESYS-based).

🔵 Process line — M340 PAC & M580 ePAC. Modular controllers for process & infrastructure, with Hot Standby. Tool: EcoStruxure Control Expert.

02 · Choose your controller

Two ladders, side by side

Each line climbs its own ladder. Tap a model to match it to a job — and notice the engineering tool changes with the line.

Machine Expert · CODESYS-based
🪜 machine controllers↑ more
Control Expert · PAC / ePAC
🪜 process PACs↑ more

Source : se.com

03 · New here, or going deep?

Two tracks, two controller lines

Skim the left panel for the plain-language version; dive into the right for the real split. The one rule to keep straight: the engineering tool changes with the line.

🌱 New to this? Beginner

Schneider has two separate controller worlds — and the software tool changes with the world.

  • Machine line (M221 → M262): compact controllers for OEM machines, programmed in EcoStruxure Machine Expert (CODESYS-based).
  • Process line (M340, M580): modular PACs for process & infrastructure, programmed in EcoStruxure Control Expert.
  • Same logo on the box, two different tools — that is the one thing not to mix up.

Mental model: two ranges under one parent brand — a city-car line and a heavy-truck line. Same badge, totally different garages and tools.

⚙️ Go deeper Advanced

Pick the line first (machine vs process), then climb that line's ladder.

  • Machine: M221 (nano) → M241 → M251 → M262 (logic + motion flagship).
  • Process: M340 modular PAC → M580 ePAC.
  • The M580 is an ePAC: Ethernet in the backplane, a deterministic RIO ring, and Hot Standby CPU redundancy.

Selection rule: OEM machine, compact, CODESYS-style workflow → Machine line (size by I/O + motion, M221→M262). Process / infrastructure, modular, needs redundancy → Process line (M340, or M580 for Hot Standby).

🧩
Picture it
Hot Standby is a co-pilot flying the exact same flight in sync — if the captain drops out, the co-pilot already has the controls and the plane never wobbles.
⏱️
Pick the right line in 10 seconds
1Building an OEM machine, want the CODESYS-style tool? → Machine line (M221–M262) in Machine Expert.
2Process / infrastructure with modular I/O? → Process line (M340) in Control Expert.
3Can't tolerate a controller outage? → M580 ePAC with Hot Standby.
⚠️
Common mistake
Expecting an M580 project to open in Machine Expert (or an M262 in Control Expert). The two lines use different tools — choose the tool with the line.

Source : se.com

04 · Check yourself

One quick question

What makes the M580 an "ePAC", and what does it add over the M340?