Troubleshooting
Recovering a Magelis HMI project with Vijeo Designer
Short answer
A Magelis panel returns an editable project only when the application was transferred with the Vijeo Designer option Include Editor Project enabled; Data Manager then retrieves the source. Without it there is no documented full-panel image backup, and recovery depends on the exact model's storage design.
On this page
You get an editable project back from a Magelis HMI only when the application was downloaded with the Vijeo Designer option Include Editor Project enabled; the Data Manager tool in Vijeo Designer then retrieves that source from the running panel. When the option was off, there is no documented full-panel image backup of the kind ProSave makes for Siemens terminals — that other world is covered in OP15 recovery with ComText, ProTool or ProSave — and what is left depends on the exact model's storage design. Work it in this order: confirm the transfer option, run the Data Manager retrieval, and only then look at cards and hardware.
What the transfer option decides #
The setting lives in the Vijeo Designer project, under Target Properties in the Download properties: a check box labeled Include Editor Project. Ticked, the download writes the editor project onto the panel as a .VDZ backup archive alongside the runtime. Unticked, the panel receives the runtime only, and the runtime is never an editable source — the same distinction drawn in why an uploaded HMI copy is not an editable project.
A panel that runs the application proves nothing either way, because the runtime always ships and the source ships only on request. Confirm the setting from the original project on the engineering PC, or from the transfer record. If neither exists, run the retrieval as a test: it either returns a .VDZ project or returns nothing, and it changes nothing on the panel.
Retrieve the source with Data Manager #
Data Manager is the documented route into a live HMI programmed with Vijeo Designer. Retrieving logged data from the target is its documented use, and the editor project comes back through the same connection when it was stored there. Access to a target is configured in the Vijeo Designer installation, so if the tool refuses the connection, that access configuration is the first thing to check.
- Confirm the transfer option was ticked for the download that is on the panel, or accept the attempt as a test.
- Connect the engineering PC over the link the project was configured for —
Ethernetwhere the target was set up for it, serial where it was not. - Open Data Manager in the installed Vijeo Designer version, connect to the target, and run the retrieval of the editor project.
- Open what comes back, check it is the application this machine runs, and keep the retrieved file as the recovery baseline; edit a working copy, never the baseline.
Targets in the GXU range are a different toolchain: the documented upload for an HMIGXU3500 runs from Vijeo Designer Basic V1.1 or later, opened with the menu command Build > Download and the upload operation chosen in that transfer dialog.
Before anything goes back onto the panel, put the machine in a safe state: a restore to the wrong target, or an older revision of the project, changes how outputs behave on restart.
The four recovery paths compared #
| Path | Prerequisite | What you get | Limit |
|---|---|---|---|
| Data Manager retrieval | Include Editor Project was ticked at the last download | The editable Vijeo Designer project | Returns nothing when the source was never stored on the panel |
| Removable card copy | The model keeps application data on an accessible SD or CompactFlash card |
The card's contents | Contents and restore steps are model-specific; a copy is not automatically a restorable image |
| Board-level flash read | Flash sits on separately mounted chips and a specialist reads them | A raw memory dump | A dump is neither a project nor a proven image; not a field repair |
| Microcontroller-integrated flash | None available in the field | Nothing by ordinary means | Source effectively gone; laboratory work only |
When the option was never set #
Read the exact model identifier off the nameplate and check that model's documentation for its storage media and its supported recovery. Some units hold recoverable data on one or two removable cards, SD or CompactFlash; older generations use other arrangements. Handle the media defensively: copy it without writing to it, keep the original untouched, and prove on a bench panel what a restore from the copy actually rebuilds.
Do not open the housing expecting a documented extraction path — for this case there is none. Where the flash is soldered on as separate chips, reading it is specialist equipment work that yields a dump, not a project, and a dump only becomes a backup once a restore from it has been demonstrated on the same model. Where the flash is integrated inside the microcontroller, the contents are effectively unreachable at field level.
A worked case, two panels #
Panel 1 is a GTU terminal and the engineering PC still has its project. The Download properties show the option was ticked on the last download, so Data Manager connects over Ethernet and the retrieval returns the source in one pass. It opens, its target settings match the machine, and it is archived with the machine documentation. Decision: recovered, and the option stays ticked for every future download to this panel.
Panel 2 is an older Magelis with no records. The retrieval runs and returns nothing, which settles the question: the source was never stored. The nameplate gives the exact model, and that model's documentation shows a CompactFlash card carrying the application. The card is copied without writing to it, the copy restores the application to a bench panel, and the machine keeps running from its own card. Decision: the copy is the operational backup; the editable source does not exist, and the screens are rebuilt as a new project at the next planned outage.
Decision for each case #
- Option confirmed, or unknown: run the Data Manager retrieval and open what returns. One attempt settles it.
- Option off, documented removable card: copy the card, prove a restore from the copy, and treat the copy as the operational backup. The editable source still has to be rebuilt — replacing an old HMI when no project files exist covers that rebuild.
- Option off, no documented card path, flash on separate chips: a specialist dump is the last resort, and it counts as a backup only after a restore from it has been demonstrated on the same model.
- Flash integrated in the microcontroller: the source is gone. When the terminal is also at end of life, rebuild the screens onto industrial panel PCs running the HMI runtime at the machine instead of sourcing another terminal of the same generation.
Make the next recovery routine #
For the panels still in service, the protection is procedural: tick the transfer-time option from the first section before the next download, switch on the auto backup feature in Vijeo Designer 6.2 so the engineering side keeps its own recovery copies, and run one retrieval per panel so the path is proven before it is needed. When the engineering PC reaches the panel only across a routed network, the connection is the same one a remote transfer uses — downloading a Vijeo Designer project to a remote HMI over VPN covers that setup.
Questions asked
Can I make a full image of a Magelis panel before replacing it?
No documented equivalent of a full-panel image exists. The nearest mechanism is the file system transfer to a USB drive, which writes a project you already have onto a panel's file system: it restores from a source, it does not clone a running terminal. Before replacing a panel, enable the transfer option, retrieve the source with Data Manager, and archive the engineering project files instead.
The old unit has a CompactFlash or SD card inside. Is a copy of it a backup?
Only when the model's documentation defines what the card holds and how it is restored. Some Magelis models keep recoverable application data on removable cards; others use them for recipes and logged data only. Treat a copy as a backup only after a restore from it has been demonstrated on a bench panel of the same model.
Can the project be saved from a panel where the option was never enabled?
Not through Vijeo Designer. The remaining routes are the model's removable card, if the documentation supports one, or a specialist read of the board's flash when the memory sits on separately mounted chips. Where the flash is integrated inside the microcontroller, the source is effectively gone and the application has to be rebuilt as a new engineering project.
How do I stop this happening on the panels still in service?
Enable the transfer option under Target Properties before every download, switch on the auto backup feature in Vijeo Designer 6.2 on the engineering side, and run one retrieval per panel to prove the path. Keep the recovered archives with the machine documentation so a future recovery never depends on the panel itself.