Citect Pty Ltd

3 Fitzsimmons Lane
Gordon NSW 2072
Australia
www.citect.com

Version5.5

CitectSCADANetworks

DISCLAIMER
CitectPty.Limitedmakesnorepresentationsorwarrantieswithrespecttothismanualand,tothe
maximumextentpermittedbylaw,expresslylimitsitsliabilityforbreachofanywarrantythatmaybe
impliedtothereplacementofthismanualwithanother.Further,CitectPty.Limitedreservesthe
righttorevisethispublicationatanytimewithoutincurringanobligationtonotifyanypersonofthe
revision.

COPYRIGHT
Copyright2003CitectPtyLimited.Allrightsreserved.

TRADEMARKS
CitectPtyLimitedhasmadeeveryefforttosupplytrademarkinformationaboutcompanynames,
productsandservicesmentionedinthismanual.Trademarksshownbelowwerederivedfrom
varioussources.
CitectSCADA,CitectHMI/SCADA,CitectFacilitiesandCitectSCADABatchareregisitered
trademarksofCitectPty.Limited.
IBM,IBMPCandIBMPCATareregisteredtrademerksofInternatrionalBusinessMachine
Corporation.
MS-DOS,Windows,Windows98,Windows2000,WindowsXPandExcelaretrademarksof
MicrosoftCorporation.
dBaseisatrademarkofBorlandInc.

GeneralNotice:
Someproductnamesusedinthismanualareusedforidentificationpurposesonlyandmaybe
trademarksoftheirrespectivecompanies.

October2003EditionforCitectSCADAVersion5.5
ManualRevision1.0
CitectSCADANetworks 2

IntroductiontoNetworks
Forlargeapplications,youcanaddaLANtotheCitectHMI/SCADAsystem,oruseanexistingLAN
supportedbyCitectHMI/SCADA.
YoucanuseNetBEUI,IPX/SPX,TCP/IP,andothernetworkprotocolswithCitectHMI/SCADA.
CitectHMI/SCADAalsosupportsallprotocolscompatiblewithNetBIOS,forexample,Novell
Netware,LANManager(withWindows3.1,WindowsforWorkgroups,andWindowsNT),and
variousothernetworkoperatingsystems.CitectHMI/SCADAcanusemultipleprotocolsatthesame
time.
CitectHMI/SCADAsupports'ScalableArchitecture',permittingyoutoinitiallyimplement
CitectHMI/SCADAonasinglecomputer,oroverasmallnetwork,andthenexpandthesystemata
laterstage(tosuitbudget,developmentpath,etc),withouttheneedtoreplaceexistinghardware,
software,orsystemconfiguration.
UsingCitectHMI/SCADAonaLANaddsmoreflexibilitytothesystem,andcoordinationwithinlarge
plantscanbemoreeasilyachieved.Youcancontrolandmonitorautonomousareaswithinthe
plantseparately,andinterrogatethewholeplantusinganyCitectHMI/SCADAcomputeronthe
networkifyouwish.
ALANcanalsobeusedto:
Distributetheprocessingloadforlargesystems.SeeUsingDistributedProcessing.
Provideredundancy.SeeBuildingRedundancyIntoYourSystem.
Thefollowingillustrationprovidesanexampleof3CitectHMI/SCADADisplayClients(with1also
performingasaCitectHMI/SCADAI/OServer)connectedtoacommonexistingLAN(whichhasa
non-CitectHMI/SCADAFileServer).

Display
Client
LAN

Display
Client

File
Server

Display Client
Server /
To
I/O Devices

EachruntimeCitectHMI/SCADAmachineisaDisplayClientoftheCitectHMI/SCADAsystem.You
candistributeDisplayClientsthroughoutyourplant,tocontrolandmonitorindividualregions(or
areas),andthroughoutyouroffices,toprovidehigh-levelinformationtotheappropriatepersonnelin
yourorganisation.Youcanconnectasmanyas256DisplayClientstoaCitectHMI/SCADAsystem.
EachCitectHMI/SCADADisplayClientPCconnectedtoanI/ODevicemustalsobesetupasa
CitectHMI/SCADAI/OServer.OneormoreCitectHMI/SCADADisplayClientscanalsobe
configuredtobeaCitectHMI/SCADAServer,usedtoprocessalarms,reports,ortrends.
CitectSCADANetworks 3

SettingupaNetwork
Toset-upaLocalAreaNetwork(LAN)forCitectHMI/SCADA,youmusthavesuccessfullyinstalled
all(non-CitectHMI/SCADA)networkhardwareandsoftwareinstrictaccordancewiththeinstructions
providedbythemanufacturerasappropriate,andyoushouldalsobequitefamiliarwiththebasic
operationofthenetwork.
YoumustinstalltheCitectHMI/SCADAsoftwareoneveryPCmachineyouwishtouseasa
CitectHMI/SCADAdesign-timedevelopmentmachine,runtimeCitectHMI/SCADADisplayClient,
CitectHMI/SCADAI/OServer,andCitectHMI/SCADAAlarm,Report,orTrendServer.
Youmustalsoset-upCitectHMI/SCADAforyournetwork,usingtheComputerSet-upWizardon
eachandeveryoneoftheafore-mentionedmachines.
ItispossibletoconfigureyourCitectHMI/SCADAsystemforusewithWideAreaNetworks(WANs).
Fordetails,seeConfiguringCitectHMI/SCADAtocommunicateoveraWAN.

TostarttheCitectComputerSetupWizard:
1. SelecttheCitectExplorer.
(orpressthisbutton)

2. Intheprojectlistarea,selectMyProjects-designatedbyacomputericon.
3. DoubleclicktheCompute SetupWizard
icon.
r
-or-
3. FromtheToolsmenuselectComputerSetup.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upCitectHMI/SCADAforyournetwork:
1. RuntheComputerSetupWizard.
2. SelectCustomSetup,andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'NetworkComputer'option.
4. Followthepromptsgivenbythewizard.Ifthecomputeristobeusedasaserver,selectthe
appropriateservertype(Alarms,Reports,Trends)whenthepageforthatservertypedisplays.
5. Onthe'Alarms,Reports,andTrendsServerSetup'page,enteranappropriatenameforthis
serveronthenetwork.Thisisthenamethatothermachinesonthenetworkwillbeconfiguredto
connectwith.
6. Onthe'NetworkSetup'page,entertheNetworkComputerNameforthismachine.
(TheNetworkcomputernamecanbeviewedinthe'NetworkProperties'taboftheWindows
SystemPropertiesdialog.Right-clicktheMyComputerIconandselectProperties.)
7. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upaCitectHMI/SCADADisplayClient:
1. RuntheComputerSetupWizard.
CitectSCADANetworks 4

2. SelectExpressSetup(youcanruninCustommodeifdesired),andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'DisplayClient'option.
4. Followtheprompts,continuetotheendofthewizard,andpresstheFinishbutton,tosavethe
settings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upanI/OServer:
1. RuntheComputerSetupWizard.
2. SelectExpressSetup(youcanruninCustommodeifdesired),andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'Server'option,andclickNext.
4. Onthe'I/OServerSetup'page,selectThiscomputerisanI/OServer.
5. SelectanappropriateI/OServer,andclickNext.
6. Followthepromptsgivenbythewizard.IfthecomputeristobeusedasanAlarm,Report,or
Trendserver,selecttheappropriateservertypewhenthepageforthatservertypedisplays.
7. Iftheserveristobeanetworkserver,the'Alarms,Reports,andTrendsServerSetup'pagewill
display.Enteranappropriatenameforthisserveronthenetwork.Thisisthenamethatother
machinesonthenetworkwillbeconfiguredtoconnectwith.
8. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upanAlarmsServer:
1. RuntheComputerSetupWizard.
2. SelectCustomSetup,andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'Server'option,andclickNext.
4. Followthepromptsgivenbythewizard.IfthecomputeristobeusedasanAlarm,Report,or
Trendserver,selecttheappropriateservertypewhenthepageforthatservertypedisplays.
5. Onthe'AlarmsSetup-Advanced'page,enterappropriatevaluestoconfigurethebehaviourof
theAlarmServer.ClickHelponthewizarddialogforoptiondetails.
6. Iftheserveristobeanetworkserver,the'Alarms,Reports,andTrendsServerSetup'pagewill
display.Enteranappropriatenameforthisserveronthenetwork.Thisisthenamethatother
machinesonthenetworkwillbeconfiguredtoconnectwith.
7. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upaTrendsServer:
1. RuntheComputerSetupWizard.
2. SelectCustomSetup,andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'Server'option,andclickNext.
4. Followthepromptsgivenbythewizard.IfthecomputeristobeusedasanAlarm,Report,or
CitectSCADANetworks 5

Trendserver,selecttheappropriateservertypewhenthepageforthatservertypedisplays.
5. Onthe'TrendsSetup-Advanced'page,clickHelponthewizarddialogforoptiondetails.
6. Iftheserveristobeanetworkserver,the'Alarms,Reports,andTrendsServerSetup'pagewill
display.Enteranappropriatenameforthisserveronthenetwork.Thisisthenamethatother
machinesonthenetworkwillbeconfiguredtoconnectwith.
7. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upaReportsServer:
1. RuntheComputerSetupWizard.
2. SelectCustomSetup,andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'Server'option,andclickNext.
4. Followthepromptsgivenbythewizard.IfthecomputeristobeusedasanAlarm,Report,or
Trendserver,selecttheappropriateservertypewhenthepageforthatservertypedisplays.
5. Onthe'ReportsSetup-Advanced'page,selectastartupreportifrequired.ClickHelponthe
wizarddialogforoptiondetails.
6. Iftheserveristobeanetworkserver,the'Alarms,Reports,andTrendsServerSetup'pagewill
display.Enteranappropriatenameforthisserveronthenetwork.Thisisthenamethatother
machinesonthenetworkwillbeconfiguredtoconnectwith.
7. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.

Toset-upaTimeServer:
NOTE: ATimeServercanONLYbeset-uponaCitectHMI/SCADAI/OServermachine.
1. RuntheComputerSetupWizard.
2. SelectCustomSetup,andclickNext.
3. Onthe'ComputerRoleSetup'page,selecttheappropriate'Server'option,andclickNext.
4. Onthe'I/OServerSetup'page,selectThiscomputerisanI/OServer.
5. SelectanappropriateI/OServer,andclickNext.
7. Followthepromptsgivenbythewizard.Onthe'TimeSetup'page,selectThiscomputeristhe
TimeServer,andclickNext.
8. ContinuetotheendofthewizardandpresstheFinishbutton,tosavethesettings.
NOTE: SeetheComputerSetupFlowDiagramformoredetailsonExpressandCustomSet-up
selections.
CitectSCADANetworks 6

UsingDistributedProcessing
Inverylargeapplicationswithlargeamountsofdata,youmightneedtodistributethedata
processingtoreducetheloadonindividualcomputers.
WithCitectHMI/SCADA,thefunctionoftheCitectHMI/SCADAServercanbedividedintofive
individualtasks.Thesetasksare:
CommunicatingwiththeI/ODevices(I/OServer)
Monitoringandprocessingalarms(AlarmsServer)
Processingreports(ReportsServer)
Accumulationandprocessingofhistoricaldatafortrending(TrendsServer)
Synchronisationofsystemtime(TimeServer)
Thesetaskscanbeperformedonasinglecomputer,orcanbedistributedbetweentwoormore
computers.

Display
Client
LAN

Display
Client

File
Server

Alarms Server
I/O Server
To
I/O Devices

Time Server Trends Server

Forverylargeapplications,youcanassignaseparatecomputerforeachtask.

Display
Client
LAN

Display
Client

File
Server

Alarms I/O Server

Time Server

Trends

Server Server Server

Display
Client

CitectSCADANetworks 7

ThisisachievedbyrunningtheCitectHMI/SCADAComputersetupWizardonthemachineyouwish
tobecometheparticularserver(I/O,Alarms,Reports,orTrends).
AnyCitectHMI/SCADAServermachinecanbeconfiguredtobehaveasaproxyserverbyapplying
appropriateCitect.INIparametersonthatmachine.Fordetails,seePROXIparametersettingsto
makethecomputeraproxyServerforI/Orequests.
AnyCitectHMI/SCADAServermachinecanbeconfiguredtobehaveasaFileTransfer(FTP)
ServerforInternetDisplayClientsifrequired.SeeINTERNETparametersettingstomakethe
computeranFTPserver.
AnyCitectHMI/SCADAServermachinecanbeconfiguredtouseTCP/IPoveraWideAreaNetwork
(WAN)ifrequired.SeeLANparametersettingstoallowtheuseofTCPIPovertheWAN.
Thelimitationsprovidedbysomenetworkconfigurationscanbeeasedbydistributingthe
processingloadacrossmultipleI/OServers.SeeSplittingtheProcessingLoadforMultipleI/O
Servers.

SplittingtheProcessingLoadforMultipleI/OServers
Youcanuseupto255I/OServersonasingleCitectHMI/SCADAsystem.Theconfigurationofthe
I/OServersdependsonhoweachI/OServerisconnectedtotheI/ODevices.Thefollowing
guidelineswillhelpyouachieveoptimumperformanceinasystemwithmultipleI/OServers.
Ifall(ormost)I/OServerssharethesamephysicallinktotheI/ODevices(e.g.aPLCnetwork)and
thePLCnetworkistheperformancebottleneck,onlyoneI/OServershouldcommunicatewiththe
I/ODevices(PLCnetwork).
However,withsomePLCnetworkstheinterfacecardintheI/OServeristhebottleneck.Inthis
situation,youshouldsharethecommunicationloadacrossallI/OServers.Youshouldalsoshare
thecommunicationloadacrossallI/OServerswheneachI/OServerhasitownphysicallinktothe
I/ODevice(forexample,individualseriallinks).
Notethattheconfigurationdependstotallyonthetypeofprotocolyouareusing.Becauseitiseasy
tochangehowtheI/OServersaresetup(youonlyneedtochangetheStartupModeintheI/O
Devicesform),youshouldexperimenttofindthebestperformanceforyourplant.
CitectSCADANetworks 8

UsingDistributedServers
Ifyourplantconsistsofanumberofdifferentsectionsorsystems,youcanconfigurea
correspondingnumberofclustersofCitectHMI/SCADAServers,andassigneachclustertoa
differentsection.AllsystemscanthenbemonitoredusingasingleDisplayClient-theGlobal
Client.

Display
Client

Display
Client

Primary Server /
Display Client

Standby Server /
Display Client
LAN

Display
Client

Display
Client

Primary Server /
Display Client

Standby Server /
Display Client

Client
Global
Cluster for Section 1 Cluster for Section 2
WAN
Bridge
Bridge
Bridge
Bridge

Eachclusterrunsitsownuniqueproject.Ithasuniquealarms,trends,reports,anddisplaypages.
TheGlobalClientcandisplayinformationfromanyoftheclusterprojects.Forexample,atthe
GlobalClient,youcoulddisplaytheTrendpagefromPlant1,thenswitchtotheTrendpagefrom
Plant2.
Ideally,aglobalsystemshouldconsistofnomorethaneightclusters.
NOTE: DistributedServersshouldNOTbeusedtosplitupasinglesiteintodiscreteareas.A
singleclustersystemwithdistributedprocessingwouldbebettersuitedtothissituation,as
itwouldnotbehamperedbythemaintenanceoverheadofadistributedserversystem
(suchasextraprojectcompilationsetc.).
SwitchingBetweenClusters
FromtheGlobalClient,youcandisplayinformationfromanyoftheclustersinyoursystem.Todo
so,youmustfirstattachtotherelevantclusterserver(AlarmsServer,ReportsServeretc.),using
theClusterSetName()function.Onceattached,youcandisplayanyinformation(suchasTrend
Tags,Alarmpagesetc.)fromthecluster'sproject.
CitectSCADANetworks 9

ConfiguringProjectsforDistributedServers
InorderfortheGlobalClienttofunctioncorrectly,somecaremustbetakenwhenthevarious
projectsareconfigured.Atypicalsystemwouldconsistof:
aGlobalIncludeProject
aClusterProjectforeachcluster
aGlobalDisplayProject
TheGlobalIncludeProject
TheGlobalIncludeProjectexistspurelytobeincludedineachoftheClusterProjects.Itwould
containCicodefunctions,fonts,devices,users,groups,andglobalkeyboardcommands.
ClusterProjects
AllClusterProjectsmustbeincludedintheGlobalDisplayProject.EachClusterProjectwould
containthefollowinginformationforitscluster:
Tags Reports
I/OServers AlarmsandAlarmCategories
I/ODevices GeniesandSuperGenies
Templates Pages
Trends Symbols
BecauseallClusterProjectsareincludedintheGlobalDisplayProject,Tagnames,I/ODevice
namesetc.mustbeuniqueforeachcluster.Forexample,youcannothaveanI/Odevicenamed
IODev_1ineachClusterProject.
TheClusterProjectswilleachbecompiledandrunfromaDisplayClientintherelevantcluster.So
ClusterProjectAwillberunfromaDisplayClientinClusterA,andsoon.
TheGlobalDisplayProject
TheGlobalDisplayProjectwouldbecompiledandrunfromtheGlobalClient.Itwouldcontaina
singlestartuppage,andwouldincludeeachoftheClusterProjects.Thestartuppagecouldcontain
anumberofbuttonsforswitchingtovariouspagesfromeachoftheclusters(usingthe
ClusterSetName()function).

ConfiguringCitectHMI/SCADAtocommunicateoveraWAN
AproxyI/OServerisusedfortheoptimisationofCitectnetworktrafficforI/Orequests.Itis
thereforeparticularlysuitedforusewithwidelydistributedIOServersoveraWideAreaNetwork.
CitectProxyServersareoftenusedwithWANsandcanalsobeusedasFileTransfer(FTP)
ServersforInternetDisplayClientsifrequired.
ThereareseveralCitect.INIparametersthatworktogethertoachievethe3typesofconfigurationas
describedbelow.
1-LANparametersettingstoallowtheuseofTCPIPovertheWAN
2-PROXIparametersettingstomakethecomputeraproxyServerforI/Orequests
3-INTERNETparametersettingstomakethecomputeranFTPserver
LANparametersettingstoallowtheuseofTCPIPoveraWAN
Atypicalarrangementofparametersandsettingsisshownbelow.Thecriticalsettingis'Tcpip=1'to
enabletheuseofWindowsSocketsbyCitect.TheReadpoolandSessionsparametershavebeen
increasedinthisexampletocaterforalargenetworkwithmanyI/OServersconnectingtotheProxi
Server.TCPIPdoesnothavethemaximumsessionslimitthatNETBIOShas(maximumof255
sessions),andsopermitsmoreCitectcommunicationsessionsthanNETBIOSallows.
[LAN]
CitectSCADANetworks 10

Node=TEST_PC
Disable=0
LanA=-1
Netbios=1
Tcpip=1
Readpool=8096
Sessions=1024
Youwillneedtoputthe'Tcpip=1'settingintothe[LAN]sectionoftheCitect.inifileforalloftheI/O
serversaswell.
TheDNSsectionmustdefinetheIPaddressfortheCitectserverandalltheI/OServersinthe
project(s).Thisismostimportantforredundancy.
[DNS]
Primary=192.168.10.33 (TheCitectPrimaryR.A.T.server)
Secondary= (anyStandbyR.A.T.server)
IOServerA=192.168.10.11 (identifyeverysingleI/Oserverhere)
IOServerN=192.168.10.99

PROXIparametersettingstomakethecomputeraProxyserverforI/Orequests
ACitectHMI/SCADAmachinecanbesettoperformasaproxyI/OServerthroughtheuseofthe
PROXIparametersettingsoftheprojectCitect.INIfileontheproxyservermachine.Forexample:
[PROXI]
IOServerA=MyProxy (anynameyouwanttogivetheproxyserver)
IOServerN=MyProxy
ORifasingleproxyI/Oserveristobeused,thefollowingsettingcanbeused,however,theabove
makesalotmoresensetootherpeoplemaintainingthesystem.
[PROXI]
ALL=MyProxy
Theothersettingsrequiredareasfollows:
[IOSERVER]
Server=1
Name=MyProxy
Where"MyProxy"isanyProxyI/Oservernameyouwanttogiveit.Thismachinewillactuallyrun
upasanI/OServer,andgetitsactualI/OdatafromthelistofI/OServers.

InternetparametersettingstomakethecomputeranFTPserver
Typicalsettingstodothisareshowninthefollowingexample:
[INTERNET]
Server=1
display=patrick (anytextpasswordforadisplaylicence)
manager=jimmeh (anytextpasswordforamanagerlicence)
RunFTP=1
ZipFiles=0
LogFile=D:\
NOTE: Donotmakethemanageranddisplaypasswordsthesame.
CitectSCADANetworks 11

TousethisconfigurationwithalargenetworkcontainingmanyI/OServersandnetworkClients,
someofthedefaultresourcesettingsofCitectmayneedtobeincreased.Inparticular,the
networkingresourcesmayneedtobeincreasede.g.[LAN]Readpooland[LAN]Sessions
parameters.The[KERNEL]Queueparametermayalsoneedtobeincreased.
CitectSCADANetworks 12

BuildingRedundancyIntoYourSystem
Whilereliabilityisakeyfeatureofmostcurrentcomputerhardware,breakdownscanstilloccur.If
some(orall)oftheprocessesinyourplantarecritical,orifthepotentialdowntimethroughfailure
couldbeexcessive,youshoulddesignalevelofredundancyintoyourCitectHMI/SCADAsystem.A
systemwithin-builtredundancyminimisesinterruptionsduetoequipmentfailure.Youcanchoose
alevelofredundancytosuittheapplication.
RedundancyisdesignedintoCitectHMI/SCADAandcanbeimplementedwithoutchangingthe
projectconfiguration.(CitectHMI/SCADAwasdesignedfortotalredundancysupport.Almost
everythinginCitectHMI/SCADAcanbemaderedundant:systemdisplay,alarms,trends,reports,
I/OServers,externalI/ODevices,DiskI/ODevices,Networkcables,NetworkFileServers,FTP
Servers,etc.)
TheCitectHMI/SCADAComputerSetupWizardallowsyoutosetupredundancywhenyoudefine
thefunctionofeachcomputeronthenetwork.

I/OServerRedundancy
SystemswithasingleI/OServerhaveasinglepointoffailure.IftheServerfails,controland
monitoringofthesystemislost.ThesinglepointoffailurecanbeeliminatedwitharedundantI/O
ServerthatisconnectedtothesameI/ODevices.TheseCitectHMI/SCADAServersarecalledthe
primaryandStandbyServers.

Display
Client
LAN

Display
Client

File
Server

Primary Server /
DisplayClient

Standby Server /
Display Client

Whenthesystemisinoperation,CitectHMI/SCADAmaintainsbothserversidentically.Ifthe
primaryserverfails,thestandbyserverassumestotalcontrolwithoutanyinterruptiontothesystem.
Whentheprimaryserverisreturnedtoservice,CitectHMI/SCADAautomaticallyreturnscontrolto
theprimaryserver.CitectHMI/SCADAalsoensuresthatnodataislost.
I/OServerredundancystabilisesthesystembyremovingthesinglepointoffailure(the
CitectHMI/SCADAI/OServer).However,intheeventoffailurebytheLAN,controlandmonitoring
bytheDisplayClientsislost(althoughcontrolandmonitoringbytheserversismaintained).
NOTE: Whenthesystemisrunning,youcanuseredundantI/OServerstosplittheprocessing
load.RedundantI/OServersresultinhigherperformance,becauseallI/OServerscanbe
runninginparallelwhenservicingtheI/ODevices.

CitectSCADANetworks 13

RedundancyandPersistence
IfyouareusingServerredundancy,PersistenceCacheskeepStandbyServersupdatedwiththe
mostrecentlyreaddevicedata.APersistenceCacheiscreatedforeachcachedI/ODevice.
Considerthefollowingsetup:

Standby
Data Path
IODev_2
IOServer1
Primary
Data Path
LAN

IOServer2
Modem Modem
PSTN
Modem
IODev_1
Modem

Every[IOServer]SavePeriod,IOServer1savesitsin-memorycachetodisk.Thecacheissavedin
PersistenceCaches,oneforeachcacheddevice.IOServer1broadcaststoallotherI/OServersthe
UNCpathofthePersistenceCaches(setwith[IOServer]SaveNetwork).FromthesePersistence
Caches,IOServer2updatesitsin-memorycacheforitsI/ODevices.
NOTE: YoucandefineanI/ODeviceonanI/OServerusingtheExpressCommunications
Wizard,orbyaddingadeviceintheI/ODevicesforminCitect'sProjectEditor.
YouarenotlimitedtojustoneStandbyServer,sincetheUNCpathnamesetin
[IOServer]SaveNetworkisbroadcasttoallI/OServers.EachI/OServerupdatesitscachefromthe
PersistenceCachesonlyfortheI/ODevicesdefinedonthatserver.Youcan,therefore,setupa
numberofI/OServerstoupdatetheirin-memorycacheswiththemostrecentlyreaddata.
Forthisexample,the[IOServer]SaveFileand[IOServer]SaveNetworkparameterswouldneedtobe
setasfollows:
OnIOServer1 OnIOServer2
[IOServer] [IOServer]
SaveFile=C:\Data\IOServer1.dat SaveFile=C:\Data\IOServer2.dat
SaveNetwork=\\IOServer1\Data\IOServer1.dat SaveNetwork=\\IOServer2\Data\IOServer2.dat

IOServer1wouldbroadcastthepath'\\IOServer1\Data\IOServer1.dat'totheotherI/OServers.
IOServer2wouldthenusethePersistenceCachestoupdateitsin-memorycachewiththedevice
datamostrecentlyreadbyIOServer1.
CitectSCADANetworks 14

DataPathRedundancy
WithmostbrandsofPLCs,youcaninstallaparalleldatapathfromtheI/OServertotheI/ODevice.
Aparalleldatapathensuresthatifonedatapathfails,yoursystemcancontinuewithout
interruption.

Standby
Data Path
I/O Device
I/O Server
Primary
Data Path
I/O Device
I/O Server

Whenyoustartyourruntimesystem,CitectHMI/SCADAconnectstotheI/ODeviceusingthe
primarydatapath.IfcommunicationwiththeI/ODevicefailsatanytime(e.g.ifthecommunications
cableiscut),CitectHMI/SCADAswitchestothestandbydatapath.CitectHMI/SCADAreconnects
throughtheprimarydatapathwhenitisreturnedtoservice.
Youcanalsousedatapathredundancyonanetwork,asinthefollowingdiagram:

Standby
Data Path
Primary
Data Path
LAN

I/O Server
Standby Primary

Inthisexample,I/ODevicecommunicationismaintainedifeitheroneoftheI/OServersorits
communicationscablefails.
IfyourI/ODevicessupportpeer-to-peercommunication,youcanprovidetotalredundancytoyour
systembyduplicatingI/ODevices-asinthefollowingdiagram:
CitectSCADANetworks 15

Standby
Data Path
I/O Device
I/O Server
Primary
Data Path
LAN

I/O Server
Standby Primary
I/O Device
Primary Standby

OneoftheseI/ODevicesisthePrimaryI/ODevice,andtheotheristheStandbyI/ODevice.(You
canalsohavemorethanoneStandbyI/ODevice.) WhenbothI/ODevicesarerunning,
CitectHMI/SCADAprocessestheI/OonthePrimaryI/ODevice.ThisreducestheI/Oloadonthe
I/ODevice(andPLCnetwork),whichiscriticalforthebestperformance.Youdonothaveto
synchronisedatabetweenthePrimaryandStandbyI/ODevices.
NOTE: AlthoughI/OServersareallthesameand,therefore,donotadoptaPrimaryorStandby
role,theyaregenerallylabelled"Primary"and"Standby".Soa"Primary"I/OServeristhe
I/OServerwiththePrimaryI/ODevicesconnectedanda"Standby"I/OServeristheone
withtheStandbyI/ODevicesconnected.OneI/OServercanconnecttoamixtureof
PrimaryandStandbyI/ODevices.
TheI/OServercansupportanynumberofStandbyDataPaths.
WARNING: Tousethisarrangement,theI/ODevicesmustsupporthot-standbyredundancy.
WhileCitectHMI/SCADAcansendwriterequeststoboththeprimaryandstandbyI/O
Devices(withtheStartupmodeStandbyWriteoption),CitectHMI/SCADAcannot
synchronisetheI/ODevicesorplant-floorequipment.
CitectHMI/SCADAclientscommunicatewithallconfiguredI/OServersatthesametime.(On
startup,theclientstrytoconnecttoallconfiguredI/OServers.IftheycannotfindanI/OServer,a
hardwareerrorisgenerated.)TheCitectHMI/SCADAclientroutestheparticularI/Orequesttothe
activeI/ODevice.Forexample,ifyouhavethreeI/OServersconfiguredasfollows:
I/O Server I/O Devices connected
IOServer1 I/ODevice1(Primary)
I/ODevice2(Standby)
I/ODevice3(Primary)
IOServer2 I/ODevice1(Standby)
I/ODevice2(Primary)
IOServer3 I/ODevice1(Standby)
I/ODevice2(Standby)
I/ODevice3(Standby)
IfallI/ODevicesarecommunicatingcorrectly,aCitectHMI/SCADAclientcreatesnetworksessions
toallthreeI/OServers.TheclientthensendsrequestsforI/ODevice1andI/ODevice3to
IOServer1,andrequestsforI/ODevice2toIOServer2.IfI/ODevice1failsonIOServer1,theclient
sendsrequestsforthisI/ODevicetoIOServer2,whileitstillsendsrequestsforI/ODevice3to
IOServer1.IfI/ODevice1alsofailsonIOServer2,theclientsendsrequeststoIOServer3.When
CitectSCADANetworks 16

I/ODevice1onIOServer1comesbackonline,theclientsbeginsendingtheirrequeststo
IOServer1.
BecauseyoucanplacePrimaryandStandbyI/ODevicesonvariousI/OServers,youshouldshare
thePrimaryI/ODevicesbetweenyourI/OServerstobalancetheloadingacrossalltheI/OServers.
(Thismightnotapplyforallprotocols,becausetheloadingcouldbedependentonthePLCnetwork,
nottheI/OServerCPU.Inthiscase,morethanoneactiveI/OServeronthesamePLCNetwork
candegradethePLCnetworkandthereforeslowthetotalresponse.)

Alarms,Reports,andTrendsServerRedundancy
Onlargesystemswithmultipleservers,youcanparalleltheAlarms,Reports,andTrendsServers.
Toachievethislevelofredundancy,youconfigurethreeothercomputers(orDisplayClients)as
standbyservers.Thenifaprimaryserverfails,itsoperationisimmediatelytransferredtoits
standbyserver.

Display
Client
LAN 1

Display
Client

File
Server 1
LAN 2
File
Server 2

Primary
I/O Server

Standby
I/O Server
Standby

Reports
Servers
Primary
Standby
Trends
Servers

Primary

Standby
Alarms
Servers

Primary

Whenthesystemisinoperation,CitectHMI/SCADAmirrorstheprimaryandstandbyservers.Ifthe
primaryReports,Alarms,orTrendServerfails,allclientsaccesstheappropriatestandbyserverfor
data.Whentheprimaryserverrestarts,theclientsstayonthestandbyserverunlessthestandby
serverfails,ortheclientisshutdownandrestarted.(BecauseCitectHMI/SCADAmaintainsidentical
dataonbothservers,itisnotimportantwhetheraclientreceivesdatafromtheprimaryorstandby
server,anditisquitenormalforsomeclientstobecommunicatingwiththeprimaryandsomewith
thestandbyserver.Thisalsosavestheextraoverheadofcheckingifaprimaryserverhascome
backonline.)

HowCitectHMI/SCADAHandlesAlarmsServerRedundancy
YoucanconfiguretwoAlarmsServersinaCitectHMI/SCADAproject-aPrimaryAlarmsServer
andaStandbyAlarmsServer.WithtwoAlarmsServers,youhavefull(mirrored)redundancyon
yourCitectHMI/SCADAsystem.
WhenbothAlarmsServersarerunning,alarmsareprocessedonbothserversinparallel,andare
loggedbythePrimaryAlarmsServer.IfthePrimaryAlarmsServerfails,theStandbyAlarmsServer
startstologalarmstodevices.
WhenanAlarmsServerstartsup,ittriestoconnecttotheotherAlarmsServer.Ifitcanconnect,it
transfersthedynamicalarmdatafromtherunningAlarmsServer.(Thisdataincludessummary
dataandthecurrentalarmstates.)IfanotherAlarmsServercannotbefound,theAlarmsServer
opensthesavefile(definedwiththe[Alarm]SavePrimaryparameter)andrestoresthedatafromthe
CitectSCADANetworks 17

file.Iftwosavefilesexist,onefromthePrimaryServerandonefromtheStandbyServer,
CitectHMI/SCADAusesthesavefilewiththelaterdate.Ifnosavefileisconfigured,theAlarms
Servercannotgettheinitialstateofthealarms,andnosummaryinformationisavailable.Inthis
case,theAlarmsServerstartsprocessingthealarms,andthenacknowledgesallthenewalarms.
WhilebothAlarmsServersareactive,theybothreaddatafromtheI/OServerandprocessthe
alarms.Theon/offstatusofeachalarmisnotpassedbetweenthetwoservers.Whenoperators
performfunctionsonalarms(forexample,acknowledge,disable,enable,addcomments,etc.),this
informationispassedbetweenthetwoAlarmsServers.(Ifanoperatoracknowledgesanalarmon
oneserver,thatservertellstheotherservertoacknowledgethesamealarm.)
CitectHMI/SCADAclientsconnecttoeitherthePrimaryAlarmsServerorStandbyAlarmsServer.
Onstartup,allclientstrytoconnecttothePrimaryAlarmsServer.IfthePrimaryAlarmsServeris
notrunning,theytrytoconnecttotheStandbyAlarmsServer.IfthePrimaryAlarmsServercomes
backonline,anyclientsconnectedtotheStandbyAlarmsServerremainconnectedtotheStandby
Server.(ItdoesnotmatterwhichAlarmsServertheclientstalkto,becausetheybothcontainthe
same(mirrored)data.)

HowCitectHMI/SCADAHandlesReportsServerRedundancy
YoucanconfiguretwoReportsServersinaCitectHMI/SCADAproject-aPrimaryReportsServer
andaStandbyReportsServer.WhenbothReportsServersarerunning,thescheduledreportsonly
runonthePrimaryReportsServer.IfthePrimaryReportsServerfails,thescheduledreportsrun
ontheStandbyReportsServer.(YoucanalsoconfiguretheStandbyReportsServersothatisalso
runsthescheduledreports-inparallelwiththePrimaryReportsServer.)Noreportdatais
transferredbetweenthePrimaryandStandbyServers.(CitectHMI/SCADAdoesnotsynchronise
thereportdatabecausereportscanwritetheirdatatoanytypeofdevice.)
CitectHMI/SCADAclientseitherconnecttothePrimaryReportsServerortheStandbyReports
Server.Onstartup,allclientstrytoconnecttothePrimaryReportsServer.IfthePrimaryReports
Serverisnotrunning,theytrytoconnecttotheStandbyReportsServer.IfthePrimaryReports
Servercomesbackonline,anyclientsconnectedtotheStandbyReportsServerremainconnected
totheStandbyserver.

HowCitectHMI/SCADAHandlesTrendsServerRedundancy
YoucanconfiguretwoTrendsServersinaCitectHMI/SCADAproject-aPrimaryTrendsServerand
aStandbyTrendsServer.WhenbothTrendsServersarerunning,trendsareprocessedonboth
serversinparallel,andwrittentodisk.(Eachservermustwritetoitsowndiskoritsownprivate
areaonthefileserver.)
WhenaTrendsServerstartsup,ittriestoconnecttotheotherTrendsServer.Ifitcanconnect,it
transfersallthetrenddatafromthelasttimeitwasshutdownuntilthecurrenttime.(Thisensures
thatnotrenddataislost.)
CitectHMI/SCADAclientseitherconnecttothePrimaryTrendsServerortheStandbyTrends
Server.Onstartup,allclientstrytoconnecttothePrimaryTrendsServer.IfthePrimaryTrends
Serverisnotrunning,theytrytoconnecttotheStandbyTrendsServer.IfthePrimaryTrends
Servercomesbackonline,anyclientsconnectedtotheStandbyTrendsServerremainconnected
totheStandbyTrendsServer.(ItdoesnotmatterwhichTrendsServertheclientstalkto,because
theybothcontainthesame(mirrored)data.)

HowCitectHMI/SCADAHandlesFileServerRedundancy
CitectHMI/SCADAallowsforredundancyofthefileserver.The[CtEdit]Backupparameterspecifies
CitectSCADANetworks 18

abackupprojectpath.IfCitectHMI/SCADAcannotfindafileintheRundirectory(i.e.asspecified
bythe[CtEdit]Runparameter),itwilllookinthebackuppath.Ifthefileisfoundinthebackuppath,
CitectHMI/SCADAwillassumethattherunpathhasfailed(i.e.thefileserverhasfailed).
CitectHMI/SCADAwillthenlookforallrelevantfilesinthebackupbeforechangingover.When
CitectHMI/SCADAchangesovertothebackuppath,itwillcalleventnumber11andgeneratethe
hardwareerrorFileserverfailed,toStandby.
Fileserverredundancywillonlyoperatecorrectlyiftheredirector(orshell)onthecomputercan
handleafailureofthefileserver.TheshellwithNovellNetwarecannotdothisandwillcause
WindowstofailwithfatalNetworkerrors-whenthefileserverfails.MicrosoftLANmanagerbased
networksandpeertopeernetworkswillallowforfileserverfailurecorrectly.Therefore,
CitectHMI/SCADAfileserverredundancywilloperatecorrectlywiththesenetworks.
NOTE: OnlyCitectHMI/SCADAswitchestoabackuppath.Anyotherapplicationsthatareusing
filesonthefileserverwillfailwhenthefilerserverfails.Thismaycausethecomputerto
waitforlongperiodsforthefilerserver(ortocrash).ThisincludesWindowsitself,soyou
shouldinstallWindowsonalocaldrive.
Toenablefileserverredundancy,setthe[CTEDIT]Backupparametertoabackupdatabasepath.
Forexample,ifyourprimarypathisF:\CITECT\USER\DB,setthebackuppathtoanotherfileserver
oralocaldrive,suchasC:\CITECT\USER\DB.
YoushouldalwaysmakesurethattheprojectintheBackuppathisthesameastheoneintheRun
directory-eachtimeyoucompiletheprojectintherundirectoryyoushouldcopyitintothebackup
directory.

