Design (Local) and Runtime (Target) tabs on the Communication Setup editor

When used with
FactoryTalk View ME
,
FactoryTalk Linx
manages two separate sets of topology data and keeps track of the shortcut references into both sets as described below:
  • the set on the local workstation, which is used to build and test applications (
    Communication Setup
    editor
    , Design (Local)
    tab. This was called the Local tab in versions prior to CPR 9.)
  • the set that will be deployed to the actual target device, for example, a
    PanelView Plus
    (
    Communication Setup
    editor
    , Runtime (Target)
    tab. This was called the Target tab in versions prior to CPR 9.)
A single shortcut can reference a different device in each topology data set.
To open the
Communication Setup
editor from the Explorer, double-click
Communication Setup
under the
FactoryTalk Linx
data provider. The two tabs on the editor,
Design
(Local) and
Runtime
(Target), provide different functions and perspectives for setting up communications.
TIP:
The
Runtime
(Target)
tab shortcuts are the only shortcuts copied into the runtime (.mer) file. You must either manually add the shortcuts to the
Runtime (Target)
tab, or copy the
Design (Local)
tab configuration to the
Runtime (Target)
tab before you create the runtime application to be able to use the shortcuts. Note that if you copy the configuration to the
Runtime (Target)
tab, you should verify that the shortcuts reference the correct devices.
Design (Local) tab
Runtime (Target) tab
Displays a view of the system from this workstation's (the development computer's) perspective. That is, it reflects the view of the topology from the
FactoryTalk Linx
server on this workstation. The
FactoryTalk Linx
Design (Local)
tab is similar to
RSLinx Classic
's online view of the system.
Displays (offline) the offline configuration from the perspective of the target HMI device that will be running the application and comprises the topology that will be loaded into the target device.
Allows you to create and test your application on this workstation before you actually deploy the application to a target device.
Allows you to create the runtime application that will be delivered to and activated on a deployment target such as a
PanelView Plus
terminal or a
FactoryTalk View ME
Station desktop computer.
Is online enabled, which means it is capable of browsing attached networks and automatically discovering devices when you click on a node (whether a device or driver) or select
Start Browsing
from the context menu on that node. The online mode and browse status indicator appear at the bottom of the tab.
Is an offline configuration tool only, which requires you to right-click and manually add drivers, devices, and shortcuts. The offline mode status indicator appears at the bottom of the tab.
As you add drivers, devices, and shortcuts to the
Design (Local)
tab, this information is stored to a file and is used for testing the application. The communications you configure on the
Design (Local)
tab are not used for the runtime project unless you copy them to the
Runtime (Target)
tab before the runtime application is created.
The runtime tab data, along with other information, is written to a .mer file when you click
Application > Create Runtime Application
. The .mer file is deployed when you use the File Transfer Utility and select a target (such as a
PanelView
700).
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal