DL7000-ETH/DH+: Ethernet/IP to AB's DH+
using CIP & 2222 Protocols.
$1495 USD List

Gateway Between Allen-Bradley DH+ PLCs and AB Ethernet / Ethernet/IP.

The DL7000-ETH/DH+:  Ethernet/IP and AB Ethernet Interface to DH+.

The DL7000 is a gateway that interfaces any Newer AB Ethernet/IP & AB Ethernet PLCs (ie. SLC 5/05, Compactlogix, Micrologix or PLC-5E) or MMI/SCADA/Programming package to any device/node on AB’s DH+.

This gateway is a cost-effective alternative to the AB Controllogix Gateway (1756-ENBT and 1756-RIO).

Applications include:

• SCADA/MMI/Programming Software (RLSINX/LOGIX/VIEW,Wondware, Kepware, Citect, Intellution, et. all) packages using AB Ethernet Drivers can read/write data from/to multiple DH+ nodes.

• Any AB Ethernet & Ethernet/IP PLC (MicroLogix, SLC 5/05, CompactLogix, FlexLogix, PLC-5E, ControlLogix) will be able to send either read or write MSG (message) instructions to any DH+ PLC (SLC 5/04, PLC-5).

For details, pricing, or to find out if this DataLink now offers the DL7000-ETH/DH+ which can significantly reduce your AB Ethernet upgrading costs. Simply make the DL3500-DH+/IAP a node on DH+ and then interface to your AB Ethernet/Ethernet/IP. AB PLC users can interface bi-directionally between Allen-Bradley Data Highway Plus (DH+) and AB Ethernet (CIP & 2222 protocols).

AB Ethernet (Master) to DH+ is the optimal communication direction. This allows multiple AB Ethernet (CIP and 2222) devices to communicate to multiple DH+ nodes using the DataLink DL7000-ETH/DH+. If cost savings are a concern, the DL7000-ETH/DH+ is your gateway solution. The DL7000-ETH/DH+ interfaces newer AB PLCs (ie. SLC 5/05) on AB Ethernet and Ethernet/IP to read/write data to PLCs on DH+. This solution provides an cost efficient alternative to upgrading your DH+

Ethernet IP to DH+ protocol converter

DL7000-ETH/DH+ Applications Include: The ability to take multiple DH+ destination addresses and map to multiple Ethernet/IP addresses or multiple PLCs. A PLC on DH+ can initiate a message through the device to read a register from a PLC5/40E using the AB 222 (ethernet) protocol.

Typical examples:

SLC 5/05 read/write files/tags to SLC 5/04 on DH+

• SLC 5/05 read/write file/tags to PLC 5 on DH+
  
  
• Micrologix on AB Ethernet/IP read/write files/tags to SLC 5/04 on DH+.
• Micrologix on AB Ethernet/IP read/write files/tags to PLC 5 on DH+.
  
  
• CompactLogix on AB Ethernet/IP read/write files/tags to SLC 5/04 on DH+.
• CompactLogix on AB Ethernet/IP read/write files/tags to PLC 5 on DH+.
  
  
• PLC 5E on AB Ethernet 2222 read/write files/tags to SLC 5/04 on DH+.
• PLC 5E on AB Ethernet 2222 read/write files/tags to PLC 5 on DH+.
   
• Flexlogix on AB Ethernet/IP  read/write files/tags to SLC 5/04 on DH+.
• Flexlogix on AB Ethernet/IP read/write files/tags to PLC 5 on DH+

Multiple DH+ Nodes to AB Single Ethernet IP address:

• Communication from either a DH+ programming station (RSLINX/LOGIX) or a DH+ PLC to one AB Ethernet node (ie. PLC 5E / SLC5/05). A typical example allowing a Message Instruction to read/write data from your existing DH+ network to your new Ethernet device.

Multiple AB Ethernet devices to any DH+ node Applications include:

• MMI (WW, Kepware, Citect, Intellution, et. all) packages using AB Ethernet Drivers can read/write data from/to multiple DH+ nodes.

• Any AB Ethernet PLC (MicroLogix, SLC 5/05, CompactLogix, FlexLogix, PLC-5E, ControlLogix) will be able to send either read or write MSG (message) instructions to any DH+ PLC (SLC 5/04, PLC-5) across the DL3500-DH+/IAP bridge.

Ethernet/IP Background

EtherNet/IP (Ethernet Industrial Protocol) is an open communications protocol developed by Rockwell Automation, managed by ODVA and designed for use in process control and other industrial automation applications. EtherNet/IP can be easily confused as a combination of Ethernet (the physical layer, link, or medium used in most office and many industrial networking environments) and the Internet Protocol, the world’s most ubiquitous (internet) networking protocol and part of the TCP/IP model, comprising a suite of protocols operating at the link, internet (or networking), transport, and application layers.

By comparison, EtherNet/IP is an industrial application layer protocol operating over the Ethernet medium and used for communication between industrial control systems and their components, such as a programmable automation controller, programmable logic controller or an I/O system. Furthermore, the “IP” in EtherNet/IP, is not an abbreviation for “Internet Protocol” but instead stands for “Industrial Protocol”, referring to Rockwell’s adoption of Common Industrial Protocol (CIP) standards as EtherNet/IP was developed.

Confusing matters further is the fact that when using the OSI Reference Model, EtherNet/IP, at the application layer, operates over both Ethernet (at the physical layer) and IP (at the network layer) and thus complements each of these technologies.

History
EtherNet/IP was developed in the late 1990’s by Rockwell Automation as part of Rockwell’s industrial Ethernet networking solutions. With little or no input taken from other ODVA members, Rockwell gave EtherNet/IP its moniker and handed it over to ODVA, which now manages the protocol and assures multivendor system interoperability by requiring adherence to established standards whenever new products that utilize the protocol are developed.

Today, EtherNet/IP is most commonly used in industrial automation settings (e.g., water processing plants, manufacturing facilities, utilities) in the US and Asia for communication to and from Rockwell Automation’s Allen-Bradley-brand control systems. However, other industrial automation and control system vendors, including Opto 22 and WAGO Corporation, have developed programmable automation controllers and I/O capable of communicating via EtherNet/IP.

Schneider-Electric developed an EtherNet/IP cards for both PLC Quantum and Premium on the Unity Platform.

EtherNet/IP classifies Ethernet nodes as predefined device types with specific behaviors. Among other things, this enables:
- Transfer of basic I/O data via UDP-based implicit messaging
- Uploading and downloading of parameters, setpoints, programs and recipes via TCP (i.e., explicit messaging.)
- Polled, cyclic and change-of-state monitoring via UDP, such as RPI and COS in Allen Bradley's ControlLogix control systems.
- One-to-one (unicast), one-to-many (multicast), and one-to-all (broadcast) communication via TCP.

For details, pricing, or to find out if this solution is suitable for your application, please contact us.