User Manual

ManualsBrandsRockwell Automation ManualsEquipment1756-DH485 ControlLogix DH-485 Communication Module User Manual

Table Of Contents

1756-UM532A-EN-P
Important User Information
Table of Contents
Purpose of This Manual
Preface
- Who Should Use This Manual
- Other Resources
1756-DH485 Module Overview
- Introduction
- What the Module Does
- Module Requirements
- Module Features
- Prevent Electrostatic Discharge
- Removal and Insertion Under Power
- Typical Applications
- Remote Messaging
  - Remote Upload and Download
- Routing Limitations
  - DH-485 and CIP Messaging
  - Alphanumeric Indicators
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
  - Node Address Identification
- Misconception about the 1761-NET-AIC Converter
- 1747-UIC USB to DH-485 Interface Converter
- Example System Configuration
  - Configure the SLC 5/03, SLC 5/04, and SLC 5/05 Controller Channel 0 for DH-485
- Important Planning Considerations
  - Hardware Considerations
  - Software Considerations
- Additional Resources
Use Data Highway 485 Network
- Introduction
- What Is Data Highway 485?
  - Link Design
- Two Methods of Communication Over a DH-485 Network
- Use DH-485 Messaging
- Configuration Information in DH-485 Messaging
- Application Timeout
- Example DH-485 Network Routing Configuration
- Use the Common Industrial Protocol (CIP) Messaging
Use RSLinx Software to Create a Routing Table
- Introduction
- Choose the Correct Software
- Use RSLinx Software to Create a Routing Table
  - What Is a Routing Table?
  - ControlLogix Routing
- Create the Routing Table
  - Set the Controller Slot
Communicate from an SLC 5/03 Controller to a Logix Controller over a DH-485 Network
- Introduction
- Hardware Configuration
- Use the Controller Slot to Route the Local Message
- Create a Local Message in RSLogix 500
- Configure the Message
- Create a Logic Map for the Local Message in RSLogix 5000 Software
Communicate Between SLC Controllers over DH+ and DH485 Networks
- Introduction
- SLC 5/04 Controller Sends a Remote Message
- SLC 5/03 Controller Sends a Remote Message
Communicate Between a PLC-5 Controller and a Remote SLC 5/03 Controller over Multiple DH-485 Networks
- Introduction
- Hardware Configuration
- Create the Routing Table
  - Configure the PLC-5 DH+ Channel 1A Link ID
- Create a Message in RSLogix 5
- Configure the Message
Communicate from an SLC 5/05 Controller to an SLC 5/03 Controller over an EtherNet/IP Network
- Introduction
- Hardware Configuration
- Create a Message in RSLogix 500
- Configure the Message
- Review the Multihop Feature in RSLogix 500
Communicate to a SLC 5/03 Controller on a DH-485 Network
- Introduction
- Hardware Configuration
- Create a Message in RSLogix 5000
- Configure the Message
Communicate from a Logix Controller to an SLC 5/03 Controller over EtherNet/IP and DH-485 Networks
- Introduction
- Hardware Configuration
- Create a Remote 1756-ENBT Message in RSLogix 5000
- Configure the Message
Specifications
Troubleshoot the 1756-DH485 Module
- Introduction
- Check Power Supply and Module Status
- Interpret the LED Status Indicators
- Interpret the Alphanumeric Indicators
- Interpret the OK Status Indicator
- Routing Errors in DH-485 Messaging
  - Routing Errors in Local DH-485 Messaging
  - Routing Errors in Remote DH-485 Messaging
Index
- Numerics
- A
- C
- D
- E
- F
- H
- L
- M
- N
- P
- R
- S
- T
- U
  - Installation Assistance
  - New Product Satisfaction Return
How Are We Doing?
Rockwell Automation Support
Backcover

Publication 1756-UM532A-EN-P - May 2006

3-12 Use Data Highway 48 5 Ne two rk

Application Timeout

When an error occurs while sending a message to a remote link, it appears to

the sending station as an application timeout because error messages are not

routed back. When an error occurs during routing, it may be dropped.

For example, if an SLC 5/03 controller sends a message to another SLC 5/03

controller, and the second SLC 5/03 controller’s buffers are full, three

things happen:

• The SLC 5/03 controller refuses the message because the buffers are

full.

• The originator detects an application timeout when no reply is received.

• The originator increments its error count.

The SLC 5/03 controller can retry to send the message later. This figure

shows an example of an application timeout.

Example of an Application Timeout

DH485

ControlLogix Chassis

44068

Routed messages sent

over the bac kplane.

1756-DH48 5 Module

SLC 5/03 Controller

1756-DH485 Module

SLC 5/03 controller detects an

application timeout and

increments an error bit.

DH-485 Link 1

DH-485

Link 2

SLC 5/03 controller

buffers are full.

AIC+

AIC