How-to
How to find the runtime file an HMI terminal actually loads
Short answer
The startup configuration, not the file list, selects the loaded .MER. Cycle power and press the white box in the lower-left corner (touch, firmware 5.0 or later) or hold F1 on a directly connected USB keyboard to reach the configuration screen and read the loaded runtime name. Copy every stored runtime off before deleting anything in File Management.
On this page
- The startup configuration picks the runtime, not the file list
- Reach the configuration screen at startup
- Copy before you delete anything
- Worked example: six stored runtimes down to one
- When neither startup method opens the door
- Prove the cleanup with a cold start
- Keep an exit path in the next project
- Questions asked
On a PanelView Plus terminal the file list never tells you which application is running. The startup configuration does, and it selects exactly one .MER file no matter how many are stored — a terminal holding six runtimes still loads exactly one of them. To find yours, cycle power and press the white box in the lower-left corner of the screen while it shows (firmware 5.0 or later), or hold F1 on a USB keyboard plugged directly into the terminal through power-up. The configuration screen names the loaded file, and its File Management display is where the unwanted copies get deleted. Copy every runtime off the terminal before you delete anything. The sections below cover the entry methods, the cleanup order with the arithmetic shown, and the recovery route for the case where neither startup method works.
The startup configuration picks the runtime, not the file list #
A PanelView Plus keeps its runtimes in internal storage and keeps one selection for boot. At every power-up the loader reads that selection and starts the named file; the other copies — older revisions, other machines' applications, backups — sit untouched. Presence in storage proves nothing about activity, and cycling power replays the same choice, so reboots on their own never reveal the name.
The usual trouble is access, not selection: a project built without a navigation object to the configuration screen leaves you no button once the runtime is up, which forces an interruption at startup. The symptoms line up like this:
| What the terminal does | What it means |
|---|---|
| Boots straight into an application at every power-up | A runtime is selected for automatic startup |
| Several .MER files sit in internal storage | Only the selected one loads; the rest are copies |
| No button exits to configuration | The project was built without a path back to it |
| No white box appears during boot | Firmware earlier than 5.0, or the box was missed |
| Boot ends in a cannot-load message | The selected file is missing or unusable — read the name before changing anything |
A cannot-load message is not evidence of a failed display or a corrupt file list. It means the configured file is gone or unusable, and the recovery route later in this article still gets you in.
Reach the configuration screen at startup #
The terminal's user manual documents the entry points in its startup sequence: the white box on touch terminals, F1 on keypad units. In the field the keyboard method covers both, and the same entries hold on PanelView Plus 7 terminals. Firmware decides which method you get:
- Cycle power and watch the whole boot sequence — the entry window comes early, not at the end.
- On firmware 5.0 or later, a small white box appears in the lower-left corner. Press and hold it while it is visible; a quick tap often lands after it has gone.
- No box, or no response: plug a USB keyboard directly into one of the terminal's USB ports. On hardware split into a display module and a logic module, use a port on the logic module itself, not a hub. Cycle power again and hold F1 from the moment power returns until the boot completes.
- When the configuration screen opens, stop restarting and record the full loaded .MER file name, extension included.
- While you are there, open Control Panel → System → Start-up Options and confirm the boot option's Detect safe mode request setting is enabled, so the next safe-mode request is honored at power-up.
Make the firmware call explicitly: on 5.0 and later, expect the white box. The firmware 3.1 terminal behind this question never displayed it, and held F1 on a directly connected keyboard failed there too. That combination does not point to a bad keyboard or a failed display — it sends you to the recovery route below.
Copy before you delete anything #
The configuration screen shows which .MER is currently loaded; the File Management display lists what is stored and is where deletion happens. Work in this order:
- Record the exact loaded name, extension included.
- Copy the loaded runtime to external storage or the engineering workstation.
- Copy the remaining stored runtimes as well, while their purpose is still unknown.
- Open each copy from the destination to confirm it transferred.
- Delete only the unwanted internal copies from the File Management display, and leave the selected file in place.
A naming convention can suggest revision order, but it can never override the name the configuration screen reports. That entry is the loaded application; everything else is a copy until proven otherwise. The same discipline holds when the cleanup is really a retirement in disguise: reading an old HMI program before panel replacement depends on getting the files off while the hardware still runs.
Worked example: six stored runtimes down to one #
Take a real case: a terminal holding six .MER files in internal storage, one of them configured to load. The configuration screen names line1_packer_r4.MER — illustrative names here; yours will carry your own machine and revision scheme. With the loaded file identified, the arithmetic is 6 stored − 5 deleted = 1 kept, and the survivor is the file the screen named, not the newest date in the folder:
| Stored .MER (illustrative names) | What the configuration check shows | Action |
|---|---|---|
| line1_packer_r4.MER | Loaded at startup | Keep |
| line1_packer_r3.MER | Older revision, same machine | Copy, then delete |
| line2_casepak_r2.MER | Different machine's application | Copy, then delete |
| line2_casepak_r1.MER | Superseded revision | Copy, then delete |
| scrap_trial_test.MER | Trial project | Copy, then delete |
| backup_old_2019.MER | Legacy backup | Copy, then delete |
Every deleted row is copied to the USB drive first; the kept row stays untouched so the startup selection still resolves at the next boot.
When neither startup method opens the door #
If the white box is absent on older firmware and held F1 on a directly connected keyboard will not interrupt the boot, the remaining route runs through the terminal's autorun mechanism, and it is disruptive: from the moment the loaded file is removed until the correct runtime is restored, the terminal has nothing to display. Treat it as planned work on a stopped machine, never on a line whose operator interface has to stay live.
Rockwell's knowledge base documents an autorun.bat that the terminal executes from removable media, and a copy-off script uses that same hook to transfer the stored runtimes to the USB drive and remove them from internal storage. On the next boot the loader reports that it cannot load the current application, names that application, and drops the terminal into the configuration screen. The name in the message is the answer to the original question. Upload the preserved file from the USB drive, select it, and start it — the terminal returns to normal operation.
Prove the cleanup with a cold start #
A manual launch from configuration proves the file works; only a cold start proves the selection. Launch the preserved runtime from the configuration screen, confirm the expected initial display opens and operator navigation reaches the required screens, then return to File Management and confirm only the intended files remain. Finish with one controlled power cycle: the same application must load by itself, with no cannot-load message.
The configuration screen answers which file loads; which project version sits inside that file is a separate check — how to verify the HMI project version running on a panel covers it. And if a restored application boots but misbehaves against the controller, suspect the pairing of runtime and terminal software: fixing an HMI MER runtime version mismatch walks that fault down.
Record three facts in the maintenance record when you close the job: the loaded .MER name, the terminal firmware version, and the entry method that worked.
Keep an exit path in the next project #
Three habits prevent a repeat. Add a button to the configuration screen in every runtime revision, restricted through the project's normal operator-access design if only technicians should reach it — but never omit the service path. Name runtimes so the machine and revision are unmistakable; a name can suggest, never decide. Keep the approved master copy off the terminal, because internal storage is deployment storage, not the archive.
Questions asked
Does loading a new .MER file delete the alarm log?
Yes. Rockwell's knowledge base lists alarm log files as being deleted when a new .MER runtime is loaded, because the alarm log is tied to the loaded application. If that history matters, copy the alarm log off the terminal through File Management before you load or restore any runtime file.
How does the documented autorun.bat route actually work?
Rockwell documents an autorun.bat that runs from the root of a USB flash drive or SD card; on PanelView Plus 6 terminals its documented job is restoring a backup file automatically. A copy-off script uses the same hook. Make the copies before anything is deleted from internal storage, because the terminal displays nothing again until the correct runtime is restored and started.
Does the newest file date or the largest file size mark the running application?
No. Dates, sizes and position in the folder are storage artifacts with no connection to the startup selection; a runtime downloaded a year ago can still be the one configured to load. The loaded-application entry on the configuration screen is the only reliable indicator, so treat every other stored file as a copy until that entry proves otherwise.
The configuration screen names a runtime that is not in File Management — what does that mean?
The startup selection points at a file that is no longer stored, which is also why some terminals boot into a cannot-load message before configuration opens. Either download the missing runtime again, or select one of the stored files from the configuration screen and start it, then re-check the loaded name so the maintenance record matches the terminal.