ReleaseNotes

(9355-WABx)RSLinxClassicisthemostwidelyinstalledcommunicationserverinautomationtoday.
Version2.59.02

CatalogNumberRSLinxClassic

Thesereleasenotesdescribeversioninformationfor(9355-WABx)RSLinxClassicisthemostwidelyinstalledcommunicationserverinautomationtoday.,
version2.59.02.

SystemRequirements
Thisreleasehasthefollowingsystemrequirements.

SystemrequirementsforRSLinxClassic2.59.02
TouseRSLinxClassicv2.59.02(CPR9ServiceRelease5),yourpersonalcomputermustmeetthefollowingminimumhardwareandsoftwarerequirements:

Hardwarerequirements

ToinstallRSLinxClassic,youneedthefollowinghardware:

aPentium100MHzprocessorwithatleast32Megabytes(MB)ofRAM.ThisversionofRSLinxClassicdoesnotrunonAlpha,MIPS,orPowerPC
processors.
atleast35MBofavailableharddrivespacemoreharddiskspacemayberequiredforspecificapplicationfeatures.
a16-color,SVGAdisplaywith800by600orgreaterresolution.
amouseorotherWindows-compatiblepointingdevice.
anEthernetcardand/orAllen-Bradleycommunicationsdeviceorcable.

Softwarerequirements

TorunRSLinxClassic,MicrosoftInternetExplorer6.0(orlater)andAdobeAcrobatReader8.1(orlater)isrequiredandoneofthefollowingoperating
systems:

MicrosoftWindowsXPProfessional,SP1,SP2,orSP3[32-bit]
MicrosoftWindowsServer2003,SP1,SP2,R2,orR2SP2[32-bit],orMicrosoftWindowsServer2003R2StandardSP2[64-bit]
MicrosoftWindowsServer2008,SP1,SP2,R2,R2SP2[32-bit],orMicrosoftWindowsServer2008StandardSP2,R2SP1[64-bit]
MicrosoftWindowsVistaBusinessSP1,SP2[32-bit]orMicrosoftWindowsVistaHomeBasicSP1,SP2[32-bit]
MicrosoftWindowsVistaHomePremium(N)SP1,SP2[32-bit]orMicrosoftWindowsVistaHomePremium(N)SP1,SP2[64-bit]
MicrosoftWindow7Professional,SP1[32-bit]orMicrosoftWindows7Professional,SP1[64-bit]

MicrosoftWindow7HomePremium[32-bit]orMicrosoftWindows7HomePremium[64-bit]

RSLinxClassicv2.59.02(CPR9ServiceRelease5)runsontheMicrosoftVistaSP1,Windows7,andWindowsServer2008operatingsystemswith
limitations.

TheinstallationofRSLinxClassicincludesMicrosoft.NETv3.5SP1.DuringtheRSLinxClassicinstallation,youarepromptedtoautomaticallyinstallthis
componentifitisnotalreadypresent.

Forthelatestsoftwareplatformqualificationinformation,refertoRockwellKnowledgebaseAnswerID42682.

Softwarecompatibility

RSLinxClassicv2.59.02isacomponentofthelatestRockwellSoftwareCoordinatedProductRelease(CPR9ServiceRelease5).RSLinxClassicv2.59.02
(CPR9ServiceRelease5)hasbeentested,andiscompatible,withtheRockwellSoftwareCPR9ServiceRelease5ofthefollowingproducts:

FactoryTalkServicesPlatform(v2.50.00)

RSLinxEnterprise(v5.50.00)

SystemFeatures
Thisreleaseincludesthefollowingsystemfeatures.

NewfeaturesforRSLinxClassic2.59.02
RSLinxClassicv2.59.02(CPR9ServiceRelease5)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.59.02(CPR9ServiceRelease5).

Micro850EDSfileisnewlysupportedinRSLinxClassicv2.59.02(CPR9ServiceRelease5).Formorehardwaresupportinformation,refertoRockwell
KnowledgebaseAnswerID58981.
Fordriversupportinformation,refertotheRSLinxClassicDriverCompatibilityMatrix.SeeRockwellKnowledgebaseAnswerID58963.
RSLinxClassicv2.59.01(CPR9ServiceRelease5)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.59.01(CPR9ServiceRelease5).

USBCIP32bitdriverpackageisupdatedto3.18.02,andUSBCIP64bitdriverpackageisupdatedto1.1.11.Formoredriversupportinformation,
refertotheRSLinxClassicDriverCompatibilityMatrix.SeeRockwellKnowledgebaseAnswerID58963.
1756-L71SEDSfileisnewlysupportedinRSLinxClassicv2.59.01(CPR9ServiceRelease5).Formorehardwaresupportinformation,referto
RockwellKnowledgebaseAnswerID58981.

RSLinxClassicv2.59.00(CPR9ServiceRelease5)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.59.00(CPR9ServiceRelease5).

DataMonitorisnowavailableinallversionsofRSLinxClassic,includingRSLinxClassicLite.
Thefollowing64bitdriverisnowsupportedwheninstallingona64bitoperatingsystem:
1784-PKTCSDriver

Formoredriversupportinformation,refertotheRSLinxClassicDriverCompatibilityMatrix,showingwhichRSLinxClassicdriversarecompatiblewithspecific
operatingsystems.SeeRockwellKnowledgebaseAnswerID58963.

TheEDSfilesforsomedeviceshavebeenaddedorupdatedinthisrelease.Thisincludessupportfornewhardwaredevices.Formoredetailed
information,refertoRockwellKnowledgebaseAnswerID58981.

RSLinxClassicv2.58.00(CPR9ServiceRelease4)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.58.00(CPR9ServiceRelease4).

RSLinxClassicv2.58.00(CPR9SR4)andlaterversionsdisplaysamessageindicatestheactivationstatuswhenyouplacethecursoroverthetray
iconinthenotificationarea.Iftheactivationstatuschangesduringruntime,themessageshowsthenewstatusafteryourestartRSLinxClassicv2.58.
SupporthotplugandplayforAllenBradley12PointMicro810USBdevices.
TheRSLinxClassic2.58.00(CPR9SR4)installationprograminstallsorupdatestheMicrosoft.NETFrameworkto3.5SP1.
EvRSIactivationisreplacedbyFactoryTalkActivationsinceRSLinxClassicv2.58.00(CPR9ServiceRelease4).IfyouareusingEvRSIactivation,
pleasecontactyourlocalRockwellAutomationSalesofficeorTechnicalSupportforinformationonmigratingyouractivationstoFactoryTalkActivation.
ForRockwellAutomationTechnicalSupportintheU.S.,call1(440)646-3434.OutsidetheU.S.,seehttp://www.rockwellautomation.com/locations/.
Thefollowing64-bitdriverisnowsupportedwheninstalledona64-bitoperatingsystem:
VirtualBackplaneDriver
1784-PCICDriver
Ethernetdevices
EtherNet/IPDriver
RemotedevicesviaLinxGateway
RS-232DF1devices
1784-U2CN/1784-U2DNUSBCIPDevices
1784-PKTX(D)/PCMKforDH+/DH485devices1
1784-U2DHPforDH+devices2
1. The1784-PKTX(D)/PCMKdrivercannotbeinstalledontheWindowsServer2003R2[64-bit]operatingsystem.
2. Ifyouhaveproblemsconnectingtoadeviceusingthe1784-U2DHPdriver,disconnectandreconnectthe1784-U2DHP.

RSLinxClassicv2.57.00(CPR9ServiceRelease3)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.57.00(CPR9ServiceRelease3).

TheinstallationprogramforRSLinxClassic2.57.00alsoinstallsthenecessaryFactoryTalkServicesPlatform(FactoryTalkServicesPlatform2.30.00
versionCPR9SR3)componentsiftheyarenotinstalledorneedtobeupdated.
IfFactoryTalkServicesPlatformCPR9,CPR9SR1orCPR9SR2isalreadyinstalled,theRSLinxClassicinstallationprogramupdatesthe
necessarycomponentstoCPR9SR3.IfyoucanceltheFactoryTalkServicesPlatforminstallation,theRSLinxClassicinstallationprogramdoesnot
updatetheFactoryTalkServicesPlatform.
IfFactoryTalkServicesPlatformCPR7orolderisalreadyinstalled,theRSLinxClassicinstallationprograminstallsonlytherequiredcomponentsthat
arecompatiblewithallversionsofFactoryTalkServicesPlatform.
RSLinxClassic2.57.00(CPR9SR3)cannowbeinstalledon64-bitMicrosoftWindowsoperatingsystems.Forthelistofsupportedoperating
systems,seeSystemrequirements.
RSLinxClassic2.57.00(CPR9SR3)supportsthefollowing64-bitdriverswheninstalledona64-bitoperatingsystem:
Ethernetdevices
EtherNet/IPDriver
RemotedevicesviaLinxGateway
RS-232DF1devices
1784-PKTX(D)/PCMKforDH+/DH485devices1
1784-U2DHPforDH+devices2
1. The1784-PKTX(D)/PCMKdrivercannotbeinstalledontheWindowsServer2003R2[64-bit]operatingsystem.
2. Ifyouhaveproblemsconnectingtoadeviceusingthe1784-U2DHPdriver,disconnectandreconnectthe1784-U2DHP.

Formoreinformation,refertotheRSLinxClassicDriverCompatibilityMatrix,showingwhichRSLinxClassicdriversarecompatiblewithspecificoperating
systems.SeeRockwellKnowledgebaseAnswerID58963.

TheRSLinxClassic2.57.00(CPR9SR3)installationprograminstallsorupdatestheMicrosoft.NETFrameworkto2.0SP1.Itnolongerinstallsthe
.NETFramework1.1.
TheRSLinxClassic2.57.00(CPR9SR3)installationprogramnowcopiesallElectronicDataSheet(EDS)filestoyourlocalcomputerina
compressedformat(MicrosoftCAB).YoucannowgetEDSfilesfromyourcomputerinsteadofneedingtoinserttheRSLinxClassicInstallationCD.
WindowsTerminalServices(RemoteDesktopConnection)aresupportedinRSLinxClassic2.57.00(CPR9SR3)withsomerestrictions.Formore
information,refertoRockwellKnowledgebaseAnswerID68346,"RSLinxClassicandTerminalServices"
 TheRSLinxClassicSDKnowsupportstheDTL_INIT_EXfunction,includingtheDTL_INIT_FLAGS_STARTUP_RSLINXand
