Setup
Page 42 of 178
Figure 3.35
–
IDS Copy
–
ControlNet Target Destination Type
The destination instance will be the connection number, which in this case is always
Connection 0
. The Destination Offset is the offset in the
Mapped Data
section of the
ControlNet input assembly from where the data must be copied. The Count is the number of
bytes
that will be copied. The
Mapped Data
section will be available when using the provided
UDT for the Input Assembly.
Figure 3.36
–
ControlNet Input Mapped Data UDT
3.5.2.
O
RIGINATOR
The ControlNet Router can operate as a ControlNet connection originator for cyclic (Class 1)
or explicit UCMM data exchange. The explicit messaging can be setup in the
ControlNet
Devices
and
ControlNet Map
in the Master configuration while the scheduled ControlNet
connections are added to the
ControlNet Connections
node under the module in the Slate
project tree.
3.5.2.1.
CONTROLNET SCHEDULED DEVICE CONNECTIONS
The ControlNet Router can establish up to
10
scheduled ControlNet connections to
ControlNet IO devices. This can be done by either manually entering the connection data into
the Connection Parameter window or by using the Import Tool. The Import Tool will
automatically extract the required connection and configuration parameters from an existing
Logix configuration.
NOTE:
A maximum total of
570 bytes
can be mapped for Scheduled ControlNet
IO devices.
