A project file carries its own version number, and the programming software opens only files at or below its own version. Read the software, project and panel firmware numbers first, install the vendor's current release, and open a copy of the project on the bench before any download to a working panel.
A project saved in a newer version of the programming software will not open in an older copy. The file is not damaged; the software on the PC is one release behind it. The fix is to update the HMI programming software from the vendor's support site, open a copy of the project on the bench, and only then plan the download to the panel. Three version numbers govern this job, and a label such as 2.68 can refer to any of them: the installed software, the project file, or the panel firmware. Read all three before installing anything, because each mismatch has a different fix and only one of the three lives on the PC.
Which of the three version numbers is blocking the project
Read each number from the place it lives and write all three down before touching the installer.
| Version | Where you read it | What it controls |
|---|---|---|
| Programming software | The About screen under the software's Help menu | Which project files open at all |
| Project | The project file's name or its file properties | Must be at or below the software's version to open |
| Panel firmware | The panel's diagnostics or system information screen | What the panel accepts at download |
A bare version label could belong to any row of that table, and the row it belongs to decides where the update goes:
- Project number higher than the software's number: the project is newer, the software is behind, and the update belongs on the PC.
- Panel firmware lower than what the software supports: the software and project are fine, and the update belongs on the panel.
The two cases fail at different steps, which is the tell. A project that opens on the PC but is refused at download points at the panel. One bench case had a panel on firmware 15 against programming software carrying device support up to version 17, and the fix there was a panel firmware update loaded through the same software. Read the panel's revision before you plan the transfer: check the HMI firmware revision before a project transfer shows where the panel keeps it.
Vendors document the first case the same way across platforms: one major HMI system states that a project saved in an older version is upgraded automatically when newer software opens it. That upgrade rewrites the project file, which is why the original copy stays untouched on the bench.
Example: opening a 2.71 project on a PC running 2.68
Inputs. Programming software at version 2.68, read from the software's About screen. Project file labelled version 2.71, read from the file name. Current release version 2.72, listed on the vendor's support site at the time of the case. The site has booked a 30-minute maintenance window for the panel download, and the project copy takes about 5 minutes to duplicate and open on the bench.
Rule. The software opens a project whose version is at or below its own. A project numbered above the software is refused at open, and the fix is on the PC, not the panel.
Arithmetic. Project against software: 2.71 is newer than 2.68 (2.71 > 2.68), so version 2.68 refuses the file. Current release against project: 2.72 is newer than 2.71 (2.72 > 2.71), so version 2.72 opens it. The 30-minute window covers the 5-minute bench check plus the download, with more than half the window left for the commissioning checks.
Result. Install version 2.72 and the 2.71 project opens inside the 5-minute bench check, with the panel untouched until the 30-minute window.
Decision. When the project's number is the higher one, update the software, and take the current release instead of the minimum that barely clears the project. If the open succeeds and the download later fails, the mismatch has moved to panel firmware, and the next update belongs on the panel.
What you need
- The installer for the vendor's current programming software, downloaded from the vendor's support site. Vendors publish compatibility tables for their own software, panel and firmware combinations; that table is the first check.
- The software code or serial that came with the original purchase. The installer asks for it when the update is installed as a replacement.
- An untouched copy of the project file, copied before anything else changes. If the only copy lives on the panel, read an HMI project from the panel before editing pulls it off first.
- The panel's firmware revision, read from the panel's diagnostics screen.
- A maintenance window for the download (30 minutes is a workable minimum for one panel), and the site's commissioning checklist for the machine the panel serves.
Update the programming software
- Close the programming software on the PC.
- Match the prerequisites the vendor lists for the update: installed build, operating system, service packs. HMI software upgrade prerequisites: match the installed build first walks that check in detail.
- Run the installer. It offers two ways: replace the existing installation, or install a separate instance beside it. A separate instance keeps the old revision runnable for projects that still live on older panels; replacement is simpler when nothing legacy remains.
- Enter the software code from the original purchase when the installer asks.
- Launch the updated software and read the About screen: the version shown there must match the release you downloaded before any project file is opened.
Open and test a copy of the project
- Copy the project file into a working folder and open the copy. The original stays where it is, untouched.
- Accept the conversion prompt when the software shows one; conversion rewrites the file, so save the result under a new name. Open an old HMI project in new software: convert it safely covers what the prompt changes and how to keep a fallback copy.
- Walk every screen in the converted copy: each one opens, no object comes through blank, and the communications settings still point at the controller the panel serves.
- Compare the panel's firmware revision against the versions the new software supports. If the software has moved past the panel, load the panel firmware update first, inside the maintenance window.
How to check it worked
A clean run goes in this order:
- The About screen shows the release you installed.
- The copied project opens with no unresolved prompts and no missing screens.
- The identified panel accepts the download inside the window.
- The panel starts to its main screen, communicates with the controller, and the machine's operator functions pass the site's commissioning checks before the line returns to production.
One boundary marks the open step: opening the file proves the software reads it; it does not prove the panel will run it. The panel test is the download itself, which is why the window, the untouched original and the firmware comparison all come before it.
Recommendation: install the vendor's current programming software as a separate instance while the plant still runs older projects, keep the original project file untouched, and download to a working panel only inside a maintenance window of at least 30 minutes after the panel's firmware revision matches what the new software supports. Project number higher: update the PC. Panel number behind: update the panel.
Questions
Can the old and new versions of the programming software share one PC?
Most HMI software installers offer the choice at install time: replace the existing installation or install a separate instance beside it. The separate instance keeps the old revision runnable, which matters when projects still live on panels only the old revision can service. Choose replacement once nothing legacy remains, and keep the installer file and the original software code either way, because a rebuilt PC needs both.
Does updating the programming software update the panel too?
The software update changes only the engineering PC. Panel firmware is a separate download on the vendor's support site, with its own release notes, and the panel keeps its current firmware until someone loads a new version deliberately. That is why a project can open on the PC and still be refused at the panel: the panel's firmware number is checked at download, not at open.
What if the installer asks for a software code you no longer have?
The code ties the update to the original purchase, and the vendor expects it before a replacement install finishes. Look on the purchase paperwork, the original installation record or the plant's software register. If it cannot be found, the vendor's official support channel can identify the registered purchase. Do not install with a code taken from another machine or another buyer.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.