1. Welcome! Thank you for joining us. We’ll get started in a few minutes.
You must join the teleconference to hear the audio portion of the broadcast. You cannot listen through your computer. Dial:
You will hear hold music until the broadcast begins. This is expected 
We will send the presentation and a recording of today’s broadcast to you within a few days after the session.

2. Messaging Through 1756-DHRIO and 1756-DH485
Name – Alex Huang
Title – Tech Support Engineer
Date – March 23rd 2017

3. 1756-DHRIO and 1756-DH485
1756-DHRIO is a dual purpose communication module
It can be used to connect DH+ Controllers like PLC and SLC504 for Programming, HMI data access, and Messages.
It can also be configured to act as a RIO Scanner.
1756-DH485 is a single purpose communication module
It can only be used to connect DH485 controllers and Devices for Programming, HMI data access, and Messages.

4. CIP Communication Syntax Basic
Before We talk about Routing In A ControlLogix Chassis, We need to know basic of CIP Syntax
The Left Most Slot in a ControlLogix Chassis is Slot “0”.
ControlLogix Message Control and Data has to be in Controller Scope.
Go To Backplane is Designated as “1”
Go Out Front Port is Designated as either “2” or “3”

5. CIP Communication Syntax Basic
A Logix Controller Message Out Through Its Own Front Serial Port. The Message Path is
2, X Where X is the Destination Node. 2 Means Going Out to Front Port.
Example 2, Message Path to Node 10
This Rule Applies to All Communication Modules on The ControlLogix Chassis.

6. CIP Communication Syntax Basic
A Logix Controller Messages Out Through Its Own Front Ethernet Port The Message Path is 2, IP Where IP Address takes Dot Format For Example 2, , Most Commonly

7. 1756-DHRIO Has Two Front Ports
In an Earlier Slide, I used “2” as “Going Out Front Port” as example. “3” Means Going Out Front Port Channel B. This Designation Only Applies to Devices with Two Ports; it Does Not Apply to Redundant Media Ports.
Channel A Has a “2” Designation in a Message Path
Channel B Has a ‘3” Designation in a Message Path

8. 1756-DH485 Also Have Two Front Ports
Channel A Has a “2” Designation in a Message Path
Channel B Has a ‘3” Designation in a Message Path

9. Without A 1756-DHRIO Routing Table
You Can Already Do A Lot Without a Routing Table. All you need to do, is to set 1756-DHRIO channel with a unique node number using its dials. (Max is Octal 77). You Can
Use RSLinx Classic Browse Across To Another ControlLogix Chassis.
Use RSLinx Classic Browse a DH+ Network.
Do CIP Messages to Another ControlLogix Controller in Another Rack Via DHRIO

10. Without A 1756-DHRIO Routing Table
Before we can do any aforementioned browsing and CIP messaging, one needs to set DHRIO Channel with a Unique node number on Its DH+ Network.
At the bottom of 1756-DHRIO, there are four dials. Use Perspective dials to set each Channel Node Address. Two dials, on the top of DHRIO, are used to set channel as RIO or DH+.

11. Without A 1756-DHRIO Routing Table
Sending A CIP MSG to Another ControlLogix Via DHRIO Without Relying On Routing Tables

12. At Default DHRIO Routing Table State
1756-L82E is Messaging through Backplane to Slot DHRIO Channel A to Node 2 of the Remote 1756-DHRIO through Backplane to 1756-L75 in Slot 1.

13. Without A 1756-DHRIO Routing Table
PLC5 or SLC504 Can Also Send A Local Message to ControlLogix Via DHRIO Without Relying On Routing Tables. We are Using L82E as target.
Needs to “Map PLC/SLC Message” Under Logic in the ControlLogix Project Using RSLogix 5000.

14. Without A 1756-DHRIO Routing Table
PLC5 or SLC504 Can Also Send A Local Message ControlLogix Via DHRIO Without Relying On Routing Tables. We are Using L82E as target.
Needs to “Map PLC/SLC Message” Under Logic in the ControlLogix Project Studio 5000.
Needs to Define the Slot of Controller in 1756-DHRIO module Configuration Under Channel Configuration Using RSLinx Classic in RSWho Window.

15. At Default DHRIO Routing Table State
PLC5 or SLC504 Can Also Send A Local Message ControlLogix Via DHRIO Without Relying On Routing Tables. We are Using L82E as target.
The Message is a Local Message Address to the Node of DHRIO Channel A. (Node 15)
The DHRIO Channel Configuration Forwards the Message to the Slot of Controller.

16. At Default DH485 Routing Table State
Without a Routine Table in DH485
Use RSLinx Classic Browse Across to Another ControlLogix Chassis
Use RSLinx Classic Browse onto DH485 Network and,
Do CIP Messages to Another ControlLogix Controller on Another Rack Via DH485
Note: You need to set the DH485 channel with a unique node number using RSLinx Classic.

