EcoStruxure Control Expert: project structure for Modicon

For Schneider Electric EcoStruxure Control Expert V15+.

Control Expert is the V15+ replacement for Unity Pro. Project tree, derived data types, sections, and where to actually write the code. This page is the working engineer's read — what the menu paths actually are in EcoStruxure Control Expert V15+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program Modicon M340 / M580 ourselves, daily; we are not a Schneider Electric sales channel.

What this is and when you need it

Control Expert is the V15+ replacement for Unity Pro. Project tree, derived data types, sections, and where to actually write the code. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of EcoStruxure Control Expert V15+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Open the Project Browser

Control Expert opens to the Project Browser on the left. The tree groups: Configuration (rack, CPU, modules), Derived Data Types (your custom DDTs and DFBs), Variables & FB instances (the global tag pool), Tasks (MAST, FAST, AUX0, AUX1), and the Animation Tables and Operator Screens at the bottom.

2. Configure the rack and CPU

Double-click 'Configuration' > the rack item. The hardware editor opens. Drop modules from the right-hand catalog. For an M580, the CPU sits in slot 0 of the local rack; remote drops via the X80 backplane are added as separate racks under 'Remote Bus'. Save (Ctrl+S) — the analyser flags slot conflicts immediately.

3. Define DDTs

Derived Data Types — Schneider's UDT equivalent — live under 'Derived Data Types'. Right-click > 'New Data Type'. Add fields with type, comment, and (for arrays) bounds. DDTs are how you carry instrument data — a Motor DDT might carry running, fault, hours, command. Save and the type becomes available in the Variables editor.

// Motor DDT example
// Running   BOOL
// Fault     BOOL
// Hours     UDINT
// Command   BOOL

4. Create a program section

Tasks > MAST > Sections > right-click > 'New Section'. Pick a language: LD (ladder), FBD, ST, IL, or SFC. Sections are the smallest schedulable unit Control Expert understands — each section runs to completion within its task before the next section begins. Order the sections via the Section Properties dialog; lower order = runs first.

5. Build, download, and animate

Build > Rebuild All Project (Ctrl+Shift+B). Errors appear in the Output window. Set Address (PLC > Set Address) to your CPU IP. Connect (Ctrl+K). Transfer Project to PLC. Animation tables let you watch and force values; right-click any tag in the editor and 'Initialise Animation Table' to add it. Forcing a tag requires the keyswitch on the CPU to be in 'F' position on hardware that supports it.

Common mistakes

• Mixing IEC 61131-3 languages within one section — Control Expert allows one language per section, so trying to drop ladder rungs into an ST section silently fails
• Editing the Configuration after a download without rebuilding — the CPU keeps the old configuration and field changes don't apply, which can be safety-critical for IO mapping
• Forgetting that DDTs are pass-by-value when used as section parameters — modifications inside a derived FB don't propagate back to the caller without explicit IN_OUT pins
• Not naming sections meaningfully — Section1, Section2, Section3 makes a 40-section project unmaintainable

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

EcoStruxure Control Expert: project structure for Modicon M580 is one of the building blocks. The full Schneider Electric curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Schneider Electric is the right call versus a different brand — see the brand hub. For region-specific context on where Schneider Electric dominates the SA install base, see the relevant city pages under /brands/schneider/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Schneider Electric curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Schneider Electric expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Schneider Electric's own documentation is the canonical reference once you are working on real hardware: Schneider Electric Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Schneider Electric programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Schneider Electric's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running ecostruxure control expert: project structure for modicon m580 in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Schneider Electric curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Schneider Electric install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Schneider Electric programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. EcoStruxure Control Expert: project structure for Modicon M580 fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.