Specifications

ManualsBrandsAllen-Bradley ManualsComputer equipmentControlLogix

Allen-Bradley ControlLogix Ethernet Driver Help

This equates to an ENI IP of 123.123.123.123. Since the device only supports Full Duplex DF1, a node ID is not

required.

Note: For more information on communications parameters, refer to Logix Communications Parameters.

Data Highway Plus™ Gateway Setup

DH+ Gateway provides a means of communicating with SLC 500 and PLC-5 series PLC on DH+ with the Allen-

Bradley ControlLogix Ethernet Driver.

Requirements

Ethernet/IP Interface module.

1756-DHRIO Interface Module with appropriate channel configured for DH+.

SLC500 or PLC-5 series PLC on DH+ network.

Note: DH+ Gateway models do not support automatic tag database generation.

DH+ Gateway Device ID

The device ID specifies the device IP address as well as the DH+ parameters necessary for making a connection.

Device IDs are specified as the following:

Designator

Type*

Description Formats Range

IP/Host Name N/A IP Address or host name. Decimal 0-255

1 Port ID Port to backplane. Decimal 1

Optional

Routing Path

Multiple Link,

port pairs

Specifies a way out of the Ethernet/IP interface module

and must equal 1 (port to the backplane).

Decimal *

DHRIOSlot Link Address Slot number of the 1756-DHRIO interface module. Decimal 0-255

DHRIO

Channel

DH+ channel to use. Alpha A and

DH+ Node ID DH+ node ID of target PLC in Decimal Format.** Decimal 0-99

*For more information, refer to Connection Path Specification.

**For more information, refer to "Node ID Octal Addressing" below.

Example

123.123.123.123,1,2.A.3

This equates to an Ethernet/IP of 123.123.123.123. The DH+ card resides in slot 2: use DH+ channel A and

addressing target DH+ Node ID 3 (dec).

Node ID Octal Addressing

The DH+ node ID is specified in Octal format in the PLC and requires a conversion to Decimal format for use in the

DH+ Gateway device ID. The node ID can be located in RSWho within RSLinx. It is displayed in Octal format.

Example

DH+ Node 10 (octal) in RSWho = DH+ Node 8 (decimal) in DH+ Gateway device ID.

It is important to verify communications with the proper controller. In the example above, if 10 was entered as

the DH+ node ID in the DH+ Gateway device ID, then communications would take place with Node 12 (octal

equivalent of 10 decimal) and not Node 10 (octal). If Node 12 (octal) does not exist, then the DHRIO module

would return DF1 STS 0x02. This means that the link layer cannot guarantee delivery of the packet. In short, the

DH+ node cannot be located on the DH+ network.

Note 1: For information on supplementing a device ID with a routing path to a remote DH+ node, refer to

Communications Routing.

Note 2: For more information on communications parameters, refer to ENI DF1/DH+/ControlNet Gateway

Communications Parameters.