5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

(/app/answers/detail/a_id/16778/related/1#)

Support Center (/app/home)

Menu

ControlLogix Gateway: Data Highway Plus Communications

16778 | Date Created: 10/01/1998 | Last Updated: 05/01/2015
Access Level: TechConnect

Emailthispage

SubscribetoUpdates

ControlLogixGatewayCommunicationBetweenDataHighwayPlusNetworks
DataHighwayPlusorPCL(PeerCommunicationsLink)wasreleasedbyRockwellAutomation(AllenBradley)in1986.DataHighwayPlusisanoldarchitecturerelativetoEthernetandControlNetusedwiththe
ControlLogixGateway.TheDataHighwayPlusprotocol/architectureisnotcapableofcontainingalltheinformationnecessarytonavigatetheControlLogixGatewayalone.Thisisthereasonforthe1756GTWY
software.RSLinxClassicv2.0orhigher(orthe1756GTWYconfigurationsoftware)providesadditionalroutingtableinformationtotheDHRIOmoduledescribingthenetworksavailablesoapathcanbeestablished
forDataHighwayPlusmessages.

What is Required by Data Highway Plus Devices to Utilize the ControlLogix Gateway
Asageneralrule,devicesthatcommunicatethroughtheControlLogixGatewayfromDataHighwayPlusmusthavetheabilitytoboth:

remotelymessage
makeuseofLinkIDs
WhendeterminingifyourdevicewillcommunicatethroughtheControlLogixGateway,lookattheotherproductbeingused.

DoesitsDataHighwayPlusporthaveaparameterordipswitchavailabletoconfigureaLinkIDforthatchannel?
DoestheproducthavethecapabilitywithitscommunicationsorinitsmessagingcommandtoRemotelymessage?
LookforthekeywordsRemoteandLinktodetermineifyourproductcanmakeuseoftheControlLogixGateway.

Link ID
ThefundamentalpurposeofaLinkIDistonumbereachDataHighwayPluswhenmultipleDataHighwayPlusnetworksexist.TheLinkIDprovidesawayfortheControlLogixGatewaytodeterminewhatData
HighwayPlusnetworkamessageshouldgoto.Ideally,alldevicesonaDataHighwayPlusnetworkshouldhavematchingLinkIDparameters.WhenadeviceisnotcapableofspecifyingitsLinkID,bydefaultitis0
orundefined(thatportionoftheDataHighwayPlusdatapacketisnotfilledout).AdevicewithoutaLinkIDcanexistonanetworkwithdevicesthathaveaLinkIDparameter.DeviceswithoutaLinkIDparameter
willnotbeabletoinitiateamessagethroughtheControlLogixGatewayandonlyhavethecapabilitytomessagewiththedevicesonthatlocalnetwork.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

1/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Note:SLC5/04processorspassthruLinkIDonChannel1mustmatchtheLinkIDvaluesetonthecorrespondingDHRIOmodulethatitisconnectedto.

Local and Remote Messaging

RemotemessagingcapabilityprovidestheabilityforadevicetomessagefromtheLocalDataHighwayPlusnetwork,throughaBridgeorGateway,toanotherRemotenetworkofsometype.

ThemaindifferencebetweenaLocalmessageandaRemotemessageistheuseofanadditionalparameterreferringtoaLocalBridgenodeaddresswhichisusedtoaccesstheremotenetwork.Aremote
messagecanalsorequiretheLinkIDoftheremotenetworkand,insomecases,specifyanetworktypelikeDataHighway(notDataHighwayIIorOther).Someolderrevisionsofprocessorfirmwarecanhave
problemsremotelymessagingwiththenewertechnology.UpdatePLC5/11,5/20,5/4x,5/60and5/8xSeriesA,B,andCtorevisionMfirmwareorlaterupdateSLC5/04toOS401FRN5orlater.

DF1interfaceslikethe1770KF3,1747KE,1770KF2and1785KEdonotsupportremoteaddressing(theDF1protocol,explainedinPublication17706.5.16,doesn'tsupportremoteLinkIDs).Thesedevices
cannotcommunicatethroughtheControlLogixGatewaytootherremotenetworks.Remember:thekeywordsinthecriteriaforusingtheDHRIOmentionedareRemoteandLink.YouwillseeneitherDataHighway
PlustoDF1device,1785KEorKF2,canusearemotelinkID.

How to Navigate Multiple Data Highway Plus with the ControlLogix Gateway
NowthatweunderstandthecriteriarequiredforadevicetoutilizetheControlLogixGateway,we'lldiscusseshowtoconfiguretheControlLogixGatewaytojoinmultipleDataHighwayPlus.Thecoreexampleforthis
documentconsistsofthreedifferentlinks:

OneDataHighwayPlusiscommontotwoControlLogixChassis
theInitiatorisconnectedtoaDataHighwayPlusassociatedwiththefirstControlLogixChassis(designatedbytheRSLinxterminal)
ThetargetisconnectedtoaDataHighwayPlusassociatedwiththesecondControlLogixChassis(designatedbythePLC)
TheInitiator(onLink51)willcommunicatethroughthefirstControlLogixChassis,ontothesharedDataHighwayPlus(Link12)intothesecondControlLogixChassis,andaccessthetargetonthethirdnetwork(Link
13).

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

2/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

SystemusedforDiscussion

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

3/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Backplane91Backplane90Backplane92

1756DHRIOSlot7
A=Node46,Link51
B=Node47,Link12

1756DHRIOSlot2
A=Node51,Link11
B=Node52,Link12

1756DHRIOSlot4
A=Node31,Link13
B=Node32,Link32

1756DHRIOSlot5

A=Node53,Link13
B=Node54,Link14

ControlLogix Gateway Chassis DHRIO Module Congurations

Basedonthediagramabove,wewillnowcompletetheroutingtableforeachDHRIOmoduleinvolvedinourcommunicationspath(forChassisBackplanes90and91)usingtheconfigurationsoftware(suchas
RSLinx2.20andhigheror1756GTWY).Itisimportanttounderstandthecompletenetworkpath,associatednodeaddresses,andLinkIDofeachdevice.Itisnecessarytohaveanetworkdiagramofthe
proposednetworktokeeptrackofwhatLinksareaccessiblefromeachchassistoeliminatemistakes.NoticethatauniqueLinkIDisassignedtoeachchanneloftheDHRIO.Remember:Thenodeaddressforeach
channelissetwiththehardwareswitchesonthebottomoftheDHRIOmodule.Sincewedon'tseethenodeaddressinformationwiththeconfigurationsoftware,thisisanotherreasonfordrawinganetwork
diagramwhichincludesalldevices,theirnodeaddress,andlinkID.ItisalsoagoodideatoestablishastandardofsomesortforassigningaLinkID.Thiswillhelpreduceconfusionwhennavigatingthe
communicationspath.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

4/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

AdropdownmenusimilartothefollowingdisplayswhereweselectConfigurationorModuleConfiguration

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

5/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Generalandfaultinformationisavailable:

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

6/26

5/14/2016

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

16778ControlLogixGateway:DataHighwayPlusCommunications

7/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

SettheChannelConfigurationforthedefaultControlLogixcontrollerslot.IfalocalmessageisreceivedbytheDHRIO,itwillforwardthemessagetothisdefaultcontroller.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

8/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Using the 1756-GTWY Software

IfyoursoftwareispreRSLinx2.20,youwillneedtousetheoriginal1756GTWYconfigurationtool.Thelastreleasewasversion1.9(or1.91withsoftwarepatch).WhenconnectingtotheDHRIOmodulewith1756
GTWYsoftware,fromthemenuselectFile,BrowseNetworks,andacalltoRSLinxismadetoselecttheDHRIOmoduleyouintendtoconfiguretheroutingtable.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

9/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Routing Table for DHRIO in ControlLogix Chassis 1

Fromtheexamplenetworkshownabove,theRSLinxterminalresidesonDataHighwayPlusLink51andisconnectedtothefirstControlLogixChassisbya1756DHRIOmoduleinslot7,usingchannelA,node46.

ChannelBcontainsthecommonDataHighwayPlusnetwork(Link12)withtheDHRIOnode52inthesecondControlLogixChassis.Toprovideapathtothesecondchassis,youmustindicateontheroutingtable
thatyouarecreatingabridgetotheotherControlLogixChassis.ThisisdonebyrightmouseclickingonChannelB,addingaDataHighwayPlusBridge,andspecifyingwhatLinkIDsareavailablefromthesecond
ControlLogixChassis(DataHighwayPlus,ControlNet,andEthernetLinkIDs).(AnotherreasontohaveanetworkdiagramistoseewhatLinksareaccessiblefromotherControlLogixChassis.)
Oncetheroutingtableisconfigured,remembertopresstheApplybuttontosendthenewconfigurationinformationtotheDHRIOmodule.ThenextstepistoconnecttoaDHRIOmoduleinthesecondchassis.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

10/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Routing table for both DHRIO modules in ControlLogix Chassis 2

NoticethattheDHRIOmodule(ChannelB)inslot2alsohasaDataHighwayPlusBridgedefined,indicatingapathbacktothe1stControlLogixChassislistingtheaccessibleLinkIDfromthatchassis.Eachchassis
musthaveabridgereferringtotheotherchassis.Thisisnecessaryforthecommunicationstobesuccessfulbetweenthenetworks.Acommunicationspathmustexistsinbothdirection.Afterthesecondrouting
tableiscompletedfortheDHRIOinthesecondchassisandyoupresstheApplybutton,noticethattheconfigurationsoftwareasksyouifyouonlywantoneorbothDHRIOupdated.PresstheSelectAllbuttonso
bothDHRIOmodulesareselected.BothmodulesinthesecondControlLogixChassishavethesameroutingtable,thatis,eachmodulewillhaveknowledgeoftheother1756DHRIOaddedtoitsroutingtable
description.
WhenalltheDHRIOmodulesareconfiguredcorrectly,anapplication(RSLinx,PLC,SLC,andsoon),canmakeuseoftheGateway.

Conguring RSLinx 1.7 SuperWho screen on Network 1 to view devices on Network 3

ToaccesstheremoteDataHighwayPluswiththetargetPLCwithRSLinx1.7,theSuperWhoneedstobeconfigured(rightmouseclickontheSuperWhoscreen)asdescribedbelow:

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

11/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

WesuggestusingaStationUpdatemodePresstheConfigurebuttontocompletetheRemoteRoutingConfiguration.Thebridgedeviceisthe1756DHRIO,referringtotheremoteDHRIO,andthepathdescribes
toRSLinxhowtonavigatefromnetwork1totheDHRIOinslot5ofControlLogixChassis2.

Remote Routing Details Explained

0
KT/KTx/PCMKCardtoDataHighwayPlus.
38
Octalnodeaddress46(Decimal38).ThefirstControlLogixGatewayentrypoint,channelAonthefirstDHRIOmoduleinChassisOne.
3
ExittheDHRIOChannelB(2representschannelAand3representschannelB).
42
Octalnodeaddress52(Decimal42).TheDataHighwayPlusbridge(secondentrypoint)channelBonthesecondDHRIOmoduleinChassisTwo.
1
RepresentstheControlLogixbackplane.ThisisnecessarytoaccessthesecondDHRIOmoduleinthesecondchassis.
5
ZerobasedslotnumberofthesecondDHRIOmodule.
TherestoftheroutingdetailsisbasicallyfillingintheblankdescribingtheDHRIOport(inChassis2)thathasthetargetPLC.ThepathweprovidetakesustothethirdorlastDHRIOmodule,andthenweonlyneed
toindicatewhatchanneltoexitandspecifywhatLinkandNodeaddressisassignedtothatchannel.AftereachdialogboxisclosedyouwillseethenodesonDataHighwayPlusnetwork3(Link13).RSLogixcan
thenbeusedtogoonlinetotheprocessor.

Onenicefeature:WhenusingRSLinx1.7,whenyouenterthecommunicationspathintotheRSLinx1.7software,ifthereisaminorerrorintheroutingtable,RSLinx1.7canstillnavigatethroughthegatewayand
communicatewiththetargetdevice.Thisatleastverifiescorrectwiring.

Conguring RSLinx 2.0 SuperWho screen on Network 1 to view devices on Network 3

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

12/26

Conguring RSLinx 2.0 SuperWho screen on16778ControlLogixGateway:DataHighwayPlusCommunications

Network 1 to view devices on Network 3

5/14/2016

ConfigurationoftheSuperwhoscreenonRSLinx2.0isnotnecessary.Aslongastheroutingtablesareconfiguredcorrectly,RSLinx2.0cannavigateboththeControlLogixChassistothedesirednetwork.The
followingisacaptureofRSLinx2.0showingthenetworkpathusedintheexample:

ForourfirstPLCmessageexample,wearegoingtosimplifythenetworkandonlynegotiateoneControlLogixChassis(BackplaneLink91).

WewilladdaSLC5/04processortothesameDataHighwayPluswheretheRSLinxterminalislocated.
ThemessagepathconsistsofleavingaSLC5/04(Node24)Channel1,enteringthe1756DHRIO(Node46)ChannelA,exitingthesameDHRIOmodule(Node47)ChannelB,andarrivingataPLC5/40
(Node2)onLink12.
Thisscenarioisonlyusinghalfofoursystemconfigurationaboveforreasonspointedoutlaterinthisdocument,themessagedusediscapturedbelow.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

13/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

FromlookingattheRSLinxscreencaptureabove,thetargetPLC5/40wouldbelocatedontheDataHighwayPluswheretheDHRIO'snodes47and52areindicated.

Initiating a Message from a SLC-5/04 on Link 51 to a PLC5 on the Link 12 (Navigate one ControlLogix chassis)

Initiator 5/04 on Link 51, Target 5/40 on Link 12, using DHRIO bridge node 46
TouseaPLC5typedread,themessagetypeyouusewillbebasedonwhatissupportedoneachprocessorplatform.Here,aRemotemessageisused.Specifyalocalbridgeaddressof46,whichisthe1756
DHRIOorControlLogixGateway,andtheroutingtableintheDHRIOroutesthemessagetotheappropriatenetwork(Link12)wherethePLC5/40resides.

NoticethattheRemoteBridgeAddressparameterisnotused.Thisdemonstrationdoesnotnavigateall3networks,butitdoesshowthatdevicesonanynetworkdefinedintheroutingtablecanbeaccessed.This
wasarelativelysimplepath,jumpingacrossoneDHRIOmoduleinonechassis.Inthefollowingexamples,youwillseethatthemessageinstructiondoesnotchangemuchwhennavigatingmorecomplexsystems.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

14/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

NOTE:WhenmessagingwiththeSLC5/04processor,makesurethefirmwareisthelatestrevision.PastversionslikeOS401FRN2cannotmessageremotelythroughthegateway.

Initiating a Message from a SLC-5/04 on Link 51 to a PLC5/40 on Link 13 (Navigate two ControlLogix chassis)
Thisnextexampleusesthewholenetworkconfigurationcreatedabove,theSLC5/04toinitiatethemessageacrossall3DataHighwayPlusnetworksasshownbytheRSLinxscreencaptureabove.Noticethat
theonlydifferenceinthemessageinstructionistheLinkIDparameter.Thetargetstaysthesame(itwasmovedtoLink13,thethirdnetwork).AlsonoticethattheRemoteBridgeAddressfieldisstillnotused
becausethisexampleonlyusesoneControlLogixGatewaychassis.

Initiator 5/04 on Link 51, Target 5/40 on Link 13, using DHRIO bridge node 46
Initiating a Message from a PLC5/40 on Link 51 to a PLC5/40 on Link 13 (Navigate two ControlLogix chassis)

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

15/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Initiating a Message from a PLC5/40 on Link 51 to a PLC5/40 on Link 13 (Navigate two ControlLogix chassis)
Thisnextexamplewillusethecompletesystemconfiguration.ItconsistsofaPLC5/40processoronLink51,initiatingamessagethroughbothControlLogixChassis,tothePLC5/40onLink13.ThePLC5/40
wouldbeonthesamenetworkastheRSLinxterminalshownabove,andinitiatingamessageacross3DataHighwayPlusnetworks.Thisisthesamethingthatyousawwiththe5/04inthepreviousexample.

Initiator 5/40 on Link 51, Target 5/40 on Link 13, using DHRIO bridge node 46
Initiating a Message from a Logix 5550 on Link 13 to a PLC5/40 on Link 51 (Navigate two ControlLogix chassis)
ThisexampleusesaLogix5550controllertoinitiateamessageonthesamenetwork(Link13)asthetargetPLC5/40.We'veplacedanotherPLC5/40asourtargetwiththeRSLinxstation(Link51)asshowninthe
originaldiagramatthetopofthepage.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

16/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

IntheLogixchassis,theprocessorinitiatingthemessageisin(zerobased)slot1,andtheDHRIOcardisinslot4.FromthecommunicationsconfigurationoftheControlLogixprocessor,thechassisbackplaneis
thefirstnetwork.ThismeansthattheroutingtableintheDHRIOthattheControlLogixisusingasitsDataHighwayPlusportneedstoreferencetheothertwoControlLogixChassisusedintheexample.Seethe
routingtablebelowforanexamplethataddsathirdchassis.ThisisthesameroutingtableusedtosuccessfullycommunicatewiththeControlLogixprocessor,throughthe2ChassisControlLogixGateway,aswas
usedwiththePLC5/40andSLC5/04.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

17/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

FromthisControlLogixmessageexample,youarereadingthesecondsbytefromthePLC5onlink51.

Using PLC-2 Typed Messages

ThereareseveralthirdpartydevicesthatcommunicatewithAllenBradleyPLC'susingthePLC2typeorUnprotected(read/write)messagingformat.WhencommunicatingwithdevicesthatareusingPLC2type
messagingformat,therearetwoprimaryconcerns:

1.Doesthedevicesupportremoteaddressing!An,MMI,DCS,orotherdevicethatinterfacestoaDataHighwayPlususingRS232(DF1)bymeansofa1770KF2or1785KE/Cwillnotbecapableofremotely
addressingasmentionedearlier.Usetherulesstatedearlier.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

18/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

2.SincethePLC2messagestructuredoesnotspecifythefile(i.e.N7:0)inaPLC5toaccess,herethe(octal)nodeaddressoftheinitiatorisusedtodeterminethedecimalfileinthePLC5thatisaccessed.On
SLCprocessorsthePLC2Compatibilityfileisalwaysfile9.

ThismessagewasusedtocommunicatewithaPLC5/40C(ControlNet)processorresidingonDataHighwayPlus.TheinitiatorwasNode24,aSLC5/04processor,sothedatawasreadfromfileN20:4(octalnode
24withabyteoffsetof8).Eventhoughthebridgewasthedevicethemessagecamefromonthatnetwork,itwasthenodeaddressoftheinitiatorofthemessagethatisusedtodeterminewhatfileinthePLC5is
accessed.OnControlNetprocessors,theprocessorStatuscontainsasectionfordefiningthePLC2Compatibilityfile.WhenaccessingaControlNetprocessoronDataHighwayPlus,itwillbehaveinthesame
mannerastheotherDataHighwayPlusprocessorsandusethenodeaddressofthemessagesinitiator.

WhencommunicatingwithanactualPLC2usingthe1785KA3tointerfaceittoaDataHighwayPlus,theKA3moduleiscapableofrespondingtoamessagesentthroughtheControlLogixGateway.However,the
PLC2willnotbeabletoinitiateamessagethroughtheControlLogixGateway.ThePLC2(1785KA3)canonlybeaccessedfromanotherdeviceinitiatingcommunications.

Adding a third, fourth, etc... ControlLogix Chassis

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

19/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Adding a third, fourth, etc... ControlLogix Chassis

ThisexampleusesathirdControlLogixChassistoaddonemorelevelofcomplexitytothesystem.Thisdemonstrateshowcriticalhavingacorrectroutingtableistosuccessfulcommunications.Themessage
instructionsremainthesame(exceptforLinkID).Younowhavetomaintain3separateroutingtablesacross4DHRIOmodules.IfoneLinkIDiswrongorleftout,thecommunicationswillnotwork.Thefollowingare
theroutingtablesusedtoremotelymessageacrossControlLogixChassisor4DataHighwayPlusnetworks:

Theoriginalnetworkmodelwasusedasshownabove.WeaddedthethirdControlLogixChassistoLink13,movedthePLC5/40ontoitsLink32,andonceagainsuccessfullycommunicatedtheSLC5/04byusing
thecorrectLinkIDsettings.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

20/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Initiating a Message from a PLC5/40 on Link 32 to a SLC-5/40 on Link 51 (Navigate three ControlLogix chassis)
ThePLC5successfullyinitiatedaSLC500typemessagefromremoteLink32totheSLC5/04onLink51.We'veusedadifferenttypeofmessagecommand,noticethattheonlymajordifferenceistheLinkID.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

21/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

ThisisanicewaytoextendtheDataHighwayPlusbeyondthe10,000feetlimitation.Eachnetworktheoreticallysupports10,000feetmaximumlength.Inthislastexample,we'vecreateaDataHighwayPlus
bridgednetworkwithapotentialdistanceof40,000feet.(theoreticallyspeaking,barringpropagationdelaysandotherconsiderations).NowthatyoucanseewhatcanbedonewithDataHighwayPlusnetworks,
reviewtheconceptsandunderstandthemwell,becausethebestuseoftheControlLogixGatewayistocommunicatebetweenDataHighwayPlus,ControlNet,andEthernet.

Initiating a Message from a Logix 5550 on Link 92(13) to a 1770-KF2 (CH 0 of PLC5/40) on the Link 13
Thisexamplemakesuseofthe1770KF2toshowthatitcanbeusedtocommunicatewithaLogix5550processor.However,thecommunicationstabonitsmessageconfigurationmustbesetupdifferentlythan
shownabove.SincetheKF2doesnotreferenceLinkID's,bydefaultitsLinkIDsettingis0orundefined.InthisexampleweputaLogix5550processorinslotoneofthethirdControlLogixChassisshowninthe
routingtableconfigurationabove.TheDHRIOmoduleisinslot4.TheConfigurationsectionofthemessageinstructionremainsthesameasourpreviousexampleabovewhennegotiating2ControlLogixchassis.
InthisLocalmessageexample,relativelyspeaking,weomitthereferencetoLinkID's.

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

22/26

5/14/2016

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

16778ControlLogixGateway:DataHighwayPlusCommunications

23/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Sincethe1770KFhasnoLinkIDreference,youmustsettheSourceLinkandDestinationLinkto0.Usethismessagecommunicationpathtoroutethecommandtothe1770KF2andtheDHRIOchannel
configuration(controllerslotparameter)forthereplybacktotheControlLogixprocessorfromtheKF2.Ifthisconfigurationdoesnotworkforyou,besurethatthecontrollerslotfortherespectivechannelinthe
DHRIOpointstothecorrectControlLogixprocessor.

Common Mistakes
YoucanroutemessagesovermoderatelycomplexControlLogixGatewayconfigurationusingtheprinciplesabove.Mostapplicationswillonlynavigateonechassis,andtheyarerelativelysimpleinconfiguration.
Typicallyproblemsthatcanpreventcommunicationsbetweendevicescanbeoneormoreofthefollowing:

Improperlyconfiguredroutingtable(mostcommonmistake).
Improperlyconfiguredprocessorcommunicationport.
Usingthewrongprocessorportinthemessageinstruction.
Wrongnodeorbridgeaddress.(typicallyanincorrectoctaltodecimalconversion)
Useofanincompatiblemessagetypewiththetargetdevice.
Physicalnetworkconnectionandwiringproblems.
Attemptingtoaccessanetworksaturatedwithcommunicationstraffic.SeetechnoteG16912(//rockwellautomation.custhelp.com/app/answers/detail/a_id/16777)StructuredTroubleshootingoftheCL
GatewayNetworksandComponentsforinformationontroubleshooting.
NotdownloadingtheroutingtabletoeachDHRIOmoduleusedinthesamechassis.
Ifthereareproblemswithremotemessaging,simplifythecommunicationspathasmuchaspossible.Firstmakethedevicescommunicatelocally,thenremotelyusingonebridgeorgateway,thenaddthesecond.
Usetheerrormessagesprovidedbythedevices,thesearecriticalindeterminingwhatiswrong.AnerrorD000istheonlyonethatisactuallygeneratedbytheDHRIOmodulewhichmeans,youspecifiedaLink
thatI'mnotawareof.AllothererrorcodesarefromtheprocessorsortheControlLogixGatewayindicatingaconditioninthenetworklike"Nodedoesnotexist".

Other Knowbase documents on Data Highway Plus Communications:

16781(//rockwellautomation.custhelp.com/app/answers/detail/a_id/16781)ControlLogixGateway:DataHighwayPlustoControlNetCommunications
16782(//rockwellautomation.custhelp.com/app/answers/detail/a_id/16782)ControlLogixGateway:DataHighwayPlustoEthernetCommunications
16783(//rockwellautomation.custhelp.com/app/answers/detail/a_id/16783)ControlLogixGateway:ControlNettoDataHighwayPlusCommunications
16785(//rockwellautomation.custhelp.com/app/answers/detail/a_id/16785)ControlLogixGateway:EthernettoDataHighwayPlusCommunications

DISCLAIMER
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

24/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Thisknowledgebasewebsiteisintendedtoprovidegeneraltechnicalinformationonaparticularsubjectorsubjectsandisnotanexhaustivetreatmentofsuchsubjects.Accordingly,theinformationinthiswebsite
isnotintendedtoconstituteapplication,design,softwareorotherprofessionalengineeringadviceorservices.Beforemakinganydecisionortakinganyaction,whichmightaffectyourequipment,youshould
consultaqualifiedprofessionaladvisor.
ROCKWELLAUTOMATIONDOESNOTWARRANTTHECOMPLETENESS,TIMELINESSORACCURACYOFANYOFTHEDATACONTAINEDINTHISWEBSITEANDMAYMAKECHANGESTHERETOATANY
TIMEINITSSOLEDISCRETIONWITHOUTNOTICE.FURTHER,ALLINFORMATIONCONVEYEDHEREBYISPROVIDEDTOUSERS"ASIS."INNOEVENTSHALLROCKWELLBELIABLEFORANYDAMAGES
OFANYKINDINCLUDINGDIRECT,INDIRECT,INCIDENTAL,CONSEQUENTIAL,LOSSPROFITORDAMAGE,EVENIFROCKWELLAUTOMATIONHAVEBEENADVISEDONTHEPOSSIBILITYOFSUCH
DAMAGES.
ROCKWELLAUTOMATIONDISCLAIMSALLWARRANTIESWHETHEREXPRESSEDORIMPLIEDINRESPECTOFTHEINFORMATION(INCLUDINGSOFTWARE)PROVIDEDHEREBY,INCLUDINGTHEIMPLIED
WARRANTIESOFFITNESSFORAPARTICULARPURPOSE,MERCHANTABILITY,ANDNONINFRINGEMENT.Notethatcertainjurisdictionsdonotcountenancetheexclusionofimpliedwarrantiesthus,this
disclaimermaynotapplytoyou.

ThispageisbestviewedinInternetExplorer10,Firefox31,Chrome37,Safari6ornewer.

Related Articles
ControlLogixGateway:DataHighwayPlustoEthernetCommunications(/app/answers/detail/a_id/16782/related/1)
16782|03/30/2015

ControlLogixGateway:EthernettoDataHighwayPlusCommunications(/app/answers/detail/a_id/16785/related/1)
16785|03/30/2015

MSGfromControlLogixtoaPLC5overDataHighwayPlus(1756DHRIO)(/app/answers/detail/a_id/41476/related/1)
41476|08/13/2015

ControlLogixGateway:EthernetCommunications(/app/answers/detail/a_id/16780/related/1)
16780|04/11/2015

PLC5/ControlLogix:MessagefromPLC5usingDataHighwayPlusthroughGatewaytoControlLogix(/app/answers/detail/a_id/30049/related/1)
30049|12/04/2014

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

25/26

5/14/2016

16778ControlLogixGateway:DataHighwayPlusCommunications

Previously Viewed Articles

New Site Feedback

GiveFeedback

(http://www.rockwellautomation.com/global/blog/overview.page)
(https://www.facebook.com/ROKAutomation)
(https://plus.google.com/+RockwellautomationInc)
(https://www.linkedin.com/company/rockwell
(http://www.slideshare.net/RockwellAutomation)
(http://twitter.com/ROKAutomation)
(http://www.youtube.com/rokautomation)
automation)

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/16778/related/1

26/26