X hits on this document





12 / 133

Allen-Bradley ControlLogix Ethernet Driver Help


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.

Designator Type Port ID Link Address

Description Specifies a way out of the interface module in question.*

If the corresponding port is the backplane, then the link address is the slot number of the interface module that will go out.

Formats Decimal Decimal

Range 0-65535 0-255

If the corresponding port is an interface module port, then 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

*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 back plane).

Note 2: Port ID0 must be 1 (port for back plane). 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 Ethernet/IP Communication Module SoftLogix EtherNet/IP Messaging Module 1756-DHRIO 1756-CNB

Port 1 Backplane Virtual Backplane Backplane Backplane

Port 2 Ethernet Network Ethernet Network DH+ Network on Ch. A ControlNet Network

Port 3 N/A N/A DH+ Network on Ch. B 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 will result 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 back plane first or avoids the back plane all together. As previously mentioned, the latter is not supported since each hop requires a ControlLogix back plane. 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:

www. kepware.com

Document info
Document views371
Page views393
Page last viewedSun Oct 23 08:31:22 UTC 2016