User Manual
Table Of Contents
- 1756-UM532A-EN-P
- Important User Information
- Table of Contents
- Purpose of This Manual
- Preface
- 1756-DH485 Module Overview
- Overview of the DH-485 Network
- Introduction
- DH-485 Network Description
- DH-485 Network Protocol
- DH-485 Token Rotation
- DH-485 Network Initialization
- Devices that Use the DH-485 Network
- 1747-AIC Isolated Link Coupler for DH-485
- 1761-NET-AIC Advanced Interface Converter Product Overview
- Operating Modes
- Device Compatibility
- Misconception about the 1761-NET-AIC Converter
- 1747-UIC USB to DH-485 Interface Converter
- Example System Configuration
- Important Planning Considerations
- Additional Resources
- Use Data Highway 485 Network
- Use RSLinx Software to Create a Routing Table
- Communicate from an SLC 5/03 Controller to a Logix Controller over a DH-485 Network
- Communicate Between SLC Controllers over DH+ and DH485 Networks
- Communicate Between a PLC-5 Controller and a Remote SLC 5/03 Controller over Multiple DH-485 Networks
- Communicate from an SLC 5/05 Controller to an SLC 5/03 Controller over an EtherNet/IP Network
- Communicate to a SLC 5/03 Controller on a DH-485 Network
- Communicate from a Logix Controller to an SLC 5/03 Controller over EtherNet/IP and DH-485 Networks
- Specifications
- Troubleshoot the 1756-DH485 Module
- Index
- How Are We Doing?
- Rockwell Automation Support
- Backcover

Publication 1756-UM532A-EN-P - May 2006
3-14 Use Data Highway 48 5 Ne two rk
Use the Common Industrial
Protocol (CIP) Messaging
Common Industrial Protocol (CIP) is the communication mechanism on
ControlLogix chassis, ControlNet, and EtherNet/IP networks with the
Encapsulation Protocol (EPIC) protocol.
Like DH-485 messaging, CIP supports communication between devices on
the same link and physically separate links. However, CIP messaging uses a
different method to route messages than DH-485 messaging.
CIP uses a relative path concept for routing messaging. Because the message
itself, or the connection the message is sent on, contains all the information
required to route the message, CIP messages do not require any routing table
or link IDs.
Devices such as ControlLogix devices, devices that use the ControlNet
network, and devices that use CIP protocol support this new type of
communication.
IMPORTANT
Your 1756-DH485 module supports bridging CIP
messaging over a DH-485 link. However, your
1756-DH485 module does not support bridging CIP I/O
data from a ControlLogix controller to an 1756-I/O
module.