Create a FactoryTalk View ME runtime application
When you create a
FactoryTalk View ME
runtime image (.mer file), the system collects the communication network configuration (topology) information from the Runtime (Target)
tab of the Communication
editor and places it inside the image. The information on the Design (Local)
tab is ignored when the FactoryTalk View ME
runtime image is created.Use the following procedure when you are ready to create a
FactoryTalk View ME
runtime image (.mer file). The steps provide an example assuming that your application reads a single data point tag from a controller on an Ethernet network. Use these steps to create the runtime application after you have designed and tested your application.To create a runtime application
- On theApplication tab, expand theFactoryTalk Linxdata server, double-clickCommunication Setup, and click theRuntime (Target) tab. You need to specify theFactoryTalk Linxconfiguration that will be active on the deployment target (for example, a terminal sitting on the shop floor).
- Often the same topology is available on both the local workstation and the target workstation. If this is true, you will need to replicate the path to the 1756-L1/A controller (as created in theCreate and test an applicationexample).
- Right-click the Ethernet driver and then clickAdd Deviceto view the devices available to the Ethernet network.
- Expand theEthernet IP Devicesfolder, expand the1756-ENBT/Adevice, clickMajor Revision 1, and then clickOK.
- Type the IP address of the 1756-ENBT/A device and clickOK.TIP:The IP address of the device can be found on theDesign (Local)tab.
- Right-click the detected1756 backplaneand then clickAdd Device.
- Expand theLogix Processorsfolder, expand the1756-L1/A, and select the latest revision. The,1at the end of the controller is the slot address in the backplane. If this is incorrect for your system, right-click and then clickPropertiesto change the address. ClickOK.
- Highlight the Line1 shortcut and then click the L1 processor you added to the configuration. Note that the Apply button becomes available. ClickApplyto save the shortcut. You have now indicated that the Line1 shortcut is attached to this L1 controller. The shortcut is not saved until you clickApply.
- ClickOKto save the configuration data and close the Communication Setup editor. The symbol Line1 is now associated with the 1756-L1/A controller on the Target tab.TIP:TheCommunication Setupeditor must be closed before you create the runtime application.
- SelectApplication > Create Runtime Applicationto create a runtime application file (.mer file) that can be executed by theFactoryTalk View MEStation.IMPORTANT:When you select to run the image packaged inside the .mer file, you will have the opportunity to either:
- Retain the currently activeFactoryTalk Linxphysical topology configuration (in other words, the configuration from a Runtime (Target) tab that is associated with a previously executed application)
or- Overwrite the currently active topology configuration with the image in the .mer file. If you answerYeswhen prompted with "Do you want to replace the terminal's current communication configuration?" the Runtime (Target) tab configuration information (in the .mer file) overwrites the currently active configuration.
Provide Feedback