Preface
Page 13 of 178
The data from the Modbus TCP Master can be mapped to any of the configured Scheduled
ControlNet IO input and output assemblies being owned by the ControlNet Router.
Figure 1.5
–
Typical Setup for Modbus TCP Slave to ControlNet IO
1.3.4.
C
ONTROL
N
ET
T
ARGET
(S
CHEDULED
)
TO
E
THER
N
ET
/IP
IO
(C
LASS
1)
When ControlNet Router is configured as a ControlNet Target and EtherNet/IP Originator, a
controller (e.g. Logix Controller) can own the ControlNet Router via Scheduled ControlNet
(e.g. via 1756-CNB/R) while the ControlNet Router owns EtherNet/IP IO using a class 1
connection.
The data from the controller (e.g., Logix Controller) can be exchanged with the ControlNet
Router using the Scheduled ControlNet input and output assembly. This data, in turn, can be
mapped to any of the configured Class 1 EtherNet/IP IO input and output assemblies being
owned by the ControlNet Router.
The ControlNet Router can also exchange data with EtherNet/IP devices using the Explicit
Messaging Map. A CIP message with specific service, class, instance, and attribute can be