About ControlNet I/O configuration
It is important to understand the difference between what is referred to as a ”ControlNet I/O configuration" and a configuration where
FactoryTalk Linx
is accessing data from a remote ControlNet device (for example, a PLC-5
C or a ControlLogix
controller via a 1756-CNB module). In a ControlNet I/O configuration, a communications interface card (1784-PKTCS for the desktop, 2711P-RN15S, 2711P-RN15C for the
PanelView Plus
device) is physically attached to the host computer upon which the FactoryTalk Linx
server is running. This ControlNet communications interface card is configured by RSNetWorx for ControlNet
to exchange I/O data on the ControlNet network. FactoryTalk Linx
, in turn, is configured to access the I/O data resident on that locally attached ControlNet communications interface. In a ControlNet I/O configuration,
FactoryTalk Linx
itself is not generating requests that cause packets to be sent on the ControlNet network. It is accessing I/O data resident on a communications interface that is locally attached to the host computer.
WARNING:
- The support for ControlNet I/O communications for the desktop has been only tested for use in application development and application test environments. Use this functionality only in a hazard-free, non-production environment. Failure to observe this precaution could result in damage to equipment, severe bodily injury, or loss of life.
- A value of 0 is assigned to any bit in the output table whose value has not been user-specified. Therefore, if an output alias does not have an initial value specified, or if an alias has not been defined for an area of the output table, a value of 0 will be assigned to it, and a warning message will be displayed. However, the ControlNet Scanner will still be able to enter run mode. You must be aware of the effect this may have on the output devices in your application since a value of 0 will be applied immediately when the ControlNet Scanner goes into run mode.
To create an application that uses I/O data from a local ControlNet Scanner, you will first configure the ControlNet Scanner in
RSNetWorx for ControlNet
. Next, you will define the I/O in the ControlNet Scanner card in the FactoryTalk Linx
user interface. This involves creating address blocks, connections, and aliases. After the I/O is defined, use FactoryTalk View ME
to associate graphic controls or other application components with the alias user names. Finally, you must copy the configuration from the
Design
tab to the Runtime (Target)
tab in FactoryTalk Linx
before you create the runtime application (.mer) and transfer it to the target CE device. Provide Feedback