How-to
How One Spare HMI Panel Covers Seven Machines
Short answer
Yes. Keep one backup archive per machine on a USB stick or memory card, and restore the needed archive to the single spare panel at the panel itself. This works without WinCC flexible only if the backup transfer option was enabled when each project was downloaded; otherwise you need a PC with ProSave, and archives restore only to the same panel model.
On this page
- Can one spare panel hold seven different machine projects?
- What do I need before touching the seven panels?
- How do I create the seven backup archives?
- How do I load the right project onto the spare panel?
- Why does a panel refuse to write its own backup?
- Can I edit an archive or restore it to a different model?
- How large does the storage medium need to be?
- Questions asked
Yes, with one condition attached. Keep one backup archive per machine on a USB stick or memory card, and restore the archive you need to the single spare panel at the panel itself — no computer, no WinCC flexible, no project file. The condition is the catch: the projects running on the seven panels must have been downloaded with the backup transfer option enabled. Where it was not, a PC running ProSave is the only restore path, and every archive restores only to the same panel model. Build the archive set once, test-restore each one to the spare before you depend on it, and keep the original engineering projects for anything that needs editing.
Can one spare panel hold seven different machine projects? #
Yes, if you split the two jobs: the panel runs one project at a time, and the storage medium holds all seven archives, so you restore the failed machine's archive to the spare each time it is swapped in.
There is no mode in which seven projects sit side by side inside one panel runtime with an on-screen picker. The runtime image loaded in the panel is one machine's configuration; the multi-project store is the set of archives on the USB stick or memory card, and the spare panel is the player you load the chosen archive into.
That makes the deliverables simple: one spare panel of the same model as the seven machine panels, one storage medium carrying seven labeled archives, and a written swap procedure that says which archive goes with which machine.
What do I need before touching the seven panels? #
You need one spare panel of the same model, one storage medium those panels accept, the Control Panel password if one is set, and the original WinCC flexible projects kept safe, because the archives themselves cannot be edited.
The Windows-based panels of this generation take a USB flash drive or a memory card, and the supported-media list is specific to each panel generation, so confirm your model's list before buying the medium. Siemens documentation for current Comfort panels names industrial USB sticks as the backup medium and specifies SIMATIC SD memory cards of at least 32 GB for the same job, so treat an industrial-grade stick as the default for a kit that lives in a cabinet.
You also need the spare to be the same model, not merely similar. An archive taken from a TP277 restores to a TP277, and its multimedia sibling follows the same rule in the other direction.
How do I create the seven backup archives? #
From each of the seven running panels, open Control Panel during startup, start the backup application, insert the storage medium, write one complete archive, and label it with the machine number before you pull the stick out.
- Power the machine's panel and, in the startup dialog, press "Control Panel" instead of "Start" — the dialog on these panels offers "Start", "Control Panel", "Transfer" and "Taskbar".
- Open the "Backup and Restore" applet in Control Panel; on current-generation panels the same function sits under the service section of the settings.
- Insert the USB stick or memory card.
- Select everything the screen offers — runtime, licenses and recipes — so the archive is a complete recovery image for that machine.
- Run the backup, then write the machine number, the panel model and the date on the medium or the folder that holds the archive.
- Repeat on the other six panels.
- Prove the set: restore each archive to the spare once, now, while nothing is down. An archive you have never restored is a hope, not a spare strategy.
A PC running SIMATIC ProSave writes the same kind of archive over the transfer connection — ProSave Backup on the way out, ProSave Restore on the way back in — and it is the documented fallback when a panel will not write its own backup. While the storage medium is in each cabinet, take the controller program too; the same one-copy-per-machine discipline is laid out in how to back up a PLC program the right way.
How do I load the right project onto the spare panel? #
On the bench, with the spare powered but not wired to the machine, insert the medium, open Backup and Restore from Control Panel, choose Restore, select the failed machine's archive, and let it finish before you reboot.
Do the restore on the bench, never live in the machine with outputs energized: a restored panel boots straight into runtime and can command the machine, so a live swap is energized work under a written permit such as a standing EEWP covering routine live access to VFD HIM modules.
After the restore:
- Reboot and confirm the opening screen identifies the intended machine, not the previous one.
- Check the communication settings against that machine's controller address — an archive carries the source panel's settings, and a swap is the moment an address conflict surfaces.
- Verify the recipes on the panel are that machine's recipes.
- Install the panel and confirm live communication before releasing the machine to production.
Why does a panel refuse to write its own backup? #
Because the project on that panel was downloaded from WinCC flexible without the backup-transfer option enabled — with it off, the panel's Backup and Restore will not produce an archive, and ProSave from a PC becomes the only way to recover the configuration.
The option is set at transfer time in the engineering tool, not on the panel, so it can only be fixed by downloading again. Open the machine's source project in WinCC flexible, enable backup transfer in the transfer settings, and download once. After that single download, the panel-side, laptop-free path works for the life of the project.
Run this check on all seven panels now, during normal operation: attempt one panel-side backup on each. The ones that refuse go on a list for a one-time re-download, and until that list is cleared the spares kit includes a laptop with ProSave, because ProSave works regardless of the option.
Can I edit an archive or restore it to a different model? #
No on both counts: a panel or ProSave archive is a recovery image, not an engineering project — it cannot be opened and edited, and it restores only to the same panel model it was taken from.
ProSave's partial backup files (.BRF) follow the same rule: not editable, same model only. That has two consequences for the seven-machine kit. First, the spare must be the exact model the machines run — if the fleet mixes the TP277 touch variant and its multimedia sibling, the MP277, you need one spare of each, because archives do not cross models. The multimedia difference is real in the field, as jobs like a TP277 live camera display fault show.
Second, keep the seven WinCC flexible source projects, because every future edit — a new screen, a new tag, a recipe change — starts there, not from the archive. When repair turns into replacement, the selection and migration questions are covered in planning an HMI terminal replacement from an older operator panel.
How large does the storage medium need to be? #
Size it from the documented worst case of 20 GB per archive — 7 × 20 GB = 140 GB — so one 256 GB industrial USB stick carries the whole set with 116 GB to spare, while a 64 GB stick stops at three worst-case archives.
The 20 GB figure is Siemens' documented ceiling for panel backups on current Comfort panels, where the amount of data on the device drives the archive size. A TP277 running a WinCC flexible project will come in far under it, so after the first backup read the archive's actual size and re-check the arithmetic: capacity needed = 7 × measured archive size. As an illustration, if the first archive measures 600 MB, the set needs 7 × 600 MB = 4.2 GB, and an 8 GB stick is comfortably enough.
Then pick the medium layout by who does the swap. One 256 GB stick with a printed index of archive names against machine numbers works when one disciplined person owns the kit. Seven individually labeled sticks — one per machine, stored with that machine's paperwork — are the better call when any technician may grab the spare under production pressure, because the wrong-archive mistake becomes impossible.
Questions asked
Can the spare panel show all seven projects on screen to pick from?
No. The panel runs one runtime image, and the choice between machines lives outside it, in the set of archives on the storage medium. Picking a machine means restoring that machine's archive before the panel is installed, so build the swap procedure around that restore step.
Do I need a different spare if some machines use the MP277?
Yes, one spare per model. The MP277 is the multimedia variant of the same platform, adding media and camera functions, but an archive still restores only to the model it came from. Seven TP277 machines need one TP277 spare; a mixed fleet of TP277 and MP277 needs one of each.
Can the backup-transfer option be enabled without reloading every project?
No. The option is applied when the project is transferred from WinCC flexible, so each of the seven panels needs one more download from its source project with the option set. Until those downloads happen, keep a laptop with ProSave in the spares kit, because ProSave remains the working path.
Do licenses and recipes come across in the archive?
On the Windows-based MP panels the control-panel backup writes runtime, licenses and recipes together, and the TP277 presents the same kind of selection screen, so read the checkboxes the first time you back up rather than assuming. Wrong recipes on a swapped panel cost as much downtime as the wrong project.