Schneider's Modicon world has its own logic — multiple tasks racing on one ePAC, a program sliced into Sections, topological I/O addresses that read like a postal code, and Modbus running in its veins. Learn it on real infrastructure: pumping stations, water treatment, power feeders — the machines Schneider actually runs.
How a Modicon ePAC actually runs your code: the MAST task (cyclic or periodic), the high-priority FAST task, event-triggered tasks, and how your program is carved into Sections that execute in order. Taught on a live pumping station with a CPU scheduler you can watch and preempt.
The Modicon address scheme: located variables mapped to real I/O by topological address (%I0.1.2), unlocated variables the CPU places, and the %M / %MW state RAM that doubles as the Modbus map. Why Schneider code reads like a rack diagram.
Control Expert speaks all five IEC languages plus SFC. Ladder for interlocks, FBD for signal flow, ST for maths, the legacy IL, and SFC (Grafcet) for sequential machines — with honest guidance on when each wins.
Schneider's reuse pair: the Derived Data Type (a struct you define once) and the Derived Function Block (your own reusable logic block with private memory). The Modicon answer to "write it once, deploy it everywhere."
The built-in toolbox: Elementary Function Blocks for timers, comms, PID and maths, the Library Manager, versioning, and building a project library your whole team pulls from.
The protocol Modicon invented, end to end: coils & registers, function codes, the %MW ↔ register mapping, serial Modbus vs Modbus TCP, and reading a device live. The lingua franca of industrial comms.
The modern Modicon architecture: the M580 ePAC with Ethernet in the backplane, distributed (DIO) and remote (RIO) I/O drops, Ethernet/IP scanning, and how a plant network hangs together.
Why infrastructure never stops: two M580 CPUs as primary & standby, state synced over a dedicated link, and a bumpless switchover when the primary fails. Build the redundant pair and pull the plug.
Debug the Modicon way: go online, build Animation Tables to watch & force variables live, read the diagnostic viewer & system bits/words (%S, %SW), and chase a fault to ground.
Critical infrastructure is a target. Application & section protection, the security profile, Achilles certification, disabling unused services, and defence-in-depth for a Modicon controller.
Open the Modicon to the level above: the M580's embedded OPC UA server, browsing the address space, certificates & security policies, and publishing tags straight to EcoStruxure and SCADA without a separate gateway.
Make the Modicon move: Lexium servo drives commanded from Control Expert with the Motion Function Blocks — power, home, then MC_MoveAbsolute. Drive a live axis, skip a step, and learn why "powered" isn't "referenced" — plus when machine motion belongs on the M262 line instead.
The face of the Modicon: Harmony panels designed in Vijeo Designer or EOTE, speaking Modbus TCP to located %MW registers. Run a live panel mock, flip to design mode to see the register bindings, and learn why the register map is a contract — and how the M580 data dictionary dissolves it.
The hardware deep dive — two lines kept distinct: the M221/M241/M251/M262 machine controllers (EcoStruxure Machine Expert) and the M340/M580 process PACs (Control Expert), as two choose-your-controller ladders.
The bigger picture: EcoStruxure Machine Expert (CODESYS-based, for the machine line) vs EcoStruxure Control Expert (for the M340/M580 PACs) — why they're separate tools, with an interactive compare.
The face of the Modicon: a live Harmony panel mock where buttons pulse %MW bits over Modbus TCP, the seal-in lives in the PLC, and a design-mode toggle reveals the register bindings — plus the scaling-convention trap and the data-dictionary escape hatch. Now live — open it →