DTL_INIT_FLAGS_OPERATION_REFCOUNTflags.Formoreinformation,seetheRSLinxClassicSDKhelp.
TheEDSfilesforsomedeviceshavebeenaddedorupdatedinthisrelease.Thisincludessupportfornewhardwaredevices.Formoredetailed
information,refertoRockwellKnowledgebaseAnswerID58981.
TheEDSfilenamenowappearsintheDevicePropertiesdialogboxtohelpyouinlocatingthedeviceEDSfile.
The1784-U2DHPserialdrivernowsupportsoffline/remotemessagingoverDF1.
ThenewFactoryTalkActivationManagerinCPR9SR3replacestheoldsetofFactoryTalkActivationTools(fromCPR9SR2).

RSLinxClassicv2.56.00(CPR9ServiceRelease2)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.56.00(CPR9ServiceRelease2).

SupporthasbeenaddedfortheExternalAccessattribute(setinRSLogix5000,startingwithversion18forcontrollersthatsupportExternalAccess).
TheRSLinxClassicDataTableMonitorhasanewcolumn,AccessRights,thatshowsthestatusoftheExternalAccesssettinginthecontroller
(Read/WriteorReadOnly).ForcontrollersthatdonotsupportExternalAccess,theAccessRightscolumnalwaysdisplaysRead/Write.
TheinstallationprogramforRSLinxClassic2.56.00alsoinstallsthenecessaryFactoryTalkServicesPlatform(FactoryTalkServicesPlatformversion
CPR9SR2)componentsiftheyarenotinstalledorneedtobeupdated.
IfFactoryTalkServicesPlatformCPR9orCPR9SR1isalreadyinstalled,theRSLinxClassicinstallationprogramupdatesthenecessarycomponents
toCPR9SR2.
IfFactoryTalkServicesPlatformCPR7orolderisalreadyinstalled,theRSLinxClassicinstallationprograminstallsonlytherequiredcomponentsthat
arecompatiblewithallversionsofFactoryTalkServicesPlatform.
SupporthasbeenaddedforbrowsingCIPquerydevicessuchasthe1797-ACNR,1794-AENT,and1794-ACN(R).
TheULINTtagtypeisnowsupported.
YoucannowuninstalltheEDSsubsystemandHarmonycomponentinstalledbyRSLinxClassic.SelectStart>RockwellSoftware>RSLinx>Tools
>UninstallEDSHardwareInstallationTool.
YoucannowstopadriverinRSLinxClassicthatisusedexclusivelybytheAutobrowsefeatureinRSLinxClassic.
AddedConnectedMessagingsupportforOPCTopicProcessorType"Devicew/EDSParameters".Thisimprovestheefficiencyofthecommunications
inRSLinxClassic,thetargetdevice,andanyintermediatedevices.Itincreasestheamountofdatathatcanbereliablyexchanged.Italsoeliminates
theburstsofmessagerequestsrequiredwhenmultipledataitemsareonscan,whichoftencausesoverloadingofthetargetdevice'sunconnected
buffersandcanresultindevicelockup.
TheEDSfilesforsomedeviceshavebeenaddedorupdatedinthisrelease.Thisincludessupportfornewhardwaredevices.Formoredetailed
information,refertoRockwellKnowledgebaseAnswerID58981.
AnewRSLinxClassicDriverCompatibilityMatrixhasbeencreated,showingwhichRSLinxClassicdriversarecompatiblewithspecificoperating
systems.Formoredetailedinformation,refertoRockwellKnowledgebaseAnswerID58963.
Theautomationinterfacewrapper,RsiOpcAuto.dll,hasnotbeenupdatedwithchangesfromtheOPCFoundationforanumberofyears.TheOPC
Foundationrecommendsusingtheupdatedautomationinterfacewrapper,OpcDaAuto.dll,whichisnowprovidedwithRSLinxClassicinsteadof
RsiOpcAuto.dll.Formoredetailedinformation,refertoRockwellKnowledgebaseAnswerID64055.

RSLinxClassicv2.55.00(CPR9ServiceRelease2)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.55.00(CPR9ServiceRelease2).

RSLinxClassicv2.55.00(CPR9ServiceRelease2)runsontheMicrosoftVistaandServer2008operatingsystemswithlimitations.
Supporthasbeenaddedtoviewandconfiguredevicelevelringmodules(forexample,1756-EN2TRand1783-ETAPxx).
Anewprocessortype,DevicewithEDSParameters,hasbeenadded.
Tip:IfyouusedDeviceNetasaprocessortypeinRSLinxClassicv2.54andearlier,pleaseselectDevicewithEDSParameterswhenusingRSLinx
Classicv2.55,andthencompleteyourDDE/OPCtopicconfigurationasusual.
The1752-L24BBBEmodulehasbeenadded.
Tip:Ifyouattempttoconfigurethe1756-L24BBBESmartGuardmodulewhenusingaDeviceNetorUSBdriver,unexpectedcommunicationerrors
occur.

Supporthasbeenaddedforthe1756-A5XT/B5SlotExtendedTemperatureChassis.
Youcannowobtainthedevicepropertiesofanunrecognizeddevice(forexample,name,vendor,producttypeandcode,revisionandserialnumber,
andanyfaultinformationpresentwhenbrowsingthedevice)inRSWhobyselectingtheunrecognizeddevice,right-clickingthemouse,andselecting
DeviceProperties.

TheEDSfilesforsomedeviceshavebeenaddedorupdatedinthisrelease.Formoredetailedinformation,refertoRockwellKnowledgebaseAnswer
ID58981.
AnewRSLinxClassicDriverCompatibilityMatrixhasbeencreated,showingwhichRSLinxClassicdriversarecompatiblewithspecificoperating
systems.Formoredetailedinformation,refertoRockwellKnowledgebaseAnswerID58963.
TheLINTtagtypeisnowsupported(excludinginstancesofRSLinxClassicv2.55.00onMicrosoftWindows2000SP4).
RSLinxClassichasbeensuccessfullytestedondual-corecomputers.
IfyouarerunningonMicrosoftWindowsVistaorServer2008,RSLinxEnterpriseandRSLinxClassicinstallandusethesamedual-channel1784-
PKTX(D)driver.RSLinxEnterpriseisassignedtothefirstchannelbydefault(thiscannotbechanged).YouconfigureRSLinxClassictousethe
secondchannel.
Usethefollowingproceduretoconfigurethe1784-PKTX(D)driverforRSLinxEnterpriseandRSLinxClassic:
Ifyoudonotalreadyhavea1784-PKTX(D)driverinRSLinxEnterprise,thenright-clickRSLinxEnterprise,clickAddDriver,andselecta1784-
PKTX(D)driverfromthelist.TheDH+DriverPropertiesorDH485DriverPropertiesdialogboxdisplays.
Verifytheinformationinthedialogboxfieldsiscorrect,andclickOK.
StartRSLinxClassic,andclickCommunications>ConfigureDrivers.TheConfigureDriversdialogboxdisplays.
FromtheAvailableDriverTypeslist,clickthe1784-PKTX(D)driver,andthenclickAddNew.
IntheAddNewRSLinxClassicDriverdialogbox,enteradrivernameorusethedefaultname.ClickOK.TheConfigure1784-PKTX/PKTXD
dialogboxdisplays.
SelectthedrivertypefromtheValuelist,andclickOK.

Ifthefollowingcommunicationcardsarealreadyinstalledonyourcomputer,theirrespectivedriversareinstalledautomaticallywhenyouinstallRSLinx
Classic:
 1784-PCID(S)
1784-PCIC(S)
1784-PKTX(D)
1784-PKTCS
Tip:IfyouareusingMicrosoftVista/Windows2008Server:DuringRSLinxEnterpriseinstallation,aWindowsSecuritydialogboxwillbe
displayedbeforeeachdriverisinstalled.ClickInstalltoinstallthedriverandcontinueproductinstallation.Toavoidhavingtorepeatthisaction
foreachdriver,selectAlwaystrustsoftwarefrom"RockwellAutomation."
However,ifyouinstallthesesamecommunicationcardsonyourcomputerafteryouinstallRSLinxClassic,youmustmanuallyinstalltheir
respectivedriversfromthefollowingpath:x:\ProgramFiles\RockwellAutomation\Drivers(wherex:isthedriveyouhaveinstalledRSLinx
Classic).
Tip:IfyoualtertheconfigurationofanyoneofthesecardsafterinstallingRSLinxClassic,youmustmanuallyconfiguretheirrespectivedrivers.

RSLinxClassicv2.54.00(CPR9ServiceRelease1)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.54.00(CPR9ServiceRelease1):

RSLinxClassicv2.54.00(CPR9ServiceRelease1)runsontheMicrosoftVistaoperatingsystemwithlimitations.
RSLinxClassicv2.54.00(CPR9ServiceRelease1)supportstheRSLogix5000(v17)partialimportonlinefeature.Usethisfeaturetoimporta
ControlLogixprojectfileintoarunningcontroller.RefertotheRSLogix5000productdocumentationformoreinformation.
Supportforthefollowingdevices:
1766-LECMicroLogix1400Controller
1756-L65ControlLogixController
1768-L45CompactLogixController
1769-L2xCompactLogixController
1769-L23E-QB1BCompactLogixController
1769-L23-QBFC1BCompactLogixController
1769-L23E-QBFC1BCompactLogixController
1756-L63SGuardLogixSafetyController
1783-MxxxManagedSwitch
1783-MS06T6PortManagedSwitchBaseUnit
1783-MS10T10PortManagedSwitchBaseUnit
1783-MX08T8PortCopperExpansionModule
1783-MX08F8PortFiberExpansionModule
1756-EN2TR(Exxx)TwoPortModule
1756-CNB/EModule
1768-CNBand1768-CNBRModule
1756-CN2/Band1756-CN2R/BModule
1757-FFLDCModule
1756-DNB/CModule
1784-U2DNModule
1756-RIOModule
1756-EN2FModule
1747-L533SLC503Controller
1734-AENTXModule
1783-MSxxxStratix8000ModularManagedSwitch
1783-EMSxxxStratix6000FixedManagedSwitch

