Specifications

ManualsBrandsAllen-Bradley ManualsComputer equipmentControlLogix

Allen-Bradley ControlLogix Ethernet Driver Help

Designator

Type

Description Formats Range

Port ID Specifies a way out of the interface module in question.* Decimal 0-

65535

Link Address If the corresponding port is the backplane, the link address is the slot

number of the interface module that goes out.

If the corresponding port is an interface module port, the link address

specifies a destination node as follows.

- DH+/ControlNet: node ID

- Ethernet/IP communication module: IP address

- SoftLogix Ethernet/IP module: IP address

Decimal 0-255

*For more information, refer to "Port Reference" below.

Single Hop

IP Address, Port ID0, [Link Address0, Port ID1, Link Address1, Port ID2], Link Address2.

Multi-Hop (N Hops)

IP Address, Port ID0, [Link Address0, Port ID1, Link Address1, Port ID2, Link Address2, ... Port ID(N+1), Link

Address(N+1), Port ID(N+2)], Link Address(N+2).

Note 1: The last port ID in the path (Port ID2 and Port ID(N+2) for single-hop and multi-hop respectively) must

be 1 (port for backplane).

Note 2: Port ID0 must be 1 (port for backplane). Link Address2 and Link Address (N+2) are the slot numbers of

the remote Logix processor/1756-DHRIO module/1756-CNB module.

Port Reference

Interface Module Port 1 Port 2 Port 3

Ethernet/IP Communication Module Backplane Ethernet Network N/A

SoftLogix Ethernet/IP Messaging Module Virtual Backplane Ethernet Network N/A

1756-DHRIO Backplane DH+ Network on Ch. A DH+ Network on Ch. B

1756-CNB Backplane ControlNet Network N/A

Application Notes

1. Messages cannot be routed in or out of the same interface module channel more than once within the

path. Doing so results in CIP error 0x01 Ext. error 0x100B.

2. For multiple channel interface modules, messages cannot be routed into and then immediately out of that

same module (using different channels), regardless of whether the message is directed to the backplane

first or avoids the backplane all together. As previously mentioned, the latter is not supported since each

hop requires a ControlLogix backplane. An example would be to route a DH+ message from one DH+ link

(such as Channel A of 1756-DHRIO) to another DH+ link (such as Channel B of same 1756-DHRIO)

through one 1756-DHRIO-interface module. This is commonly referred to as Remote DH+ messaging and

is not supported.

Routing Examples

The routing examples below include the entire device ID minus the IP of the local 1756-ENBT. The perspective of

the device ID/routing path is from the local 1756-ENBT Module. Hop descriptions are in the following form:

Link Address (N), Port ID(N+1), Link Address(N+1), Port ID(N+2)

Note: For more information, refer to Connection Path Specification. For further details on building a

connection/routing path, refer to Allen-Bradley Publication 1756-6.5.14, pp. 4-5 through 4-8.

In the illustration below, all DH+/ControlNet node IDs are specified in Decimal format. The node ID specified in

the PLC and displayed in RSWho is in Octal format. Descriptions of the colors are as follows:

l Green = Ethernet

l Blue = DH+