PLC Simulator
Modicon and Control Expert practiceProgramming + simulator

Schneider PLC Programming and Modicon Simulator

Practice Schneider-style IEC Instruction List, rack/module/bit addresses and legacy Modicon references in a browser—then move the verified logic into EcoStruxure Control Expert.

Run your first PLC program — no signupStudy the address map

Independent learning tool. No hardware connection, vendor project import or controller download. Technical scope verified August 7, 2026.

Program memory
Schneider / Modicon IL
(* 0:00001 = start, 0:00002 = stop *)LD    0:00001ANDN  0:00002ST    1:00001
INPUTOUTPUT

Supported Schneider practice path

Every capability below is tied to the current parser instead of a generic vendor claim.

  • IEC IL contacts, stores and latches
  • Three-segment rack/module/bit addresses
  • Legacy 0:, 1: and 4: Modicon references
  • Clear single-rack runtime boundary

Two address traditions appear in Schneider maintenance work

Unity Pro and EcoStruxure Control Expert projects use IEC-style located variables, including rack/module/bit forms such as %I0.1.0. Older Modicon material may use reference families such as 0:00001, 1:00001 and 4:00001.

The browser parser accepts both forms so learners can practice translating existing logic. It models one training rack and therefore collapses the rack segment rather than reproducing a complete Modicon hardware configuration.

Schneider’s software family matters: Machine Expert and Machine Expert Basic serve different machine-controller ranges from Control Expert. The parser documented here targets the Unity/Control Expert IL and Modicon addressing context, not every Schneider controller under one label.

Address translation sheet

Read the memory map before the rung

These are the address forms this learning runtime recognises. The final column states the simulator behavior, including intentional simplifications.

Device / areaRoleExampleBrowser behavior
%I / %QLocated IEC I/O%I0.1.0, %Q0.0.0Three segments collapse to module.bit because the training runtime models one rack.
0:Legacy discrete input0:00001Converts a one-based Modicon reference to runtime input memory.
1:Legacy discrete output1:00001Converts to the matching runtime output bit.
4:Holding register4:00001Maps the one-based reference to %MW0.
%M / %MWInternal bit / word%M0.0, %MW0Runs as native internal memory in the training engine.

Executable now

Supported instruction groups

IEC IL logic
LD, LDN, AND, ANDN, OR, ORN and NOT
Grouping
AND(, OR( and closing parenthesis
Outputs and latches
ST, STN, S and R
Address translation
IEC two/three-segment and Modicon 0:/1:/4: forms

Do not assume

Not in the current subset

  • %KW constant words
  • Complete Unity/Control Expert instruction and function-block libraries
  • Multiple racks, module configuration and device communication
  • Safety PLC behavior, process I/O fidelity and production commissioning

Choose the right simulator

Browser practice vs official engineering simulation

Both are useful, but they answer different questions. Start here to make the logic observable; use the vendor environment to validate a real controller project.

DecisionThis browser simulatorOfficial vendor environment
Primary jobLearn syntax and scan behavior quicklyEngineer a project for a selected controller
Runtime scopeThe exact subset published on this pageController- and version-specific implementation
Project formatText exercises inside the training appNative vendor project, libraries and configuration
Hardware transferNot supportedUpload, download and online diagnostics

Worked example

A legacy Modicon start/stop output

The parser translates the one-based 0: input references and 1: output reference into the training I/O bus before execution.

Run your own program
Schneider / Modicon ILParser-valid example
(* 0:00001 = start, 0:00002 = stop *)
LD    0:00001
ANDN  0:00002
ST    1:00001

Learning sequence

Practice the translation, then the logic

  1. 01

    Identify the address family

    Separate located IEC variables from legacy Modicon references before editing.

  2. 02

    Normalize one rung

    Translate the input and output points, then follow LD/ANDN/ST.

  3. 03

    Add grouping and state

    Practice parenthesised branches plus S/R behavior in small programs.

  4. 04

    Validate in Control Expert

    Configure the real rack, modules, tasks and controller-specific instructions.

Engineering boundary

A syntax-and-logic simulator, not Control Expert

This page supports learning and legacy-code interpretation. It does not emulate a Modicon CPU, Unity project, rack, fieldbus or safety execution environment.

  • The first rack segment is deliberately discarded by the one-rack training runtime.
  • %KW constant words are rejected instead of approximated.
  • Use official tools and hardware tests for every production decision.

Technical evidence

Sources and verification

Page claims and the simulator support matrix were reviewed against the production parser and these primary technical sources on August 7, 2026.

Continue through the cluster

Related programming and simulator guides

PLC Instruction List simulator

Learn the common IL accumulator model behind the Schneider subset.

CODESYS alternative

Compare another IEC-oriented learning and engineering path.

PLC programming simulator

Explore the broader vendor-neutral practice environment.

Questions

Schneider PLC Programming and Modicon Simulator FAQ

Yes. The parser accepts those legacy input, output and holding-register references and maps them into the training runtime.

Practice Schneider and Modicon address translation

Run a small IL program, inspect the mapped I/O, and build confidence before touching a controller project.

Run your first PLC program — no signupCompare all dialects

Independent vendor-platform field guide

Schneider PLC programming simulator: transfer checklist

Direct answer

The learner can test a bounded IEC behavior and identify the exact controller family, engineering suite, device and runtime assumptions still requiring official validation.

Written for learners and technicians transferring IEC 61131-3 skills into Schneider controller, software, device and simulation contexts.

System map / 02

NODE 01observable

Platform context

The Schneider controller family, engineering product, software version, firmware, IEC language, device configuration and simulation need.

NODE 02observable

Tags and addressing

Typed variables and IEC logic through task execution, simulated I/O and generic machine feedback.

NODE 03observable

Reference pattern

A start-stop, timer, counter and data example compiled and observed from a known state.

NODE 04observable

Timing and limits

Software-family mismatch, device support, library, retentive state, task timing, simulation and restart.

NODE 05observable

Diagnostics

A project, device, library, syntax, task, mapping or feedback mismatch.

NODE 06observable

Official-tool transfer

The example recreated, compiled and tested in the correct official Schneider environment and target.

PLC dialect transfer path

Keep the control pattern while the syntax changes

Compare address families and mnemonics around the same machine task, then validate the final project in the target vendor tool.