IMDTouchKnowledge BaseShop main store

How-to

Converting a version 5.10 MER file for FactoryTalk View 7.0

HMI and touchscreens Published 5 min read

Short answer

Restore the version 5.10 archive in FactoryTalk View Studio 6.10 on a 32-bit Windows host; opening it there converts the tag database to the current format, so you export the tags and import them into the version 7.0 project on the 64-bit host. The Legacy Tag Database Conversion utility never runs, because Rockwell documents it as unnecessary once the upgrade to 6.1 or later happens on 32-bit Windows.

On this page
  1. Why the 64-bit host stops at the tag database
  2. What you need on each host
  3. Converting the archive, step by step
  4. Worked example: a version 5.10 archive on a 32-bit Windows XP host
  5. When the restore is refused outright
  6. Moving onward from version 7.0
  7. Questions asked

Restore the .MER on a 32-bit Windows machine running FactoryTalk View Studio 6.10, export the tag database from the project there, and import that export into the version 7.0 project on the 64-bit host. Studio 7.0 asks for the Legacy Tag Converter because the tag database inside a version 5.10 archive is in the pre-64-bit format, and the utility's export step does not run on 64-bit Windows. On a 32-bit host that wall disappears: Studio 6.10, the last fully 32-bit release, converts the database to the current format when the restored project opens, so the conversion utility is never needed on this path. One 32-bit host with 6.10 installed, used once, is the whole requirement.

Why the 64-bit host stops at the tag database #

FactoryTalk View Studio restores archives created by its own version and earlier, so a version 5.10 file opens in 6.10 without a prompt. On the 64-bit host, Studio 7.0 restores the same archive, finds a tag database in the older format, and offers the Legacy Tag Database Conversion utility — the same wall that shows up as the older-format MER file conversion error. The documented procedure for that utility is a two-system job: run it on a 32-bit system first to export the database to a CSV file, then run it again on the 64-bit system to import the CSV. Your 64-bit machine can only ever do the second half.

Rockwell's documentation for the utility also states the way around it: the utility is not needed when the upgrade to FactoryTalk View 6.1 or later happens on a 32-bit Windows operating system. Studio 6.10 performs that upgrade by itself when the restored project opens, and a tag export from 6.10 followed by an import into 7.0 finishes the move. Carrying a tag database between incompatible project formats by export and import is a general pattern, not a FactoryTalk quirk — the same idea sits behind an Excel export/import workflow for renaming TIA Portal PLC tags.

What you need on each host #

  • A 32-bit host — Windows XP SP3 or Windows 7 32-bit, a physical machine or a VM — with FactoryTalk View Studio 6.10 installed. That host runs an operating system past vendor support: keep it off the plant network and move files with removable media.
  • The 64-bit development host with FactoryTalk View Studio 7.0 at its current patch level.
  • The source .MER where both machines can reach it.
  • Administrator rights on both hosts.

Converting the archive, step by step #

  1. Confirm the version the Application Manager reports for the file; anything created at 6.10 or older takes this same path.
  2. On the 32-bit host, open the Application Manager and restore the archive with File → Restore.
  3. Open the restored project in FactoryTalk View Studio 6.10. Opening it converts the tag database to the current format — do not launch the Legacy Tag Database Conversion utility at any point.
  4. In the project tree, right-click the Tags node and select Export Tag Database, and note where the XML export lands.
  5. Copy the original .MER and the XML export to the 64-bit host.
  6. Restore the same .MER in Studio 7.0 with the Application Manager. When 7.0 offers the Legacy Tag Converter for the old-format database, decline it: the application comes across, and the current-format database arrives in the next step.
  7. Right-click the Tags node in the 7.0 project and select Import Tag Database, pointing at the XML export.
  8. Recheck what a database conversion touches. Tag names and addressing carry across unchanged; expressions and derived tags recompile against the new database, so clear those errors before building.
  9. Build a fresh .MER at version 7.00 for the terminal you are feeding — one FactoryTalk View ME project builds one PanelView runtime. Load it over the old runtime, and if the terminal rejects it, sort out the MER runtime version mismatch first.

Worked example: a version 5.10 archive on a 32-bit Windows XP host #

