Rockwell Automation Allen-Bradley DriveLogix 5730, User Manual

Page: 153 / 209

Communicating with Devices on an ControlNet Link 7-19
Example 1: Total Connections Required by DriveLogix1
The following table calculates the connections used in this example.
If you configured the remote I/O modules as rack-optimized, you would
only need a rack-optimized connection to the 1794-ACNR15, reducing the
above example by 3 connections.
Example 2: DriveLogix5730
Controller to
DriveLogix5730 Controller In the following example, one DriveLogix5730 controller communicates
with another DriveLogix5730 controller over ControlNet. Each DriveLogix
controller has its own local I/O.
Example 2: Sending a MSG Instruction
To send a MSG from DriveLogix1 to DriveLogix2:
1. For DriveLogix1, create a controller-scoped tag and select the
MESSAGE data type.
2. Enter a MSG instruction.
In this example logic, a message is sent when a specific condition is met.
When count_send is set, the ladder logic sends the count_msg MSG.
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 remote 1794-ACNR15 1
DriveLogix1 to 4 remote I/O modules (through 1794-ACNR15)
all I/O modules configured as direct connection
no connection to the 1794-ACNR15 4
total connections used: 9
DriveLogix5730 Controller
(
DriveLogix1 )
ControlNet
DriveLogix5730 Controller
(
DriveLogix2 )
workstation