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-8 Use Data Highway 485 Network
Programming Message Block Instructions in a Controller for Remote DH-485
Messaging
Before programming your message block instructions in your controller, you
must:
• determine which links will send and receive remote DH-485 messaging.
• draw a network to make sure you meet the design requirements for
remote DH-485 messaging.
If you are using remote DH-485 messaging, you must also:
• assign link numbers.
The numbers must be a decimal value between 1-199. ControlLogix
chassis backplane may also be assigned link IDs.
• assign DH-485 node numbers.
• use RSLinx software to load routing tables into each 1756-DH485
module.
When using remote DH-485 messaging, you must include the following in the
message instruction:
• Destination link ID - A user-defined number representing a network in
your system.
• Remote node or slot - The node or slot on the remote network with
which you want to communicate.
If the message originates on a DH-485 network, you must also include a local
DH-485 node. The node on your local DH-485 network is capable of routing
the message. If the message originates on EtherNet/IP, ControlNet, or
ControlLogix, you must also include a CIP path to the first 1756-DH485
module.