Preface
Page 12 of 178
1.3.2.
E
THER
N
ET
/IP
T
ARGET TO
C
ONTROL
N
ET
IO
(S
CHEDULED
C
ONTROL
N
ET
)
When ControlNet Router is configured as a EtherNet/IP Target and ControlNet Originator, a
controller (e.g. Logix Controller) can own the ControlNet Router via EtherNet/IP Class 1 while
the ControlNet Router, in turn, owns ControlNet IO using Scheduled ControlNet.
The data from the controller (e.g., Logix Controller) can be exchanged with the ControlNet
Router using the EtherNet/IP Class 1 input and output assembly. This data, in turn, can be
mapped to any of the configured Scheduled ControlNet IO input and output assemblies being
owned by the ControlNet Router.
The ControlNet Router can also exchange data with ControlNet devices using the Explicit
Messaging Map. A CIP message with specific service, class, instance, and attribute can be
configured to execute at a configured rate with the data being stored in the internal data
space (IDS).
Figure 1.4
–
Typical Setup for EtherNet/IP Target to ControlNet IO
1.3.3.
M
ODBUS
TCP
S
LAVE TO
C
ONTROL
N
ET
IO
(S
CHEDULED
C
ONTROL
N
ET
)
When ControlNet Router is configured as a Modbus TCP Slave and ControlNet Originator,
Modbus TCP Master and read and write data to the ControlNet Router internal Modbus
Registers while the ControlNet Router owns ControlNet IO using Scheduled ControlNet.