How-to
Convert an Old MER File to FactoryTalk View 13
Short answer
Renaming a v4.0 .mer or picking a newer runtime in Studio converts nothing: the documented path is restoring the runtime in FactoryTalk View Studio, auditing what came back, and rebuilding what did not. Plan for alarm messages to be lost on a v4.0 restore.
On this page
A version 4.0 .mer from a PanelView Plus 700 does not become a FactoryTalk View 13 application by renaming it, and picking a newer runtime version at creation time converts nothing either. The documented path is to restore the .mer in FactoryTalk View Studio, audit what comes back against the old terminal, and rebuild whatever did not survive. Reported results on v4.0 restores are that alarm triggers come back while alarm message text does not, so plan for message loss from the start. With the old station identified as 2711P-RP1 Series E Rev C, the replacement 2711P-T7C21D8S, and FactoryTalk View version 13 installed, this is an application migration, not a terminal fault.
Why the file will not simply move across #
A .mer is the runtime package Machine Edition builds for a terminal to execute; it is not an editable project. Two shortcuts are therefore closed.
Renaming the file or its extension does not touch the runtime version stamped inside the package. And the runtime version selected when a new .mer is created in Studio only sets the target of an application that is already editable; it never reads an old runtime in.
Reuse is closed the same way. Rockwell's published PanelView Plus application and firmware compatibility documentation states that Machine Edition applications of versions 5.10, 6.00, 6.10 and 7.0 Compact run on PanelView Plus 7 Standard terminals. Version 4.0 is not in that set, so this file must be converted rather than reused. When versions do line up and the terminal still refuses the file, that is a different fault, starting with fixing an HMI MER runtime version mismatch; the hardware-side decisions around the swap are covered in planning an HMI terminal replacement from an older operator panel.
Restore the runtime in FactoryTalk View Studio #
- Keep the original untouched. Work on a duplicate of the .mer only, and keep the old terminal powered as the working reference — it is the only place the current alarm text and screen behavior still exist.
- Confirm the version from the software. Studio reports the runtime version during the restore attempt. Expect 4.0 here; the machine's build year is background, not a version check.
- Confirm what is installed. The restore runs in the Machine Edition development component of FactoryTalk View Studio; a runtime-only installation restores nothing. Version 13 with the Studio development tools is the working environment for this job.
- Run the restore. Point Studio's documented restore function at the duplicate .mer, converting the runtime back into an editable application, without running the application as a runtime. A load-time error can appear while the restore still proceeds; the messages the restore itself produces are the ones that decide the outcome.
- Record every message verbatim. "Conversion failed" distinguishes nothing; the exact wording separates a file-version limitation from a missing software component.
- Keep the restored project and the .mer apart. Opening the restored application in version 13 changes its development format, so the untouched .mer remains the fallback if the audit fails.
Audit what came back, then decide #
An alarm trigger is the condition that activates an alarm; the alarm message is the operator-facing text that explains it. One surviving does not establish the other, so count them separately.
Worked example with illustrative numbers: a v4.0 restore returns an application with 22 displays, 156 tag expressions, and 34 alarm triggers with 0 alarm messages, while the old terminal's banner shows 34 distinct alarm texts. That leaves 34 − 0 = 34 message texts to rewrite from documentation, and 22 + 156 = 178 displays and expressions to check one by one against the running panel.
The decision line, and it holds for any v4.0 file: missing alarm messages keep you on the restore path, because text is rewritten from approved documentation and verified line by line. Missing or mangled expressions, commands, security assignments or displays move you to the rebuild path, because logic cannot be guessed back from a trigger name. Runtime user accounts need a separate check in every case — why a restored MER loses your PanelView Plus runtime users covers what to re-create before commissioning.
When Studio refuses the restore #
Restore support is version-specific: Rockwell publishes a patch that restores version 5.1 .mer files in Machine Edition v6 and later, and that patch does not cover 4.0. A refusal on a v4.0 file therefore ends the documented restore route, and two moves remain — vendor support with the exact file and verbatim messages, or the rebuild below. Studio rejecting an older-format .mer during conversion is its own error pattern with its own fixes, covered in fixing the older-format MER conversion error.
Rebuild when logic did not survive #
The rebuild draws on approved machine documentation, the controller tag database, and the old terminal while it still runs: photograph every screen, capture the alarm banner in each alarm state, record the tags the application touches, and rewrite each alarm message from verified machine-specific text. Never infer an operator message from a trigger name — an operator acting on guessed alarm text is working with wrong information, and that is a safety exposure, not a cosmetic gap. The full procedure when no project exists anywhere is covered in replacing an old HMI when no project files exist.
If the rebuild coincides with a hardware decision, a Machine Edition application also runs as a PC runtime, so industrial panel PCs are a valid target for the same rebuilt application.
Prove the application before the machine runs #
Create the new .mer at a runtime version the replacement terminal's firmware supports, per the same compatibility documentation, and clear every generation error and warning before transferring. Then test in a controlled maintenance state: a startup screen proves only that the terminal loads the file. Walk every screen, exercise every command, force each alarm and read its text, and compare displayed values against the controller. Screens that load while values sit dead point to a communication fault rather than a conversion fault — start with why an MER download shows no live data on the HMI. Retire the old terminal only after the audit items are closed.
Questions asked
Can a version 4.0 .mer run directly on a PanelView Plus 7?
No. Rockwell's compatibility documentation lists Machine Edition application versions 5.10, 6.00, 6.10 and 7.0 Compact as running on PanelView Plus 7 Standard terminals, and 4.0 is outside that set. Read the replacement terminal's firmware version from the terminal itself before applying the list, because the supported combinations are stated per firmware family.
Will renaming the .mer to .zip and extracting it work?
No. Renaming changes the file name, not the runtime version stamped inside the package, and extracting the archive recovers fragments at best — it does not produce an editable Machine Edition application. The supported route is Studio's restore function. If that refuses the file, the routes are the vendor's documented patch path or a rebuild, not manual extraction.
What is usually missing after restoring an old .mer?
Reported experience with version 4.0 restores is alarm triggers surviving while alarm message text does not, with other content sometimes incomplete as well. Judge the result by what you can verify against the old terminal, not by what opens: a running display proves nothing about its commands, expressions or security. Treat anything you cannot verify as missing and rewrite it from documentation.
Where should rewritten alarm message text come from?
From approved machine documentation: the machine builder's alarm list, the OEM manuals, or your own controlled records. Verify each line against the old terminal's banner in the matching alarm state. Trigger names are engineering shorthand, not operator text, so they are a cross-check at most and never the source of the message.
Do runtime users and passwords survive the conversion?
Plan on them not surviving. Runtime user accounts are held separately from the application content, so a restored or freshly downloaded .mer can arrive without them. Re-create the accounts from your security records, verify each login before the machine returns to service, and resist widening access to save commissioning time.
Does the old terminal need to stay in place during all this?
Yes, until commissioning is finished. It is the only running copy of the current screen behavior and alarm text, and every audit count in the procedure is checked against it. Photograph the screens and the alarm banner in each alarm state before anyone disconnects it, so the reference survives even if the hardware does not.