17. At Default DH485 Routing Table State
How To Set 1756-DH485 Channel Node Address
In RSLinx Classic RSWho Window, Right Click on the 1756-DH485 and Select Module Configuration to Access
Channel Configuration Tabs To Set Channel Node # and Controller Slot.

18. At Default DH485 Routing Table State
Sending A CIP MSG to Another ControlLogix Via DH485 Without Relying On Routing Tables
The Message Path from L82E To L75 is
1, 8, 3, 5, 1, 1
The Message Path from L75 To L82E is
1,2,2,11,1,0

19. At Default DH485 Routing Table State
L82E MSG A SLC5/05 with Chan 0 Set as DH485 Via 1756-DH485 Without Relying On A Routing Table

20. At Default DH485 Routing Table State
DH485 SLC Can Message the L82E Without Relying On A Routing Table.
You Will Need to Map Tags In L82E Just like for PLC earlier.

21. DCS Consideration
Most DCS system that migrated from PLC to ControlLogix will work
Mapping Tags
Define The Slot of ControlLogix Controller using RSLinx Classic Module Configuration on DHRIO.

22. Why Using a Routing Table
Routing Table Advantage:
Extends The Reach of A PLC or SLC on DH+ or DH485 Network To Another Network Such as Ethernet, Controlnet plus Logix Backplane.
Limitations And Restrictions:
Not All PLC, SLC can take advantage of this Feature. There Are Hardware and Firmware Restriction.
PLC, SLC Can Only Address One Logix Controller On the Same Chassis Unless you Place Both Channel on the Same Network.
What We Need to Remember:
All 1756-DHRIO and 1756-DH485 on the same Rack uses identical Routing Table,
A Link ID is actually a PCCC implementation that Provides a unique Identifier to a Network.
Valid Link ID ranges 1 to 199 and it must be unique in the same Routing table.

23. Defining a Routing Table
You Can Define A Routing Table Using Either 1756-DHRIO or 1756-DH485 Routing Table Configuration UI If They Are On The Same Rack.

24. Defining a Routing Table
We Are Using L82E’s 1756-DH485 RT UI to Demonstrate The Process
Right Click On Backplane [Link Undefined], One can edit Link ID or Add New Communication Modules – CNB, ENET, DHRIO or DH485.
CNBR, CN2 are treated as CNB. EN2T, EN3T are Treated as ENET. Channel Link ID can be Defined by Right Click on Channel.
Note:
When Adding a New 1756-DHRIO or DH485 To A Rack That Already has An Existing 1756-DHRIO/DH485, It is better to use Existing 1756-DHRIO/DH485 to “Add” Routing Table.

25. Defining a Routing Table
We Are Using L82E’s 1756-DH485 RT UI to Demonstrate The Process

26. Defining a Routing Table
We Are Using L82E’s 1756-DH485 RT UI to Demonstrate The Process

27. Defining a Routing Table
We Are Using L82E 1756-DH485 RT UI to Demonstrate The Process

28. Defining a Routing Table
We Are Using L82E 1756-DH485 RT UI to Demonstrate The Process
As mentioned earlier, 1756-DHRIO and 1756-DH485 on the Same Rack have identical Routing Table.

29. Defining a Routing Table
This Time, We Are Using L75’s 1756-DHRIO RT UI to Demonstrate The Process

30. Defining a Routing Table
We Are Using L DHRIO RT UI to Demonstrate The Process

31. Routing Tables Of The Two Logix Racks

32. MSG Through Routing Table
After Saving the Routing Tables. The SLC505 on Link ID 11
Can MSG Node 45 PLC on Link ID 13
Can Message L75 Controller on Link ID 20
The PLC5 on Node 45 can also Message the SLC505 On DH485.

33. DH485 Node 5 SLC MSG PLC Node 45

34. DH485 SLC MSG to Link 20 L75
Map a Controllogix Tag in PLC/SLC In RSLogix 5000 (Offline)
Define the Controller Slot in 1756-DHRIO Channel

35. DH485 SLC MSG to Link 20 L75

36. Node 45 PLC MSG Node 5 SLC505

37. Adding Ethernet Controller/PC to the Mix
We Are Going To MSG
A 1756-L82E Via a 1756-EN2T in slot 1 (IP ),
The 1756-L82E Front Ethernet Port ( IP )
A SLC505 (IP ),
A Computer Running RSLinx Classic With a RSLinx CSDK Sample Application (IP ).

38. Adding Ethernet Devices to the Mix
The Purpose is to Associate an IP with a unique Link ID
1756-EWEB is on the 1756-L75 Rack, so Adding Ethernet Devices is done using Routing Table Configuration GUI of 1756-DHRIO or 1756-DH485 of that rack.
Remember to save the same Routing Table to Both 1756-DHRIO and 1756-DH486 on the same rack.

