12/08/2021 FactoryTalk ME Runtime (MER) Conversion Compatibility

Rockwell Automation
Rockwell logo
Automation
Listen
Think
Solve
Support Center Get Support  Training & Webinars Online Forum My TechConnect henriquesa… 
logo

Customer Care 

ID: IN3482 | Access Levels: Everyone

FactoryTalk ME Runtime (MER) Conversion

Compatibility
READ LATER:  Email this page  Print

To find an answer using a previous Answer ID, click here

Search Knowledgebase... SEARCH

ADD TO FAVORITES
A Inserção segura dos dados com o teclado está ativada
Document ID IN3482

Published Date 09/08/2020

Summary
FactoryTalk ME Runtime (MER) Conversion Compatibility

Content

Question
Which FactoryTalk View ME Runtime (.MER) files can be converted back to FactoryTalk View ME Development
(.MED) files with in FactoryTalk View Studio?

Note: A recent patch has been created to allow you to restore a legacy 6.00, 5.10, or 5.00 .MER or .APA file, that
was created on a 32-bit OS, on your 64-bit OS with FactoryTalk View 6.10 or higher.

Refer to Patch: Legacy ME Studio can’t restore MER created later than V10, FactoryTalk View
6.107.08.08.108.209.00. Also restore 5.0, 5.10, and 6.0 MER files on 64-bit OS.

Note: If the legacy .MER file was created on a 64-bit OS it is not restorable at all. Refer to FactoryTalk View ME
error: The runtime application file was saved in a protected format.

Answer
Read table as follows:

When a User has a Legacy MER file (a MER file compiled for version 4.0, 5.0, 5.10, 6.00) that has been Created
with 6.10 Studio (x32) (FactoryTalk View Studio ME release 6.10 on a 32-bit OS ) and wants now to upload &
convert on a x32 OS Hosting Legacy Application Manager (the Application Manager from release 4.0, 5.0, 5.10,

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/456868/loc/en_US#__highlight 1/3
12/08/2021 FactoryTalk ME Runtime (MER) Conversion Compatibility

6.00) it is Compatible

Common Compatibility Guidelines – Machine Edition:

When creating 5.0, 5.1, 6.0 FactoryTalk View ME Run-Time Files (MER) using
FactoryTalk View Studio v6.1 on a 32-bit OS, the Convert to Development option can
be set to either Allow or Never allow, since the 32-bit Watcom database can be
included in the MER file.
When creating 5.0, 5.1, 6.0 FactoryTalk View ME Run-Time Files (MER) using
FactoryTalk View Studio v6.1 on a 64-bit OS, the only Convert to Development option
is Never allow, since the 32-bit Watcom database cannot be included in the MER file.
FactoryTalk View Studio v6.1 on a 32-bit or 64-bit OS can create an MER File for
versions 3.2, 4.0, 5.0, 5.1 and 6.0.
FactoryTalk View Studio v6.1 on a 64-bit OS cannot create an MER File for versions
5.0, 5.1, and 6.0 for a 32-bit Pre-6.1 FactoryTalk View ME Station running on a None-
Windows CE based computer.
FactoryTalk View Machine Edition MER Files for versions 3.2 and 4.0 on a 32-bit or
64-bit OS do not have the option allow conversion in Conversion to Development
setting and once the .MER file is created, it can not be converted back to a .MED
Project.
FactoryTalk View Machine Edition MER Files for versions 5.0, 5.1, and 6.0 are able to
use the Conversion to Development setting.
Never allow conversion does not include the .MED Project (with DB) in the .MER
File.
Allow includes the .MED Project (with DB) in the .MER File and allows for a
restore.
FactoryTalk View Studio v6.1 on a 64-bit OS can create an MER File for versions 5.0,
5.1, and 6.0 with Never allow conversion set.
FactoryTalk View Machine Edition MER Files for versions 5.0, 5.1, and 6.0 are NOT
able to use the allow Conversion to Development setting.
Never allow conversion does not include the .MED Project (with DB) in the .MER
File and .MER File Creation is permitted.
When needed, you can use Windows XP mode in Windows 7 64bit to upload and
open older MER files (5.00, 5.10, 6.00)

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/456868/loc/en_US#__highlight 2/3
 12/08/2021 FactoryTalk ME Runtime (MER) Conversion Compatibility

The latest patch update Patch Roll-up for CPR9 SRx should be applied to your 64-bit
engineering workstation before you restore your .APA/.MER file that was converted in
a 32 bit OS using FactoryTalk Studio 6.10.

Was this answer helpful?

Yes No

RATE CONTENT

Recently Viewed

RSLogix 5000/Studio5000:
CIP Motion: Error When FactoryTalk View ME 5.00.00
Error 731-0 Failed to upload
Associating Axis with CIP (CPR9) Patch for MER will not
project. Reverting to the last
Servo Drive convert back to MED in CPR9
saved copy o...

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive
treatment of such subjects. Accordingly, the information in this web site is not intended to constitute application, design, software or other
professional engineering advice or services. Before making any decision or taking any action, which might affect your equipment, you should
consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS
WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION
CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING
DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE
POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING
SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND
NON-INFRINGEMENT. Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not
apply to you.

www.rockwellautomation.com

Copyright © 2021 Rockwell Automation, Inc. All Rights Reserved.

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/456868/loc/en_US#__highlight 3/3