IMDTouchKnowledge BaseShop main store

Troubleshooting

Why an Uploaded HMI Copy Is Not an Editable Project

HMI and touchscreens Published 5 min read

Short answer

Use an HMI runtime backup to restore device data. To edit the project, recover the original engineering files or use the vendor's source-upload function if the source was saved to the panel. If you have only the runtime backup, keep it for restore and plan a rebuild.

On this page
  1. What the upload actually contains
  2. Why the edit tool reports the project as missing
  3. When the panel also has editable source
  4. Recovery steps before you edit
  5. Matching the recovered source to the panel
  6. Worked example: search effort versus rebuild
  7. The decision, case by case
  8. Questions asked

First identify the operation that produced the file. A device backup serves restore and replacement work. A separate source upload, where the vendor supports it and an engineer previously saved the source to the panel, can recover a project for editing. Keep the backup and look for the original engineering project or a supported source archive before rebuilding.

What the upload actually contains #

For a Siemens panel, check the selected data type in SIMATIC ProSave. The WinCC help topic Backing up and restoring data of the HMI device documents that choice. A complete backup can preserve the loaded runtime for restoration on a documented-compatible device. A backup that selected only recipes or another data type protects that selection alone. Restore the file with the documented procedure for the panel.

The article on a TP 277 backup that is transferable but not editable has a model-specific example. The engineering project is the file you open when you need to change screens, tags or scripts.

Why the edit tool reports the project as missing #

An engineering tool opens its native project or a supported engineering archive. A runtime image serves a different file format and purpose. If the editor reports a missing project after you select a backup file, check its file type and the tool that created it. Look for the engineering source or a separately saved source package.

Record the operation that raised the error. At file-open, verify the file type and engineering tool version. During transfer or load, read the full message and check the configured panel model, device version and installed firmware before making changes.

When the panel also has editable source #

On supported legacy Siemens panels, selecting Enable back transfer during a WinCC flexible download saves a separate .pdz package from the original .hmi source. Use the WinCC flexible Back transfer command to retrieve the package. WinCC flexible decompresses it and opens the project so you can save it. The package contains the HMI project. Keep the complete integrated engineering project separately when it includes PLC work. Siemens documents the two steps in Panel back transfer, entry 21907703, sections 2.1 and 2.2.

Beijer iX Developer uses Download all source code (for later upload) to save a separate ZIP on the target. Check the Transfer group in the iX Developer Reference Manual for the supported download and upload procedure. Verify that any retrieved source corresponds to the runtime currently on the panel.

Recovery steps before you edit #

  1. Check the vendor procedure and use the site's approved safe state before starting panel backups, transfers or restores. A restore or download can change what the operator sees and controls.
  2. Keep the uploaded copy and record which operation produced it. If you need to make a backup, uploading a program from an old touchscreen HMI describes the backup and source-transfer paths.
  3. Record the exact model, panel image version, tool and message. Identify whether it appeared while opening a file, backing up the device, or transferring a project.
  4. Hunt for the original source: the engineering PC, project folders, email attachments, the integrator's handover media, network shares. The full route for recovering an HMI program when the source file is lost applies unchanged here.
  5. Confirm that scheduled backups contain the editable engineering files. Separately check which HMI project data the platform backup contains before relying on it for device recovery.
  6. If a candidate source file turns up, verify it against the panel before editing, as the next section describes.
  7. If the hunt comes back empty, commit to the rebuild and extract everything the runtime can still tell you; reading an old HMI program before panel replacement covers what to record while the old panel still runs.

Matching the recovered source to the panel #

Before downloading anything, compare the source project and configured panel device version against the installed panel. Use Load preview to check any reported image mismatch and follow the vendor's firmware procedure if an update is required. Use a compatible panel image and storage medium if your model supports offline transfer. After any download, check the runtime against known machine behavior before releasing it to the operator.

Worked example: search effort versus rebuild #

Worked example with illustrative inputs — replace them with your own counts. Your runtime shows 18 screens. Rebuilding at 45 minutes per screen, plus 3 hours of tag and communication setup and 2 hours of checkout:

18 screens × 45 min = 810 min = 13.5 h

13.5 h + 3 h + 2 h = 18.5 h ≈ two and a half shifts

If an initial search of the engineering PC, backups and handover files would take 2 hours, spend that time before committing to an 18.5-hour rebuild when there is a reasonable chance of recovery. Allow time to verify the revision and estimate any repairs to the recovered project. Keep the device backup in either case.

The decision, case by case #

  • The original engineering project is available. Verify that it matches the running panel, then make changes in the engineering tool. Keep any device backup with the machine records.
  • Source was saved to the panel. Use the vendor's source-transfer tool, save the recovered engineering project, and verify its revision against the running panel.
  • Only a runtime backup is available. Keep it for restore, document the running application and rebuild the engineering project from the available evidence.

Questions asked

Does the panel keep a copy of the engineering project anywhere?

Some panels can store a separate source archive when the engineering tool transfers the project. On supported WinCC flexible panels, Enable back transfer saves a PDZ package. Beijer iX Developer can save a ZIP with Download all source code (for later upload). Check that the recovered source matches the application running on the panel.

Can I edit the uploaded runtime file directly and load it back?

Use the device backup with the vendor's restore tool. Make screen, tag or script changes in the original engineering project or an editable project recovered through the documented source-upload procedure. Compile and load the revised application after making the changes.

Do recipe or data exports from the panel help rebuild the project?

Recipe and CSV exports can save time re-entering data. Capture them alongside the screens, alarm messages and other operator-facing details you can document safely while the old panel still works. Recreate the screen and control logic in the engineering project.

How do I keep this from happening on the next machine?

Keep the complete editable project with the machine documentation and record the engineering tool version. Include the project folders in scheduled backups and test that a saved copy opens. Where the panel supports source transfer, treat a protected copy on the panel as a second recovery path.

Corrections

  • : Distinguished restore backups from editable source packages and added the documented Siemens and Beijer recovery options.

Keep reading

  • How-to

    How to Recover an HMI Program When the Source File Is Lost

    If an editable backup was stored on the HMI at download time, upload it and open it as a project. If the terminal holds only the compiled runtime, no upload can recreate the source: document every screen and tag behavior from the running unit, rebuild against the controller project, and convert the runtime only where the vendor documents a path.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Project That Fails After a Git Clone

    The clone is broken because a referenced bitmap .PLK was never committed, not because of an ignore rule. Read the HMI Output tab for the exact filename, prove the file is untracked with git check-ignore followed by git ls-files, then restore and commit it and re-test from a clean clone. Track the .tgt and .def files for the HMI BIOS version as well.

    HMI and touchscreens

  • Troubleshooting

    Verify HMI project data is inside your platform backup

    A backup is proven at restore, not at completion. Platform archives such as the ctrlX appData scope have returned configuration while omitting HMI application projects — WebIQ data sat outside that scope until WebIQ 2.16 added save and restore on core22. Record the project inventory, restore into an isolated target, and count the projects that come back: that count, not the completion message, tells you the machine is recoverable.

    HMI and touchscreens