Inthisrelease,thesupportforthefollowingdrivershasbeenremoved:
S-SSD/SD2forDH+devicesdriver
1784-KT/KTX(D)forDH+/DH-485devicesdriver
1784-KTC(X)forControlNetdevices

TheLINTtagtypeisnowsupported(excludinginstancesofRSLinxClassicv2.54.00onMicrosoftWindows2000SP4).

RSLinxClassicv2.53.00(CPR9)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.53.00(CPR9):

RSLinxClassicv2.53.00(CPR9)runsontheMicrosoftVistaoperatingsystemwithlimitations.
Supportforthe1784-U2DHPCommunicationsSmartCable.
Supportfor1756-RMSeriesAdevice.
RSLinxClassicLitev2.53.00(CPR9)nowenablesOPCconnectivitytoFactoryTalkViewSE(localandremote),FactoryTalkViewME(localonly),and
FactoryTalkViewStudio.RSLinxClassicforFactoryTalkView(formallyRSLinxClassicforRSView)isonlyrequiredwhenusingRSLinxClassic
v2.52.00andearlier.

RSLinxClassicv2.52.00(CPR9)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.52.00(CPR9):

WhenconfiguringanEthernetdriver(AB-ETH),youcanappendanoption(:EIP)totheEtherNet/IPaddressthatspecifiesthedriverwillalwaysuse
theEtherNet/IPprotocolforEthernetdevices(forexample,130.130.130.130:EIP).ThisfeatureeliminatesconnectionfailurestoEthernetdevicesvia
satellitelinks.
EvRSIactivationwillbereplacedbyFactoryTalkActivationinafuturerelease.IfyouareusingEvRSIactivation,pleasecontactyourlocalRockwell
AutomationSalesofficeorRockwellAutomationTechnicalSupportforinformationonmigratingyouractivationstoFactoryTalkActivation.

ForRockwellAutomationTechnicalSupportintheU.S.call1(440)646-3434.OutsidetheU.S.seehttp://www.rockwellautomation.com/locations/.

InRSLinxClassicv2.52.00(CPR9),thesoftwaresupportsasevendayactivationgraceperiod,allowingyoutoaccessthesoftwareregardlessofthe
 validactivations'availability.

RSLinxClassicv2.52.00(CPR9)canbeusedoncomputerswithhyperthreadingturnedonresultinginnoperformancedegradation.
AllRockwellSoftwareproductsinthisrelease,includingRSLinxClassic,havebeentestedusingthelatestanti-virussoftware.Formoredetailed
information,refertoRockwellKnowledgebasetechnicalnoteA160252633.

RSLinxClassicv2.51.00(CPR7)

ThefollowingfeatureshavebeenaddedinRSLinxClassicv2.51.00(CPR7):

SupportfortheSmartGuard600(Catalognumber:1752-L24BBB)safetydevice.ToreadabouttheSmartGuardUSBdriverthatwasaddedforthe
device,clickhere.
IMPORTANT!KeepthefollowinginmindwhenworkingwiththeSmartGuard600safetydevice:
IfyouareinstallingSmartGuarddriveronacomputerthatalreadyhasRSLinxClassicinstalled,makesuretore-startRSLinxClassicafter
installingtheSmartGuarddriver.Ifyoudonotre-startRSLinxClassic,youwillnotbeabletoconfigurethedriver.
AlthoughyoucancommunicateovertheDeviceNetnetworkthroughtheUSBportoftheSmartGuarddevice,theUSB-to-DeviceNetbridging
capabilityislimited.Forexample,youcanNOTconfigure1734-ADNor1753-DNSImodulesthroughSmartGuard.UseanotherDeviceNet
interface,suchasa1784-PCDcard,toconfigurethesedevices.

Supportfor1756-EN2T/A,1756-CN2R/B,1756-L64,and1768-CNBdevices.
SupportforDH-485UICdevices(forexample,1747-UICdevice).ADH-485UICdrivertypewasaddedtothelistofavailabledrivers.
IMPORTANT!KeepthefollowinginmindwhenworkingwithDH-485UICdevices.
Ifyouplug-inyourDH-485UICdeviceonacomputerthatisrunningWindows2000andhas1752-L24BBBSmartGuardcontrolleralready
installed,thedevicewillnotberecognizedbytheWindows2000PlugandPlayfeature.Tofixtheproblem,followthesesteps:
1. GotoStart>Settings>ControlPanel>System.OntheSystemPropertiesdialogbox,clicktheHardwareTab.

2. OntheHardwareTab,clicktheDeviceManagerbutton.

3. IntheDeviceManagerwindow,expandtheUniversalSerialBuscontrollerstree.

4. YouwillseeanentryforFTDIFT8U2xxDevice.Right-clickit,andselectProperties.

5. OnthePropertiesdialogbox,clicktheUpdatedriverbuttontoupdatethedriver.
6. IfyouchangetheStationNumber(nodeaddress)ofaDH-485UICdevicewithoutfirstremovingorre-installingthedevice,thedevicewill
stopfunctioning.IfyouwanttochangetheStationNumber,youmustre-installtheDH-485UICdevice,andthenusetheConfigureUIC
devicesdialogboxtosettheStationNumber.

UploadEDSfilefromdevice.ThisfeatureallowsyoutoregistertheEDSfileforyourdevicefromwithinRSLinxClassicbyfollowingthestepslisted
below:
1. Connectyourdevicetothecomputer.
2. OpenRSLinxClassic,andlookforthedevice.
3. Onceyoufindit,right-clickit,andselecttheUploadEDSfilefromdeviceoption.

4. RuntheEDSwizardtoregistertheEDSfile.

AutoloadandshortcutfeatureforUSBDriver.ThisfeatureallowsRSLinxClassictoautomaticallyconfigureitselfwhenconnectingtoanetwork
interfaceviaaUSBport.Supportednetworkinterfacesarethe1756-EN2Tandthe1756-CN2R.
RSLinxClassicv2.51.00doesnotsupportthe1784-KT,1784-KTX(D)and1784-KTC(X)cardsonWindows2003R2.Theyaresupportedonlyon
Windows2000andWindowsXP.

RSLinxClassicv2.51.00nolongersupportsthe1747-PICdeviceinWindows2003orlater.

CorrectedAnomalies
Thisreleasecorrectsthefollowinganomalies.

AnomaliesfixedforRSLinxClassic2.59.02
ThefollowinganomalieswerefixedinRSLinxClassicv2.59.02(CPR9ServiceRelease5):

EDSfeaturegroupcannotbecustomizedduringRSLinxsilentmode.[272825]
InsufficienterrormessagewhensettingEthernetportspeedorduplexon1769-L3y.[272617]
RSLCstopsservingOPCdatawhenfirstchanceexceptionoccurs.[272608][272624]
1784-PKTCSDrivercannotbeinstalledonMicrosoftWindowsServer2008SP2[64-bit]orMicrosoftWindowsVistaBusinessSP2[64-bit]operating
system.[272724]

UnexpectedoptionssetinparallelinRSLinxClassicv2.58.00EN2TPortConfiguration.[294099]

KnownAnomalies
Thisreleasehasthefollowingknownanomalies.

KnownanomaliesforRSLinxClassic2.59.02
ThefollowingknownanomaliesexistinRSLinxClassicv2.59.02(CPR9ServiceRelease5):

Micro800seriescontrollersdonotsupportread/writetagsviaOPCorDataMonitor.Toaccessthecontrollerdata,youcanusetheModbusdriverof
KEPServerEnterprise.
The1784-PKTX(D)/PCMKdrivercannotbeinstalledontheWindowsServer2003R2[64-bit]operatingsystem.[289762]
Ifyouhaveproblemsconnectingtoadeviceusingthe1784-U2DHPdriver,disconnectandreconnectthe1784-U2DHP.[269399]
RSLogix5000,startingwithversion18,allowsyoutochangetheExternalAccessattributeforatagwhileonlinewiththecontroller(forcontrollersthat
supportExternalAccess).PleasebeawareofthefollowingissuesthatmayrequireyoutorestartRSLinxClassicanddataclients:
Ifacontrollerisreplacedwithadifferentcontroller,evenifithasthesameprogram.[265753]
Iftagattributesfortagsonscanarechangedandanewprogramisdownloadedtothecontroller.
IftagattributesfortagsonscanarechangedafteranAliasTopicswitch.[265756,266168]
AddingtheSLC500(DH485)EmulatordriverinRSLinxClassic,andthenclickingCancelontheConfigureSLC500(DH485)EmulatorDriverdialog
boxmaycauseRSLinxClassictoexitunexpectedlyonWindowsVista,Windows2008,andWindows7operatingsystems.[269134]
FactoryTalkViewStudioperformancetendstodegradeovertimewhentherearealargenumberofdevicesonthenetwork.Thesolutionistodelete
theHarmony.HRCandHarmony.RSHfileslocatedin"C:\ProgramFiles\RockwellSoftware\RSCommon".[218691]
Install,upgrade,anddowngradeissueswithRSLinxClassicv2.57(CPR9SR3)andtheRedundancyModuleConfigTool(RMCT):
TheRSLinxClassic2.57(CPR9SR3)InstalleralsoinstallsRMCTv6.2.10.0.IfRMCTv6.2.10.0hasalreadybeeninstalledmanuallywitha
priorversionofRSLinx(beforev2.57),itmaynotfunctionorstartafterupgradingtoRSLinxClassicv2.57(CPR9SR3).TorestoreRMCT,shut
downRSLinxClassic,startAddorRemoveProgramsfromWindowsControlPanel.SelectRedundancyModuleConfigTool,andthenclick
Change/Remove.WhentheRedundancyModuleConfigToolSetupstarts,selectRepairclickNexttocontinue.WhenyourestartRSLinx
Classicv2.57(CPR9SR3),theRMCTwillberestored.
IfyouuseAddorRemoveProgramstoremovethermctafterremovingaRSLinxClassicversionbeforev2.57,youmayseeerrormessages
about.dllfilesfailingtounregister.ClickOKinthemessage,andtheremovalprocesswillcompletesuccessfully.
IfyouhavealreadyinstalledaversionoftheRMCTv6.2.10orhigher,andyouwanttoreverttoRSLinxClassicv2.55orearlier(withthe
bundledRMCTv5.2.3orearlier),thecurrentversionoftheRMCTmustberemovedpriortoremovingRSLinxClassicv2.57(CPR9SR3).
Otherwise,youwillseeanerrormessageandthenewerversionoftheRMCTwillremaininstalledafterinstallingRSLinxClassicv2.55.
Iftherearealargenumberoftagsinthecontrollerandthenetworkperformanceislow,allofthetagsmaynotbedisplayedinOPCortheData
Monitor.[261725]
Toresolvethiscondition,performthefollowingsteps:
1. CloseRSLinxClassic.
2. ClickStart>Run.
3. IntheRuncommandline,type:regedit.TheRegistryEditorappears.
4. IntheRegistryKeywindow,navigatetoHKEY_Local_Machine\Software\RockwellSoftware\RSLinx\Settings.
5. UndertheSettingskey,clickEdit>New>DWORDvalue,andthentypethefollowingDWORDname:ACDTimeout.
6. Double-clicktheDWORDACDTTimeOuttheEditDWORDValuedialogboxappears.
7. IntheValueDatafield,enteratimeoutvalue(inseconds)largerthanthedefaulttimeoutvalue(21seconds).
Tip:RockwellAutomationsuggestsatimeoutvalueof180seconds.Thisvaluecanthenbeadjustedbasedonthenumberoftagsinyour
controllerprogram.

8. ClickOK.
9. ExittheRegistryEditor.
10. RunRSLinxClassicagaintoconfirmthatthenewtimeoutvalueissufficientforthenumberoftagsinyourcontrollerprogram.

IfyouareusingMicrosoftWindowsVistaandattempttogoonlinewithacontrollerthrougha1784-PKTXcardtoaremoteDH-485toDH+network,
RSLogix5maycrash.[263358]
IfyouareupgradingaclientcomputertoFactoryTalkServicesPlatformversion2.30.00(CPR9ServiceRelease3),ensureyoualsoupgradethe
computerhostingtheFactoryTalkNetworkDirectoryServertothelatestversionoftheFactoryTalkServicesPlatforminstalledonanyclientcomputer
onyournetwork.FailuretodosomightcauseunexpectedresultsforRSLogixArchitect,RSNetWorx,andRSLogix5000,version18.

RSLinxClassicv2.53.00(CPR9)andlatersupportsthe1747-PIC/AICdriveronWindowsXP,XPSP1,orXPSP2only.
DonotgivethesamenametoRSLinxEnterpriseshortcutsandRSLinxClassictopics.Ifashortcuthasthesamenameasatopic,tagswillnotbe
displayedforoneofthemduringatagbrowse.
Ifyouwanttobackup/restoreyourRSLinxClassicconfigurations,youmusthaveWindowsadministratorprivilegesonthecomputer.Ifyoudonothave
Windowsadministratorprivileges,youwillnotbeabletobackup/restoreyourRSLinxClassicconfigurations.
KeepthefollowinginmindwhenworkingwiththeSmartGuard600safetydevice:
IfyouareinstallingSmartGuarddriveronacomputerthatalreadyhasRSLinxClassicinstalled,makesuretore-startRSLinxClassicafter
installingtheSmartGuarddriver.IfyoudonotrestartRSLinxClassic,youwillnotbeabletoconfigurethedriver.
AlthoughyoucancommunicateovertheDeviceNetnetworkthroughtheUSBportoftheSmartGuarddevice,theUSB-to-DeviceNetbridging
capabilityislimited.Forexample,youCANNOTconfigure1734-ADNor1753-DNSImodulesthroughSmartGuard.UseanotherDeviceNet
interface,suchasa1784-PCDcard,toconfigurethesedevices.
KeepthefollowinginmindwhenworkingwithDH-485UICdevices:
Ifyouplug-inyourDH-485UICdeviceonacomputerthatisrunningWindowsandhas1752-L24BBBSmartGuardcontrolleralreadyinstalled,
thedevicewillnotberecognizedbytheWindowsPlugandPlayfeature.Tofixtheproblem,followthesesteps:
1. GotoStart>Settings>ControlPanel>System.OntheSystemPropertiesdialogbox,clicktheHardwareTab.
2. OntheHardwareTab,clicktheDeviceManagerbutton.
3. IntheDeviceManagerwindow,expandtheUniversalSerialBuscontrollerstree.
4. YouwillseeanentryforFTDIFT8U2xxDevice.Right-clickit,andclickProperties.
5. OnthePropertiesdialogbox,clicktheUpdatedriverbutton.
IfyouchangetheStationNumber(nodeaddress)ofaDH-485UICdevicewithoutfirstremovingorre-installingthedevice,thedevicewillstop
functioning.IfyouwanttochangetheStationNumber,youmustre-installtheDH-485UICdevice,andthenusetheConfigureUICdevices
dialogboxtosettheStationNumber.
YoucannotdownloaddatatoaStandardPanelViewonaDH+networkifyourcomputerisconnectedtotheStandardPanelViewviaRSLinxClassic
>EtherNet>1756-ENBTBackplane>1756-DHRIO>DH+networkpath.
YoucannotuseDDE/OPCtoreadorwritedatainaLogixprocessorthathasatagmappedtoaPLC/SLCfilenumberandatopicconfiguredasa
PLC-3processortype.UseaPLC-5typedtopicinstead.
WhenaccessingRSLinxClassicOnlineHelpfromHelp>RSLinxClassicHelpTopics,youseethefollowingerrormessage"Anerroroccurredwhile
tryingtostarttheonlinehelpforRSLinxClassic."
Topicsincompiledhelpfiles(.chm),donotdisplaywhenthehelpfileisopenedfromaremotecomputerorUNCpath.ThisaffectsmostonlineHelp
 andreleasenotesforRockwellSoftwareproducts.
Ifyouhaveinstalledsecurityupdate896358orWindowsServer2003SP1orlater,youmayexperiencethefollowingsymptoms:
ThefeaturesofsomeofWebapplicationsonthecomputernolongerwork.Forexample,atopicmaynotbedisplayedafteryouclickalink.
WhenyoutryuseaUniversalNamingConvention(UNC)pathtoopenaCompiledHelpModule(.chm)fileonanetworksharedfolder,topicsin
the.chmfiledonotappear.
WindowsServer2003SP1andsecurityupdates896358and840315includechangestotheInfoTechprotocol.Microsoftintroducedthese
changestoreducesecurityvulnerabilitiesinHTMLHelp.
Asaworkaround,openthehelpfilesfromtheinstallationCDorcopythemtoafolderonyourlocalcomputer.Ifyouwantthehelpfilestobe
accessiblefromanetworkdirectory(sharedfolder),youmustusetheRegistryEditortomodifycertainregistryentries.Microsoftdoesnot
recommendyoudothisbuthasprovidedthestepsinMicrosoftKnowledgeBasearticle896054.

WhenRSLinxClassicisre-installed,allsecuritysettingsthatwerepreviouslyconfiguredfornetworksanddevicesarelost.Youmustredefinethese
securitysettingsintheNetworksandDevicestree,orinRSWho.

OPCbrowseisnotsupportedfor.NETOPCapplications.

IfyouencounteraconditionwhereyouarenotgettingdatafromaSLC500processorandthatprocessor:

refusesaconnectionfromRSLinxClassic,and
generatesa:6AherrorintheDDE/OPCCommunicationsEventLog(forexample,AB_ETH-1\130.130.130.130:S:42:09/26/03-13:47:28:
6Ah)
youcanappendanoption(:V4)totheEtherNet/IPaddresswhileconfiguringanEthernetdriver(AB-ETH)thatspecifiesthedriveralwaysuses
thelegacyCSPV4protocolforSLC500processors.Forexample,130.130.130.130:V4.

Offlinebrowsingwillnotworktoan.acdfileonadifferentnetworkmachine.The.acdfilemustbeonthelocalmachine.
EtherNet/IPdrivercannotrecognizePLC5andSLCdeviceswhenusingRemotesubnet.
SincebothPKTXDcardchannelssharethesameinterrupt,youcannotconfigureonechannelofthecardforSoftLogix5andtheotherforRSLinx
Classic.YoucanconfigureRSLinxClassicandSoftLogix5touseseparatePKTX(D)cards.TherearenoknownissueswiththeKT(X)(D)card.
DonotuseanetworkshortcuttogoonlinewithRSNetWorxforDeviceNet.
RSLinxClassiccannotuseinterruptsontheKTorKTXdriverswheninstalledinaDELLOptiplexGXProcomputer.TheKTorKTXcarddefaultstono
interruptsforthiscomputer.
IfyouattempttoautoconfigaDF1driveranditdoesnotsucceed,placetheprocessorinprogrammodeandattempttheautoconfigagain.
RSLinxClassicdoesnotsupportDHconnectedtoaKF2.
WhenconfiguringtheWinLinxTCPClientdriverwithRSLinxClassicGateway,theRefreshDeviceListbuttondoesnotreturnalistofactivestations
onaspecificnetwork.
Ifyouhaveadisconnectednetworkdrivemappingandtheservermachineisnotup,RSLinxClassichangsforuptotwominutesduringstartupasit
checksthedeaddriveforanactivationfile.Toworkaroundthis,eitherdisconnectthedrivemappingifyounolongerneedit,orifyouractivationsare
allontheCdrive,addCHECKDRIVES=Ctothe[Common]sectionofthe%WINDIR%\ROCKSOFT.INIfile.
Multipleconfiguring,deleting,andre-configuringKT/KT(X)/PKTX(D)/PCMKdeviceswithRSLinxClassicmayresultinsituationswheretheABKTdriver
reportsresourceconflictsormemoryconflictsintheSystemEventlog.Theresultistheinabilitytostartthespecificinstancesofdriversreportingthe
errors.Ifyouencounterthissituation,theworkaroundistodeletealldriverinstances,rebootWindowsNT,andreconfigurethedrivers.Thislimitation
onlyappliestotheWindowsNTversionofthe1784-KT/KT(X)/PKTX(D)/PCMKdriver.
Duplicatenodesarenotdetectedwhenconfiguringthe1784-KT(D)card.Whenconfiguringthe1784-KT(D)card,useastationaddressthatisnotin
usebyanotherdevice.
The1794-ACNadapterdoesnotrespondtoUCMMrequestssentfromthe1770-KFCdriver.
RSLinxClassicwillnotbrowseRemoteDevicesviaLinxGatewayorSoftLogixdriversconfiguredonaLinxGatewayfromaclientbrowsingthe
gateway.
WhenusingRSWhotoselectaprocessorforRSLogix5,RSLogix500,orRSLogixFrameworks,youcannotgoonlinetothatprocessorifyouselected
itusingtheRSWho"LinxGateways"driver.ToselectaprocessorconnectedtoaLinxGateway,configureaRSLinxClassicdriverusingthe"Remote
DevicesviaLinxor1756-ENETGateway"driver.OnlyselectionsmadefromtheRSWho"LinxGateways"driverareunusable.
The1770-KF2and1770-KF3donotsupportofflinkmessages.Therefore,whenusingthesedevicesyoucannotbrowsethroughbridgessuchas
1785-KA,1785-KA5,or1756-DHRIO.
Ifthe1784-PCMKdriverisaduplicatenode,allstationsinRSWhoappearasaquestionmarkwitharedX.
WhenrunningRSLinxClassicasaserviceininteractivemode(withalogged-inuser),youcannotperformsecuredactions.Youwillreceivethe"The
usernamecouldnotbefound"errorforallactionsbecausesecurityinterpretstheRSLinxClassicuserof"SYSTEM"running.Therefore,itisnot
recommendedthatyouuseRSLinxClassicConfigurationSecuritywhenrunningRSLinxClassicasaservice.
FortheKFDModemDialerdrivertoproperlyconfigureandrun,thehardwarehandshakingbetweentheremotemodemandtheKFDmustbe
disabled.

IntheRSLinxClassichelpfile,theHomeselectionontheOptionbuttondoesnotfunctionproperly.

ApplicationNotes
Thisreleasehasthefollowingapplicationnotes.

ApplicationnotesforRSLinxClassic2.59.02
ViewingtheEDSparametersforaCIP-enableddevice

1. SelectStart>RockwellSoftware>RSLinx>Tools>EDSHardwareInstallationTool.FollowtheinstructionsonthescreentoinstalltheEDSfile
fortheCIP-enableddevicewhosepropertiesyouwanttoview.
2. SelectDDE/OPC>TopicConfiguration.TheDDE/OPCTopicConfigurationdialogboxisdisplayed.
3. ClickNew.AnewtopicisaddedtotheTopiclist.
4. Enteranameforthetopic.
5. InRSWho,locateandclicktheCIP-enableddevicewhoseEDSparametersyouwanttosee.
 6. ClicktheDataCollectiontab.
1. UnderProcessorType,clickDevicewithEDSParameters.
2. IfyouareusinganOPCclientfordataacquisition,underPolledMessages,enter8640000.ThisallowstheOPCclienttobettercontrolthe
dataupdaterate.
IfyouarenotusinganOPCclientfordataacquisition,gotostep6-3.
3. UnderLimitMessagePackets,changethesettingto1.
Tip:Initially,enteravalueof1.Later,youcanreturntothisdialogboxandslowlyincrementthevalueuntilyoureachapointwhereyouareno
longergettingdata.Atthattime,youcanthenslowlydecrementthevalueuntilyouarereceivingdataagain.
7. ClickApply,andthenclickDone.
8. Navigatetoyourclientprogram(forexample,RSView32ortheOPCTestClient),andlocatethetopicnamethatyouspecifiedinstep4.
9. ClickthattopictheOfflinebranchisdisplayed.
10. ClickOfflinealloftheparametersfortheCIP-enableddevicespecifiedinstep5aredisplayed.

DisplayinglargenumbersoftagsinOPCortheDataMonitor

Ifyouhavealargenumberoftagsinthecontrollerandrecognizethatthenetworkperformanceislow,allofyourtagsmaynotbedisplayedinOPCorthe
DataMonitor.Toresolvethiscondition,performthefollowingsteps:

1. CloseRSLinxClassic.
2. ClickStart>Run.
3. IntheRuncommandline,type:regedit.TheRegistryEditorappears.
4. IntheRegistryKeywindow,navigatetoHKEY_Local_Machine\Software\RockwellSoftware\RSLinx\Settings.
5. UndertheSettingskey,clickEdit>New>DWORDvalue,andthentypethefollowingDWORDname:ACDTimeout.

6. Double-clicktheDWORDACDTTimeOuttheEditDWORDValuedialogboxappears.
7. IntheValueDatafield,enteratimeoutvalue(inseconds)largerthanthedefaulttimeoutvalue(21seconds).
Tip:RockwellAutomationsuggestsatimeoutvalueof180seconds.Thisvaluecanthenbeadjustedbasedonthenumberoftagsinyourcontroller
program.

8. ClickOK.
9. ExittheRegistryEditor.
10. RunRSLinxClassicagaintoconfirmthatthenewtimeoutvalueissufficientforthenumberoftagsinyourcontrollerprogram.

Configurethe1784-PKTX(D)driverforRSLinxEnterpriseandRSLinxClassic(Vista,Windows2008,Windows7)

WhenyouarerunningRSLinxEnterpriseandRSLinxClassiconthesamecomputer(runningVista,Windows2008,orWindows7),andyourRSLinx
EnterpriseorRSLinxClassicconfigurationconsistsofadual-channel1784-PKTX(D)driver,youconfigurethedriverforbothRSLinxEnterpriseandRSLinx
Classic.

Usethefollowingproceduretoconfigurethe1784-PKTX(D)driverforRSLinxEnterpriseandRSLinxClassic:

1. Ifyoudonotalreadyhavea1784-PKTX(D)driverinRSLinxEnterprise,thenright-clickRSLinxEnterprise,clickAddDriver,andselecta1784-
PKTX(D)driverfromthelist.TheDH+DriverPropertiesorDH485DriverPropertiesdialogboxdisplays.

2. Verifytheinformationinthedialogboxfieldsiscorrect,andclickOK.

3. StartRSLinxClassic,andclickCommunications>ConfigureDrivers.TheConfigureDriversdialogboxdisplays.

4. FromtheAvailableDriverTypeslist,clickthe1784-PKTX(D)driver,andthenclickAddNew.

5. IntheAddNewRSLinxClassicDriverdialogbox,enteradrivernameorusethedefaultname.ClickOK.TheConfigure1784-PKTX/PKTXDdialogbox
displays.

6. SelectthedrivertypefromtheValuelist,andclickOK.

RunningRSLinxEnterpriseandRSLinxClassiconthesamecomputer

RSLinxEnterpriseandRSLinxClassiccanrunsimultaneouslyonthesamecomputer.Thisisacommonsetupifyouneedtocreateoreditaprogramusing
RSLogix5,RSLogix500,andRSLogix5000software(whichrequireRSLinxClassic)foruseinanapplicationandyoumustaccomplishthisusingonlyone
computer.

Vista,Windows2008,andWindows7operatingsystems

IfyourRSLinxEnterpriseconfigurationconsistsofa:

Dual-channel1784-PKTX(D)driver

AsofCPR9SR2,RSLinxEnterpriseandRSLinxClassicbothinstallandusethesame1784-PKTX(D)driver.RSLinxEnterpriseusesthefirstchannel
(assignedbydefaultandcannotbechanged).RSLinxClassicusesthesecondchannel.

IfyouarerunningonVista,Windows2008,orWindows7andyourRSLinxEnterpriseorRSLinxClassicconfigurationconsistsofadual-channel1784-
PKTX(D)driver,youconfigurethedriverforbothRSLinxEnterpriseandRSLinxClassic.

NOTE:Thisappliesonlytothedual-channel1784-PKTX(D)driverthesingle-channel1784-PKTXdrivercanbeconfiguredinonlyoneRSLinxproductata
time.

Alloperatingsystems

IfyourRSLinxEnterpriseconfigurationconsistsofa:
1784-PKTXdriver

IfyourRSLinxEnterpriseconfigurationconsistsofa1784-PKTXdriver,andyouneedRSLinxClassictocommunicateusingthatsamedriver,thenyoumust
sharethedriverwithinRSLinxEnterprisewithRSLinxClassic.

TIP:YoucanusethisprocedureforVista,Windows7,andWindowsXPoperatingsystemshowever,thepreviousprocedureisthepreferredmethod.

Serial-DF1driver(RS232DF1devices)

IfyourRSLinxEnterpriseconfigurationconsistsofaSerial-DF1driver(RS232DF1devices),andyouneedRSLinxClassictocommunicateusingthatsame
driver,thenyoumustsharethedriverwithinRSLinxEnterprisewithRSLinxClassic.

1784-PCIC(S)driver

IfyourRSLinxEnterpriseconfigurationconsistsofa1784-PCIC(S)driver,youconfigurethedriverinRSLinxEnterprise,thenaddavirtualbackplaneto
RSLinxClassic.ThevirtualbackplaneisasharablecomponentbetweenRSLinxClassicandRSLinxEnterprise.Sincethe1784-PCIC(S)plugsintothe
virtualbackplane,itissharableaswell.

SharinganRSLinxEnterprisedriverwithRSLinxClassic

TheSerial-DF1(RS232DF1devices)and1784-PKTXdriversareconfiguredinRSLinxEnterprise.Therefore,ifyoualreadyhaveoneofthesedrivers
configuredinRSLinxClassic,youmustdeleteitfromRSLinxClassicbeforeperformingtheprocedurebelow.

ToshareoneoftheseRSLinxEnterprisedriverswithRSLinxClassic,usethefollowingprocedure:

Note:ThisproceduredescribesthestepsusedtoshareaSerial-DF1driver.However,itisalsovalidforsharinga1784-PKTXdriver.

