Troubleshooting
Compile the uploaded MER to the ME Station version
Short answer
Compile the replacement MER to the terminal's ME Station version or lower — 8.0.10.12 in this example — never to the OS version 02.36.0.0 shown on the same screen. Copy the running runtime over USB from Configuration Mode, and set the allow-decompile checkbox before compiling so the next recovery stays possible.
On this page
- Which version decides the compile target for a replacement MER?
- Which MER file on the terminal is actually running?
- How do I copy the MER to a USB stick without a network?
- What does the allow-decompile checkbox change when compiling?
- How do I prove the backup is complete?
- When is rebuilding not worth it?
- Questions asked
A PanelView Plus that runs fine with no source files left behind is a backup job, and the backup lives in one file: the runtime MER the terminal loads at power-up. Copy that MER over USB from Configuration Mode, restore it to an editable application in FactoryTalk View Studio 10.00, and compile every future runtime to the terminal's ME Station version or lower — 8.0.10.12 on the terminal in this example. The OS version 02.36.0.0 shown on the same System Resources screen is platform software, not a compile target. Before you compile anything, also verify the checkbox that allows decompiling, so the next engineer can repeat this recovery.
Which version decides the compile target for a replacement MER? #
The ME Station value decides: compile the replacement runtime to ME Station 8.0.10.12 or any lower ME version, and never to the OS value 02.36.0.0 shown on the same System Resources screen.
The two numbers describe different software layers. The OS value identifies the platform software the terminal boots; the ME Station value identifies the FactoryTalk View Machine Edition runtime environment that loads and executes the MER. A runtime built for a later ME version can carry features or a file format the installed station cannot load, so the terminal's ME version is the ceiling for the target, and the OS number never enters the choice.
Worked example, using the values this case displays:
- Terminal screen: OS 02.36.0.0, ME Station 8.0.10.12. Development seat: FactoryTalk View Studio 10.00.
- Target 8.0.10.12: major 8 = 8, minor 0 = 0, build 12 = 12, so it matches the station and loads.
- Target 8.0.00.00: 8 = 8, 0 = 0, and build 00 ≤ 10, so it sits below the station and loads.
- Target 9.00.00.00: major 9 > 8, so it sits above the station and the terminal rejects the file at load.
- OS 02.36.0.0: a platform value, not an ME runtime version at all, so it is never a compile input.
The seat can serve the old target. Rockwell's release notes document that FactoryTalk View Studio 9.00.00 or later creates a PanelView Plus 7 Standard runtime (.mer) at v8.20 or earlier, and 8.0 falls below 8.20, so an 8.0-family target is inside the documented range of a 10.00 seat. The floor moves with the application, not the hardware: if the restored screens use features introduced after the chosen target, the build rejects them, and the answer is to read those build messages rather than upgrade terminal firmware. A runtime compiled above the terminal fails at load, not at compile; that failure mode and its fixes are covered in fixing an HMI MER runtime version mismatch.
One caution on identification: catalog number 2711P-RDT10C, Series B names a PanelView Plus 1000 touch display module, and this terminal generation carried communications as add-on modules, so read both versions from the terminal's own System Resources screen instead of inferring firmware from the catalog number.
Which MER file on the terminal is actually running? #
The startup setting decides, not the newest timestamp: open Terminal Settings in Configuration Mode, find the startup options, and record the exact filename configured to run at power-up before you copy or convert anything.
Terminals that have been serviced rarely carry a single MER. Commissioning copies, revisions and abandoned tests accumulate, and neither the file name nor the date tells you which application controls the machine. Put the running application in a safe operating state, then photograph or transcribe:
- the startup MER filename from the startup options,
- the OS version value from System Resources,
- the ME Station version value from System Resources,
- the rest of the startup settings page as displayed.
Copy every MER you find for preservation, but the recorded startup file is the only one you treat as production. If the running application blocks entry to Configuration Mode, stop before forcing a reset or editing startup behavior; the objective is extraction, not reconfiguration. The full identification walk-through is in how to find the runtime file an HMI terminal actually loads.
How do I copy the MER to a USB stick without a network? #
Copy over USB from Configuration Mode: the stick removes the terminal's Ethernet address, subnet and communications module from the task, and users of this terminal generation report it as simpler and generally faster than the Ethernet route.
- Enter Configuration Mode by the panel's documented access method; the entry routines are covered in how to enter configuration mode on a touch HMI.
- In Terminal Settings, confirm the startup filename you recorded.
- Insert a USB storage device the terminal recognizes.
- Open the terminal's file-management function and run the application-copy operation on the startup MER.
- Copy any other MER files into a separate, clearly labeled archive folder.
- Wait for the copy-complete report before removing the stick.
- On the engineering computer, make a second untouched copy of the terminal-originated MER before attempting any conversion.
In this case the copied runtime converted to an editable application in FactoryTalk View Studio 10.00 without errors, which confirms this particular MER was built with restoration permitted; it proves nothing about the other files on the stick. The conversion workflow — opening an uploaded runtime as an application — is the subject of PanelView Plus MER file recovery: opening uploaded HMI applications.
What does the allow-decompile checkbox change when compiling? #
It decides whether the MER you compile can ever be restored to an editable application: before every compile, verify that the utility's checkbox allowing decompile or restoration is set, because some View Studio releases defaulted it to not allow.
The checkbox sits in the runtime-creation utility next to the version target. Allowed means the .mer carries restoration rights and can be opened as source later; disallowed means it runs on the terminal but never converts on a PC — the exact wall you hit when a predecessor's file refuses to open. Releases have flipped this default over the years, so check it on every compile rather than trusting the installation. If a recovered MER will not convert, assume its compiler cleared the box: keep the file as a loadable archive and rebuild any screen changes in a fresh application compiled to the same target.
How do I prove the backup is complete? #
A copy and a clean conversion are checkpoints, not proof: open the restored application, walk its displays, tags, alarms and communications, then compile a test runtime at a target at or below 8.0.10.12 and read every build message.
Work the checklist in order and keep the results with the archive:
- The USB copy shows a nonzero file size and duplicates to a second drive without error.
- The terminal-originated MER stays byte-identical; it is the rollback artifact.
- The record sheet carries the startup filename, the file size, the startup status and both displayed versions, OS 02.36.0.0 and ME Station 8.0.10.12.
- The restored application opens with its displays, global objects, tags, alarms, communications, macros and startup display present.
- The test runtime compiles clean at or below 8.0.10.12; missing components or unsupported features leave the project incomplete even when it opens.
- The test runtime sits on separate removable media, apart from the production archive.
Do not download the rebuilt MER to the running terminal to prove the compile worked; a machine that will run gets a controlled test window, a rollback copy, and verified screen and communications operation before any file is swapped.
When is rebuilding not worth it? #
Rebuild the application when edits are needed and the runtime converts; replace the terminal when the hardware is failing or the platform is discontinued, because a perfect backup does not repair a display module or revive an obsolete terminal.
- Healthy terminal, no source, runtime converts: the backup is done once the test runtime compiles clean, and every future MER compiles at or below ME Station 8.0.10.12.
- MER will not convert: it was compiled with restoration disallowed, so archive it as a loadable file and rebuild screen changes in a fresh application at the same target.
- Several MERs and no startup record: treat the job as recovery, not backup — return to Terminal Settings and read the startup option before trusting any file.
- Failing or discontinued hardware: migrate rather than rebuild. The application travels with the backup, the hardware choice follows the criteria in planning an HMI terminal replacement from an older operator panel, and where that migration lands on a computer-based station, the hardware kind is an industrial panel PC.
Questions asked
Can I upload the editable source project from a PanelView Plus?
No. The terminal stores compiled runtime MER files, not the Studio project that produced them, so an upload never returns editable source. The editable application comes back only through the restore workflow in View Studio, and only when the runtime was compiled with decompile or restoration allowed. A runtime compiled with that option cleared runs on the panel but refuses to convert.
What happens if I download a runtime compiled above the terminal's ME Station version?
The compile finishes on the PC, but the load on the terminal fails with a version error and the application does not start. The fix stays on the PC: recompile with the ME target lowered to the ME Station value recorded from System Resources. Recompiling against the OS number never fixes it, because the OS value is not an ME version.
Does restoring the application change anything on the terminal?
No. Restore and conversion run entirely on the engineering computer, and the panel keeps executing its own copy untouched. The terminal only changes when someone deliberately downloads a runtime to it in a planned transfer window, which is why the restore is the safe place to inspect the recovered application before anything touches the machine.
Which FactoryTalk View Studio release handles an old uploaded MER?
Restore and compile tooling moves forward, not backward: newer Studio seats build runtimes for older terminals, and the release notes document Studio 9.00.00 or later creating PanelView Plus 7 Standard runtimes at v8.20 or earlier. Studio 10.00 postdates that, so this generation is covered. The direction that fails is a runtime compiled for an ME version newer than the terminal.