HowCitectHMI/SCADAHandlesFTPServerRedundancy
CitectHMI/SCADAsupportsFTPServerredundancy.IfthePrimaryFTPServergoesdown,
CitectHMI/SCADAwillattempttoconnecttotheFTPServerontheStandbymachine.Thisoccurs
independentlyofI/OServerRedundancy,sothetwoFTPServersmusthavethesamepasswords
andthesamedirectorystructure.
FTPServerRedundancyisconfiguredbysettingparametersinthe[CLIENT]and[DNS]sectionsof
thePrimaryFTPServer'sCitect.inifile.TheseparametersaredownloadedbytheInternetDisplay
Client(IDC)toitsownCitect.inifileifthePrimaryFTPServerfails,providedthe
[INTERNET]Redundancyparameterhasnotbeensetto0(zero).TheIDCthenusesthe
downloadedredundancyinformationtoconnecttotheStandbyFTPServer.
NOTE: StandbyFTPServersneednotbeInternetServers.TheStandbyFTPServercanbeany
serverusingTCP/IPthattheIDCcanconnectto,providedthereareIDClicencespresent
inthenetwork.

LANRedundancy
AsecondLocalAreaNetwork(LAN)andfileserverwouldensuresystemstabilityevenintheevent
ofnetworkfailure.
CitectSCADANetworks 19

Display
Client
LAN 1

Display
Client

File
Server 1
LAN 2
File
Server 2

Primary Server /
Display Client

Standby Server /
Display Client

Intheaboveillustration,halfofthecomputersremainoperableifoneoftheLANsoraserverfails.
Withtwonetworkcardsineachcomputer,fulloperationofallcomputerscanbemaintainedinthe
eventofafailureofoneoftheLANs(oraserver).

Display
Client
LAN 1

Display
Client

File
Server 1
LAN 2
File
Server 2

Primary Server /
Display Client

Standby Server /
Display Client

CitectSCADANetworks 20

NetBIOSErrors

1024 NoNetBIOSerror
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1025 Invalidbufferlength
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1027 Invalidcommand
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1029 Commandtimedout
CitectHMI/SCADAistimingoutwhensendingdataonthenetwork.Ifthiserroroccursfrequently,
increasethetimeoutperiodinthe[LAN]SendTimeoutparameter.Thiserrorislikelytooccurifyou
arerunningCitectHMI/SCADAonaslownetworkoraWideAreaNetwork.

1030 Incompletereceivemessage
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1032 Invalidsessionnumber
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1033 Noresourceavailable
Increasenetworkresourcesormemory.IncreasetheWindowsparameterNetHeapSizeinthe
SYSTEM.INIfile(orothernetworkparameters).SeeSettingUpaNetwork.

1034 Sessionhasbeenclosed
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1035 Commandcancelled
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1037 Duplicatenameinlocaltable
Thiserrorshouldnotoccurinnormaloperation.ContactCitectSupport.

1038 NetBIOSnametablefull
IncreasethenumberofnamesinthelocalnametablesetupinthenetworkNetBIOSconfiguration.
SeeSettingUpaNetwork.

1041 NetBIOSsessiontablefull
CitectHMI/SCADAhasrunoutofNetBIOSsessions.IncreasethenumberofNetBIOSsessionsin
thenetworksetup.SeeSettingUpaNetwork.

1044 Servernamenotfound
CitectSCADANetworks 21

Thespecifiedservercannotbefoundonthenetwork.Eithertheserverhasnotstartedoranetwork
problemispreventingcommunication.

1046 Nameinuseonremoteadaptor
TwoCitectHMI/SCADAserversonthenetworkaretryingtousethesamename.Configureeach
CitectHMI/SCADAserverwithauniquename.

1049 Nameconflict
TwoCitectHMI/SCADAserversonthenetworkaretryingtousethesamename.Configureeach
CitectHMI/SCADAserverwithauniquename.

1058 Toomanycommandsoutstanding
CitectHMI/SCADAhasrunoutofNetBIOScontrolblocks(NCBs).IncreasethenumberofNCBsin
thenetworkNetBIOSconfigurationorreduceCitectHMI/SCADA'suseofNCBsintheCITECT.INI
file.SeeSettingUpaNetwork.
CitectSCADANetworks 22

CiNet
CiNetisnolongersupported.CiNetwasdesignedasalowspeedWideAreaNetwork(forremote
monitoringapplications).Ifyouhaveawidely-distributedapplicationwhereCitectHMI/SCADA
computersareseparatedbyvastdistances,usingaLANtoconnectyourDisplayClientscanbe
expensive.ToconnectDisplayClientsinthisinstance,youshoulduseMicrosoft'sRemoteAccess
Server(RAS)oraMicrosoftapprovedsolution-suchasShivaLanRover.

CitectSCADANetworks 23