Schneider Magelis HMI tag import from Control Expert

For Schneider Electric EcoStruxure Control Expert V15+.

Vijeo Designer pairs with Magelis HMI panels and imports tags from Control Expert via the .xvm tag-export format. The workflow and the gotchas. 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

Vijeo Designer pairs with Magelis HMI panels and imports tags from Control Expert via the .xvm tag-export format. The workflow and the gotchas. 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. Export the tag file from Control Expert

In Control Expert, open the project > Tools > Variables > Data Editor. Filter to the variables to expose to the HMI (typically a 'HMI_' prefix convention). File > Export > Variables. Choose XVM format. Save to a path Vijeo Designer can reach. The XVM is XML — readable, version-controllable, and re-importable on changes.

2. Create the Vijeo Designer target

Open Vijeo Designer V6.2+ > File > New Project. Choose target panel: Magelis GTO (5.7", 7", 10.4") or GTU (open box). Set the runtime resolution and the start screen. The Navigator pane on the left shows IO Manager, Variables, Panels, Reports, Recipes, Alarms — the working areas of a Vijeo project.

3. Add the IO Manager driver

Right-click IO Manager > New Driver > Modbus TCP/IP for an M580 over Ethernet, or Uni-Telway for an older M340 over USB. Set the equipment IP and slave address. Test connection — green tick = good, red cross = wrong path or driver. The driver becomes the conduit for every tag binding.

4. Import the XVM file

Right-click Variables > Import Variables. Browse to the XVM. Vijeo lists every variable with checkboxes — select the HMI_ prefixed ones, leave the rest. The mapping wizard binds each variable to the IO Manager driver. Click Finish. The Variables list now shows the imported tags with type, address, and driver source.

// XVM excerpt (Control Expert export)
// <variable name="HMI_Motor1_Status" type="BOOL" address="%M100"/>
// <variable name="HMI_Tank1_Level" type="REAL" address="%MF200"/>
// <variable name="HMI_Recipe_Name" type="STRING" address="%MW300"/>

5. Bind a screen object and download

Open a panel screen. Drop a Numeric Display object. Properties > Variable > pick HMI_Tank1_Level from the dropdown. Properties > Format > select REAL with 2 decimal places. Build > Compile (F7). Errors flag tag-binding issues. Download via Build > Download — over Ethernet for GTO, over USB for GTU. The runtime starts on completion.

Common mistakes

• Importing the full variable list without filtering — the HMI ends up polling 5000 unused tags and the panel scan slows past 500 ms
• Re-importing after a Control Expert tag rename without checking the old tag is removed — the orphan tag stays bound to a screen object and shows '???' at runtime
• Mixing Modbus TCP and Uni-Telway drivers in one project without setting different update rates per driver — the slow Uni-Telway tags drag the whole panel
• Forgetting that XVM exports do not include comment fields by default — operator-helpful descriptions are lost unless 'Include comments' is ticked at export

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

Schneider Magelis HMI tag import from Control Expert 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 schneider magelis hmi tag import from control expert 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. Schneider Magelis HMI tag import from Control Expert 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.