This is the field case that settles the question: a customer-supplied archive, created at version 5.10, that must become editable in Studio 7.0 on the shop's 64-bit computer.

Inputs. Source archive at version 5.10, read from the Application Manager at restore. A 32-bit Windows XP host running FactoryTalk View Studio 6.10 — the configuration the conversion was performed on. A 64-bit host with FactoryTalk View Studio 7.0. One XML export of the tag database as the carrier between them.

Rule. Studio restores archives from its own version and earlier, and 6.10 on 32-bit Windows brings the tag database to the current format when the project opens, with no utility involved.

Arithmetic.\n

  • 5.10 ≤ 6.10, so the restore into 6.10 is native: zero conversion prompts on the 32-bit host.
  • 7.00 > 5.10, so restoring the original archive on the 64-bit host trips the legacy-database check: one prompt, declined.
  • Version hops: 5.10 → 6.10 → 7.00 — two hops, two hosts, one XML file carried across, zero runs of the conversion utility.

Result. The application restores in 7.0, the imported tag database is in the current format, and the project builds a version 7.00 runtime.

Decision. Any .MER created at 6.10 or earlier needs the 32-bit 6.10 host exactly once. Anything created at 7.00 or later restores directly on 64-bit Studio with no legacy step. If the shop owns no 32-bit host, that missing machine is the entire blocker — reinstalling 7.0 changes nothing.

When the restore is refused outright #

A legacy Studio build can refuse a restore before tags are ever in play, and Rockwell publishes a patch for exactly that: answer ID 1059820 covers legacy FactoryTalk View Studio versions that cannot restore .MER files, with archives created in version 10.00 restoring into 9.00 and earlier, and 5.00, 5.10 and 6.00 archives among what it addresses. Take the patch from Rockwell's own support site, not from any other source.

Moving onward from version 7.0 #

Once the project is saved at 7.00 you are on the 64-bit line, and the 32-bit host retires from the story. Later releases restore earlier archives, so the jump to current software — converting an old MER file to FactoryTalk View 13, for example — starts where this conversion ends.

Questions asked

Can I run the Legacy Tag Database Conversion utility on the 64-bit machine instead?

No. The export half of that utility is built for 32-bit Windows and will not do its job on a 64-bit host, which is why the documented procedure splits it in two. Restoring the archive through Studio 6.10 sidesteps the utility altogether, and that is the simpler path whenever a 32-bit host exists.

My archive is version 5.00 or 6.00, not 5.10. Does the same procedure apply?

Yes. Studio 6.10 restores archives from its own version and earlier, so 5.00, 5.10 and 6.00 files all open there natively and take the same export-and-import path. The version on the label changes nothing about the 32-bit host requirement.

Can I skip the tag export and restore a 6.10 copy in 7.0 instead?

Yes. A project restored in 6.10 can be saved back out as a version 6.10 archive, and 7.0 restores that directly because it is a single version step up. Use the export-and-import route when the 7.0 project already exists or the two hosts belong to different shops; both routes end at a current-format database.

Does the same method work for FactoryTalk View SE or RSView32 projects?

No. Site Edition migrations from RSView32 use the Legacy Tag Database Conversion utility itself, run twice: once on the 32-bit RSView32 system to export the tag database, and once on the 64-bit FactoryTalk View SE system to import it. The 6.10 restore described here is the Machine Edition path.

Keep reading

  • How-to

    Convert an Old MER File to FactoryTalk View 13

    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.

    HMI and touchscreens

  • Troubleshooting

    Why FactoryTalk View Studio Cannot Save the Tag Database

    Build a small test project first. If it creates a runtime, the workstation is fine and the fault is in your application — most often a parameter-file name whose extra space does not match its GoToScreen button assignment, because saving a display never validates that reference. If every project fails, check the real project path for a OneDrive-redirected Documents folder, then write access, roll-up patches, a full shutdown, and finally a FactoryTalk Linx or RSLinx reinstall.

    HMI and touchscreens

  • How-to

    Open a legacy Vijeo Designer project in version 6.2

    Open the project in the release the error names — Vijeo Designer 4.7 in this case — compile and save it there, then climb release by release until 6.2 opens and builds it. Only then change the target to HMIGTO6310, configure Unitelway, and choose one documented transfer route.

    HMI and touchscreens