1. StarteitherFactoryTalkViewStudioortheFactoryTalkAdministrationConsoleandclicktheCommunicationstab.
2. Onthecommunicationstree,right-clicktheEthernetdriver(EtherNet,EtherNet),andthenclickProperties.TheEthernetPropertiesdialogbox
displays.
3. ClicktheAdvancedtab,andthenselectListenonEthernet/IPEncapsulationPortusingthecheckbox.ClickOK.
4. IfyoudonotalreadyhaveaSerial-DF1driverinRSLinxEnterprise,thenright-clickRSLinxEnterpriseandclickAddDriver,andselecttheSerialDF1
driverfromthelist.TheSerial-DF1DriverPropertiesdialogboxdisplays.
5. OntheGeneraltab,selectUseAuto-configuration.ClickOK.
Note:Whenyouadda1784-PKTXdriver,theDH+DriverPropertiesorDH485DriverPropertiesdialogboxdisplays.Verifytheinformationinthe
dialogboxfieldsiscorrect,andclickOK.
6. StartRSLinxClassic,andclickCommunications>ConfigureDrivers.TheConfigureDriversdialogdisplays.
7. FromtheAvailableDriverTypeslist,clickRemoteDevicesviaLinxGateway,andthenclickAddNew.
8. IntheAddNewRSLinxClassicDriverdialogbox,enteradrivernameorusethedefaultname.ClickOK.TheConfigureRemoteDevicesviaLinx
Gatewaydialogdisplays.
9. ClickBrowsetorefreshthelistofdrivers.FromtheServerNamelist,selectyourcomputernametodisplayalistofdriverstowhichyoucanconnect.
10. FromtheRemotedrivernamelist,clicktheSerialDF1driver,andclickOK.
Note:WhenusingRSLogix,selecttheremotedriver(e.g.,TCP-1)insteadofthedirectserialDF1(e.g.,AB_DF1-1).
11. ClickClosetoclosetheAddNewRSLinxClassicDriverdialogbox.

YounowhaveconnectivityforbothRSLinxEnterpriseandRSLinxClassicclientstheRSLinxEnterprisedriverappearsinRSLinxClassic.

If,aftercompletingthisprocedure,yourlocalworkstationisnotdisplayed,restartthehostcomputer.

SharingtheRSLinxEnterprisevirtualbackplanewithRSLinxClassic

ThevirtualbackplaneisasharablecomponentbetweenRSLinxClassicandRSLinxEnterprise.TosharetheRSLinxEnterprisevirtualbackplanewith
RSLinxClassic,usethefollowingprocedure:

1. StarteitherFactoryTalkViewStudioorFactoryTalkAdministrationConsole,andclicktheCommunicationstab.
2. Onthecommunicationstree,right-clickthevirtualbackplane(1789-A17,Backplane),andthenclickProperties.TheVirtualBackplaneProperties
dialogboxdisplays.
3. SelectAutoConfigureandthenclickOK.
4. Right-clickRSLinxEnterpriseandclickAddDriver,andselecttheControlNetdriver(1784-PCIC(S))fromthelist.TheControlNetPropertiesdialog
boxdisplays.
5. OntheGeneraltab,verifytheinformationinthedialogboxfieldsiscorrect,andclickOK.
6. StartRSLinxClassic,andclickCommunications>ConfigureDrivers.TheConfigureDriversdialogboxdisplays.
7. FromtheAvailableDriverTypes,clickVirtualBackplane(SoftLogix58xx),andthenclickAddNew.
8. IntheAddNewRSLinxClassicDriverdialogbox,enteradrivernameorusethedefaultname.ClickOK.
9. ClickClosetoclosetheConfigureDriversdialogbox.

YounowhaveconnectivityforbothRSLinxEnterpriseandRSLinxClassicclientstheRSLinxEnterprisevirtualbackplane(1789-A17,Backplane)appearsin
RSLinxClassic.

If,aftercompletingthisprocedure,yourlocalworkstationisnotdisplayed,restartthehostcomputer.

ConfigureanOPCclienttoobtaindatafromaprocessorusinganaliastopic

ToconfigureanOPCclienttoobtaindatafromaprocessorusinganaliastopic,performthefollowingsteps:

1. Usingoneoftherealtopicsassociatedwiththealiastopic,browsethetargetprocessortocollectnamesoftheOPCItems.
2. Oncecollected,addtheOPCItemstobeusedintheOPCclient.
3. FromtheOPCclient,exportthetagdatabasetoatextfile.
 4. Openthetextfile,andreplacethetopicnamewiththealiastopicname.
5. Savethetextfile,andimportitintotheOPCclienttagdatabase.

Routingthroughbridgedevices

Keepthefollowinginmindwhencommunicatingusingbridgedevices:

RSLinxClassiccannotcommunicatethroughanexternalbridgedevicewhenusingthe1756-DHRIObridgedevicewiththeTCPorCNETdriver.The
problemexistswhenthefirstbridgeisa1756-DHRIOdeviceandthesecondbridgeisnota1756-DHRIOdevice(forexample,PyramidIntegrator).In
thiscase,thesourcelinkIDremainsatzeroandtheresponsepacketsfail.Thefollowinglimitationscurrentlyexist:
Offlinkroutingworksthroughonebridge.
Offlinkroutingworksthroughtwoormorebridgesifthefirstbridgeisa1756-DHRIOmodule.
Offlinkroutingdoesnotworkthroughtwoormorebridgesifthefirstbridgeissomethingotherthan1756-DHRIOdevice.

YoucannotgofromaDHRIOmodulethrougha1785-KAbridgedevicetoaDHnetwork.
TogofromaDHRIOmodulethrougha1785-KA5bridgedevicetoaDH485network,theDHRIOmodulemustbeconfiguredusingtheControlLogix
GatewayConfigurationtool.Forexample,ifa1785-KA5bridgeisonaDH+networkatnode4andtheDH485LinkIDis13,completethefollowing:
1. SelectFile>BrowseNetwork.
2. SelecttheDHRIOmodule.
3. Gototheroutingtableconfigurationtab.
4. Right-clickthechannelbeingusedandselectAddModule.
5. SelecttheDH+Bridge.
6. EntertheDH+nodenumberoftheKA5(4inthisexample),andtheLinkIDoftheDH485(13inthisexample).
7. ClickApply.YoucannowbrowsethroughtheKA5module.

OtherApplicationNotes

ForanumberofyearstherehavenotbeenanychangesorupdatesfromtheOPCFoundationtotheautomationinterfacewrapper,RsiOpcAuto.dll.
TheOPCFoundationrecommendsusingtheupdatedautomationinterfacewrapper,OpcDaAuto.dll,whichisnowprovidedwithRSLinxClassicinstead
ofRsiOpcAuto.dll.Formoredetailedinformation,refertoRockwellKnowledgebaseAnswerID64055.
Youcannotconfigurea1747-PICdriverwhileRSLinxClassicisrunningasaservice.ConfigureaPICdriveronlyifRSLinxClassicisrunningasan
application,andtheReserveCOMPortforExclusiveusebythisDriverisenabled.ThischeckboxensuresRSLinxClassicworksproperlyifyourunit
asaservice.Then,whenbackingupandrestoringthedriver,updatetheCOMPortforthePIContheCommunicationPort(COM1)inthedevice
manager.
UnsolicitedmessageswithaLogix5000controlleronanEthernetnetworkoraDH+network.
ToreceiveunsolicitedDDEmessagesfromaprocessorthroughaDHRIOmodule,andthroughanENETmoduleoveranEthernetnetwork,select
yourDDEtopicfromtheDDE/OPCTopicConfigurationdialogbox.Then,selectAdvancedCommunication,clickRemote,andmanuallyenterthe
RemoteLinkIDoftheDHRIOchannelthroughwhichthemessageisbeingsent.
NewlycreatedDDEtopicsdefaultto20forLimitMaximumPackets.Thismakestheupdatesmoresymmetricalforthegroupofoptimizedpacketsfor
eachtopic.ForthesamefunctionalityonolderDDEtopics,setLimitMaximumPacketsontheDDE/OPCTopicConfigurationdialogbox,Data
Collectiontabto20,orthebestvalueforthePLCandaccessmethod.
WhenconfiguringDDE/OPCtopicstoreceiveunsolicitedmessagesfromaControlNetdevice,fromtheDDE/OPCTopicConfigurationdialogbox,
selecttheAdvancedCommunicationtabandselectLocalrouteforLocalorRemoteAddressing.
WhensettingupaDDEtopictoaremoteprocessorviaControlLogixGateway,ensurethatunsolicitedmessagescomingtoRSLinxClassictowork
properlybysettingtheRemoteLinkIDtomatchtheLinkIDoftheremotemodule(suchasDHRIO).
Blockreadsandwritesdonotworkwithuserdefinedtypes(Logix5000controller).
InWindowsNT,thePIC/AIC+andtheDF1PollingMaster/Slavedrivers(withRTScontrolenabledonly)driversneedtheirownserialdriver
(RSSERIAL.SYSratherthanSERIAL.SYS)andcannotthereforeshareaninterruptwithanotherserialdevice.
Whenusingautoconfigurationona1770-KF2/KF3device,youmustsettheStationNumbertothatoftheKF2/KF3beforeclickingAuto-Configure.
Otherwise,Auto-Configuretriestodetectthedeviceatthecurrentlyselectedstation,andifthedeviceisaPLC,Auto-ConfigureconfigurestothePLC
ratherthantheKF2/KF3.
IfyourestoreaWindowsNTconfiguration,andyouhaveaconfiguredKTC(X)orPCMKdriver,youmustrebootthecomputertostartthedriver.
Afterthefirsttimeyouconfigurea1784-PCCdriverinWindowsNT,youmustrebootyourcomputerbeforeusingthedriver.
The1784-PCCdrivercannotreceiveunsolicitedmessagesfromaprocessor.
Forthe1794-AENTand1756-ENBmodules,modulestatisticsonthePortDiagnosticstabdisplayallzeroseventhoughthemodulesworkproperly.
WhenyouinstallRSLinxClassic,DTL32.DLLremainsinthesystemdirectoryifitislockedbyanotherapplication.
YoumusthaveWindowsNTAdministrativeprivilegestoinstallRSLinxClassicand/orconfigureRSLinxClassicdrivers.
WhenreceivingunsolicitedmessagesfromanSLC500processorviaa1785-KA5Bridge,theDDEtopic'sremoteconfigurationmustbesetto
Internetmode.Also,intheSLC500messageinstruction,theremotebridgenodeaddressmustbesetto0.Also,unsolicitedmessagessentfroma
PLCorothernodetoRSLinxClassicwillcauseerrorsifnoDDEclientsorC-APIapplicationsarerunningtoreceivethem.
WhendownloadingaprogramtoanSLC500,stopalldataconnectionsactivetothatstation.Undercertaininstances,theprocessormayfaultif
applicationscontinuetopolltheSLCduringadownload.
RSLinxClassicwillnotrereadaUserDefinedStructurelistforSoftLogixuntilthetopicisstoppedandrestarted.
RSLinxClassicsupportsno-interruptconfigurationswhenusingAllen-Bradleynetworkcardshowever,werecommendassigninganinterruptto
increasedriverperformance.
IfyouhaveAutoHideonforthetaskbar,everytimeyougotothetaskbar(ifanimationison),itreducesyourpackets/secspeedduetocomputation
times.
DonotusethepowersaveroptiononyourcomputerwhenrunningRSLinxClassic.UseeithertheBIOSorControlPaneltodisablethisoption.

