Unity Pro to EcoStruxure Control Expert: migration without

For Schneider Electric EcoStruxure Control Expert V15+.

Unity Pro V11/V13 projects open in Control Expert V15+ with a one-time migration. Here is what converts cleanly, what needs hand work, and what to test. 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

Unity Pro V11/V13 projects open in Control Expert V15+ with a one-time migration. Here is what converts cleanly, what needs hand work, and what to test. 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. Audit the source Unity Pro project

Open the project in Unity Pro V11 or V13. PLC > Project Properties > General tab — note the project version, the target CPU model (M340, M580 if early V13), and the section count by language. Tools > Cross References — capture the FB call graph. Save the project as .stu (Unity Pro source format). Control Expert V15+ accepts .stu directly; older .ssu source-only files need an intermediate save in Unity Pro V11 first.

2. Open in Control Expert V15+

Control Expert V15+ > File > Open. Browse to the .stu file. The migration tool runs automatically and asks: target firmware (pick the latest stable for the CPU), target Control Expert version (V15 default), and whether to preserve absolute addressing. Click Migrate. The tool produces a new .stu file under Control Expert format, plus a .log file with every conversion note.

3. Triage the migration log

Common log entries: 'EFB replaced — IODDT_T_ANA_IN_GEN replaced by analog channel struct' (action: rewire EFB calls); 'Section language reset to LD due to unsupported FBD construct' (action: re-author the section); 'DFB instance count adjusted' (action: verify each instance still maps to its original tag). The pattern: warnings are usable as-is; errors block compilation until manually fixed.

// Migration log shape (excerpt)
// Section: MotorControl, Language: LD, Status: Migrated
// DFB: PID_Wrapper, Status: Migrated, 2 warnings
// EFB: READ_VAR replaced with READ_VAR_M580
// DDT: Motor_UDT, Status: Migrated

4. Rebuild and test in simulator

Build > Rebuild All Project (Ctrl+Shift+B). Errors must hit zero before testing. Control Expert ships with a built-in simulator: PLC > Simulation Mode > Connect. Set Address (PLC > Set Address) to 127.0.0.1 — the sim listens locally. Transfer Project to PLC. Animation tables show live values; force a few inputs and watch the program respond. Catch timer scaling differences and EFB signature changes here, not on hardware.

5. Plan the on-site download

Take an upload from the running CPU (PLC > Transfer Project from PLC) before any download. Schedule cutover during a planned outage. Set Address to the live CPU IP. Transfer Project to PLC — Control Expert prompts for a stop confirmation. After download, retentive variables retain values only if 'Save initial values to retain' was ticked in the source project; otherwise the running state is reset to declared initial values.

Common mistakes

• Assuming the migration converts cleanly for any Unity Pro version — V8 and V9 projects need an intermediate V11 save before Control Expert will open them at all
• Skipping the simulator test and going straight to hardware — EFB signature changes only fail at runtime and can leave the plant in an unsafe state on first cycle
• Forgetting to preserve absolute addressing for SCADA-bound variables — Control Expert renumbers Mxxx and %MWxxx in some cases and the SCADA loses its bindings
• Migrating a hot-standby M580 project without first applying the Control Expert V15 SP3 patch — the hot-standby sync block conversion is broken in the un-patched migrator

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

Unity Pro to EcoStruxure Control Expert: migration without surprises 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 unity pro to ecostruxure control expert: migration without surprises 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. Unity Pro to EcoStruxure Control Expert: migration without surprises 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.