Specifications

Allen-Bradley ControlLogix Ethernet Driver Help

Cable Diagrams

Communications Routing

Routing provides a way to communicate with a remote device over various networks. It can be thought of as a

bridge between the local device and a remote device even if they are on two different field bus networks. Access

to a remote (destination) backplane allows for direct communication with the supported modules located on this

backplane. Supported modules include the following:

l ControlLogix 5500 processor for ControlLogix applications.

l SoftLogix 5800 processor for SoftLogix applications.

l 1756-DHRIO interface module for DH+ Gateway applications.

l 1756-CNB or 1756-CNBR interface module for ControlNet Gateway applications.

A routing path is a series of backplane hops, whose last hop points to the destination backplane. Each hop

requires a Logix backplane (not a Logix processor). An individual hop can utilize one of the following networks as

its medium:

l ControlNet

l DH+

l TCP/IP (Ethernet/IP)

Important: Routing is not supported for ENI and MicroLogix 1100 models.

Connection Path Specification

The routing path is specified in the device ID. As with non-routing applications, communication originates from

the Allen-Bradley ControlLogix Ethernet Driver on the PC and is directed at the local Ethernet module. Once at this

local Ethernet module, the device ID specifies a way out of the module and onto the backplane, just like with non-

routing applications. The routing path directs the message to the desired Logix backplane. The device ID also

determines what device is communicated with (such as the ControlLogix processor, SoftLogix processor, DH+

node, or ControlNet node).

The routing path specification begins and ends with the left and right bracket respectively ([]). The path itself is

a series of port/link address pairs, identical to the communication path syntax in RSLogix 5000 Message

Configuration dialog.