Example 1: DriveLogix5730
Controller and
Distributed I/O
In the following example, one DriveLogix5730 controller controls
distributed I/O through a 1794-AENT module.
EtherNet/IP
1794-AENT with distributed I/O
(Remote1)
Controlling Distributed I/O
This example has DriveLogix1 controlling the I/O connected to the remote
1794-AENT module. The data the DriveLogix5730 controller receives from
the distributed I/O modules depends on how you configure the I/O modules.
You can configure each module as a direct connection or as rack optimized.
One chassis can have a combination of some modules configured as a direct
connection and others as rack optimized.
All analog modules require direct connections. Diagnostic modules support
rack-optimized connections, but require direct connections to take full
advantage of their diagnostic features.
Total Connections Required by DriveLogix1
The following table calculates the connections used in this example.
Connection:
DriveLogix1 to 4 distributed I/O modules (through 1794-AENT)
all I/O modules configured as direct connection
no connection to the 1794-AENT
total connections used:
If you configured the distributed I/O modules as rack-optimized, you would
only need a rack-optimized connection to the 1794-AENT, reducing the
above example by 3 connections.
Communicating with Devices on an EtherNet/IP Link
DriveLogix5730 controller
(DriveLogix1)
Amount:
4
4
6-31
Need help?
Do you have a question about the Allen-Bradley DriveLogix 5730 and is the answer not in the manual?