How-to
Replacing an old HMI when no project files exist
Short answer
There is no free configuration software for a legacy Magelis or PanelMate panel that arrived without it, so choose one of three licensed routes: buy the matching engineering package, hire an integrator who owns it, or have a distributor upload and print. If no editable project can be recovered, capture the running application, map every tag against the live controller, and rebuild on confirmed writes.
On this page
There is no free configuration software that will open a Magelis or a PanelMate project, and the file inside the panel is unreadable without the engineering package that matches its model generation. So the decision is not whether to recover but which licensed route you take, and the first concrete step is the same either way: read the model and catalog number off the terminal label and match it to its package — Vijeo Designer (the upload examples use version 6.2) for the Magelis terminals it supports, EcoStruxure Operator Terminal Expert for the current Magelis line, the Visual Designer import tool for PanelMate. Buy the package, hire an integrator who owns it, or have a distributor perform the upload and print the result. If no editable project can be recovered, the running machine becomes the specification: capture the screens and behavior while the old terminal still works, map every tag against the live controller, and prove each write before you retire the panel. The sections below walk that path end to end, including a two-point check that recovers an analog scaling from observed states.
Confirm the terminal and hunt for an existing source #
Start with the label, not the software. Photograph the full model and catalog number on each terminal, its connectors, and every cable run to the PLC, network device, or printer it touches. Power each terminal under normal machine conditions and record whether it reaches the application, sits on a system screen, or reports a fault; a terminal that cannot run closes the capture path later in this article.
Then search before you spend. Engineering PCs, removable media, equipment files, and the original machine build folder may hold an editable project, an export, a printout, or screenshots, and a real source file changes the whole job — reading an old HMI program before panel replacement shows how to open and document one. A printout found in the machine file can settle most of the tag map on its own.
The model number also decides which package could ever open an uploaded file. The Magelis range spans several software generations: the low-end XBT N/R/RT range has its own configuration package, documented as the replacement for XBT-L1000; Vijeo Designer, which Schneider's own upload and download examples use at version 6.2, serves the Magelis terminals it supports; and the current Magelis line is configured with EcoStruxure Operator Terminal Expert. PanelMate went a different way: Eaton's support knowledge base states the line was sold off and is now supported by Advanced Technology Services. Matching a model to its exact package generation is its own subject — which HMI software works with which HMI panel hardware works through it.
Recover the project #
Work the recovery as six steps:
- Match the exact model from the label to its licensed engineering package, and confirm with the vendor or an integrator that the package uploads from that model.
- Ask separately whether the upload returns editable source or only a runtime image. A runtime image runs but cannot be opened, edited, or printed, so a file that copies off the panel is not automatically a recovery.
- Book an integrator who owns the package for a one-off terminal; buy the package when a fleet of the same model is still to migrate, and make the first recovered project the reference for the rest.
- Ask a distributor of the line whether it performs uploads for customers before you commit to either purchase. Some do, and the worst outcome is a no.
- Take delivery of two artifacts: the native recovered file and a readable export or printout showing screens, object properties, addresses, alarm definitions, and communication settings.
- Open the file in the package, navigate several displays, and inspect object definitions before you accept the recovery. A file that will not open is not a recovery.
The wider playbook, including what to salvage when only part of a project survives, is in recovering an HMI program when the source file is lost.
Capture the running application #
When no editable project can be recovered and the terminal still runs, preserve behavior before anything else changes. Screenshots record appearance; commissioning a replacement needs actions, limits, navigation, security behavior, and the controller exchange behind every object. Work through the live application against this table and record each row while the machine runs normally.
| Capture item | What to record | Confirmed when |
|---|---|---|
| Navigation | Every button and its destination screen | No screen is unreachable or undocumented |
| Operator commands | Button text, mode permissives, observed machine response | Controller response matches the recorded action |
| Numeric entry | Units, decimal places, entry limits, default values | Entered and displayed values agree with the controller |
| Alarms | Message text, trigger condition, acknowledge and reset behavior | Active and cleared states are distinguishable |
| Status objects | Text, colors, animation states, controller signal behind each | Each state ties to a live controller signal |
| Data features | Recipes, trends, counters, retained values | Storage and transfer behavior is documented |
One safety rule governs the whole capture: exercise only commands the machine's operating procedure permits, and where an alarm or interlock state cannot be produced safely, read its trigger from the controller program instead of forcing the machine into that condition.
Reconstruct the tags and scaling #
Migrations fail at the data boundary more often than at the screen. Build a tag map with one row per object: old object description, controller address or tag, data type, read/write direction, displayed units, scaling, entry limits, and the replacement object. Read the controller program and cross-reference every signal behind a command, display, alarm, setpoint, or interlock, then confirm each mapping against live values rather than similar names. Mark anything uncertain for a controlled test instead of assigning it by appearance.
Where scaling is unknown, recover it from two observed states while the old terminal still runs. Worked example, one analog temperature object:
- State 1: the old panel displays 175.0 °C and the controller register behind it holds the integer 3500 counts.
- State 2: at a higher machine temperature the panel displays 240.0 °C and the register holds 4800 counts.
- Slope: (240.0 °C − 175.0 °C) ÷ (4800 counts − 3500 counts) = 65.0 °C ÷ 1300 counts = 0.05 °C per count.
- Offset: 175.0 °C − (3500 counts × 0.05 °C per count) = 175.0 °C − 175.0 °C = 0.0 °C.
The recovered scaling is displayed temperature = counts × 0.05 °C per count + 0.0 °C. Prove it at a third independent state before writing it into the replacement: at 6000 counts the old panel must display 6000 × 0.05 = 300.0 °C. The method assumes a linear scale and a raw integer register; a transmitter re-range shifts the slope or the offset, which is exactly what the third state exposes, and every analog object gets its own two-point recovery.
If a recovered project does exist, treat its address list as a starting point, not proof: controller revisions and undocumented field changes leave archived files behind the running installation, so compare file contents, live values, and controller logic before building.
Build and prove the replacement #
Select hardware after the recovery decision, not before. The replacement must support the controller connection and every data operation the capture listed, fit the existing cut-out or door space, suit the environment, and match the supply and ports. Where the rebuild runs HMI runtime or SCADA client software on a Windows-class machine rather than a proprietary terminal, industrial panel PCs combine the touchscreen, mounting, and compute in one unit, and the checklist for verifying an obsolete HMI replacement before ordering covers the part-number and fit checks to run first.
Confirm the driver question before anything is ordered: the replacement package must have a documented driver for your controller, and what to do when the HMI software has no driver for your PLC covers the paths when it does not.
Then prove in this order. First, communications and a read-only page: display several values of different data types and compare each against the live controller. Second, one controlled command using the documented address, action type, permissives, and feedback, confirming both the written value and the machine state before duplicating the pattern. Third, the full rebuild: navigation, process displays, alarms, recipes, trends, and security from the capture table, with units, scaling, decimal formatting, and limits taken straight from the tag map. Retire the old terminal only after a complete pass down the capture table as the acceptance list.
The decision #
- One Magelis or PanelMate terminal, still running: book the upload-and-print through an integrator or a distributor, treat a runtime-only upload as a failed recovery, and move to capture.
- Two or more identical terminals still to migrate: buy the licensed package, recover one terminal as the reference project, and roll the rest out yourself.
- The terminal is already dead and no file exists anywhere: skip recovery; the controller program becomes the specification.
- Editable source is in hand: validate it against the live machine before building, because archived files can lag the running installation.
- Every case: no write-capable object moves to the new terminal until its address, data type, and machine response are confirmed on the running machine.
Questions asked
Can I copy the project file off the terminal and read it without the software?
No. The file is a proprietary binary that only the matching engineering package can decode, and an upload may return a runtime image rather than editable source. Without the package you cannot extract screens, addresses, alarm text, or communication settings, and opening the file in an editor or a different vendor's tool yields nothing usable. Budget for the licensed route instead.
Is a runtime image recovered from the panel a usable backup?
Only on the terminal family it came from. A runtime image re-loads and runs on the same hardware but cannot be opened, edited, or printed, so it does not help you document or migrate the application. Ask before any upload whether the result is editable source, and request the native file plus a readable printout so the recovery is useful beyond the old panel itself.
What can I do when the old terminal is already dead and no file exists?
Skip recovery and rebuild from the controller side. List every register and bit the terminal wiring can reach, derive commands, permissives, and alarm triggers from the PLC program, and take scaling from transmitter ranges and nameplate data instead of the two-point observation check. A dead terminal removes the observed-behavior path, so the controller program and the drawings carry the whole specification.
Will a new third-party HMI import the old project directly?
Assume not until the replacement vendor documents it for your exact model. Import tools exist but are narrow: the PanelMate line, for example, is documented to import through the Visual Designer import tool, not through a generic converter. Most replacements of this kind are rebuilt from a recovered project, a printout, or captured behavior, with the tag map as the bridge between old and new.