39. For SLC5/05 We Need To Do More
We Need to Add SLC505 Ch1 with a DHRIO Link ID.

40. DH+ PLC MSG To Ethernet Devices
Since All Four PLC Remote Messages Structure Are really the same; so we will just examine one
L82E IP Link ID 32
Remote Station Address is the slot # of Destination Logix Controller in Octal.

41. DH+ PLC MSG To Ethernet Devices
A caveat For PLC Remote Message to RSLinx Classic Station.
The Remote Station Address is always 77 Octal or 63 Decimal.

42. DH485 SLC MSG is no Different
It can message out its serial port configured as DH485 to 1756-DH485 and let 1756-DH485 Routing Table To Take care of rest of the Message Delivery. All We need is to add Link ID.
This Routing Table only says the Remote Link ID can be reached on Node 2 of a remote 1756-DHRIO.
Using RSLinx Classic to
Access Routing Table of the 1756-DH485 on the L82E rack. Add Link ID under DH+ Bridge Node 2.
Remember Saving the Routing Table to Both 1756-DHRIO and 1756-DH485.

43. DH485 SLC MSG To Ethernet Devices
Since All Four SLC Remote Messages Structure Are really the same; so we will just examine one
RSLinx Classic PC is (Link ID 38)
Remote Station Address is always 77 Octal 0r 63 Decimal.

44. DH485 SLC MSG To Ethernet Devices
Here is Data Reporting in Unsol Utility and RSLogix500 N7 Table. I used Radix Hex Format, so We can see the same Type of Number Shows Up.
In Unsol Utility Data Report, It is Two Byte (INT is two bytes).

45. Ethernet SLC MSG Across DHRIO
Let’s Use A Ethernet SLC do a Ethernet MSG to a DH+ PLC, ControlLogix or SLC Ch0 Itself

46. Ethernet SLC MSG Across DHRIO
Common To All These Ethernet MSG
These MSG are MultiHop MSG and the Control is 51 Words in Size Verses 14 Words PCCC MSG.
On Local/Remote, Select Remote.
On MultiHop, Select Yes; The Go ahead to Click on MultiHop

47. Ethernet SLC MSG Across DHRIO
Since L75 is The First Controller on the 1756-EWEB rack, Lets take a look at the MultiHop to It.
First Line shows going to which is 1756-EWEB’s IP.
Second Line shows from Logix Backplane to Slot 1 which is 1756-L75’s Slot.

48. Ethernet SLC MSG Across DHRIO
Let’s Take a Look at the MultiHop MSG To PLC5 at Node 45 On Link ID 13
First Line shows going to which is 1756-EWEB’s IP.
The Second Line goes to the 1756-DHRIO Slot.
The Third Line Shows MSG is Going to Remote Link ID 13
Last Line shows the Remote Station Node.
MultiHop Treats 1756 DHRIO/DH485 Modules as Equal.

49. Ethernet SLC MSG Across DHRIO
Now Let’s Take a Look at the MultiHop MSG to SLC505 Node 5 on Link ID 11
First Line shows going to which is 1756-EWEB’s IP.
The Second Line goes to the 1756-DHRIO Slot.
The Third Line Shows MSG is Going to Remote Link ID 11
Last Line shows the Remote Station Node 5.
Again. MultiHop Treats 1756 DHRIO/DH485 Modules as Equal.

50. Ethernet SLC MSG Across DHRIO
As you can see once Routing Tables and associated controller channel Link ID are setup. The Message Instructions are easy to do.

51. What Have We Noticed
Routing Table Makes Communication Possible for Older Devices Between Different Type of Networks.
Routing Table Makes Communication Possible for Older Devices to New Devices On Different Networks,
Routing Table Makes MSG programming Simple.
Routing Table also Makes Transition From Older System to A Newer System a Little Painless.

52. Commonly Seen Errors Illegal Command From Local Processor -
Data or Mapping Does not Existing in Target Controller.
Reply Not Received Before user-specified Timeout -
Potentially Destination Does not Exist or MSG path is Too Long for MSG to Complete in Time.
No IP address configured for the network -
Routing Table Link ID may not exist or MSG hit a Device that cannot forward the MSG, or Channel Link ID of the Sender is incorrectly defined.

53. Commonly Seen Errors Connection was Broken -
Check Channel Link ID assignment in Sender.
Message Time Out In local Controller -
The Destination Link ID May be Wrong or Node Address does not exist, or Not Enough Time to deliver the Message.

54. References
Knowledgebase AID ControlLogix Gateway: Data Highway Plus Communication,
Knowledgebase AID /03 on DH485 initialing a remote message to 5/04 on Data Highway Plus,
Knowledgebase AID 7335 SLC/PLC Message Mapping,
Knowledgebase AID Enhanced & Ethernet PLC5 Processor Series and Revision Enhancement History,

55. Questions