WindowsandRSLinxClassic2.59.02issues
WindowsXPProfessionalandWindows2003

Youmayexperiencedifficultyconfiguringthe1784-KTC(X)orthe1784-KTX(D)inWindowsXPbecauseofhowtheselegacyISAcardsobtain
 resources.WerecommendusingthePCIbasedcardswhenusingWindowsXP.ForControlNet,usethe1784-PCIC(S)card,andforDH+orDH-485,
usethe1784-PKTX(D)card.
HardwarehandshakingwiththeDF1pollingmasterandDF1SlavedriversisnotsupportedinWindowsXP.
Plug-n-Playdriversforthe1747-UIC,1784-PCC,1784-PCD,andSmartGuardUSB-KernelDriversarelocatedontheRSLinxClassicCDinthe
PnP_Driversdirectory.
Youmusthaveadministrativeprivilegestoconfiguredriversandtopics.
YoumusthaveadministrativeprivilegestousetheRS-232DF1driver.ThisdriveronlydisplaysinRSWhoandintheconfigureddriverslistifyouhave
administrativeprivileges.
Ifyoureceivean"UnabletoopenHKCU\Software\RockwellSoftwarekeyintheregistry!"message,checkwithyoursystemadministratortoget
administrativeprivileges.
WindowsXPcannotgointostand-bymodeifRSLinxClassichasa1784-PCCora1784-PCMKdriverrunning.

onsiderationswhenusingRSLinxClassic2.59.02withWindowsVista,Windows7,orServer2008
KeepthefollowinginmindwhenusingRSLinxClassicv2.59.02(CPR9ServiceRelease5)withMicrosoftWindowsVistaBusinessSP1[32-bit],Microsoft
WindowsVistaHomeBasicSP1[32-bit],MicrosoftWindows7[32/64-bit],orMicrosoftWindowsServer2008[32/64-bit]:

RSLinxClassicdefaultstostartingasanapplication.IfRSLinxClassicisrunningasaservice,thereisnographicaluserinterface(GUI).Ifyouneed
toconfigureRSLinxClassic,youmustbeinapplicationmode.ToswitchbetweenrunningasaserviceorapplicationusetheRSLinxClassicLaunch
ControlPanel.
ThefollowingcommunicationdriversAREsupportedandareavailableontheConfigureDriversdialog:
1784-U2DHPforDH+
RS-232DF1devices
Ethernetdevices
Ethernet/IPDriver
1784-PKTX(D)/PCMKforDH+/DH-485devices
DF1PollingMasterDriver
1784-PCIC(S)forControlNetdevices
DF1SlaveDriver
DH485UICdevices
VirtualBackplane(SoftLogix58xx,USB)
DeviceNetDrivers(1770-KFD,1771-SDN,and1747-SDN)
SLC500(DH485)Emulatordriver
SmartGuardUSBDriver
RemoteDevicesviaLinxGateway
ThefollowingcommunicationdriversARENOTsupported:
1784-PCCforControlNetdevices
1747-PIC/AIC+Driver
DeviceNetDrivers(1784-PCD/PCIDS)
PLC-5(DH+)Emulator
SoftLogix5driver

TheDF1PollingMasterDriverandDF1SlaveDriverdonotsupporthardwarehandshakingcontrol.
AttheendoftheRSLinxClassicinstallation,theinstallationprogramattemptstoinstalltheRockwellAutomationUSBCIPDriver-thisdriverisused
forRockwellAutomationUSBdevicesandisrepresentedbythe'VirtualBackplane(SoftLogix58xx,USBdriver)'typeontheConfigureDriversdialog.
Tosuccessfullyinstallthisdriver,youmustclick'Installthisdriversoftwareanyway'ontheWindowsSecuritydialogthatisdisplayed.
RSLinxClassicdoesnotstartproperlywhenitisconfiguredtorunasanadministratorandyouattempttologonasastandarduser.
WhenyouruntheBackup/Restoreutility,theRestartRSLinxClassicwhenfinishedcheckboxisnotavailableontheShutdownRSLinxClassicdialog
box.
IfyouattempttoviewtheSupportServices(support.hlp)orActivation(copyprot.hlp)information,anerrormessageislaunchedandtheonlinehelp
filesarenotdisplayed.ToviewtheSupportServicesorActivationinformation,pleaseseetheGettingResultsGuideforyourproduct.
UserAccountControl(UAC)isafeatureofMicrosoftWindowsVistathathelpsprotectyourcomputerfromdamagebyprogramsthatattemptto
performadministrativetasksonyourcomputerwithoutyourknowledge.Bydefault,UserAccountControlisactive,andpromptsyouforadministrative
credentials,ortoconfirmthatanexecutablefile(*.exe)associatedwithamenuitem,button,orotheritem,issafetorun.IfyouhaveUserAccount
Controlenabled,youarepromptedtoconfirmyouradministratorprivileges(enterausernameandpassword)whenperformingthefollowingRSLinx
Classic-specifictasks:
InstallingRSLinxClassic
RunningtheBackup/RestoreUtility
RegisteringEDSfilesviatheEDSHardwareInstallationTool
Savingrelatedfiles(forexample,theeventlog)totheC:driveonyourcomputer.Youwillbeinstructedtosavetoanalternatedrivelocation.

DataExecutionPrevention(DEP)settingsforRSLinxClassic2.59.02
DataExecutionPrevention(DEP)isasecurityfeaturethatissupportedbybothhardwareandsoftware.Itisintendedtopreventrunningmaliciouscodein
theMicrosoftWindowsXP(ServicePack2andServicePack3)andMicrosoftWindowsServer2003(ServicePack1andR2)operatingsystems.

DEPSettings

TheDEPsettingsdeterminewhichapplicationsandcomponentsarecoveredbyDEPprotection.Theyapplytobothhardware-supportedandsoftwareDEP
features.Oncomputerswiththenecessaryhardwarecapabilities,hardware-supportedDEPfeaturesareenabledforthesamesetofapplicationsand
componentsasthesoftwareDEPfeatures.ThefollowingtableexplainsthepossibleDEPsettingsandifthosesettingsaresupportedbyRockwellSoftware
products.
Note:RockwellSoftwarerecommendsthatyouusetheOptInDEPsettingsunlessyouhaveaspecificreasontochangethem.

DEPSetting Description SupportedbyRockwellSoftware

AlwaysOn FullDEPprotectionfortheentiresystem(allapplicationsand No
components,noexceptions).
OptIn DEP-enabledonlyforWindowssystemcomponentsandfor Yes
applicationsthatexplicitlyoptin.Thisisthedefaultsettingfor
MicrosoftWindowsXP(ServicePack2).
OptOut DEP-enabledforallprocessesexceptthosethatexplicitlyoptout.ThisYes
isthedefaultsettingforMicrosoftWindowsServer2003(ServicePack
1andR2).
DEPprotectionisdisabledfortheentiresystem(allapplicationsand
AlwaysOff components,noexceptions) Yes

Note:RockwellSoftwaredoesnotrecommendusingthissetting,since
itwillmakeyoursystemmorevulnerabletomaliciouscode.
ChangingDEPsettings

TochangetheDEPsettings,selectControlPanel>System>Advanced>PerformanceSettings>DataExecutionPrevention.TheTurnonDEPfor
essentialWindowsprogramsandservicesonlysettingcorrespondstotheOptInsettingandtheTurnonDEPforallprogramsandservicesexceptthoseI
selectsettingcorrespondstoOptOutsetting.

Tip:Keepthefollowinginmind:

Youmustbeanadministratorofyourcomputertochangethesesettings.
YoumustrebootthecomputerfortheDEPsettingchangestotakeeffect.

HardwareDEPSettings

HardwareDEPusestheprocessortomarkmemorysothatcodecannotbeexecutedfromdataregions.Whencodeattemptstoexecuteinthesemarked
areas,theprocessorgeneratesanexception.IfyouareusingMicrosoftWindowsXP(ServicePack2)orMicrosoftWindowsServer2003(ServicePack1
andR2)operatingsystems,theoffendingprogramisterminated.HardwareDEPisalsoenabledasthefactorydefaultsetting.Thisfeatureisturnedonor
offinthecomputerBIOSsettings.

TodetermineifyourhardwaresupportsDEP,refertothehardwaremanualorcontactyourhardwaremanufacturer.

Foradditionalinformation,seetheMicrosoftKnowledgebasearticleat:http://support.microsoft.com/kb/875352.

SilentinstallationforRSLinxClassic2.59.02

RSLinxClassicv2.59.02(CPR9SR5)supports"silentmode"toinstallthesoftwarewithoutanydialogboxes,messages,oruserintervention.Thecommand
linesyntaxis:

Setup.exe/qALLUSERS=1

Thecommandlineinstallhastheseoptions:

/qb:basicuserinterface

/qn:nouserinterface

/qor/quiet:quiet,nouserinteraction

Pleasenotethefollowingwhenusingsilentmodeinstallation:

