Home

1756-UM532 - Rockwell Automation

1. e The remote 1756 DHRIO module is node 12 octal or 10 decimal 2 a DD BE DH RII Ll oa il Channel A 4 0 ie i A E I E lel Q le S iis DH 485 network e The communication path goes from the local ni RRE 1756 DHRIO module across the DH network to through link another 1756 DHRIO module on the same DH Fs couplers 5 network 1 AIC lo e This 1756 DHRIO module at node 12 is located on the same backplane as a 1756 DH485 module in slot 14 3 Channel A 4 of the 1756 DH485 module is on a DH 485 network 5 with an SLC 5 03 controller as node 1 6 The SLC 5 03 controller receives the message 6 Publication 1756 UM 532A EN P May 2006 Communicate to a SLC 5 03 Controller on a DH 485 Network 93 Create a Messa ge in This is the message fot the example configuration RSLogix 5000 2S RSLogix 5000 MainProgram messages B Bist amp ejej ef mm y Se re Evi eei RemRun i E Run Mode x v ES Vi Controller OK See ae TIE A Input Output E 1 0 Not Responding I3Ed rianoy MN B al Jed zd wise sex wish a Controller dwight1 Controller Fault H 2 Power Up Handle bit dh485 1 B a MainProgram Type SLC Typed Read Program T Message Control msg dhrio remote
2. Personal Computer Q o SLC 5 03 5 04 or 5 05 3 M odular Controller SLC 500 20 Point Fixed DBA HE Eus Controller with 2 Slot 7 1 1747 UIC e Expansion Chassis Interface cV S f Converter LAUR L761 NETAIC DH 485 Network q a Interface max length 1219 m 4 000 ft 7 onverter n 1747 Al z a age E DeC a ima ET Link NET m 1761 NETAIC uae 6 E Data Table BIETCISEFIEEEE co Access q np es x M odule mi d din SLC 5 01 M odular Controller A F M ER or al A SLC 500 Fixed Controller SLC 5 02 M odular Controller Publication 1756 UM 532A EN P M ay 2006 PanelView ControlLogix Controller an Communications M odule d 1756 DH485 44138 DH 485 Overview of the DH 485 Network 2 9 Configure the SLC 5 03 SLC 5 04 and SLC 5 05 Controller Channel 0 for DH 485 The RS 232 port channel 0 of the SLC 5 03 SLC 5 04 and SLC 5 05 cont
3. LL EG ODE y gt ona SLC 5 03 PanelView Publication 1756 UM 532A EN P M ay 2006 MicroLogix SLC 5 03 PanelView 44056 1756 DH485 M odule Overview 1 9 Alphanumeric Indicators When you apply power to the module the alphanumeric display begins to cycle through the following sequence 1 2 10 All LEDs flash on then off CHA CHB OK OK displays red then changes to green INIT displays Firmware Revision flashes on scrolling display DH 485 Channel A and the network used for channel A Channel A node address Channel A status Channel B and the network used for channel Channel B node addtess Channel B status This sequence runs continuously during normal module operation SIN LIE For example if your module uses the following e Channel A for DH 485 with node address 14 e Channel B is not connected and the channels are operating properly you see the following sequence A DH A 14 A OK B DH B 00 ONLY NODE Refer to Appendix B Troubleshoot the 1756 DH485 Module and publication 1756 IN587 the ControlLogix DH 485 Communications Module Installation Instructions for more information about LEDs and status indicators Publication 1756 UM 532A EN P M ay 2006 1 10 1756 DH485 M odule Overview Notes Publication 1756 UM 532A EN
4. a ono jooo o dins A AC AIC Link Coupler p i un A OA 0 AIC Link Coupler la BH BEE E BEER BB 44052 SLC 5 03 Controller Because a local DH 485 message has only enough address information to get the message to a target node on the same DH 485 network the 1756 DH485 module that receives this message cannot identify where to send the message The 1756 DH485 module uses the Controller Slot configuration parameter in RSLinx software to send the message to the local controller Local DH 485 messaging does not require a populated routing table Local DH 485 messaging does require a default or applied controller slot for each channel configured for a DH 485 network IM PORTANT Local DH 485 Messaging can target only one ControlLogix controller per DH 485 channel The ControlLogix controller must reside in the same chassis as the 1756 DH485 module receiving the message Refer to Remote DH 485 Messaging on page 3 5 for more information Use Data Highway 485 Network 3 5 Limitations of Local DH 485 Messaging When using Local DH 485 Messaging you must remembet the DH 485 message contains only a node ID for a node on the DH 485 network e a local DH 485 message sent to the node ID of a port on the
5. DH Network AIC DH485 network communicating D A9 through link couplers le EHE E ERE mG 6 A B EN EHE ER SLC 5 04 Controller initiates the message 1 44063 SLC 5 03 Controller 4 Publication 1756 UM 532A EN P May 2006 Communicate Between SLC Controllers over DH and DH485 Networks 6 3 Create the Routing Table in RSLinx Software These are the routing tables needed for the example configuration This is the routing table forthe 1756 DH485 module In this example the e SLC 5 04 controller is on the DH netwotk e SLC 5 04 controller is node 10 octal SLC 5 04 controller connects to a 1756 DHRIO module at node 56 octal or 46 decimal connection is on Channel B of the 1756 DHRIO SLC 5 04 controller sends a remote message to the SLC 5 03 controller that is on a DH485 network The SLC 5 03 controller is located at node 1 SLC 5 03 controller is connected to Channel A of the 1756 DH85 module 1756 DHRIO module is in slot 8 of the 1756 rack and is in the same rack is a 1756 DH485 module The 1756 DH485 module is in slot 14 1756 DH485 Configuration 1756 DH485 Slot 14 i Channel 0 DH485 Link 1 Channel 1 DH485 Link Undefined Ef 1756 DHRIO Slot 8 Channel A DH Link 2 2 44 DH Bridge Node 46 i Bridge Link 12 Channel B DH Link 2
6. lo EtherNet IP Network 2 AIC jg 1756 DH485 communicates through link couplers 4 AIC O BERE B 8 EJES JE 6 EE O EEE ea a a a e Bo s SLC 5 05 controller 44065 initiates the message 1 SLC 5 03 Controller 4 Publication 1756 UM 532A EN P M ay 2006 Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller over an EtherNet IP Network 8 3 Create a M essage in This is the message for the example configuration Click on Setup Screen to RS Logix 500 configure the message RSLogix 500 Pro ETHERNET SLC505 File Edit View Search Comms Tools Window Help DS Sm E WR amp amp D e ave No Forces g H O JE 34 lt gt 4 gt ABL as pl No Edits Iz Forces Disabled 4 User 4 Bit Timer Counter Input Output Compare Lie Driver AB ETH 1 Node Od eis Ee amp Project Af E gg Help gg Controller Controller Properties B30 N120 MsG i P mm T Read Write Message E o Processor Status 1 15 Type Peer To Peer A lo Configuration Read Write Read HDN Bf Channel Configuration Target Device SOOCPU E Muttipoint Monitor ee t d meo CER ontrol Bloc a Program Files Control Block Length 51 B svso Click on Setup Screen to ccr B svsi configure the message J 4 LAD2 N120 TU Y Data Files JE Count Up ecu Cross Refe
7. Load From File Save to File Restore Defaults Refresh Cancel Apply Help Publication 1756 UM 532A EN P M ay 2006 Use RSLinx Software to Create a Routing Table 4 7 7 Assign a Link ID for the chassis backplane 1756 DH485 Configuration fs w r o MES General Routing Table Channel 0 Configuration Channel 1 Configuration Serial Port Settings A Right click on the Backplane E EEA E B Click Edit M odule mg 1756 DH485 Slot 3 Add Module Channel A DH Channel B DH Delete Module Edit Backplane Link ID C Assign Link IDs and click OK _ Link ID E Cancel Help Load From File Save to File Restore Defaults Refresh Cancel Apply Help 8 Click OK The software prompts you to download routing table changes ControlLogix Gateway Tool You have made changes to the Routing Table Do you want to download these changes to the device Answering No will discard these changes No 9 Click Yes This completes the routing table creation process Publication 1756 UM 532A EN P M ay 2006 4 8 Use RSLinx Software to Create a Routing Table A Change the controller s needed B Click OK Publication 1756 UM 532A EN P M ay 2006 Setthe Controller Slot Setting the controller slot location creates a simple way for the SLC controllers to exchange data with the ControlLogix controller as long as the SLC controller is on the same DH 485 network as
8. ER ControlLogix Controller i ControlLogix Controller 1756 DH485 oque E a Vs gt Ze looa BER y eel El B O 8 o S h 7 G 1 AIC Link Coupler E AIC Link Coupler DH485 Network re E h AIC E AIC Link Coupler tg AIC Link Coupler i p v M icroLogix an E T eT AIC Link Coupler A m fage T OX A FsBBBEB B A SLC 5 03 Controller SLC 5 03 Controller lt 4 44136 Publication 1756 UM 532A EN P M ay 2006 Remote M essaging 1756 DH485 M odule Overview 1 7 The configuration of remote messaging is similar to data highway remote I O DHRIO It is achieved through routing table functions and module configuration The multi hop functionality is available in RSLogix 5 and 500 version 6 3 or later Remote Upload and Dow nload You can bridge EtherNet IP and ControlNet networks to a DH 485 network using the 1756 DH485 module You can upload and download all MicroLogix and SLC 500 controllers on DH 485 from NetLinx netwotk by using RSLinx Classic software e PanelView Standard terminals on DH 485 from NetLinx network by using RSLinx Classic Logix controllers message via a NetLinx network through a ControlLogix gateway to the DH 485 network to all MicroLogix and SLC 5 03 and above controllers on DH 485 network RSLinx Classic software on the DH 485 network can browse through the
9. Exa mple DH 485 Network The Example of DH 485 Routing Configuration figure below shows an example DH 485 routing configuration All node numbers on DH 485 are Routi ng Configuration given in decimal Node numbers on ControlNet and slot numbers in ControlLogix chassis ate given in decimal Links IDs for all networks are given in decimal IMPORTANT Some devices in this figure have the same node number because they are on different networks Devices on the same network must have unique node numbers You must assign the node numbers Example of DH 485 Routing Configuration 1756 DH485 M odule 1756 DH485 M odule Channel A Node 15 Channel A Node 30 Channel B Node 16 Channel B Node 31 ControlLogix Controller ControlLogix Controller Slot 0 Slot 5 1 ControlLogix Chassis 1 Link ID 6 IC SLC5 03 Controller Node 30 a DH 485 Link ID 4 DH 485 Link ID 2 Link ID 5 SLC 5 03 Controller No
10. Remote Connection Betw een a Computer Running Programming Software and an SLC 500 Controller RSLogix 500 Software 1747 UIC OY A elsa m 1747 AIC 3 oooo 2000 0000 0000 0000 2000 0000 0900 0000 jc 0009 oO gt 1 8m 6 ft d d 1747 C11 k Publication 1756 UM 532A EN P M ay 2006 2 6 Overview of the DH 485 Network 1761 NET AIC Advanced Interface Converter Product Overview Operating M odes Device Compatibility Publication 1756 UM 532A EN P M ay 2006 The AIC advanced interface converter provides a communication link between various networks devices Ports 1 2 and 3 are used for making the communication connections The AIC is compatible with a variety of SLC and MicroLogix controllers and the 1756 DH485 communications module The MicroLogix controllers provide power to the AIC via port 2 s cable However if a controller is not connected to port 2 a 24V dc power supply connected to the converter s external power terminals is required The DC power source selector switch needs to be set for your particular configuration The baud rate selector switch is used to match the baud rate filter of the AIC to the netwotk baud rate This switch does not change the network baud rate and is normally left in the AUTO position In high noise environment
11. Routi ng Errors in DH 485 This section describes routing errors in local and remote messaging Messaging Routing Errors in Local DH 485 Messaging If the 1756 DH485 module has a problem with routing a DH 485 message it may return a response with an error status of DO hex A PLC 5 controller displays this error as D000 hex when monitoring the message instruction If you receive this error message take the following actions Check your message instruction to make sure a valid destination node was entered Check your default slot configuration to make sure that it matches the location of the ControlLogix controller in the chassis Make sure the 1756 DH485 module is turned on and verify chassis power is recognized by the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 Routing Errors in Remote DH 485 M essaging Troubleshoot the 1756 DH485 M odule B 5 If the 1756 DH485 module has a problem with routing a Remote DH 485 Message it may return a response with an error status of DO hex An SLC controller displays this error as D000 hex when monitoring the message instruction If you receive this error message take the following actions Check your message instruction to make sure a valid local node destination link ID and destination node were entered Check your routing table in each 1756 DH485 module that the message passes through Connect and apply power to all 1756 DH485 modules Interpret the Chann
12. Yes Yes for CIP remote messaging only Publication 1756 UM 532A EN P M ay 2006 3 10 Use Data Highway 485 Network Publication 1756 UM 532A EN P M ay 2006 Limitations of Remote DH 485 M essaging Remote DH 485 messages ate encapsulated in CIP messages and sent on CIP connections when they ate sent across ControlNet EtherNet IP and the ControlLogix chassis backplane Although this is transparent to the user there ate resource limits associated with CIP on the 1756 DH485 module The 1756 DH485 module supports up to 32 CIP connections These connections are made when devices want to send a DH 485 message out of a 1756 DH485 module s DH 485 channel The 1756 DH485 module makes these connections when it receives DH 485 message traffic The 1756 DH485 module recovers connections if they are not being used Because of the various paths involved the 1756 DH485 module responds to out of connections in one of the following ways e The 1756 DH485 module may generate a Routing Error on DH 485 for DH 485 message requests if there are no connections available e The Message Originator may generate an application timeout if a remote 1756 DH485 module has no connections available for a DH 485 Message response For more information on application timeouts refer to Application Timeout on page 3 12 The Message Originator may receive an out of connections error if the path from the originator to the 1756 DH485
13. 5 6 RSLogix 5000 Software IMPORTANT The examples use SLC 5 03 modules to send DH 485 messages In each case the use of these devices is strictly for example purposes and not an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 5 2 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Network Hardw are Configuration In this hardware configuration the communications are initiated by an SLC 5 03 controller The message is sent to a 1756 DH485 module and the 1756 Lx controller is located in slot 11 Communications Betw een an SLC 5 03 Controller and a 1756 DH485 M odule 1756 L1 Controller 1756 DH485 1 m se aon E Sa E M o ooo ooo oooO aoa ooo fle i B o B B U J j J lo o le S Ee AIC B SEB BEBE DH485 netw ork communicating through link couplers SLC 5 03 Controller 44070 Publication 1756 UM 532A EN P May 2006 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Network 5 3
14. 8 multiple netw orks connection of 1 5 netw ork definition of the Data Highway 485 DH 485 3 1 hardware considerations 2 10 plannng considerations 2 10 use the Data Highway 485 DH 485 network 3 1 P planning considerations for a network 2 10 PLC 5 communicate to a remote SLC 5 03 7 1 7 2 configure a message 7 5 configure the PLC 5 DH Channel 1A Link ID 7 4 RSLogix 5 message 7 4 prevent electrostatic discharge ESD 1 3 R remote upload and download 1 7 remote connection between a computer running programming software and an SLC 500 controller 2 5 remote Data Highw ay 485 DH 485 messaging 3 5 limitations 3 10 link IDs 3 6 programming message block instructions in a controller routing errors B 5 using routing tables 3 7 removal and insertion under power RIUP 1 4 Publication 1756 UM 532A EN P M ay 2006 routing errors in local Data Highway 485 DH 485 messaging B 4 in remote Data Highway 485 DH 485 messaging B 5 routing limitations for messages sent via the 1756 DH485 module 1 8 routing tables 4 2 4 7 definition 4 2 in remote Data Highway 485 DH 485 messaging 3 7 SLC 5 04 6 3 RSLinx create routing table 4 1 4 7 create routing tables 4 2 4 3 4 7 set the controller slot 4 8 RSLinx softw are requirement 1 1 RSLogix 500 local message 5 4 use in Data Highway 485 DH 485 messaging 4 1 RSLogix 5000 use in Data Highway 485 DH 485 messaging 4 1 S SLC 5 03 1756 DHRIO 9 4 channel 1 link ID 6 4 com
15. A ESD Immunity IEC 61000 4 2 4 kV contact discharges 8 kV air discharges Radiated RF Immunity IEC 61000 4 3 10 V m with 1 kHz sine wave 80 AM from 80 2000 M Hz 10 V m with 200 Hz 5096 Pulse 100 AM at 900 M hz Publication 1756 UM 532A EN P M ay 2006 A 2 Specifications Environmental Specifications Attribute Value EFT B Immunity IEC 61000 4 4 1 2 KV at 5 kHz on communications ports Surge Transient Immunity IEC 61000 4 5 1 kV line earth CM on communications ports Conducted RF Immunity IEC 61000 4 6 10 Vrms with 1 kHz sine wave 80 AM from 150 kHz 80 M Hz Magnetic Field Immunity IEC 61000 4 8 30 A m at 50 Hz Enclosure Type Rating None open style Certifications Attribute Value Certifications c UL us UL Listed for Class Division 2 Group A B C D Hazardous when product is marked Locations certified for U S and Canada See UL File E194810 CE European Union 89 336 EEC EM C Directive compliant with EN 50082 2 Industrial Immunity EN 61326 M eas Control Lab Industrial Requirements EN 61000 6 2 Industrial Immunity EN 61000 6 4 Industrial Emissions C Tick Australian Radiocommunications Act compliant with AS NZS CISPR 11 Industrial Emissions See the Product Certification link at www ab com for Declarations of Conformity Certificates and other certification details Publication 1756 UM 532A EN P M ay 2006 Introduction Check Pow er Supp
16. APP READ Stan 3j RSLogix 500 Stc 503 LEA amu 7 12PM Publication 1756 UM 532A EN P May 2006 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Network 5 5 Confi gure the Messa ge This is the Setup dialog for the example message MSG N9 0 14 Elements Ioj x Publication 1756 UM 532A EN P May 2006 5 6 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Network Create a Logic Map for the Local Message in RSLogix 5000 Softw are Publication 1756 UM 532A EN P M ay 2006 You must logically map the SLC data address to the ControlLogix tag To get to the Logix Map in RSLogix 5000 software go to Logic gt Map PLC SLC Messages This is the logic map needed for the example message PLC2 3 5 SLC Mapping Mala T B Introduction Chapter 6 Communicate Betw een SLC Controllers over DH and DH485 Networks This chapter describes how to set up the message communications between two SLC controllers For See SLC 5 04 Controller Sends a Remote M essage 6 2 Hardware Configuration 6 2 Create the Routing Table in RSLinx Software 6 3 Create a M essage in RSLogix 500 6 6 Configure the M essage 6 7 SLC 5 03 Controller Sends a Remote M essage 6 8 Hardware Configuration 6 8 Create the Routing Table in RSLinx Software 6 9 Create a Remote M essage in RSLogix 500 6 10 Configure the M essage 6 11 IMPORTANT The
17. ControlLogix controllers SLC controllers and other devices that use the DH 485 network These devices are called stations You can connect a maximum of 32 stations to a single DH 485 link Publication 1756 UM 532A EN P M ay 2006 3 2 Use Data Highway 485 Network Two Methods of Communication Overa DH 485 Netw ork Publication 1756 UM 532A EN P May 2006 Link Design When you design your DH 485 link you should use good design practices including laying out the link before installation We also recommend you consider the following when designing your DH 485 link e All performance requirements e Maintenance Possible future changes to the link Use a Belden 9842 or a Belden 3106A cable to connect your module to DH 485 Only connect a DH 485 network using a daisy chain configuration If you need to know how to install a DH 485 network refer to publication 1747 UM011 SLC 500 Modular Hardware Style User Manual The 1756 DH485 module acts as a bridge for two methods of communication These methods are e DH 485 Messaging Common Industrial Protocol CIP Messaging The table Types of Communication on the 1756 DH485 Module lists the devices that support each communication method Types of Communication on the 1756 DH485 M odule Type of Communication Devices and Software Support DH 485 messaging SLC 500 5 05 5 04 5 03 5 02 5 01 M icroLogix Logix controllers RSLinx and RSLogix 500 software Common Indu
18. ControlLogix gateway to any device on a NetLinx network IMPORTANT Logix controllers on a NetLinx network will not be able to initiate messages through the ControlLogix gateway to the DH 485 network to fixed SLC 500 SLC 5 01 or SLC 5 02 controllers on a DH 485 network Publication 1756 UM 532A EN P May 2006 1 8 1756 DH485 M odule Overview Routing Limitations The 1756 DH485 module can route a message through up to four communications networks and three chassis This limit applies only to the routing of a message and not to the total number of networks or chassis in a system DH 485 and CIP M essaging The 1756 DH485 module lets devices such as ControlLogix PLC and SLC controllers exchange information With the 1756 DH485 module you may exchange information between the ControlLogix PLC or SLC controllers on different networks Communication between SLC controllers on different networks is accomplished using remote messaging Communication Between SLC Controllers on Different Netw orks Data Collection and Recipe Management RSView Programming Terminal Oo O 5 5 SSS EtherNet IP Network 8 8 8 Se eleda El SS leon BE O m ControlLogix OFF ControlLogix Chassis Chassis y fa E ls o S O S DH 485 DH 485
19. Converter Product Ovetview 2 6 Operating Modest es ESAE ESSIEN n 2 6 Device Compatibilty ves wilted du p ware rent edad PCR o 2 6 Node Address Identification ooooooooooomoooooo 2 7 Misconception about the 1761 NET AIC Converter 2 7 1747 UIC USB to DH 485 Interface Converter oo ooo oo o 2 7 Example System Contado dreht e are Pla 2 8 Configure the SLC 5 03 SLC 5 04 and SLC 5 05 Controller Channel 0 for DE 485 o ilk eM RE ERR 2 9 Important Planning Considerations coser gn 2 10 Hardware Considerations 0 susunu cece ees 2 10 Softwate Considerations Vii RA Ve RARUS 2 12 Additional Reso tces ida Eu NC ARR 2 13 Publication 1756 UM 532A EN P M ay 2006 Table of Contents ii 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 Publication 1756 UM 532A EN P M ay 2006 Chapter 3 o e voe tie w teda cet eur d a ae d e Ru E ua Rd e 3 1 What Is Data Highway 485 144 edes us o uw REY eww a se REOR 3 1 Link esiti an a Ove rr SA rr dece 3 2 Two Methods of Communication Over a DH 485 Network 3 2 Use DEAS a M e5saging e Gui SOS a Oh tale ee ro aig 3 3 Local DH 485 Messaging rita tiber is en Rh 3 3 Limitations of Local DH 485 Messaging oooooooomoo o 3 5 Remote DH 485 Messaging ont ia edo eee ES 3 5 Configuration Information in DH 485 Messaging 3 11 Applicatio
20. M ay 2006 Table of Contents iv Communicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Netw orks Specifications Troubleshootthe 1756 DH485 Module Index Publication 1756 UM 532A EN P M ay 2006 Chapter 10 O ICO d a veu we er d a M C AS RO e RR MG A 10 1 Hardware Gong p Mrd OE ds pita d e ew PEEL E Ie Ie ot 10 2 Create a Remote 1756 ENBT Message in RSLogix 5000 10 3 Configure the Wes SAO o e ll p ictus 10 4 Appendix A Appendix B PONCE OMe eo a each eoa d RA cQ e pha Sept pg B 1 Check Power Supply and Module Status oo o ooomoommo ro B 1 Interpret the LED Status Indicators 442r re mni B 2 Interpret the Alphanumeric Indicators 4 2 a B 3 Interpret the OK SAS TACICHOT Leva qtu t kn Pte e Pare dut ra e sti Pa B 4 Routing Errors in DH 485 Messaging o ooocoocoocommmm B 4 Routing Errors in Local DH 485 Messaging o o ooo ooo B 4 Routing Errors in Remote DH 485 Messaging B 5 Rockwell Automation Support oooooooocmom cos Backcover Installation Assistance a ek ee EROR Backcover New Product Satisfaction Return 00 Backcover Preface Purpose of This Manual This manual describes how to understand configure and troubleshoot your ControlLogix Data Highway 485 communication interface module This manual also provides step by step procedures on how to use the 1756 DH485 module to send DH 485 messages between Contr
21. P M ay 2006 Chapter 2 Introduction DH 485 Netw ork Description Overview of the DH 485 Netw ork The information in this chapter will help you plan install and operate devices on a DH 485 network This chapter also contains information that describes the DH 485 netwotk functions network architecture and performance characteristics For See DH 485 Network Description 21 DH 485 Network Protocol 2 2 DH 485 Token Rotation 2 2 DH 485 Network Initialization 2 2 Devices that Use the DH 485 Network 2 3 1747 AIC Isolated Link Coupler for DH 485 2 4 1761 NET AIC Advanced Interface Converter Product Overview 2 6 Operating M odes 2 6 Device Compatibility 2 6 1747 UIC USB to DH 485 Interface Converter 2 7 Example System Configuration 2 8 Important Planning Considerations 2 10 Additional Resources 2 13 The DH 485 network passes information between devices on the plant floor The network monitors process parameters device parameters device status process status and application programs to support data acquisition data monitoring program upload download and supervisory control The DH 485 network offers e interconnection of 32 devices e multi master capability token passing access control the ability to add or remove nodes without disrupting the network e maximum network length of 1219 m 4000 ft 1 The network can be extended to 2 438 meters 8 000 feet b
22. Refresh You must build the routing table based on the 1756 DH485 modules in the ControlLogix chassis Each link ID for example chassis backplane channels A and B of any 1756 DH485 module in the chassis is initially undefined Publication 1756 UM 532A EN P M ay 2006 Use RSLinx Software to Create a Routing Table 4 5 6 You must assign link IDs as shown below 1756 DH485 Configuration ls w r o RAE General Routing Table Channel 0 Configuration Channel 1 Configuration Serial Port Settings A Right click on the Backplane Link Undefined 1756 DH485 module 8 LEBER UM Channel O DH 404 Modul B Click Edit M odule Channel 1 DH Be A Edit Module Module Information y r i Type 1 C Assign Link IDs and click OK ue M Slot Number E y r Link 1D s Channel 0 10 Channel 1 20 Load From File E __ Caneel Lone Cancel Apply Help IMPORTANT seep track of your Link ID assignments You need the Link ID values when you send messages via RSLogix 500 and RSLogix 5000 software Publication 1756 UM 532A EN P M ay 2006 4 6 Use RSLinx Software to Create a Routing Table The 1756 DH485 routing table displays with the link IDs defined 1756 DH485 Configuration General Routing Table Channel 0 Configuration Channel 1 Configuration Serial Port Settings amp Backplane Link Undefined E 1756 DH485 Slot 3 Channel 4 DH Link 10 Channel B DH Link 20
23. Search Comms Tools Window Help DSE 8 RAQOD o ALETE oo NN Q Treo o o mm No Edits e Forces Disabled IBI Driver AB KT 1 Node 1d Uzer lt SIX Ea Sia Bit Timer Counter Input Output Compare Project Help Y Controller n Controller Properties B3 0 N9 40 Ms H Processor Sei ii Tt Resets Menge mii 2 15 Type Peer To Peer W 10 Configuration Read Write Read OND Bis Channel Configuration Target Device S00CPU cer He i Local Remote Remote Bl Mutipoint Monitor Control Block N9 40 g Program Files Control Block Length 14 syed Click on Setup Screen to Sepan SYS1 amp LaD2 on configure the message Y Data Files 0011 JE Count Up cu T Cross Reference 13 Counter C5 6 Preset 32000 lu DN ems Accum 77236 Ej 00 output El n input El s2 status E 83 BNARY x Ej T4 Timer Aa JE E cs COUNTER E rs CONTROL E n7 INTEGER E F8 FLOAT E na 0013 END E n gg Force Files Ej 00 output E n input Custom Data Monitors gt gt UTP File 2 Lecu HCDN Entry is Valid 2 0012 APP Publication 1756 UM 532A EN P M ay 2006 In this example the SLC 5 03 controller is connected to Channel A of the 1756 DH485 module The 1756 DH485 node address on the DH 485 network is node 0 Communicate Between SLC Controllers over DH and DH485 Networks 6 11 Configure the Message This is the Setup Scre
24. States 1 440 646 3223 M onday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 UM 532A EN P May 2006 PN 957988 29 Copyright 2006 Rockwell Automation Inc All rights reserved Printed in the U S A
25. The DH485 network is Efor Dscuplion assigned as link 1 No errors Publication 1756 UM 532A EN P M ay 2006 6 8 Communicate Between SLC Controllers over DH and DH485 Networks SLC 5 03 Controller Sends I this example an SLC 5 03 controller initiates a remote message and sends it Remote M essage to an SLC 5 04 controller Hardware Configuration In this hardware configuration an SLC 5 03 controller initiates a message to an SLC 5 04 controller on a DH 485 network 1 e This SLC 5 03 controller connects to Channel A on the 1756 DH485 module 2 e The SLC 5 04 controller is connected to Channel B of the 1756 DHRIO module in the same rack as the 1756 DH485 module 3 e The SLC 5 04 controller receives a remote message from the SLC 5 03 controller through the 1756 DHRIO on the DH network 4 Communication Betw een Two SLC Controllers Over DH 485 and DH Networks 1756 DHRIO 1756 DH485 ControlLogix Controller o ono ooo comm o ooo ooo ooo E ee jooo ooo ooo e Channel A 2 Channel B 3 n DH Network AIC F DH485 network I communicating AIC a through link couplers A E ERE Rg 3 Unt SLC 5 04 Controller 4 A 44064 The SLC 5 03 controller initiates the mess
26. The SLC 5 04 controller remote link ID needs to be programmed to match the link IDs configured into the 1756 DH485 module These ate labeled in the channel configuration as the Channel 1 Passthru Link ID Channel Configuration General Chan 1 System Chan 0 System Chan 0 User Channel 1 Driver Write Protected Passthru Link ID dec 20 Edit Resource Owner Timeout 41 sec 60 Diagnostic File o y Channel 0 System Driver DF1 Full Duplex Mode System y White Protected Passthru Link ID dec f Edit Resource Owner Timeout x 1sec 60 Diagnostic File o User Driver scil Mode Change Enabled Mode Attention Character Mb System Mode Character is User Mode Character U Publication 1756 UM 532A EN P M ay 2006 6 6 Communicate Between SLC Controllers over DH and DH485 Networks Create a Message in RSLogix 500 This is the message for the example configuration RSLogix 500 Pro SLC5 504 REMOTE DH485 503 File Edit View Search Comms Tools Window Help Du a Vy amp amp neo ALET e REMOTE RUN 3 No Forces ni H LT JE Yt lt gt gt gt ab aes P No Edits 2 Forces Disabled 2 Diver AB KTA Node 100 C gt User ABE X Tmericounter K npdiOuipui K Compare ei cr E Project 3 Help Y Controller 33 0 MSG i Controller Properties Read Write Message Type Peer To Peer a Processor Status Read Write Read AM 1O Configuratio
27. a routing table for your 1756 DH485 module you must assign link IDs to all networks including ENET and CNET that route information through the module Link IDs are numbers from 1 to 199 DH 485 module addressing provides the link IDs and node addresses The routing table translates link IDs and node address information into path or routing information Thus the routing table specifies a map to other links in the system Routing tables are set up at each node to build accurate connections ControlLogix Routing The ControlLogix routing protocols use CIP a message based protocol that implements a relative path to send a message from the source device in a system to the destination device In this way the source device in a networks system contains the path information that steers the message along the proper route to reach its destination Since the source device holds this information other devices along the path simply pass this information they do not need to store it ControlLogix routing has two significant benefits You do not need to configure routing tables in the bridging module greatly simplifying maintenance and module replacement You maintain full control over the route taken by each message enabling you to select alternative paths for the same end device Use RSLinx Software to Create a Routing Table 4 3 Create the Routi ng Table To create a routing table for your application follow these steps 1 Start
28. adapter e Compatible with SLC 5 03 controllers or later Publication 1756 UM 532A EN P M ay 2006 1 2 1756 DH485 M odule Overview Module Features The 1756 DH 485 module offers the following features e Sends messages between devices on DH 485 networks and devices on other networks such as ControlNet EtherNet IP or other DH 485 netwotks Bridges support to other NetLinx networks via the CLX gateway Configure channels and ports using RSLinx Classic software version 2 43 or later Accesses other networks by using a routing table editor that lets DH 485 devices use the 1756 DH485 module and ControlLogix chassis e Supports all benefits and attributes of a ControlLogix communication module e Supports firmware upgrades TIP Download firmware upgrades via the backplane Do not use DH485 network for downloads e Removal and insertion under power RIUP can be removed and inserted under power without disrupting powet to other modules in the chassis WARNING When you insert or remove the module while backplane power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that power is removed or the area is nonhazardous before proceeding Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation e 4 character display e Default C
29. link couplers 6 A DN JE ERE JEJE IE D AIC SLC 5 03 Controller 4 TE AIC ooo ooo 000 44067 Publication 1756 UM 532A EN P May 2006 Communicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Networks 10 3 Create a Remote 1756 ENBT This is an example remote 1756 ENBT message Message in RSLogix 5000 Click the button to configure the message ET Lele ole mm Bisbal ie BS ala LEE all d amp D e 2 FF 1 0 Not Responding io bit dh485 2 msg_remote_enbt_to_503_via_gate EN a Type SLC Typed Write Message Control msg_remote_enbt_to_503_via_gate msg_remote_enbt_to_503_via_gate DN T Count Up Counter dh485 counter 2 net diagnostics Preset 1000000 Accum 1410 compute msg remote enbt to 503 via gate ER TU Count Up a Counter dh485_counter 3 N5 Publication 1756 UM 532A EN P M ay 2006 10 4 Communicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Networks Configure the M essage M essage Type SLC Typed W rite Source Element interger slc dh485 20 M ake sure you specify the starting array element for example 20 Number of Elements 1 Destination Element N 7 20 Publication 1756 UM 532A EN P M ay 2006 This dialog
30. shows example values on the Configuration tab for the remote message Message Configuration msg remote enbt to 503 via gate m integer slc dh485 20 neci 7 20 Path Item series A Communicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Networks 10 5 Description This means go to the backplane to slot 5 where the 1756 ENBT named Series A is located Series A is defined as backplane 1 slot 5 This is the Communication tab for the remote message 2 EtherN et IP port 100 100 100 7 The remote 1756 ENBT 1 Go to the backplane of the remote 1756 chassis 14 Go to the slot location of the 1756 DH485 module Go out Channel A of the 1756 DH485 module Go to Node 1 or the location of the SLC 5 03 controller Message Configuration msg remote enbt to 503 via gate beries A 2 100 100 100 7 1 14 2 1 7 AS 9 L Destination bn SGUTGE Lite Destination fa Gu E Jo Gornected Tamil aera l Cache Connections You do not need to create a routing table when your communication method is CIP messaging Publication 1756 UM 532A EN P M ay 2006 10 6 Communicate from a Logix Controller to an SLC 5 03 Controller over EtherN et IP and DH 485 Networks Notes Publication 1756 UM 532A EN P M ay 2006 Appendix A Specifications ControlLogix DH 485 Communications M odul
31. the module The SLC controller can use local messaging to send data to a ControlLogix controller with this feature No routing table is required IMPORTANT This is not the slot location of the 1756 DH485 module it is the slot location of the ControlLogix controller where you want to send the local message The controller slot is the physical location of a ControlLogix controller in a DH 485 application The default setting is slot 0 If necessary use the Channel Configuration tabs to change the controller slot number 1756 DH485 Configuration General Routing Table Channel O Configuration Channel 1 Configuration Serial Port Settings Error Detection lot if Protocol C CRC Station Address n MV Enable Duplicate Detection es Controller Slot 0 Protocol Settings Max Station Address 31 Token Hold Factor 1 Cancel For mote information about using the DH 485 netwotk refer to Chapter 3 Use Data Highway 485 Network Chapter 5 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Netw ork Introduction This chapter describes how to set up the communications initiated by an SLC 5 03 controller through a 1756 DH485 module to a 1756 Lx controller For See Hardware Configuration 5 2 Use the Controller Slot to Route the Local M essage 5 3 Create a Local M essage in RSLogix 500 5 4 Configure the M essage 5 5 Create a Logic M ap for the Local M essage in
32. 0 1756 DHRIO Configuration Ee Backplane Link 5 1756 DHRIO Slot 8 Channel DH Link 2 DH Bridge Node 46 i Bridge Link 12 Channel B DH Link 20 ef 1756 DH485 Slot 14 Channel 0 DH485 Link 1 Channel 1 DH485 Link Undefined This is the routing table for the 1756 DHRIO module Publication 1756 UM 532A EN P M ay 2006 6 4 Communicate Between SLC Controllers over DH and DH485 Networks Configure the SLC 5 03 Controller Channel 1 Link ID The SLC 5 03 remote link ID needs to be programmed to match the link IDs configured into the 1756 DH485 module These are labeled in the channel configuration as the Channel 1 Passthru Link ID Channel Configuration General Chan 1 System Chan 0 System Chan 0 User m Channel 1 Driver Write Protected Passthru Link ID dec Zz Edit Resource Owner Timeout x1 sec jeo Diagnostic File fo Channel 0 System Driver DF1 Half Duplex Slave Mode System Y Write Protected Passthru Link ID dec la Edit Resource Owner Timeout x 1sec go Diagnostic File jo User Driver las Cll Mode Change Enabled Mode Attention Character Mb System Mode Character s User Mode Character U Cancel Apply Help Publication 1756 UM 532A EN P M ay 2006 Communicate Between SLC Controllers over DH and DH485 Networks 6 5 Configure the SLC 5 04 Channel 1 Link ID
33. 1756 DH485 module is forwarded to a single user configured controller slot e messages on one DH 485 network cannot be routed to other networks Logix controllers message via a NetLinx network through a ControlLogix gateway to DH 485 network to all MicroLogix and SLC 5 03 and above controllers on DH 485 network RSLinx Classic on DH 485 network can browse through ControlLogix gateway to any device on NetLinx network IMPORTANT Logix controllers on NetLinx network will not be able to message through ControlLogix gateway to DH 485 network to fixed SLC 500 SLC 5 01 or SLC 5 02 controllers on DH 485 network Remote DH 485 Messaging Devices use remote DH 485 messaging to communicate between devices on physically separate networks A device that uses remote DH 485 messaging must be able to generate Remote Data Highway 485 network packets e support Remote Data Highway 485 network protocol e send and receive messages Remote DH 485 messaging should be used when e The message originating device or the message target device is one of the supported devices Refer to table Types of Communication on the 1756 DH485 Module on page 3 2 e There is a DH 485 network link in the message s path from originator to target The originating and the target devices are on separate networks communicating through a ControlLogix gateway Publication 1756 UM 532A EN P M ay 2006 3 6 Use Data Highway 485 Network Publication 1756
34. 6 UM 532A EN P May 2006 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over Multiple DH 485 Networks 7 3 Create the Routi ng Table These are the routing tables for the message in the example configuration This is the routing table for the 1756 DH485 module This is the routing table for the 1756 DHIRO module 1756 DH485 Configuration Channel 0 DH485 Link 1 Channel 1 DH485 Link Undefined E f 1756 DHRIO Slot 8 Channel A DH Link 2 E 44 DH Bridge Node 46 i Bridge Link 12 Channel B DH Link 20 1756 DHRIO Configuration Backplane Link 5 1756 DHRIO Slot 8 Channel DH Link 2 E 4 DH Bridge Node 46 Bridge Link 12 i Channel B DH Link 20 m 1756 DH485 Slot 14 Channel 0 DH485 Link 1 Channel 1 DH485 Link Undefined Publication 1756 UM 532A EN P M ay 2006 7 4 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over M ultiple DH 485 Networks Configure the PLC 5 DH Channel 1A Link ID The PLC 5 DH Channel 1A Link ID needs to be configured This is an example of the channel propetties Edit Channel Properties Channel 0 Channel 1A Channel 1B Channel 34 ni Diagnostic File 53 C Remote 1 0 Scanner C Remote 1 0 Adapter Node ddress fi Link ID 2 Global Status Flags File 52 Create a M essage in This is an example of a remote message for the ex
35. 85 applications For more information on the configuration software refer to the online help in each For See Choose the Correct Software 4 1 Use RSLinx Software to Create a Routing Table 4 2 Create the Routing Table 4 3 The programming software you need is dependent on what products you are using with the 1756 DH485 module The table below explains what software is needed for your application Software Needed for 1756 DH485 Applications If you are using this product w ith the 1756 DH485 module to read w rite data in a DH 485 application SLC Controllers You must use this software RSLinx version 2 43 or later RSLogix 500 version 6 3 or later ControlLogix Controllers RSLinx version 2 43 or later RSLogix 5000 Publication 1756 UM 532A EN P M ay 2006 4 2 Use RSLinx Software to Create a Routing Table Use RSLinx Software to Create a Routing Table Publication 1756 UM 532A EN P May 2006 DH 485 protocols do not use the Common Industrial Protocol CIP the communication protocol used in the ControlLogix architecture The 1756 DH485 module is the transition point from the DH 485 network to ControlLogix In this capacity the 1756 DH485 module serves as the DH 485 message source and requires a full message route or path to deliver the message A routing table using link IDs and node addresses provides the full path What Is a Routing Table Before you can create
36. A5 2711 T9A5 2711 K9A1 and 2711 T9A1 PanelView 550 and PanelView 900 Operator Terminals Panel M ount Provides electronic operator interface for SLC 500 2711 UM 014DF controllers 1784 PKTX 1784 PKTXD PC DH 485 Interface Card 1 This product is no longer available for order 1747 AIC Isolated Link Coupler for DH 485 Publication 1756 UM 532A EN P M ay 2006 PCI Bus Provides DH 485 or DH connection 1784 6 5 27 Use the isolated link coupler 1747 AIC to connect SLC 500 family devices to the DH 485 network as shown on page 2 5 The coupler provides a 6 position removable terminal block for connection to the DH 485 communication cable To establish network connections for e SLC 500 controllers SLC 5 03 and below use a 304 8 mm 12 in cable supplied with the link coupler catalog number 1747 C11 If you need to connect a peripheral device that is between 1 8 m 6 ft and 6 1 m 20 ft away use the 1747 C20 cable To protect connected devices the coupler provides 1500V dc isolation between the communications cable and the attached SLC 500 controller and peripheral devices Overview of the DH 485 Network 2 5 You can also use the isolated link coupler to provide connectivity between devices for distances greater than 1 8 m 6 ft up to a maximum of 1219 m 4000 ft Below is an example of a remote connection between a computer running your programming software and an SLC 500 controller
37. Allen Bradley ControlLogix DH 485 Communication Module 1756 DH485 User Manual mn e i Rockwell Automation Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls publication SGI 1 1 available from your local Rockwell Automation sales office or online at http literature rockwellautomation com describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipment or software described in this manual Repro
38. Controller over an EtherNet IP Network Notes Publication 1756 UM 532A EN P M ay 2006 Chapter 9 Communicate to a SLC 5 03 Controller on a DH 485 Network Introduction This chapter describes how to configure remote CIP communication from a 1756 L55 controller to an SLC 5 03 controller through DH and DH485 networks For See Hardware Configuration 9 2 Create a M essage in RSLogix 5000 9 3 Configure the M essage 9 4 IMPORTANT The examples use the 1756 DH485 module to initiate the message to the SLC 5 03 module In each case the use of these devices is strictly for example purposes and not an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 9 2 Communicate to a SLC 5 03 Controller on a DH 485 Network Hardw are Configuration In this hardware configuration the ControlLogix controller initiates a CIP message from the 1756 DHRIO module to an SLC 5 03 controller located on a DH 485 netwotk ControlLogix 1756 DHRIO 1 Controller m DH RIO ciem O oo ooo ooo es2 e ooo oco foco ALS M A NN DH Network ControlLogix 1756 DHRIO 2 1756 DH485 3 M y 2 O O
39. IC Link Coupler AIC Link Coupler A i SLC 5 03 Controller UM PanelView SLC 5 03 Controller Publication 1756 UM 532A EN P M ay 2006 1 6 1756 DH485 M odule Overview The second example shows how you can connect or migrate a legacy system to a new installation with RSLogix software Connect multiple DH 485 networks together for inter network communications Message between SLC 5 03 controllers e Provide connection to other NetLinx networks Access through a single point and download to an SLC controller MicroLogix controller and Panelview display e Allow communications between legacy and ControlLogix systems for high integration of control systems except for fixed SLC controllers Phase SLC systems into ControlLogix architecture by using a migration tool Connect or Migrate a Legacy System to a New Installation Computer with RSlogix 500 and RSLogix 5000 Software
40. RSLinx 2 Browse the netwotk 3 Right click on the 1756 DH485 module 4 Use the left side navigation bar to see your DH 485 application as shown in the example below 89 Backplane 1756 A10 A 00 1756 CNB D 1756 CNB D 5 045 Build 010 01 1756 ENBT A 02 1756 L61 LOGIX5561 3 Channel 0 DF1 E os 1756 DH485 4 1756 DH485 A A Expand the configuration tree until the module appears B Right click on the Channel 0 DF1 Remove 1756 DH485 module 35 Channe 5 Channel 1 DF1 04 1756 SIM A 1756 SIM A DIG ANA SIMULAT Dri A river Diagnostics 05 1756 IF6I A 1756 IF6I A AAAAAA Configura Driver 06 1756 OF6VI A 1756 OF6VIJA XXXXXX z Station Diagnostics C Select M odule Configuration E 07 1756 MOSSE 8 Axis SERCOS interface Device Properties 08 1756 IB16D A 1756 IB16D A DCIN DIAG Module Statistics 09 1756 OB16D A 1756 OB16D A DCOUT DIA rare amp j 10 88 95 3 1757 FFLD Foundation Fieldbus Linking Device 170711 LO ver 1 0 Publication 1756 UM 532A EN P M ay 2006 4 4 Use RSLinx Software to Create a Routing Table 5 Select the DH 485 Routing Table tab 1756 DH485 Configuration General Routing Table Channel 0 Configuration Channel 1 Configuration Serial Port Settings 740 J Backplane Link Undefined BH 1756 DH485 Slot 3 Channel 0 DH485 Link Undefined Channel 1 DH485 Link Undefined Load From File Save to File Restore Defaults
41. UM 532A EN P May 2006 This figure shows an example of remote DH 485 messaging between SLC 03 or later controller A and SLC 5 03 or later controller B In this example the following information must be included in the remote DH 485 message routing message instruction e Local DH 485 node 020 e Destination link ID 2 e Remote DH 485 node 030 Remote DH 485 Messaging Between SLC 5 03 Controller A and SLC 5 03 Controller B 1756 DH485 M odule pe BA ControlLogix Chassis i Link ID 1 Channel A Node 020 Channel B Node 025 Link ID 2 Al A E BEER SLC 5 03 Controller A SLC 5 03 Controller B Node 030 44053 Link IDs To use remote DH 485 messaging each network that is an originating network or target network must have a unique link ID The 1756 DH485 module requires these link IDs to be decimal values between 1 199 Each DH 485 channel on a 1756 DH485 module must have its own unique link ID Use Data Highway 485 Network 3 7 The message originates on the source network The destination network is the message s target network This applies to all source and destination networks including DH 485 ControlNet EtherNet IP and a ControlLogix chassis backplane Miras For remote DH 485 messaging the Contr
42. Use the Controller Slot to hi a a d pr PS is PRA the s bn s dn E routed to the controller based on the configured slot number In this case the Route the Local M essage 1756 Lx controller is in slot 11 A routing table is not needed 1756 DH485 Configuration Enter the slot number of the controller Publication 1756 UM 532A EN P M ay 2006 5 4 Communicate from an SLC 5 03 Controller to a Logix Controller over a DH 485 Network Create a Local M essage iN This is an example of a local message being initiated by the SLC 5 03 RS Logix 500 controller RSLogix 500 Sic_503 5 x File Edit View Search Comms Tools Window Help name Esse a JARAT Ran v e oree El RIT URDU EMEN Driver AB PIC 1 Node 1d Slc_503 ioj xj B Project E Help Eg Controller i Controller Properties Op Bn masss TocessOr SITS 3t Read Write Message Jl 10 Configuration Type Peer To Peer b Channel Configuration Read Write El Muttipoint Monitor Target Device i Local Remote Program Files Control Block syso Control Block Length syst Setup Screen amp LAD2 Data Files Cross Reference Ej 00 output E i input El s2 status E 83 BINARY Ej 14 Timer Count Up E cs COUNTER Counter c53 Ej R6 CONTROL Preset 32000 E N7 INTEGER Accum El F8 FLoaT E na E ma Eig Force Files Ej oo output Bi it input Custom Data Monitors Ej com 0 untitled Entry is Valid z0006
43. age 1 Publication 1756 UM 532A EN P M ay 2006 Communicate Between SLC Controllers over DH and DH485 Networks Create the Routing Table in RSLinx Software These are the routing tables needed for the example configuration In this example the e SLC 5 03 controller is connected to Channel A of the 1756 DH485 module The 1756 DH485 node address on the DH 485 network is node 0 e 1756 DHRIO and the 1756 DH485 modules are on the same backplane e 1756 DH485 module is in slot 14 e 1756 DHRIO module is in slot 8 e Link ID of Channel B of the 1756 DHRIO is Link 20 e SLC 5 04 controller is connected to Channel B of the 1756 DHRIO e node address of the SLC 5 04 controller on DH is 10 octal or 8 decimal e SLC 5 03 controller initiates a remote message to the SLC 5 04 controller 1756 DH485 Configuration Bridge Link 12 i Channel B DH Link 20 1756 DHRIO Configuration o FB ackplane Link 5 1756 DHRIO Slot 8 Channel A DH Link 2 44 DH Bridge Node 46 i Bridge Link 12 Channel B DH Link 20 1756 DH485 Slot 14 Channel 0 DH485 Link 1 Channel 1 DH485 Link Undefined 6 9 Publication 1756 UM 532A EN P M ay 2006 6 10 Communicate Between SLC Controllers over DH and DH485 Networks Create a Remote Message in RSLogix 500 This is the example message for the hardware configuration RSLogix 500 Pro SLC503_REMOTE_504 File Edit View
44. ample configuration RSLogix 5 AP E E Da c B e gt eme ARANA AQO 2 ra e REMOTE RUN s Forces installed 8 HE see Co IE Bl No Edits Forces Disabled 8 Diver AB KTA ito CINU Ait A TimeriCounter K nputiOuput K Compare 5 Project Aela 3 Y Hep B Controller i Controller Properties a Processor Status MSG AU 10 Configuration Read Write Message ps Channel Configuration Control MG132 Passwords and Privileges Setup Screen B Program Files Bi svso CTU Y Lap2 Count Up Counter C5 10 AY LAD3 Preset 32000 4j LAD 4 SUB_4 Accum 30535 AY LaDS Pl 4 Lape E Data Files Count Up B Cross Reference Counter C511 E oo m 32000 Dn ceum B s2 Entry is Valid Class 1 2 0005 APP READ BAstart c S ERstogix 5 Pro Dwr RSLogix 5000 S nsunx Classic Gateway SHARH 1 35PM Publication 1756 UM 532A EN P M ay 2006 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over Multiple DH 485 Networks 7 5 Confi gure the Messa ge This is the Setup dialog for the message in the example configuration MSG MG13 2 1 Elements Publication 1756 UM 532A EN P M ay 2006 7 6 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over M ultiple DH 485 Networks Notes Publication 1756 UM 532A EN P M ay 2006 Chapter 8 Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller ov
45. c motors transformers rectifiers generators arc welders induction furnaces ot sources of microwave radiation If you must run the cable across power feed lines run the cable at right angles to the lines If you do not run the cable through a contiguous metallic wireway or conduit keep the communication cable at least 0 15 m 6 in from ac power lines of less than 20A 0 30 m 1 ft from lines greater than 20A but only up to 100k VA and 0 60 m 2 ft from lines of 100k VA or more If you run the cable through a contiguous metallic wireway or conduit keep the communication cable at least 0 08 m 3 in from ac power lines of less than 20A 0 15 m 6 in from lines greater than 20A but only up to 100k VA and 0 30 m 1 ft from lines of 100k VA or more Running the communication cable through conduit provides extra protection from physical damage and electrical interference If you route the cable through conduit follow these additional recommendations Use ferromagnetic conduit near critical sources of electrical interference You can use aluminum conduit in non critical areas Use plastic connectors to couple between aluminum and ferromagnetic conduit Make an electrical connection around the plastic connector use pipe clamps and the heavy gauge wire or wire braid to hold both sections at the same potential Ground the entire length of conduit by attaching it to the building earth ground Do not let the c
46. codes that provide diagnostic information about your module The alphanumeric display flashes the codes at approximately one second intervals This table summarizes the codes Alphanumeric Display Descriptions Message Description Recommended Action ONLY NODE Only node on Check the cables DH 485 link OFF LINE DH 485 link is in STOP Correct the configuration state DUPL NODE DH 485 Duplicate Choose another node address node address ONLY NODE Only node on Check the cables DH 485 link OFF LINE Not trying to None Normal state if controller is not communicate controlling remote 1 0 OK Normal operation None Publication 1756 UM 532A EN P M ay 2006 B 4 Troubleshoot the 1756 DH485 M odule Interpret the OK The three LED status indicators on the module provide information about A your module and the status of each channel The following tables outline the Status Indic ator indicator condition and the corresponding status and explain what each condition means Interpreting the OK Status Indicator If the Module OK Module Status Recommended Action Indicator is Off Not operating Apply chassis power Verify module is completely inserted into chassis and backplane Red then Off Performing self test None normal operation Green Operating and routing Verify module configuration messages Red In major fault Reboot module If red reoccurs then replace module
47. de 20 SLC 5 03 Controller Node 20 SLC 5 03 m Controller gnarlView Node 20 Koden O 44054 Publication 1756 UM 532A EN P M ay 2006 3 14 Use Data Highway 485 Network Use the Common Industrial Protocol CIP Messaging Publication 1756 UM 532A EN P M ay 2006 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 netwotk 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 Introduction Choose the Correct Softw are Chapter 4 Use RSLinx Software to Create a Routing Table This chapter describes how to configure your 1756 DH485 module in DH 4
48. de Hex 0 1756 DH485 module Error Description The 1756 ENBT module is No errors in slot 10 and the 1756 DH485 is in slot 14 of the ControlLogix rack The SLC 5 03 controller is connected to Channel A of the 1756 DH485 module and is communicating through link couplers The firmware in the SLC 5 05 controller must be capable of handling CIP protocol CIP protocol is what the 1756 ENBT module supports The firmware for the SLC 5 05 controller has been upgraded to handle both CSP and CIP protocols Refer to Knowledgebase document G16915 for minimum firmware revisions needed for the SLC 5 05 controller to communicate to a 1756 ENBT controller The SLC 5 05 controller needs to be at a minimum Series A 08501 Firmware 5 Publication 1756 UM 532A EN P M ay 2006 Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller over an EtherNet IP Network 85 Review the M ultihop The multihop feature of RSLogix 500 takes care of routing this remote Feature in RSLo gix 500 message No routing table is required This is the multihop dialog for the example configuration MSG Rung 2 0 N12 0 General Ins Add Hop Del Remove Hop This Processor EtherNet IP Device str 100 100 100 7 ControlLogix Backplane ie 1756 Backplane Slot dec 14 1756 DHRIO or 1756 DH485 Channel Station oct dec tollid Publication 1756 UM 532A EN P M ay 2006 8 6 Communicate from an SLC 5 05 Controller to an SLC 5 03
49. dhrio back dh485 503 MainRouti arithmetic ascii Click to configure the message bulletin 1 cnet diag compute copy counters devicenet Fal Fife SG Publication 1756 UM 532A EN P M ay 2006 9 4 Communicate to a SLC 5 03 Controller on a DH 485 Network Configure the M essage Path Item dhrio ser B Description W hen you browse to the local 1756 DHRIO module appears if you have it configured in the I O configuration tree in RSLogix 5000 software These are the configuration dialogs for the example message Message Configuration msg dhrio remote dhrio back dh4859503 SLC Typed Read n Data table memory is in the SLC 5 03 controller The message is coming from the ControlLogix controller Destination storage is in the 1756 L55 controller Message Configuration msg dhrio remote dhrio back dh4852583 Hhrio ser B 2 10 1 14 2 1 10 Channel A of the 1756 DHRIO module The remote 1756 DHRIO is node 12 octal or 10 decimal Backplane 14 1756 DH485 module in slot 14 Channel A of the 1756 DH485 module SLC 5 03 Controller Node Address Publication 1756 UM 532A EN P M ay 2006 7 Connected D ramen oia Lite SOUTCE LITE Destination IW aes af sej Jv Gache Connections You do not need to create a routing table when your communication method is CIP messaging Introduction Chapter 10 Commu
50. duction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss Identifies information that is critical for successful application and IMPORTANT understanding of the product Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence ATTENTION SAATTA Labels may be located on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present FTIFTETTVZCDE Labels may be located on or inside the equipment for example a drive or motor to alert people that surfaces may be dangerous temperatures lala lla The first line of trademarks is an example the brand or product name changes according to publication but the rest of the line should remain the same The second line should be used exactly as listed below in any case where it applies Allen Bradley ControlLogix and RSLinx are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automati
51. e 1756 DH485 Attribute Value Module Location ControlLogix chassis Maximum Backplane Current Load 850 mA 45 1V dc and 1 7mA 24V dc from I O chassis backplane Power Dissipation 45W Thermal Dissipation M ax 15 4 BTU hr Isolation Voltage 50V Tested to withstand 750V dc for 60 s Available Communication Rates 19 2 Kbps default and 9600 Kbps Wiring Category 2 on communications ports Use this Conductor Category information for planning conductor routing Refer to Publication 1770 4 1 Industrial Automation W iring and Grounding Guidelines Environmental Specifications Attribute Value Operational Temperature IEC 60068 2 1 Test Ad Operating Cold IEC 60068 2 2 Test Bd Operating Dry Heat IEC 60068 2 14 Test Nb Operating Thermal Shock 0 60 C 32 140 F Storage Temperature IEC 60068 2 1 Test Ab Unpackaged Nonoperating Cold IEC 60068 2 2 Test Bb Unpackaged Nonoperating Dry Heat IEC 60068 2 14 Test Na Unpackaged Nonoperating Thermal Shock 40 85 C 40 185 F Relative Humidity IEC 60068 2 30 Test Db Unpackaged Nonoperating Damp Heat 5 95 noncondensing Vibration IEC 60068 2 6 Test Fc Operating 29 10 500 Hz Operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 30g Non operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 50g Emissions CISPR 11 Group 1 Class
52. e network environment e Number of devices on the network Connection and grounding quality in installation e Amount of communication traffic on the network e Type of process being controlled e Network configuration The major hardware and softwate issues you need to resolve before installing a network are discussed in the following sections Hardware Considerations You need to decide the length of the communication cable where you will route it and how to protect it from the environment where it will be installed Before you install the communication cable you need to know how many devices are to be connected during installation and how many devices will be added in the future The following sections will help you understand and plan the network Number of Devices and Length of Communication Cable You must install a link coupler communications adapter 1747 AIC or 1761 NET AIC for each node on the network If you plan to add nodes later provide additional link couplers during the initial installation to avoid recabling after the network is in operation The maximum length of the communication cable is 1219 m 4000 ft This is the total cable distance from the first node to the last node on the network Overview of the DH 485 Network 2 11 Plan Cable Routes Follow these guidelines to help protect the communication cable from electrical interference e Keep the communication cable at least 1 52 m 5 ft from any electri
53. el Status Indicators Ifthe ChannelA In This Channel Then the Channel Take This Action or B Indicator Mode Status is is Off All Not online Place channel online DH485 No other node on the Check cables network Green DH485 Operating None normal operation Publication 1756 UM 532A EN P M ay 2006 B 6 Troubleshoot the 1756 DH485 M odule Notes Publication 1756 UM 532A EN P M ay 2006 Numerics 1747 AIC link coupler using on the DH 485 network 2 4 1747 UIC description 2 7 example network 2 7 1756 DH485 module overview 1 1 1 9 module requirements 1 1 What does the module do 1 1 1756 ENBT remote message 10 3 10 5 1761 NET AIC communication link 2 6 description 2 6 device compatibilty 2 6 operating modes 2 6 A AIC device compatibility 2 6 interface converter 2 7 node address identification 2 7 operating modes 2 6 overview 2 6 alphanumeric indicators 1 9 B 3 C cable routes planning 2 11 Common Industrial Protocol CIP messaging 1 1 Common Industrial Protocol CIP messaging 3 2 3 14 communication between SLC controllers on different networks 1 8 Common Industrial Protocol CIP messaging 1 1 1 8 3 14 Data Highway 485 DH 485 messaging 1 8 data highway 485 DH 485 messaging 1 1 Local 1 1 remote 1 1 types supported by the 1756 DH485 module 1 1 3 2 3 14 configuration controller slot 4 8 Data Highway 485 DH 485 messaging 3 11 controller
54. en for the example message Ex MSG N9 40 14 Elements This Controller Communication Command Target Device Error Description No errors Data Table Address Size in Elements Channel Message Timeout Data Table Address Local Bridge Addr dec Local Remote Remote Bridge Addr dec Remote Station Address dec Remote Bridge Link ID Control Bits 500CPU Read Ignore if timed out TO 0 To be retried NR 0 Awaiting Execution EW Continuous Run CO 0 Error ER 0 Message done DN 8 Message Transmitting ST 8 Message Enabled EN octal o Waiting for Queue Space 0 emote Error Error Code Hex O Publication 1756 UM 532A EN P M ay 2006 6 12 Communicate Between SLC Controllers over DH and DH485 Networks Notes Publication 1756 UM 532A EN P M ay 2006 Chapter 7 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over Multiple DH 485 Netw orks introduc tion This chapter describes how to set up the communications for a remote PLC 5 controller to send a message to a remote SLC 5 03 controller over multiple DH 485 Networks For See Hardware Configuration 7 4 Create a Message in RSLogix 5 7 4 Configure the M essage 1 5 Create the Routing Table 1 3 IMPORTANT The examples use SLC 5 03 modules to send DH 485 messages In each case the use of these devices is strictly for example purposes and n
55. er an EtherNet IP Network Introduction This chapter desctibes the communications from an SLC 5 05 controller to an SLC 5 03 controller over an EtherNet IP network For See Hardware Configuration 8 2 Create a Message in RSLogix 500 8 3 Configure the M essage 8 4 Review the Multihop Feature in RSLogix500 8 5 IMPORTANT The examples use SLC 5 05 controllers to send DH 485 messages In each case the use of these devices is strictly for example purposes and not an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 8 2 Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller over an EtherNet IP Network Hardware Configuration In this hardware configuration an SLC 5 05 controller communicates to an SLC 5 03 controller over an EtherNet IP network e The SLC 5 05 controller initiates a message 1 e The message is sent over an EtherNet IP network to a 1756 ENBT module 2 e The message is then sent over the backplane to a 1756 DH485 module 3 e The 1756 DH485 module then sends the message through channel A and link couplers to the SLC 5 03 controller 4 ControlLogix Controller 1756 ENBT 3 pra ETHERNET E ood ooo 1756 DH485 3 ea oo DH RIO coo E ODO a oo 9000 oooj ooo e ooo 000 000 hannel A 4
56. er is to accomplish two tasks The first is to convert RS232 electrical signals to RS485 electrical signals and RS485 electrical signals to RS232 electrical signals The second function is to provide electrical isolation between all three communication ports This protects against ground loops and voltage differences between devices connected to the 1761 NET AIC converter A common misconception is that the 1761 NET AIC device converts protocol this is not true it passes the protocol but converts the electrical signals An example device that would convert protocol and electrical signal is the 1747 KE module Refer to the Isolation Interface Converter AIC User Manual publication 1761 UM004 for complete information The 1747 UIC lets you connect DH 485 devices directly to a computer s USB port It features an RS 232 port for connection to SLC 5 03 and higher controllers MicroLogix PanelView 300 and higher terminals 1761 NET AIC and Logix controllers as well as an RS 485 port for connection to SLC 5 03 and lower controllers PanelView 300 and higher terminals and 1747 AIC The converter can communicate with devices on the DH 485 network at 19 2K baud Publication 1756 UM 532A EN P M ay 2006 2 8 Overview of the DH 485 Network Example System Configuration Below is an example of a DH 485 network Example DH 485 Netw ork System Configuration Personal Computer l
57. ete this form and mail it back to us visit us online at ww w ab com manuals or email us at RADocumentCommentsQ ra rockw ell com Pub Title Type ControlLogix DH 485 Communication M odule Cat No 1756 DH485 Pub No 1756 UM532A EN P Pub Date May 2006 PartNo 957988 29 Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 3 How can we make this publication more useful for you i i Completeness 2 3 Can we add more information to help you all necessary information procedure step illustration feature is provided P example guideline other explanation definition TechnicalAccuracy 1 2 3 Can we be more accurate all provided information is correct text illustration Clarity 1 2 3 How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Location Phone Your Title Function TT Would you like us to contact you regarding your comments No there is no need to contact me Yes please call me ___ Yes please e mail me at ___Yes please contact me v a Return this form to Allen Bradley M arketing Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Phone 440 646 3176 Fax 440 646 3525 E mail RADocumentCommentsQ ra rockw ell com Publication ICCG 5 21 anua
58. examples use SLC 5 03 and SLC 5 04 controllers to send DH 485 messages In each case the use of these devices is strictly for example purposes and not an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 6 2 Communicate Between SLC Controllers over DH and DH485 Networks SLC 5 04 Controller Sends a 17 this example an SLC 5 04 controller initiates a remote message and sends it Remote M essage to an SLC 5 03 Controller Hardware Configuration In this hardware configuration an SLC 5 04 controller sends a remote message to an SLC 5 03 controller e The SLC 5 04 controller is on a DH network 1 e The SLC 5 04 controller connects to Channel B on the 1756 DHRIO module 2 e The SLC 5 03 controller connects to Channel A of the 1756 DH485 module in the same rack as the 1756 DHRIO module 3 e The SLC 5 04 controller sends a remote message to the SLC 5 03 controller on a DH485 network 4 ControlLogix Controller 1756 DHRIO 2 1756 DH485 E e 9 E DH RIO L1 Su rex ooo ooo ooo ud i Channel A 3 Channel B 2 f i le S
59. hrough modems 1785 KA5 DH DH 485 1771 PLC Provides communication between stations on the 1785 6 5 5 Gateway Chassis PLC 5 DH and SLC 500 DH 485 networks Lets 1785 1 21 1785 KA5P Standal communication and data transfer from PLC to SLC i angalone 500 on DH 485 network Also enables software programming or data acquisition across DH to DH 485 1784 KTX 1784 KTXD PC DH 485 Interface ISA Bus Provides DH 485 or DH connection 1784 6 5 22 Card 1784 PCM K PCM CIA Interface PCMCIA slotin Provides DH 485 or DH connection 1784 6 5 19 Card computer 1761 L M icroLogix Standalone Programmable Controllers 1761 UM 003 1762 L Programmable 1762 UM 001 1763 L Controllers 1763 UM 001 1764 L 1764 UM 001 1756 L Logix Programmable 1756 Chassis or Programmable Controllers 1756 UM 001 1769 L Controllers DIN Rail 1769 UM 011 1794 L 1794 UM 001 Publication 1756 UM 532A EN P May 2006 2 4 Overview of the DH 485 Network Devices that Use the DH 485 Network Catalog Number 2707 L8P1 2707 L8P2 2707 L40P1 2707 L40P2 2707 V40P1 2707 V40p20 2707 V40P2N U 2707 M 232P3 and 2707 M 485P3 Description DTAM Plus and DTAM Micro Operator Interfaces Installation Function Publication Requirement Panel M ount 2107 800 2107 803 Provides electronic operator interface for SLC 500 controllers 2711 K5A2 2711 B5A2 2711 K5A5 2711 B5A5 2711 K5A1 2711 B5A1 2711 K9A2 2711 T9A2 2711 K9
60. 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 e 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 yout system e 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 netwotk 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 Use Data Highway 485 Network The following table lists what the controllers are capable of on DH 485 Controllers and the Types of Messaging Capable on a DH 485 Network 3 9 Controller Respond to Initiate Local Respond to Initiate Messaging Local DH 485 DH 485 Remote Remote DH 485 DH 485 MicroLogix 1000 Yes Yes Yes No MicroLogix 1100 Yes Yes Yes Yes MicroLogix 1200 Yes Yes Yes Yes MicroLogix 1500 Yes Yes Yes Yes SLC 500 fixed Yes No No No SLC 5 01 Yes No No No SLC 5 02 Yes Yes No No SLC 5 03 Yes Yes Yes Yes SLC 5 04 Yes Yes Yes Yes SLC 5 05 Yes Yes Yes Yes Logix Yes Yes Nol
61. ly and Module Status Appendix B Troubleshoot the 1756 DH485 M odule This chapter describes diagnostics and methods of troubleshooting the module For See Check Power Supply and M odule Status B 1 Interpret the LED Status Indicators B 2 Interpret the Alphanumeric Indicators B 3 Interpret the OK Status Indicator B 4 Routing Errors in DH 485 M essaging B 4 When you apply power to the module three events take place simultaneously Alphanumeric status indicator on the module illuminates and cycles through the following sequence of messages INIT Channel A and the network used for channel A Channel A node address Channel A status Channel B and the network used for channel B Channel B node address Channel B status This channel sequences run continuously during normal module operation EXAMPLE Por example if your module uses the following e Channel A for DH485 with node address 14 Channel B for DH485 with node address 0 but being the only node on the network e A DH A244 A OK B DH B 0 ONLY NODE Module OK status indicator flashes red then goes solid green Publication 1756 UM 532A EN P M ay 2006 B 2 Troubleshoot the 1756 DH485 M odule Interpret the LED Status Indicators Publication 1756 UM 532A EN P M ay 2006 If the alphanumeric indicator on the 1756 DH485 module does not cycle through these messages when you apply power refer to the f
62. module is a ControlLogix chassis a ControlNet network or an EtherNet IP network Use Data Highway 485 Network 3 11 Configurati on Information When you are doing DH 485 messaging you must first set up the 1756 DH485 module configuration The following configuration information in DH 485 M essaging is stored in the non volatile NVS memory on your 1756 DH485 module when you configure the module using RSLinx software e Any routing table that may be needed to send DH 485 messages through the module This information must be applied to the module s configuration separately from other information Use RSLinx to apply the routing table For more information about routing tables see the section Use RSLinx Software to Create a Routing Table in Chapter 4 Controller slot assignment for each DH 485 channel Refer to Set the Controller Slot on page 4 8 for more information on local messaging e The node numbet of the module IMPORTANT If you restore defaults with RSLinx software the slot number will remain the 1756 DH485 module s non volatile memory but the routing table and the controller slot for both DH 485 channels will be reset Publication 1756 UM 532A EN P M ay 2006 3 12 Use Data Highway 485 Network 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 ate not routed back When an error occurs du
63. municate from 5 1 Communicate from a Logix Controller hardware configuration 10 2 communicate on a DH 485 network 9 1 communicate to an 1756 DH485 module 5 2 communication from a Logix controller 10 1 configure a message 9 4 configure a remote message 10 4 hardware configuration 9 2 remote message 10 3 remote message hardware configuration 6 8 routing table 6 9 sends a remote message 6 8 SLC 5 04 channel 1 link ID 6 5 configure a message 6 7 hardware configuration 6 2 send a remote message 6 2 SLC 5 05 communicate over EtherNet 8 1 communicate to an SLC 5 03 8 1 configure a message 8 4 EtherNet IP hardware configuration 8 2 SLC controllers communitcate between 6 1 softw are choose the correct softw are for DH485 applications 4 1 RSLinx 4 1 RSLogix 5 4 1 RSLogix 500 4 1 RSLogix 5000 4 1 Specifications 1756 DH485 module A 1 environmental conditions A 1 status indicators for use in troubleshooting B 4 system configuration example 2 8 Index iii T troubleshoot B 1 B 5 power supply and module status B 1 use the alphanumeric indicators B 3 use the status indicators B 4 typical applications 1 5 1 6 U upload remote 1 7 Publication 1756 UM 532A EN P M ay 2006 iv Index Notes Publication 1756 UM 532A EN P M ay 2006 How Are We Doing Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback NL You can compl
64. n DIBIeout s sis iae otc Ha Ne eee Saeed dee tm 3 12 Example DH 485 Network Routing Configuration 3 13 Use the Common Industrial Protocol CIP Messaging 3 14 Chapter 4 ItibOQ BHO ipa s end air dre ande re tdt bus Soa id 4 1 Choose the Correct Software Les ceo cete AC o Y RC EAR 4 1 Use RSLinx Software to Create a Routing Table 4 2 What Is a Routing Table it osea aah rette Pete 4 2 ControlLog x Routing 4 ires rr 4 2 Create the Routing Tables vtr td c rau d 4 3 Set the Controler slo oi cae de m ME ev 4 8 Chapter 5 Int OduC lotio tcc see es ob he aR E Cic Dee et 5 1 Hardware Oft vta OE A Eos cogor A tic Ne REN 5 2 Use the Controller Slot to Route the Local Message 5 3 Create a Local Message in RSLogix 500 V osse cert RC Y 5 4 Configure the Mestalla Vereor er ops Pt reae ns 5 5 Create a Logic Map for the Local Message in RSLogix 5000 SO WAFG v Ditta rro S ET EP ER ba RRR LEWD 5 6 Communicate Betw een SLC Controllers over DH and DH485 Networks Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over Multiple DH 485 Netw orks Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller over an EtherNet IP Netw ork Communicate to a SLC 5 03 Controller on a DH 485 Netw ork Table of Contents iii Chapter 6 LO ucHOt ene Mu uty Meek eee eens aS RT Fou RS ay 6 1 SLC 5 04 Controller Sends a Remote Message sess 6 2 Hardware Corntguralioh O
65. n Target Device SO0CPU be Channel Configuration a uc E Muttipoint Monitor f LENS SIE E La Procrom Ftes Click Setup Screen to weet svso configure the message SYS1 LAD2 Y Data Files Cross Reference E 00 output Bj n input E s2 status E 83 BINARY Ej 14 TIMER E c5 COUNTER Ej re CONTROL E N7 INTEGER E Fs FLOAT E ns B ato B sm E m2 E ms 4 File 2 For Help press F1 2 0000 APP 14 Start Publication 1756 UM 532A EN P May 2006 Communicate Between SLC Controllers over DH and DH485 Networks 6 7 Configure the Message This is the Setup dialog for the example message Ez MSG N7 0 14 Elements This Controller Control Bits Communication Command 500CPU Read Ignore if timed out TO e Data Table Address To be retried NR 0 Size in Elements Awaiting Execution EW e The SLC 5 04 controller connects inde Continuous Run C0 p to a 1756 DHRIO module at node Enor ER 0 56 octal or 46 decimal Target Device Message done DN Message Timeout Message Transmitting ST 0 Data Table Address E Message Enabled EN The SLC 5 04 controller sends a Local Bridge Addr dec octal Waiting for Queue Space 0 remote message to the SLC 5 03 Local Remote controller that is on a DH48 Remote Bridge Addr dec Error network emote Station Address dec Remote Bridge Link ID Error Code Hex 0 The SLC 5 03 controller is located at node 1
66. n you insert or remove the module while backplane power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that power is removed or the area is nonhazardous before proceeding Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation Publication 1756 UM 532A EN P May 2006 1756 DH485 Module Overview 1 5 Typi cal A ppl ications The first example is a typical gateway application connecting multiple networks together In this example you can upload and download SLC 500 and Panelview display programs e seamlessly communicate between SLC controllers connect multiple DH 485 networks together for inter network communications for example messages between SLC 5 03 controllers e provide connection to other NetLinx networks such as EtherNet TP to allow a single point access for example upload and download to an SLC controller MicroLogix controller and Panelview display Connection of Multiple Networks Computer with RSlogix 500 and RSLogix 5000 Software EAS 1756 ENBT 1756 DH485 DLL d I8 apes ICICI a y AIC Link Couplers A
67. nicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Netw orks This chapter describes how to set up communication from a Logix controller to an SLC controller over an EtherNet IP network For See Hardware Configuration 10 2 Create a Remote 1756 ENBT Message in 10 3 RSLogix 5000 Configure the M essage 10 4 IM PORTANT The examples use SLC 5 03 modules to send DH 485 messages In each case the use of these devices is strictly for example purposes and not an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 10 2 Communicate from a Logix Controller to an SLC 5 03 Controller over EtherNet IP and DH 485 Networks Hardware Configuration In this hardware configuration a Logix controller communicates to an SLC 5 03 controller over EtherNet IP e The 1756 ENBT module 1 to communicate to a remote 1756 ENBT module 2 over the EtherNet IP network backplane e The 1756 DH485 module 3 then communicates through Channel A to the SLC 5 03 4 controller through link couplers over a DH 485 Network 1756 ENBT 1 1756 ENBT 2 1756 DH485 3 ControlLogix Controller 8 8 e es luso Boss grim ala Channel A y K Backplane ieee ne Ici IDIOT gt T El pe ISI 1756 DH485 communicatin through
68. ode addresses IMPORTANT The SLC 500 Series A only controllers set the maximum node address to 31 when power is cycled increasing initialization and response time of the network M aximum Number of Communicating Devices SLC 500 fixed and SLC 5 01 controllers can be selected by two initiators maximum at the same time Using more than two initiators to select the same SLC 500 fixed and SLC 5 01 controllers at the same time can cause communication timeouts Refer to the manuals listed in the table Devices that Use the DH 485 Network on page 2 3 Publication 1756 UM 532A EN P May 2006 2 14 Overview of the DH 485 Network Notes Publication 1756 UM 532A EN P M ay 2006 Chapter 3 Use Data Highway 485 Network Introduction This chapter describes the basics of the Data Highway 485 system and the operation of a DH 485 network For See What Is Data Highway 485 3 1 Two Methods of Communication Over a DH 485 Network 3 2 Use DH 485 M essaging 3 3 Configuration Information in DH 485 M essaging 3 11 Application Timeout 3 12 Example DH 485 Network Routing Configuration 3 13 Use the Common Industrial Protocol CIP M essaging 3 14 W hat Is Data Highw ay 485 On the most basic level Data Highway 485 is a wire or cable and a protocol that connects computers and peripheral devices so that they can communicate The wire used for a network is called the network medium A DH 485 link transfers data between
69. olLogix PLC and SLC controllers in DH 485 applications W ho Should Use This Use this manual if you program applications that use 1756 DH485 modules Manual We assume you have a good understanding of the Data Highway 485 protocol This user manual contains a brief description of the Data Highway 485 network in Chapter 2 Overview of the DH 485 Network Other Resources Refer to the manuals listed in the table Devices that Use the DH 485 Network on page 2 3 Publication 1756 UM 532A EN P M ay 2006 Preface ii Notes Publication 1756 UM 532A EN P M ay 2006 Chapter 1 1756 DH485 M odule Overview Introduction This chapter describes the 1756 DH485 module and what you must know and do before you begin to use it For See W hat the M odule Does 1 1 M odule Requirements 1 1 M odule Features 1 2 Prevent Electrostatic Discharge 1 3 Removal and Insertion Under Power 1 4 Typical Applications 1 5 Remote M essaging 1 7 Routing Limitations 1 8 W hat the Module Does The 1756 DH485 module supports the following types of communication e Data Highway 485 DH 485 Messaging Connectivity to two separate DH 485 networks in one module Common Industrial Protocol CIP Messaging M odule Requirements The following are required for using the 1756 DH485 communication module e RSLinx Software version 2 41 or later Node address within the range of 0 31 e AIC link coupler 1761 NET AIC communications
70. olLogix chassis backplane should be considered a separate independent netwotk Therefore a system of 1 DH 485 network and one ControlLogix chassis is a two link system The ControlLogix chassis backplane is required to be a separate independent link for DH 485 messaging if there is more than one message target ControlLogix controller in a ControlLogix chassis Routing Tables in Remote DH 485 M essaging The 1756 DH485 module contains a routing table that you define for your application The routing table contains information used to steer Remote DH 485 Messages through the system to remote nodes located on separate networks By using the routing table the 1756 DH485 module lets existing devices such as an SLC controller to use DH 485 Remote Addressing for messaging You must use RSLinx software to configure your routing table Refer to Use RSLinx Software to Create a Routing Table on page 4 2 for more information Publication 1756 UM 532A EN P M ay 2006 3 8 Use Data Highway 485 Network Publication 1756 UM 532A EN P M ay 2006 Programming M essage Block Instructions in a Controller for Remote DH 485 M essaging Before programming your message block instructions in your controller you must determine which links will send and receive remote DH 485 messaging draw a netwotk 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
71. ollowing table and to the troubleshooting section that follows Power Cycle Indicators Ifthe POWER Power Supply Recommended Action Indicator is Status is Off Not operating Turn power ON Check power wiring connections Check fuse On Operating None normal operation The LED status indicators on the module provide information about your module and the status of each channel The following tables outline the indicator condition and the corresponding status and explain what each condition means Interpret the LED Status Indicators Module OK Module Status Recommended Action Indicator Off Not operating Apply chassis power Verify module is completely inserted into chassis and backplane Green flashing Operating but not routing messages None if no messages are actively being routed through the module To route messages configure module with RSLinx software Solid Red then Off Performing self test None normal operation Solid Green Operating and routing Verify module configuration messages Solid Red In major fault Reboot module If red reoccurs then replace module Red flashing In major fault or Check alphanumeric indicator and take configuration fault action described in the Alphanumeric Display Descriptions table Interpret the Alphanumeric Indicators Troubleshoot the 1756 DH485 M odule B 3 Your 1756 DH485 module displays alphanumeric
72. on are property of their respective companies Preface 1756 DH485 Module Overview Overview of the DH 485 Netw ork Table of Contents Important User Information s pea om o Det A A 1 2 Purpose or This Manual asc vt ver at eed owen sanss Preface i Who Should Use This Manual o ooooooooo oo Preface i Other Resoufees sese pest decada Preface i Chapter 1 TAO UCA o d es x Se etre onte et o eie emp te titus 1 1 What the Module Does ooooooooomomormomoonromooo 1 1 Module Requirements erue utet re rette tie MARRS 1 1 Module Eeat tes 3 iiw ve iR VEI dui PE 1 2 Prevent Electrostatic Dischatpesiscuse n4 oex Perd PR e RR 1 3 Removal and Insertion Under Power o ooooooooooooo 1 4 Typical Applicators itt aee doc AN t A Marte V d aee 1 5 Remote Messapi Lco eire ead pe ne ONE ate ol e 1 7 Remote Upload and Download 41 tercii br s 1 7 Routine ni doti A emer dte tiia 1 8 DH 485 and CIP Messaging eiecit RR 1 8 Alphanumeric Indicators fov err RAF ydo uh e RR 1 9 Chapter 2 T ttoduCtota std it ed E S eb EU NR EA Ss 2 1 DH 485 Network Description S 42 ao uuu on URS Ie en 2 1 DH 485 Network Protocol lesen 2 2 DH 485 Token Rotation o oooooooooroconornomoroomoo 2 2 DH 485 Network InitializatioN oo ooooooooomoomooo 2 2 Devices that Use the DH 485 Network o ooooooomooo 2 3 1747 AIC Isolated Link Coupler for DH 485 000 2 4 1761 NET AIC Advanced Interface
73. onduit touch the plug on the cable Arrange the cables loosely within the conduit The conduit should contain only serial communication cables Install the conduit so that it meets all applicable codes and environmental specifications For more information on planning cable routes see Industrial Automation Wiring and Grounding Guidelines Publication Number 1770 4 1 Publication 1756 UM 532A EN P May 2006 2 12 Overview of the DH 485 Network Publication 1756 UM 532A EN P M ay 2006 Softw are Considerations Software considerations include the configuration of the network and the parameters that can be set to the specific requirements of the network The following are major configuration factors that have a significant effect on network performance e Number of nodes on the network Addresses of those nodes Baud rate e Maximum node addtess selection e SLC 5 03 SLC 5 04 and SLC 5 05 controllers only token hold factor e Maximum number of communicating devices The following sections explain network considerations and describe ways to select parameters for optimum network performance speed Number of Nodes The number of nodes on the network directly affects the data transfer time between nodes Unnecessary nodes such as a second programming terminal that 1s not being used slow the data transfer rate The maximum number of nodes on the network is 32 Set Node Addresses The best network performance occu
74. ontroller Slot feature for local messaging e Serial Port Configuration e No limit on number of modules per chassis up to the number of available slots and the capabilities of the power supply This figure shows the external features of the 1756 DH485 module Publication 1756 UM 532A EN P May 2006 Prevent Electrostatic Discharge 1756 DH485 M odule Overview 1 3 External Features of the 1756 DH485 Module Alphanumeric Door Backplane Status Indicator Label Connector REZO Channel A T and ono CHA CHB OK Module Status Indicators Channel A Connector Channel B Connector 43842 The DH 485 module is sensitive to electrostatic discharge ATTENTION This equipment is sensitive to electrostatic discharge which can cause internal damage and affect normal operation Follow these guidelines when you handle this equipment Touch a grounded object to dischatge potential static e Wear an approved grounding wriststrap Do not touch connectors or pins on component boards Do not touch circuit components inside the equipment e Use a static safe workstation if available e Store the equipment in approptiate static safe packaging when not in use Publication 1756 UM 532A EN P M ay 2006 1 4 1756 DH485 M odule Overview Removal and Insertion You can install or remove the module while chassis power is applied if you Under Power obsetve the following precautions WARNING Whe
75. ot an indication of restrictions on the 1756 DH485 module Publication 1756 UM 532A EN P M ay 2006 7 2 Communicate Between a PLC 5 Controller and a Remote SLC 5 03 Controller over M ultiple DH 485 Networks Hardware Configuration In this hardware configuration a remote PLC 5 controller sends a message to an SLC 5 03 controller Communications Between a PLC 5 and a Remote SLC 5 03 Controller on a DH 485 Netw ork ControlLogix Controller 1756 DHRIO 1756 DH485 O e oo DH RIO cado oo joon oco ooo ea ooo 000 000 Channel A 2 3 e The 1756 DHRIO and the 1756 DH485 are on the same backplane DH Network AIC E DH485 network communicates through link couplers PLC 5 controller sends a message to an SLC 5 03 controller 1 44069 SLC 5 03 Controller 5 The PLC 5 controller sends a message to an SLC 5 03 controller located on a DH 485 network e The PLC 5 controller is located on a DH network 1 e The PLC 5 controller is connected to channel A on a 1756 DHRIO module located at node 12 2 e The 1756 DHRIO is on the same backplane as the 1756 DH485 module and is located in slot 8 of the chassis 3 The 1756 DH485 module is located in slot 14 of the chassis 4 e The 1756 DH485 module uses channel A to connect to the SLC 03 controller located at node 1 ovet the DH 485 netwotk 5 Publication 175
76. qua adeant 6 2 Create the Routing Table in RSLinx Software 6 3 Configure the SLC 5 03 Controller Channel 1 Link ID 6 4 Configure the SLC 5 04 Channel 1 LinkID 6 5 Create a Message in RSLoet 500 20 navy tee te eth RS 6 6 Configure the Message e eed ax des Re eap ete ea a 6 7 SLC 5 03 Controller Sends a Remote Message sess 6 8 Hardware Configuration s ind si Ee E Cro ee a eR hen 6 8 Create the Routing Table in RSLinx Software 6 9 Create a Remote Message in RSLogix 500 iussu 6 10 Configure the Message cocer adeo ua E eod bore c 6 11 Chapter 7 TIPO CM CHOI dada do ld e ae LALO tl 7 1 Hardware Configuration vesc xe ee RAE REA EROR a 7 2 Greate th Rog ne Table Dit PRORA e 7 3 Configure the PLC 5 DH Channel 1A Link ID 7 4 Create a Message in RSEOGBES qv Va Sar OR UV NON Nil 7 4 Configure the Message cv bcati NP DH IESER gat Reese 7 5 Chapter 8 THE ORUCHOR ashi eve esce ebd ER REL AGI od lere 8 1 Hardware Config ratiori eo 8 2 Create a Message in RSLogix 500 4 ese eere ete 8 3 Configure th Messabcussesuriieten eode SA i nh eo bdo 8 4 Review the Multihop Feature in RSLogix 500 o o o oooo o o 8 5 Chapter 9 o uc t dude AA 9 1 Hardware Configuration x uxo PE PV we du erc oar PHAR Ed 9 2 Create a Message in RSLogix 0000 ws yh aay cee eines 9 3 Configure the Messages A Ad dass og petra Ce dA do pa ed 9 4 Publication 1756 UM 532A EN P
77. rence 12 Counter C50 E o0 output pe a LDN ceum E n input E s2 status B3 BINARY N12 0 TU gt T lt TIMER E Count Up ecu E 13 Counter C51 E c5 COUNTER Preset 32000 lt jeu DN e D Rs CONTROL Accum 25225 E nz INTEGER B F FLOAT N1220 TU D as JE Count Up ccu E mo 13 Counter C52 El ma Preset 32000 DN Accum 3789 El m2 E sms El nso 12 20 TU 3 Count Up u El lt gt _ ld For Help press F1 2 0000 APP 500 Pro ET Publication 1756 UM 532A EN P M ay 2006 8 4 Communicate from an SLC 5 05 Controller to an SLC 5 03 Controller over an EtherNet IP Network Configure the M essage This is the setup screen for the example configuration In this example the Ex MSG N12 0 51 Elements e The SLC 5 05 controller on E MultiHop an EtherNet IP network This Controller Control Bits with it s IP address at Communication Command 500CPU Read Ignore if timed out o Data Table Address N10 20 To be retried NR 100 100 100 8 D Size in Elements 1 Awaiting Execution EW 0 Channel Continuous Run CO 0 e The SLC 5 05 controller Tace Devi Error ER 0 age ewe Message done DN nenas He NEED Re Message Timeout Message Transmitting Ru SLC 5 03 controller on a Data Table Address N11 0 Message Enabled EN DH 485 netwotk via the Waiting for Queue Space 0 1756 ENBT module at IP Local Remote MultiHop address 100 100 100 7 over Error the backplane to a Error Co
78. ring 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 e The SLC 5 03 controller refuses the message because the buffers are full e The originator detects an application timeout when no reply is received e 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 DH 485 Link 1 1756 DH485 M odule 1756 DH485 M odule ControlLogix Chassis 6 amp i e ra a ea ml 1 8 a IS Routed messages sent over the backplane DH 485 Link 2 SLC 5 03 controller buffers are full AIC EE Ej SLC 5 03 controller detects a application timeout and increments an error bit Publication 1756 UM 532A EN P M ay 2006 44068 A SLC 5 03 Controller Use Data Highway 485 Network 3 13
79. rollers can be configured for DH 485 protocol You can connect channel 0 of the SLC 5 03 SLC 5 04 and SLC 5 05 controllers to a DH 485 network using the 1747 CP3 cable and a 1761 NET AIC Advanced Interface Converter AIC In this case the AIC must be powered with 24V dc The 1746 P1 P2 P4 P5 and P6 power supplies provide 24V dc user power that may be used to power the AIC Configure an SLC Controller for DH 485 SLC 5 01 SLC 5 03 5 04 or 5 05 1747 AIC V Bi oA 9 s s lem BB e Estes 2920 1 24V dc Power g Supply El 1747 C11 1761 NET AIC u 1761 CBL PM 02 or f 1747 CP3 DH 485 ii RS 232 24V dc User Power Personal Computer Connection 1761 NET AIC e T m Mt 1747 CP3 or 9j z l 1761 CBL PM 02 lt lt 24V dc User Power Connection Publication 1756 UM 532A EN P M ay 2006 2 10 Overview of the DH 485 Network Important Planning Considerations Publication 1756 UM 532A EN P M ay 2006 Carefully plan your network configuration before installing any hardware Listed below are some of the factors that can affect system performance Amount of electrical noise temperature and humidity in th
80. rs when node addresses start at 0 and are assigned in sequential order Controllers cannot be node 0 Also initiators such as personal computers should be assigned the lowest numbered addresses to minimize the time required to initialize the network Set Controller Baud Rate The best network performance occurs at the highest baud rate All devices must be at the same baud rate Additional Resources Overview of the DH 485 Network 2 13 M aximum Node Address Setting The maximum node address parameter should be set as low as possible This minimizes the amount of time used in soliciting successors when initializing the network If all nodes are addressed in sequence from 0 and the maximum node address is equal to the address of the highest addressed node the token rotation will improve by the amount of time required to transmit a solicit successor packet plus the slot timeout value You cannot add any nodes to the network without affecting the response time On the other hand since the time required to hold an open station address is gteater than the time required to pass a token it can be useful to leave a temporary device such as a personal computer connected if there is only one such device A solicit successor packet requires the same transmission time as the token pass but there is an added slot timeout period See your programming software user manual for the procedures to set node addresses controller baud rate and maximum n
81. ry 2001 PN O55107 02 Other Comments PLEASE FASTEN HERE DO NOT STAPLE PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERM IT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Allen Bradley PERAGERE ROCKWELL SOFTWARE DO DGE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES Rockw ell Automation Support www rockwellautomation com Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http suppott rockwellautomation com Installation Assistance If you expetience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United
82. s the baud rate selector switch should be taken out of the AUTO mode and set to the same baud rate as the network The AIC can be used in the following modes for DH 485 point to point RS 232 isolator e RS 232 to RS 485 isolator Communication is established using hardware handshaking or auto transmit signals The AIC can be used to interconnect the following devices e SLC 500 5 01 5 02 and 5 03 controllers channel 1 e SLC 5 03 5 04 and 5 05 controllers channel 0 MicroLogix controllers Logix Controllers Operator interface devices PC serial ports or any 9 pin DTE serial port e Logix controller serial port DH485 mode e 1756 DH485 module TIP The 1761 HHP B30 Hand Held Programmer is not connectable to the AIC advanced interface converter Misconception about the 1761 NET AIC Converter 1747 UIC USB to DH 485 Interface Converter Overview of the DH 485 Network 2 7 Node Address Identification There is no node address associated with the network port Port 3 Port 2 Node Address The node address is configured in the device connected to Port 2 Port 1 Node Address The node address is configured in the device connected to Port 1 Use this write on area to mark the node address of each connection DC SOURCE CABLE EXTERNAL The function of the 1761 NET AIC convert
83. slot set 4 8 use to route a local message 5 3 Index D Data Highway 485 DH 485 3 1 definition 3 1 Data Highw ay 485 DH 485 messaging 1 8 3 2 configuration 3 11 example 3 6 3 12 3 13 local 3 3 remote messaging 3 5 Data Highw ay 485 DH 485 network link design 3 2 Devices that use the DH 485 netw ork listing of devices 2 3 listing of related manuals 2 3 DH 485 configure an SLC for 2 9 example system configuration 2 8 DH 485 network 2 1 2 13 description 2 1 devices that use 2 3 example system configuration 2 8 initialization 2 2 isolated link coupler 2 4 planning considerations 2 10 protocol 2 2 token rotation 2 2 dow nload remote 1 7 electrostatic discharge ESD prevent 1 3 F features of the 1756 DH485 module alphanumeric indicators 1 9 B 3 external features 1 3 H hardware configuration 5 2 L legacy system migrate 1 6 limitations of Data Highway 485 DH 485 messaging 3 5 of remote Data Highway 485 DH 485 messaging 3 10 routing limitations for messages sent via the 1756 DH485 module 1 8 Publication 1756 UM 532A EN P M ay 2006 ii Index link coupler 1747 AIC 2 4 1761 NET AIC 2 6 link design on a Data Highway 485 DH 485 network 3 2 link IDs for remote Data Highway 485 DH 485 messaging 3 6 local Data Highw ay 485 DH 485 messaging 3 3 limitations 3 5 Receiving messages 3 4 routing errors B 4 M messaging Common Industrial Protocol CIP 3 14 Data Highway 485 DH 485 1
84. strial Protocol Logix controllers CIP messaging RSLogix 5000 and RSLinx software Use DH 485 Messaging Use Data Highway 485 Network 3 3 DH 485 Messaging offers the following benefits e You can send messages between devices on the same link You can send messages between devices on different links DH 485 messaging is divided into two types Local DH 485 Messaging See page 3 3 e Remote DH 485 Messaging See page 3 5 Before you can design a control system to meet your application needs be aware of the difference between Local DH 485 Messaging and Remote DH 485 Messaging Local DH 485 M essaging Devices use local DH 485 messaging to communicate between devices on the same physical link A device that uses local DH 485 messaging must generate local DH 485 packets e support local DH 485 protocol e send and receive messages TIP SLC 5 01 controller receives and replies but does not initiate Publication 1756 UM 532A EN P M ay 2006 3 4 Use Data Highway 485 Network Publication 1756 UM 532A EN P May 2006 This figure shows an SLC controller sending a local message to Channel A on the 1756 DH485 module Because the controller slot for Channel A is configured to 0 the message is forwarded to the ControlLogix controller in slot 0 SLC Controller Sending a Local Message to Channel A on the 1756 DH485 M odule v 1756 DH485 M odul ControlLogix Chassis 56 DH485 M odule 8 8 Ble
85. ter maximum node address The default value for this parameter is 31 for all initiators and responders The allowable range of the node address of an initiator is 0 to 31 The allowable address range for all responders is 1 to 31 There must be at least one initiator on the network Network initialization begins when a period of inactivity exceeding the time of a link dead timeout is detected by an initiator on the network When the time for a link dead timeout is exceeded usually the initiator with the lowest address claims the token When an initiator has the token it will begin to build the network The network requires at least one initiator to initialize it Building a network begins when the initiator that claimed the token tries to pass the token to the successor node If the attempt to pass the token fails or if the initiator has no established successor for example when it powers up it begins a linear search for a successor starting with the node above it in the addressing When the initiator finds another active initiator it passes the token to that node which repeats the process until the token is passed all the way around the network to the first node At this point the network is in a state of normal operation Overview of the DH 485 Network 2 3 Devices that Use the Presently the following SLC 500 devices support the DH 485 network DH 485 Netw ork Devices that Use the DH 485 Net
86. w ork Catalog Number Description Installation Function Publication Requirement 1756 DH485 ControlLogix DH485 ControlLogix Bridge DH485 messages in ControlLogix 1756 UM 532 Communication Chassis Module 1747 Lxxx SLC 500 SLC Chassis Programmable controllers 1747 UM 011 Programmable Controllers 1747 KE DH 485 DF1 SLC Chassis Provides a non isolated DH 485 interface for 1741 IN006 Interface M odule SLC 500 devices to host computers over RS 232 using full or DF1 half duplex protocol Enables remote programming to an SLC 500 controller or the DH 485 network through modems Ideal for low cost RTU SCADA applications 1747 UIC USB to DH 485 Standalone Provides connection to personal computer s USB port 1747 IN063 Interface Converter and features an RS 232 and an RS 485 port for connection to SLC 500 controllers 1747 AIC Isolated Link Coupler Standalone Provided connection to SLC 500 family devices to the 1747 UM 011 DH 485 network The coupler provides a 6 position removable terminal block for connection to the DH 485 communication cable 1761 NET AIC Advanced Interface Standalone Provides a communication link between various 1761 UM 004 Converter networks devices 1770 KF3 DH 485 DF1 Standalone or Provides an isolated DH 485 interface for SLC 500 1770 6 5 18 Interface M odule desktop devices to host computers over RS 232 using full or DF1 half duplex protocol Enables remote programming to an SLC 500 controller or the DH 485 network t
87. y connecting two AIC Advanced Interface Converters 1761 NET AIC Refer to the AIC Advanced Interface Converter User M anual publication number 1761 6 4 Publication 1756 UM 532A EN P M ay 2006 2 2 Overview of the DH 485 Network DH 485 Netw ork Protocol DH 485 Token Rotation DH 485 Netw ork Initialization Publication 1756 UM 532A EN P M ay 2006 The protocol used to control message transfers on the DH 485 network supports two classes of devices initiators and responders All initiators on the network get a chance to initiate message transfers To determine which initiator has the right to transmit a token passing algorithm is used A node holding the token is able to transmit a configurable number of message packets plus two retries onto the network before having to pass the token on to the next node This configuration parameter is called the Token Hold Factor and has a minimum value of one and a maximum value of four Once a node holding the token has sent any messages that it has to send up to its Token Hold Factor maximum allowed it attempts to pass the token to its successor by sending a token pass packet If no network activity occurs the initiator sends the token pass packet again After two retries a total of three tries the initiator will attempt to find a new successor IM PORTANT The maximum address that the initiator will search for before wrapping to zero is the value in the configurable parame

1756-UM532 - Rockwell Automation

Contents

Download Pdf Manuals

Related Search

Related Contents