How-to
Migrate a PanelView Plus 6 project from ME 5.0 to 10.00
Short answer
Yes, the application can move from FactoryTalk View ME 5.0 to 10.00, but the runtime file itself is never version-converted. Confirm the terminal is a PanelView Plus 6 700-1500 or Compact 1000, restore an editable application from the .apa archive or a restorable .mer, convert it in FactoryTalk View Studio ME 10.00, build a new .mer at the 10.00 runtime version, and download it after flashing firmware 10.00-20180411. Part 11 compliance is a separate validation job.
On this page
Yes, the application moves from FactoryTalk View ME 5.0 to 10.00 and loads with the screens and settings intact. No, it does not move by converting the .mer runtime in place — no supported step changes a runtime file's version. The path is: confirm each terminal is in the 10.00 firmware package's hardware list, restore an editable application from the .apa archive or a restorable .mer, convert that application in FactoryTalk View Studio ME 10.00, build a new runtime at the 10.00 version, flash the terminal, download the new .mer. Every step runs on copies, so the original backups survive untouched.
Check the terminal against the firmware package first #
The migration targets PanelView Plus 6 700-1500 Firmware Upgrade Package 10.00-20180411. Its documented hardware requirements name exactly two groups: PanelView Plus 6 (PVP6) 700-1500 terminal types and PanelView Plus 6 (PVP6) Compact 1000 terminal types. The 5.0 label on the project proves nothing about the terminal; 5.0-era applications ran on more than one hardware generation.
The catalog number does not encode the generation, so read it from the unit: the terminal's identification screen and rating label state the PanelView Plus generation and the size group. Confirm each terminal against the package's entry in Rockwell's Product Compatibility and Download Center, where the compatibility data and the package itself live; Getting the Right Firmware File for a Legacy HMI Panel covers choosing the package file. The component revisions bundled in the package, such as FactoryTalk View Machine Edition 10.00.00 and FactoryTalk Linx 6.00.02, identify its contents and do not widen the hardware list.
Decision: a terminal whose identification screen reports PanelView Plus 6 in the 700 to 1500 band, or a Compact 1000, takes the flash-and-download path. Any other terminal — a 400 or 600 size, or the earlier PanelView Plus generation — has no firmware route to this package. Rockwell's release notes draw this boundary hard on other packages too: 6.10-20140122 states outright that it is not compatible with PVP6 400-600 terminals. An out-of-list terminal is replaced, not flashed; the same converted application downloads to the replacement, and where the operator station itself is due for replacement, industrial panel PCs carry the FactoryTalk View ME runtime on a supported touchscreen platform.
Back up the running terminal before anything changes #
Start on copies. Save the .mer the terminal actually runs — How to find the runtime file an HMI terminal actually loads walks the check when the terminal and the project records disagree — and locate the .apa application archive if one exists. Copy both somewhere the migration cannot reach.
Record what a project file does not carry: each terminal's identification and firmware data read from the terminal's own screens, network settings, startup behavior, and the device shortcuts and controller addresses the application talks to. Then capture the operator baseline — representative screens, navigation paths, displayed values with units and decimal places, alarm behavior, login behavior — so the converted application can be tested against something concrete. A screen opening proves only that it loaded; it proves nothing about its connections, security, alarms or data recording.
One caution, stated once: the firmware upgrade rewrites the terminal's software image, so treat everything on the terminal as disposable from the moment the flash starts — backups first, stable power, and no interruption partway through.
Turn the backup into an editable application #
The conversion runs on an editable FactoryTalk View Machine Edition application, never on a runtime file. What you hold decides the route:
| File in hand | Route | Decision |
|---|---|---|
| .apa application archive | Restore through the application-management tools in FactoryTalk View Studio | Preferred route; the result opens editable, with displays, tags, communications, alarms and security available for inspection |
| .mer with restore allowed | Use the supported restore procedure; version 5.0 and later runtimes convert back to projects when the restore option was set when the runtime was built | Usable, but check every screen — a restored runtime is a reconstruction, not the developer's original |
| .mer with restore blocked, or no backup | No conversion exists; renaming the file changes nothing | Obtain the development project from the machine builder or owner, or plan a controlled rebuild against the baseline |
Install a licensed FactoryTalk View Studio for Machine Edition at the 10.00 level, restore a working copy, and confirm it opens editable before changing anything. Save a separate migration archive of the restored application so the restore point survives your own edits.
Convert, rebuild and download #
Keep three operations separate: application conversion, runtime build, firmware installation.
- Open the restored application copy in FactoryTalk View Studio ME 10.00 and follow the application-conversion prompts. Work through every message — missing resources, unsupported objects, changed communications — before touching anything else. The screens do not need redrawing just because the development version changed, but preserved graphics still get functionally tested against the baseline.
- Verify the converted application against the recorded baseline: display sizes, object placement, fonts, navigation, alarms, security assignments, device shortcuts.
- Create a new .mer at the 10.00 runtime version. The development environment's version does not set what the terminal can run; the runtime version must match the terminal's firmware, and a lower runtime target can drop features the application needs. Any later edit repeats this build — Why an HMI Edit Needs a New Runtime Download explains why nothing new reaches the terminal without one.
- Flash the terminal with the 10.00 firmware upgrade package, using the upgrade path the package documents.
- Download the new runtime with the Transfer Utility, which sits on the Tools menu in FactoryTalk View Studio, then exercise the screens against the baseline.
If the terminal rejects the download with a version complaint, that is the runtime-versus-firmware mismatch case; Fixing an HMI MER runtime version mismatch covers the symptom and the fix. Keep the original archive, the converted development archive and the generated runtime in separate folders so each artifact stays identifiable.
Working the 2711P-T10C4D1 and 2711P-T6C5D pair from ME 5.0 to 10.00 #
Inputs: two terminals, 2711P-T10C4D1 and 2711P-T6C5D, running applications built in FactoryTalk View ME 5.0; target firmware PanelView Plus 6 700-1500 Firmware Upgrade Package 10.00-20180411; package hardware requirements of PVP6 700-1500 and PVP6 Compact 1000, from the package's release notes; one backup per application, .apa or .mer.
Rule: a terminal takes the package only if its identification screen reports a listed group, and a .mer runs only when the runtime version equals the installed firmware version.
Arithmetic: the running applications are 5.0 and the flashed terminal runs 10.00; 5.0 ≠ 10.00, so both existing .mer files stop working at the flash and two new 10.00 runtimes get built, one per application. The T10 catalog size code is the 1000 class; 1000 sits inside the 700-1500 band, so a Plus 6 generation of that size is listed. The T6 size code is the 600 class; 600 is below the band's 700 floor, and the package's only other group, Compact 1000, is a 1000-class terminal, so no 600-class unit of any generation is listed.
Result: the 2711P-T10C4D1 converts and flashes once its identification screen confirms the PanelView Plus 6 generation — flash 10.00-20180411, download the new 10.00 .mer, originals untouched. The 2711P-T6C5D has no firmware path in either generation, so it is replaced and the same converted application downloads to the replacement. That settles the original question: the screens and settings migrate while the old backups stay untouched, because every step writes new files and only reads the originals.
Decision and threshold: identification screen reports PanelView Plus 6 at 700, 1000, 1250 or 1500, or a Compact 1000 → flash and download. Anything else → replace the terminal; never flash it.
Where 21 CFR Part 11 actually starts #
The job bundles two efforts. Moving the application from ME 5.0 to 10.00 is a software migration, and the steps above complete it. Making the system support 21 CFR Part 11 is a design and validation effort that begins after the conversion is functionally proven: access control matching the site's procedures, audit trails recording who changed what and when, secure electronic records, and documented testing on the running machine. Version 10.00 is the supported platform for configuring those features; installing it configures none of them. Decision: run Part 11 as its own work package with its own acceptance evidence, sequenced after the migration — not as a by-product of the firmware upgrade.
Questions asked
FactoryTalk View Studio refuses to open the old runtime. Is the file lost?
Usually not. Rockwell's support knowledge base documents that opening or converting a runtime application from version 9.0 or earlier requires installing a patch first. Install the patch that applies to your Studio version, retry the restore, and only write the runtime off if the restore still fails or the file was built without the restore option allowed.
Can the old terminal keep running on its 5.0 application while the migration is prepared?
Yes, and that is the safe sequence. Nothing in the conversion touches the terminal; the flash and the download happen only after a converted 10.00 runtime has been built and functionally checked against the baseline. The terminal then goes down once for the upgrade and the new download, instead of sitting half-migrated while the project is still being edited.
Does moving to ME 10.00 make the HMI 21 CFR Part 11 compliant?
No. Version 10.00 is a supported platform for the features a Part 11 review examines: access control, audit trails, secure electronic records and, where required, electronic signatures. Compliance comes from configuring those features, testing them on the running machine and documenting the validation. Budget that as its own work package with its own sign-off; the firmware upgrade does not discharge it.
Do the original 5.0 files stay usable as a fallback after the conversion?
Yes. The conversion reads the .apa archive or the saved .mer and writes the converted application and the new runtime as separate files, so the originals are never modified. Keep them, with the terminal configuration record and the baseline captures, in storage the migration cannot reach; recovery then means redeploying untouched originals, not undoing a conversion.