OnWindowsVista,Windows2008,andWindows7,RSLinxClassicdefaultsto"RunasApplication".
IfFactoryTalkServicesPlatformisnotinstalled,youmustinstallFactoryTalkServicesPlatformfirst.IfFactoryTalkServicesPlatformCPR9,CPR9SR
1,orCPR9SR2isinstalled,youcanoptionallyupdateFactoryTalkServicesPlatformfirstbeforeyouinstallRSLinxClassicv2.59.02(CPR9SR5).
IfRSLinxClassic2.59.01(CPR9SR5)isinstalledusing"silentmode",youmustmanuallyinstalltheRedundancyModuleConfigToolafteryou
completetheRSLinxClassicv2.59.02installation.TomanuallyinstalltheRedundancyModuleConfigTool,runtheRMCTSetupprogramfromthe
RSLinxClassicv2.59.02(CPR9SR5)installation:\Redist\RSLinx\ENU\Redist\RMCT\DISK1\Setup.exe.
IfRSLinxClassic2.59.01(CPR9SR5)isinstalledusing"silentmode"on64bitoperatingsystems,youmustmanuallyinstallx64driverpackageafter
youcompletetheRSLinxClassicv2.59.02installation.Tomanuallyinstallx64driverpackage,runitfromRSlinxClassic2.59.01(CPR9SR5)
installation:\Redist\RSLinx\ENU\Redist\KN64Bit\DriverPkgx64.msi.
IfRSLinxClassic2.59.01(CPR9SR5)isinstalledusing"silentmode"on32bitoperatingsystems,youmustmanuallyinstallUSBCIPpackageafter
youcompletetheRSLinxClassicv2.59.02installation.TomanuallyinstallUSBCIPpackage,runitfromRSlinxClassic2.59.01(CPR9SR5)
installation:\Redist\RSLinx\ENU\Redist\USBCIP\Setup.Exe
IfRSLinxClassic2.59.01(CPR9SR5)isinstalledusing"silentmode",youmustmanuallyinstallWindowsFirewallConfigurationUtilityafteryou
completetheRSLinxClassicv2.59.02installation.TomanuallyinstallWindowsFirewallConfigurationUtility,runitfromRSlinxClassic2.59.01(CPR9
SR5)installation:\Redist\RSLinx\ENU\WindowsFirewallConfigurationUtility1.00.06.msi.
 DuringtheRSLinxClassicsilentinstallation,youmayseeoneortwoWindowsSecuritydialogs:
Ifthedialogstates,"Windowscan'tverifythepublisherofthisdriversoftware",pleaseclickInstallthisdriversoftwareanywaytocontinue
theinstallation.
Ifthedialogasks,"Wouldyouliketoinstallthisdevicesoftware?",pleaseselecttheAlwaystrustsoftwarefromRockwellAutomationcheck
boxandthenclickInstall.Selectingthecheckboxpreventsthisdialogfromappearingagain.

UpgradeinstructionsforRSLinxClassic2.59.02
PerformthefollowingstepstoupgradetoRSLinxClassicv2.59.02(CPR9ServiceRelease5):

1. CloseyourcurrentversionofRSLinxClassic.
2. InserttheRSLinxClassicv2.59.02(CPR9ServiceRelease5)productCD.Performtheinstallationstepsaspresentedonthescreen.
Tip:TheoldversionofRSLinxClassicthatexistsonyourcomputerisautomaticallyuninstalledwhenyouinstallRSLinxClassicv2.59.02(CPR9
ServiceRelease5).

3. Rebootyourcomputer.

UpgradingtheFactoryTalkServicesPlatformsoftwareforRSLinxClassic2.59.02
FactoryTalkServicesPlatforminstallsalongwiththesoftwareproductsthatrequireit.Installationandupgradestepsvary,dependingonwhichproductsyou
areinstallingorupgrading.Forstep-by-stepinstructions,seeeachproduct'sinstallationinformation.

IfyouareupgradingaclientcomputertoFactoryTalkServicesPlatformversion2.50.00(CPR9ServiceRelease5),youmayalsoneedtoupgradethe
computerhostingtheFactoryTalkNetworkDirectoryServertoFactoryTalkServicesPlatformversion2.50.00.Inthisrelease,severalproductsaddednew
SecurityPoliciesthatwillnotfunctioncorrectlyiftheFactoryTalkNetworkDirectoryServerisnotupgradedtoincludethem.Foradditionalinformationon
upgradingapreviousversionoftheFactoryTalkNetworkDirectoryServerorupdatesfortheotherproductsthatmayrequireupdates,seeRockwell
AutomationKnowledgebaseAnswerID54605.

WhenupgradingFactoryTalkplatformsoftware:

WhenyouupgradetoFactoryTalkServicesPlatform2.10(CPR9)orlateronacomputerthathasanearlierversionofFactoryTalkServicesPlatformor
FactoryTalkAutomationPlatforminstalled,theinstallationprocess:

createsabackupfileforanyexistingFactoryTalkDirectoryalreadyconfiguredonthecomputer.Shouldyoulaterneedtouninstallthecurrent
versionandreinstalltheearlierversion,restorethisbackupfiletoreturntheFactoryTalkDirectorytoitsearlierstate.SeeRestoreanearliersystem
afterupgradingFactoryTalkplatformsoftware.
checksforbothaLocalDirectoryandaNetworkDirectoryonthecomputer.Ifadirectoryisfound,theinstallationprocessupdatesitwith
supportfornewpoliciesandfeatures,butleavesoriginalsecurityandpolicysettingsunchanged.
Ifeitherdirectoryhasnotbeencreatedorconfigured,theinstallationprocesscreatesitandconfiguresitbyautomaticallyaddingthelocalcomputer
accountandthelocalWindowsAdministratorsgrouptothedirectory,andbysettingadefaulttograntallnewuseraccountsfullaccesstothe
directory.ThisstepallowsanyuseraccountwithWindowsAdministratorprivilegestobeabletoimmediatelylogontothedirectory,withoutfirsthaving
tocreateaFactoryTalkAdministratoraccount.
ifnecessary,updateseachFactoryTalkDirectorywithnewproductpolicies,systempolicies,andsupportfornewfeatures.
leavesalloriginalsecuritysettings,useraccountsandgroups,andpolicysettingsunchanged.

Whenupgradingcomputersinadistributedsystem

UpgradeclientcomputersonlyiftheversionoftheFactoryTalkplatformsoftwareinstalledontheFactoryTalkDirectoryservercomputerisnot
compatiblewiththenewversionsoftheproductsyouareinstalling.FordetailsaboutcompatibleversionsoftheFactoryTalkplatformsoftware,seethe
documentationprovidedwithyourproducts.
Ifyoudoneedtoupgradeclientcomputers,werecommendthatyouupgradeclientcomputersfirst,thenupgradetheservercomputerhostingthe
FactoryTalkDirectoryServer,andfinally,upgradeanyremainingrun-timeservercomputerslast.
WhenupgradingclientcomputersfromFactoryTalkAutomationPlatformversion2.00(CPR7),youmustupgradeclientcomputersfirst,and
thenupgradetheFactoryTalkDirectoryservercomputerlast.YoucannotconnectCPR7clientstoaCPR9orlaterFactoryTalkNetworkDirectory
Server.
TousethenewfeaturesavailablewithFactoryTalkServicesPlatform2.10(CPR9)orlater,theFactoryTalkDirectoryServercomputermustbe
upgraded.AnynewfeaturesarenotsupportedonaFactoryTalkDirectoryServercomputerthatisrunninganearlierversionoftheFactoryTalk
platformsoftware.
IftheFactoryTalkNetworkDirectoryServercomputerisupgradedtoFactoryTalkServicesPlatform2.10(CPR9)orlater,thentheproductsinstalled
onallclientcomputersonthenetworkmustalsobeupgradedtocompatibleversions.Fordetails,seethedocumentationsuppliedwithyourproducts.

Toupgradeclientcomputers:

1. BeforeupgradingtoFactoryTalkServicesPlatform,shutdownallRockwellAutomationsoftwareproductsrunningonthecomputer.
2. SomeRockwellAutomationsoftwareproductsrunasservicesinthebackground.BeforeupgradingtoFactoryTalkServicesPlatform,youmightneed
touninstallthoseproducts.Fordetails,seethedocumentationforyourproduct.

Toupgradeservercomputers:

1. BeforeupgradingFactoryTalkServicesPlatform,allrelatedservicesrunningonthecomputerareautomaticallyshutdown.Toavoidlossofdata,shut
downallRockwellAutomationsoftwareproductsrunningonthecomputerbeforebeginningtheupgrade.
2. Beforeupgradingaservercomputer,disconnectthecomputerfromthenetwork.Thispreventsclientcomputersfromaccessingtheserverduringthe
 upgrade.IfyouarerunningFactoryTalkserverproductsonyourcomputerandyoucannotdisconnectthecomputerfromthenetwork,uninstallthe
serverproductsbeforeupgradingFactoryTalkServicesPlatformonthecomputer.
IfyouareupgradingtheFactoryTalkNetworkDirectoryServercomputer,youmustdisconnectthecomputerfromthenetworkbeforeperformingthe
upgrade.
3. SomeRockwellAutomationsoftwareproductsrunasservicesinthebackground.BeforeupgradingtoFactoryTalkServicesPlatform,youmightneed
touninstallthoseproducts.Fordetails,seethedocumentationforyourproduct.
4. Whentheupgradeiscomplete,reconnecttheservercomputertothenetwork.

AfterupgradingtheFactoryTalkplatformsoftware,youmightneedtoinstallupdatesfortheproductsyouareusing.

ToidentifytheinstalledversionoftheFactoryTalkplatformsoftware:

1. OntheWindowsStartmenu,clickControlPanel.
2. Double-clickAddorRemovePrograms.
3. Inthelistofinstalledprograms,eitherFactoryTalkAutomationPlatformorFactoryTalkServicesPlatformappears,withtheversionnumber
shownbesideit.

Copyright2017RockwellAutomation,Inc.Allrightsreserved.
RockwellAutomation,Allen-Bradley,andRockwellSoftwarearetrademarksofRockwellAutomation,Inc.
ToviewacompletelistofRockwellAutomationtrademarkspleaseclickhere.
TrademarksnotbelongingtoRockwellAutomationarepropertyoftheirrespectivecompanies.