HMI firmware load says not a supported file

What the rejection actually checks

The check runs on the PC. When you select the firmware file in the load dialog, the programming software reads it, tests it against the releases it supports, and refuses it before the transfer opens. The panel never sees a file the software rejects, so no panel-side move can clear the pop-up.

A firmware file issued for a newer software release fails that check on an older install. A download truncated by a dropped connection fails it too, and the message reads the same. Retrying the load, renaming the file and moving it between folders all leave the check untouched, so none of them can change the outcome.

Version pairing runs in both directions. The panel's own firmware revision matters before a project transfer as well, so check the firmware revision before a transfer as its own step. Panel makers document the same pairing rule on the project side, where an error-free compiled configuration can still be refused at load.

Symptoms and what each points to

• "Not a supported file" pops up at file selection, before the transfer starts. Programming software older than the firmware file's release, or a download that arrived damaged. The panel is not involved yet.
• The software reports the update finished while the panel screen stays at updating exec 213. The update defect that lived in software builds 1.3.7.21 and 21a. Bring the panel back with the corner-hold recovery, which is the recovery path the panel is designed to offer without cutting power, then move the software to 1.31 Build 7.27 or later.
• The same words appear on the panel itself when opening files, on a panel that runs Windows Embedded Compact 7. An OS-level file handling problem; Microsoft documents a fix for that case, and it comes through the OS vendor's support, not the programming software.
• The transfer stops because a file is missing from the PC. A different fault: a project transfer missing its firmware file has its own steps.

Check the software build before the file

Read the build number from the programming software's version display before you touch the file again. The firmware file ea0130072a.eas was issued when v1.30 Build 07.21A was the current release, so an install older than that rejects the file on sight, with the same message a damaged download gives.

1. If the installed build is older, install a current release. Install the newest one available for the panel model; 1.31 Build 7.27 is the minimum, and the worked example below shows why.
2. If the build is already current and the file still bounces, suspect the download: delete the local copy, download ea0130072a.eas again from the panel maker's official support page, leave the file name unchanged, and compare the size with the size the download page lists where it lists one.
3. Reopen the load dialog and select the fresh copy. If the pop-up still appears on a current build with a fresh copy, stop loading and check the maker's release notes for the minimum build the file requires.

This is the same rule that governs software upgrades: match the installed build first.

Recommendation: read the programming software's build number first and install the newest release, 1.31 Build 7.27 or later, before loading a new firmware file. A build older than the file's release produces the rejection, and the 07.21A-era builds carry the exec 213 hang, so one install to the newest build clears both faults and skips the recovery path entirely.

Worked example: ea0130072a.eas rejected, then frozen 20 minutes at updating exec 213

Inputs. Firmware file: ea0130072a.eas, the file being loaded. Software build at the time of the load: the 07.21A-era release, later confirmed as one of the two affected builds. Transfer time the software reported: 230 s. Time the panel had sat at updating exec 213 before recovery: about 20 min, or 1200 s. All four come from the case this article works.

Rule. The panel's own screen is the authority over the PC's progress bar. Once the panel has sat frozen for twice the transfer time the software reported, stop waiting and start the recovery path.

Arithmetic. The waiting threshold is twice the reported transfer time: 2 × 230 s = 460 s. The panel had sat for 1200 s, and 1200 s ÷ 460 s ≈ 2.6, so the freeze was already about 2.6 times past the point where "busy" stopped being believable. Measured in whole transfers, 1200 s ÷ 230 s ≈ 5.2, five transfers' worth of sitting.

Result. Frozen, not busy. There was nothing left to wait for.

Decision. No power cycle. Hold the upper left corner of the screen to reach the settings menu, load the firmware again from the programming software, and let the second load run to the end without interruption. The panel in the case came back this way at 1200 s frozen, with power never interrupted. Then make the repair permanent: install software build 1.31 Build 7.27 or later, because the hang lived in builds 1.3.7.21 and 21a and was fixed in 1.31 Build 7.27. Threshold to carry to your own panel: twice whatever transfer time your software reports, 460 s in this case.

Load the firmware and watch the panel screen

1. Open the firmware load dialog and select the copy that passed.
2. Start the load and leave the panel alone: panel power and the programming link stay undisturbed until the panel restarts on its own.
3. Watch the panel screen rather than the PC progress bar. The PC finishing first is normal; the panel screen is the one that tells you the state.
4. Confirm the panel restarts into runtime with the project screens and communications up.

Bringing back a panel frozen at updating exec 213

The recovery that worked runs through the panel's own settings menu, reached by holding the upper left corner of the screen. From there, load the firmware again from the programming software and let the second load run to completion without interruption. The panel in the case restarted normally after that second load.

Do not cycle power to hurry a panel along: a firmware load writes to flash, and a power cut mid-write can leave the panel without a working loader. If the corner hold opens nothing and the screen ignores touch, stop there and get the panel maker's support involved before anyone touches power.

The recovery restores the panel for now. The defect lives in the software builds, so install 1.31 Build 7.27 or later and the next update passes exec 213 unassisted.

Verify the panel before it goes back in service

• The software build reads 1.31 Build 7.27 or later.
• The firmware file loads with no pop-up.
• The panel passes updating exec 213 on its own and restarts.
• The project screens and communications come up. If the panel restarts and then will not communicate after a firmware update, that fault has its own checks.
• The panel's firmware version matches the file loaded. Where it displays varies by software build, so check both the settings menu and the software's panel information screen.

Questions