Explainer
Why a PSB Backup Cannot Run in WinCC Flexible PC Runtime
Short answer
No. A .psb file is a ProSave device image that restores only to the panel model it came from, and Siemens documents that it cannot be loaded or edited in the engineering tool. To run the application on a PC, open the source .hmi project, change the device type to the PC runtime, recompile and license it.
On this page
No, and the behavior you have already seen is the rule, not an exception. A .psb file is a ProSave device image: the panel's stored content copied as one block and compiled for that device family. Siemens documents that a backup file cannot be loaded or edited in ProTool or WinCC flexible, and that it returns only to the original panel or another panel of the same type through a restore. A PC running WinCC flexible Runtime is a different target with a different device type. The PC needs the source .hmi project, its device changed to the PC runtime device type, recompiled and licensed — the .psb contributes nothing to that build.
What a .psb backup actually contains #
ProSave, the transfer utility that installs with the engineering software, copies the complete stored content of the panel into the .psb file: the compiled runtime project plus the device data the backup function writes alongside it. The compiled project is built for one device family, with that family's fixed screen resolution, memory layout, object set and interfaces. That is why the engineering software treats the file as opaque — it never was a project file, it is an image in the panel's own format.
The documented restore limit follows from that: the .psb returns to the original panel, or to another panel with the same part number, ideally on the same firmware. The restore procedure itself is short — put the panel into transfer mode with its Transfer option, then run the restore from ProSave against that panel.
Why the PC runtime cannot consume it #
WinCC flexible PC Runtime executes a project generated for the PC runtime device type, and that project is produced in the engineering software from the source. The decisive property is the device type recorded in the project: a panel image and a PC runtime target do not share it, and no setting on the PC converts one into the other.
That also answers the runtime-loader idea. The loader is the panel-side start and transfer environment that waits for a project to arrive from the engineering PC or from ProSave; it is not a PC-side import function. A .psb is a payload for a matching panel, so pointing a PC at it through any loader or start-up setting extracts nothing. The only input PC runtime accepts is a project transferred to it from the engineering software.
The four routes, compared #
| Route | What it needs | Result |
|---|---|---|
| Restore the .psb to a same-model panel | Same panel type or part number, panel in transfer mode, ProSave | Panel returns to its backed-up state — you have already done this |
| Recompile the source project for PC runtime | The .hmi source, a PC with WinCC flexible Runtime and a license covering the tag count | Application runs on the PC; tags, resolution, scripts and storage paths need review |
| Upload the project from the panel | Upload enabled in the transfer settings when the project was loaded, matching engineering version | An editable project when the project permits upload |
| Run the .psb in PC runtime | Nothing that exists | Not supported; the file is not an input to the PC runtime |
Recompiling the source project for PC runtime #
- Recover the original .hmi project from the engineering workstation, a project archive or a backup, and keep one untouched copy of the file.
- Open it in the matching WinCC flexible edition and change the device recorded in the project properties to the PC runtime device type.
- Rework the connections: a link that used a panel interface — MPI, PROFIBUS or Ethernet — must map to an interface or communications processor that exists in the PC. Tag addresses stay the same; the connection parameters do not.
- Compile and clear the error list: screen layout at the PC resolution, scripts calling panel-only functions, and recipes or data logs writing to panel storage paths.
- Install the runtime with a license that covers the project's tag count, transfer the project, and test it against the PLC before service.
Any supported Windows PC can host the runtime; at the machine, industrial panel PCs put the runtime and the touchscreen in one unit. Obtain the runtime software and its licenses only from Siemens or its distributors.
Worked example: screen area after the device change #
Illustrative numbers, not a measured test. Say the panel screens were drawn at 640 x 480 and the PC monitor runs 1024 x 768.
- Drawn area: 640 x 480 = 307,200 pixels.
- Monitor area: 1024 x 768 = 786,432 pixels.
- Coverage: 307,200 / 786,432 = 0.39, so the drawn screens fill about 39 percent of the monitor, and 786,432 - 307,200 = 479,232 pixels are spare.
- If you redesign instead: 786,432 / 307,200 = 2.56, so the monitor offers 2.56 times the drawing area.
The decision from those inputs: keep the original layout and accept a windowed or letterboxed display after one layout review pass, or spend the redraw effort to claim the 2.56x area. The device change does not redesign the screens for you, whichever you choose.
When the source project is gone #
The .psb stays useful for exactly what it was made for — disaster recovery to the same panel model — and your restored panel proves it. For a PC copy with no source, the documented options are, in order:
- Upload from the panel, if upload was enabled in the transfer settings when the project was loaded and the engineering version matches. Start with the steps for recovering an HMI program when the source file is lost. Then check what you actually received, because why an uploaded HMI copy is not an editable project sets the limits of that file.
- Get the project from the machine builder or integrator who delivered the line; they keep sources more often than plants do.
- Rebuild the screens in the engineering software using the running panel as the reference.
No supported tool converts a .psb into an editable project; the editing restriction is part of how the file is defined, so do not spend plant time hunting for one. For password-protected projects, recover through the owner of the project. Keep the .psb and the source in the same archive, labeled with the panel model and the ProSave version that made the backup.
The decision, case by case #
- A same-model replacement panel exists: restore the .psb with ProSave and finish. That is the file's only job, and in your case it is already done.
- You want the application on a PC and the source project exists: change the device type, recompile, license, test. The .psb plays no part in this build.
- You want the application on a PC and the source is gone: upload if it was enabled, the integrator's copy, or a rebuild against the running panel, in that order. The .psb still cannot help.
- You are tempted to point a loader at the .psb: do not. It is a restore payload for a matching panel and nothing else.
Questions asked
Can the panel runtime loader run a .psb file on a PC?
No. The loader is the panel-side environment that receives a project from the engineering PC or from ProSave; it is not a PC import function. On the PC, WinCC flexible Runtime starts from a project transferred to it by the engineering software, and a .psb is never that input. Time spent trying loader settings on the PC is time lost.
Will the .psb restore to a newer panel from a different family?
No. The documented restore target is the original panel, or another panel with the same part number. A panel from a different family is a different device type by definition, with its own firmware and format expectations, so the restore does not apply. Keep the .psb for the model that produced it.
Is the .psb worthless once the PC version runs?
No. It remains the disaster-recovery image for the panel model it came from. Archive it next to the source project, labeled with the panel model and the ProSave version used for the backup, so a future restore matches both.
How do I check the runtime license against the project?
Read the tag count the project reports in the engineering software and compare it with what the installed license covers. Example: a project reporting 240 tags under a 256-tag license leaves 256 minus 240, or 16 tags, of headroom, which is tight for later edits. Anything below the project count will not license the application for service.
What happens if the PC runtime has no license?
The runtime falls back to the trial mode the software provides, which is not a condition to run a plant station in. Install a license that covers the project's tag count before the PC goes into service, obtained from Siemens or its distributors.