7-22
Communicating with Devices on an ControlNet Link
Each produced tags requires one connection for the producing controller
and an additional connection for each consuming controller. Each
consumed tag requires one connection.
Example 2: Total connections required by DriveLogix1
The following table calculates the connections used in this example.
If you configured the local I/O modules as rack-optimized, you would only
need the DIN-rail connection to the I/O modules, reducing the above
example by 3 connections.
Example 3: DriveLogix
Controller to Other Devices
In the following example, one DriveLogix controller communicates with a
Logix5550 controller and a ControlNet PLC-5 controller over ControlNet.
Connection:
Amount:
DriveLogix1 controller to 3 local I/O modules
rack-optimized connection for the DIN rail
direct connection for each I/O module
1
3
DriveLogix1 controller to local 1788-CNC
0
DriveLogix1 controller to remote 1788-CNC
0
connected, cached MSG from DriveLogix1 to DriveLogix2
1
produced tagA
produced from DriveLogix1 to DriveLogix2
other consumer (2 are configured)
1
1
produced tag
A
produced from DriveLogix1 to DriveLogix2
other consumer (2 are configured)
1
1
consumed TagB
1
total connections used: 10
DriveLogix5730 Controller
(
DriveLogix2
)
ControlNet
DriveLogix5730 Controller
(
DriveLogix1
)
ControlLogix Controller
(
Control1
)
ControlNet PLC5
Controller
(
PLC5C1
)
Summary of Contents for Allen-Bradley DriveLogix 5730
Page 6: ...4 ...
Page 10: ...p 4 Notes ...
Page 22: ...1 12 What is DriveLogix5730 Notes ...
Page 68: ...3 20 Placing and Configuring Local I O Notes ...
Page 134: ...6 36 Communicating with Devices on an EtherNet IP Link Notes ...
Page 182: ...9 10 Communicating with Devices on a DH485 Link Notes ...
Page 200: ...B 10 Access Procedures Notes ...
Page 205: ......
Page 206: ......
Page 207: ......