Backup & retrieve PLC/HMI programs when source is lost — how & cautions

Many plants have no program source for their PLC/HMI: the old OEM never handed it over, the previous engineer left, the second-hand machine came without code. When the PLC fails, it is all gone — no repair, no duplication. The solution: upload the program from the running device, back it up and document it while it can still be read.

Why back up NOW (don't wait for failure)

• PLC/HMI can die suddenly — dead memory battery, bad card, lightning, abrupt power loss.
• Legacy is hard to source — device + memory cards no longer sold, recovery is costly.
• Duplicate & modify — with source you can edit logic, add features, build a second machine.
• A plant asset — the program is the line's “intelligence” and must be preserved.

What can be backed up

1. PLC program — uploaded from the CPU (Rockwell, Siemens, Mitsubishi, Omron, Beckhoff, Schneider…).
2. HMI application — the runtime/app on the panel (PanelView, WinCC, Proface, Weintek…).
3. Drive/VFD parameters — read & save the parameter set (PowerFlex, Sinamics, ABB, SEW, Danfoss…).
4. Network & device config — IP, GSDML/EDS, gateway and switch configs.

How to do it (safely, without stopping the machine)

1. Identify device & software PLC/HMI/drive model + the right tool/version to upload (Studio 5000, TIA, GX Works, CX-One, TwinCAT…).
2. Connect on the right port Prepare the right cable/adapter (Ethernet, USB, MPI/Profibus, serial PC-Adapter, DH+…).
3. Upload (read out) Upload the program from the device to the PC — a read operation, not touching the running logic.
4. Save drive parameters Read the VFD/servo parameter set, export a file + print the parameter table.
5. Document it Name it, record version, date, machine location; keep multiple copies (external drive + internal cloud).
6. Verify Reopen the backup file to confirm it reads; note the software + license needed to open it.

When to call an expert

The right tool + right cable + right connection per vendor (especially legacy DH+, MPI, serial) is the barrier. DeepDebug supports remote backup or on-site guidance, multi-vendor — and advises setting up a periodic backup procedure so you never lose source again.