Home

Driver User manual Document

1. Q What is this enable Device Name PLC Type Description e A o6 jo7 57300 Backup channel is only 09 m Primary Device Connection Address applicable to ISO protocol see danc J Enable Q What is this enable A enables backup address Q What is the Backup device connection A see the section on redundancy N Add Delete Q What are the meaning of these symbols E voe As see the io sani cil is Good Q What is exception type A not used with citect Q What is Access time A When Citect stops accessing the data the block goes offscan after this time Q When the driver is active more and more messages appear Are these messages errors or is it just a message about writing to the DBs What does 0 en 1 mean A These messages indicate write actions Generally an important indication of what the SCADA is doing Itis our experience that many SCADA developers are unaware how often their systems write which affects performance We recommend you write your Cicode scripts to first read the variable then only write new value if new value is different The 1 means this data is written along with 0 in one packet 0 I 1 writing 57 06 DB222 B78 len 8 offset 0 vy 4 gt TX 20611 RX 25139 Polls Sec 95 Scotts International NL 12 05 PM NUM Q The latest version 7 9 54 has P
2. Default Allowable values Set to the same as the Device name in the Driver Configurator Unless a N xx is supplied in which case the xx is used instead Must be blank or unique used by citect for redundancy See above Specifies addressing amp back end driver PSDIRECT lt n gt See table above Refers to the port previously defined in ports form This field is user defined and is not used by the driver FALSE Not used no cacheing300 but set cache to FALSE 8 6 Reference Data types Note This driver is designed to mimic other CitectSCADA drivers amp should supply all the same addresses amp data types as the equivalent CitectSCADA driver does Note the PSDIRECT6 32bit blocking protocol does not support STRINGS amp Arrays 8 6 1 Reference Tag Addressing This driver supports many different Addressing formats depending on the device in use 8 6 1 1 Siemens S7 Addressing The S7 addressing is designed to be compatible with that used by the Standard Citect S7NT Driver Address Format DB lt no gt lt index gt lt bitno gt Dl lt no gt lt index gt lt bitno gt A lt index gt lt bitno gt Q lt index gt lt bitno gt E lt index gt lt bitno gt l lt index gt lt bitno gt M lt index gt lt bitno gt PA lt index gt lt bitno gt PQ lt index gt lt bitno gt PE lt index gt lt bitno gt Pl lt index gt lt bitno gt T lt index gt 10ms T lt index gt 100ms T lt in
3. VOS CPLALATE MT Condiguestue P fhe peie Debug Pot thp Local Ethemet Address Peer Services Be0006010003 PLCI READ s PLCI WRITE Time Informations l Enable PLC Time Update TF Services TF Yariables They look like this eE Transpost Connection Name PLCT_HEAD ine TRESS Transport Profle TPHOFOS0S SPS l Local TSAP Length fe HEX 5245 41 4452 45 At 44 ASCH READREAD EJ G State ne G lea T banere Renate ee FTTH TSAP Lengi F Hoe 5543504350435043 accu PCPCPCRC Soe GED See e Local TSAP must be exactly 8 chars e Local TSAP is the link to the backend configuration see below e Remote Ethernet address should be 0000 accepts any incoming connection e This should be a read Passive job e The Write job should be a Write passive e All jobs remote TSAP must be PCPCPCPC Copyright www proscada com PSDIRECT driver for CitectSCADA a a Transport Connection Name PLOIWRITE Type Treesport Profle TPROF 0505 SPS f Local TSAP Length 8 HEX 57 52 4954 57 52 4954 ASC WRITWRIT 5jabe Remote Etheinet Addiess 000000000000 TSAP Langth HEX 50 4350 4950 495043 ASC PEPEPEPE dob oK Cancel 19 1 2 Configuring Redundant SCADA servers To allow multiple SCADA s to access the PLC you need to configure a pair of the above jobs per SCADA IO server In this case it is recommended
4. comms fail unit offline PROSCADA_ADDRESS_ERROR 0x10B Address does not exist on backend PROSCADA_UNDEFINED_PROTOCOL 0x10C e The Unit address settings were not recognised PROSCADA_HEARTBEAT_FAILED 0x10D PLC is in Stop mode OR heartbeat monitoring is enabled but the variable is not changing PROSCADA_BACKEND_NOT_RUNNING Ox10E The backend driver SIXSPOLL EXE has stopped running 8 9 Parameters options and settings 8 9 1 Standard Parameters Parameter Default Allowable values Block bits 2048 8 2048 PSDIRECT6 32 Delay mS 30000 1000 60000 MaxPending 8 Not critical with this driver it replies instantly Polltime mS 1000 Not critical but do not change used for unit status Timeout mS Not used Retry Not used WatchTime Sec 10 rate at which offline IO devices are checked 8 9 2 Driver Specific Parameters Parameter Default Allowable values AlwaysReturnNoError 0 0 Should be selected for Backup failover amp displaying COM on screen It is useful to set this to 1 when testing with no PLC then you can use the learn address feature even if you have no PLC ValuelfCommsErr 0 Value to display on screen if Communications to PLC fail set to something like 888 to make it obvious Copyright www proscada com PSDIRECT driver for CitectSCADA HeartBeatAddress_ lt devname gt No Hb The S7 driver continues polling normally when the PLC is in Stop mode resulting in frozen valu
5. driver For further information this should be read in conjunction with http proscada com DOC Interoperability Definition for IEC 870 5 101 amp 104 Protocol pdf 21 5 Note on installation e Install the PSDIRECT front end and the IEC 870 backend e Ensure there is a copy of the file I87STSR DLL in the Citect Bin directory 21 6 CiTect configuration 21 6 1 Boards Form None 21 6 2 Ports Channels Form Same as other PSDIRECT profiles just create one port with port number 0 21 6 3 IO Devices Units Form All IO Devices can link the one port The name links to the backend RTU name The Protocol is PSDIRECT5 The address is the IEC Common asdu address of all the tags on this IO Device 0 65536 21 6 4 CITECT INI Settings To configure Time Stamped Alarms you need to set the following option because the Timer Expr Value for this driver is a 24h Millisecond counter Alarm HresType 7 Alarm HighResOff 1 Usually set to rising amp falling edge Alarm Hres24HrDeadBand 3600 set to 1 hour 21 7 Input tag values Copyright www proscada com PSDIRECT driver for CitectSCADA Note for DPI amp SPI the driver data represents a 16 bit INT this can be accessed either by bits 0 15 in DIGITAL tags or as an analogue with INT tags Same memory The bits are accessed by string names as follows note the separator SPI amp DPI VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7
6. wi ui gt j System and d Web server Time of day v User interfa z Connection f Overview of v lt h m gt NI wi gt oo ae Cancel l e UN TICK the property optimized block access attribute on the DB s you want to read in SCADA Data block 1 DBT 4 General General r Attributes Information Time stamps Compilation _ Onlystore in load memory Asescimioh B Data block write protected in the device Attributes Tloptimized block On the driver side e Set TSAP to R 0 S 1 Copyright www proscada com PSDIRECT driver for CitectSCADA 17 Configuring for Redundancy 17 1 Standard CiTect redundancy This driver is designed to emulate the traditional S7NT driver and it also emulates the error amp UNIT status modes of the S7NT driver This means that CiTect lO device level redundancy failovers work in the traditional CiTect way Normally this is simply twin CiTect IO servers with the same IO devices configured on both using the same IO device number The backend configurations are identical Normally for load sharing the PLC s are divided in two groups one group primary on server A amp Standby on Server B Primary amp standby devices vice versa on IO server B 17 1 1 Notes e The Backend status of the pollblocks is kd meaning CiTect is not currently using the data the backend is actually polling the data every 60 seconds e Differ
7. Local MPI Addr fi Retries 2 Multi Master Copyright www proscada com PSDIRECT driver for CitectSCADA 5 Quick start Simple CitectSCADA configuration Follow the following steps to configure a CitectSCADA application to the sample above there is an example CitectSCADA project installed with the PSDIRECT Front end driver in C Program Files Citect CitectSCADA PSDIRECT Sample Read more about it in The Appendices at the end of this document The following is a simple Fresh setup m Create a new CitectSCADA Project m DO NOT create a Boards object 7 Add a Port amp Call it PS PORT set address to 0 all other fields blank incl the board 7 Add an IO device call it S7PLC connect to the port PS_PORT m Set the address to S7 Ethernet or S7 MPI for serial m Set the Protocol to PSDIRECT1 7 Add a Tag with IO device S7PLC amp IO Address MO data type set to INT m Put the tag on a mimic compile the application and start CitectSCADA m Verify the correct data is displayed on the mimic Copyright www proscada com PSDIRECT driver for CitectSCADA 6 Frequently asked questions amp troubleshootine Q What is this A the driver s channel network settings select protocol timouts iP Siemens Industrial Ethernet Configuration Scotts International NL D DYNAMICS PD File View Options Help O s e S a 2 a 2 PLC Device List
8. NOTES 1 Addressing format T TDB TDI TM When one of these address formats is used the driver will convert a time value from CiTect HMI SCADA Real to Siemens S5Time or vice versa using the smallest time base it can fit in Range 0 9990 00 seconds 0 lt Values lt 0 01 will be truncated to 0 and Values gt 9990 01 will generate an Alarm Precision may suffer in the conversion e g 10 01 will be converted to 10 00 1100 S5Time format Note having 1 timer value in a DB recommended datatype is REAL However for gt 1 you MUST set datatype to INT this means you loose subseconds unfortunately Addressing DB DI A E M PA PE TDB TDI and TM are using byte addressing T C and Z are using word two bytes addressing They are the same as in STEP7 STRING data type CiTect HMI SCADA STRING data type is not the same as Siemens STRING data type It is equivalent to Siemens CHAR Array data type A NULL terminator Siemens BYTE data type value 0 is required by CiTect If Siemens STRING needs to be accessed use the SDB Address the TDB amp TM S5 timer datatypes are supported however note the following caveat If the tag datatype is INT the value returned is in seconds the address in the PLC is a 16 bit int and arrays function normally If the datatype is REAL the value is also in seconds amp subseconds but addresses must be on 4 byte boundaries skipping blank word addresses in the PLC CitectSCADA S7 Drive
9. This then leaves more resources available for other data that needs to be faster For example poll analogs at 5 second interval setpoints amp run hours at 30 second interval Operator perception of speed is associated to digital status and alarm inputs These can be polled at 0 5 seconds intervals Copyright www proscada com PSDIRECT driver for CitectSCADA 3 The data is already available when a client polls it and data is displayed immediately without delay For example popup screens open instantly with data from the cache 4 The back end polls raw blocks of data from the PLC The front end can then request any data type from this one polled block This results in substantial efficiencies when you have many mixed data types in close address proximity For example Siemens Instance DB s User Defined types like the PID loop DB s are very complicated structures containing floats words amp bits The CitectSCADA S7NT driver would generate a poll for each data type whereas this driver would read the information in one network poll block of bytes to be stored in the cache the Front end driver then processes a CitectSCADA Driver request for each data type from the same cached data 5 Communications can be configured and debugged outside CitectSCADA 1 4 Advantages over the Siemens Softnet Solutions This section refers to the Siemens Ethernet back end To setup Siemens Simatic Net on a PC and to test the communication can be
10. e What it has done is use the NIO messages to stretch the block this configuration then needs to be made active by Reloading the configuration al During reload the driver stops amp has to re start which causes momentary COM but when it stabilises again you should be polling all data and the process only takes seconds of work Read more Can the driver communicate with Proflnet Copyright www proscada com PSDIRECT driver for CitectSCADA A Technically NO however all Proflnet capable CPU s communicate S7 Functions thru the same Ethernet port so it does not matter The driver will work remember the driver communicates with the PLC program NOT IO The PSDIRECT driver uses a protocol called S7 Function or GET SEND of Object oriented large chunks of data Instance DB s and is processed in the PLC asynchronously in 10 variable millsecond rates this is more appropriate between a SCADA amp PLC Proflnet is more about remote IO and processing that in sub millisecond interrupt driven processing In this sense your Proflnet remote IO is more appropriately handled by the PLC program It is dangerous to use the PLC as a gateway to directly access the IO Copyright www proscada com PSDIRECT driver for CitectSCADA 7 7 1 7 2 7 3 7 4 Reference Required components CitectSCADA CitectSCADA V5 41 or higher CitectSCADA V5 50 has the most installations at this time CitectSCADA V6 0 has been succ
11. 24 LUAL RPXRM_03 LUAL BYTE DB0205 0155 155 38 75 25 ERWA RPXRM_03 ERWA BYTE DB0205 0165 165 41 25 Address 126 4 is 31 5 26 _ERAA RPXRM_03_ERAA BYTE DB0205 0166 166 41 5 27 LEA RPXRM_03_LEA BYTE DB0205 0176 176 44 28 EP1 RPXRM_03_EP1 LONG DB0205 0260 260 65 29 EP2 RPXRM_03 EP2 LONG DB0205 0264 264 66 pre PRE 30 EP3 RPXRM_03_EP3 LONG DB0205 0268 268 67 a mn 31 _EP4 RPXRM_03 EP4 LONG DB0205 0272 272 68 er ee eee 32 EP5 RPXRM_03 EP5 LONG DB0205 0276 276 69 39 cnc Mmmvnaa N CMe LAMA nmonone MON non 7A Q What do the Icons in the configurator mean A v The block is healthy amp contains current data x Communications failure g The block is currently not in use it is off poll all the blocks on a standby server should be in this state clock with green slash This block is newly configured amp is not currently being polled You need to reload the configuration to activate note if Citect uses this address it will cause the NIO Address errors until configuration reload Q The driver configurator is using all my PC s CPU time and the whole machine is slow what is wrong A You have many error messages flooding the bottom window of the configurator this scrolling is consuming CPU time Pull the horizontal splitter down to close the bottom window this reduces CPU time Use Menu gt Options gt Learn addresses to solve the NIO Address errors then driver reload Copyright www proscada com
12. Back end Driver Install the Siemens Ethernet Driver by running the setup exe provided The recommended install location is the Citect Bin Directory Recommended Program Group on the Start menu is CitectSCADA Step 3 Install Siemens H1 ISO transport Not used for TCP IP This step is optional depending on the protocols used to talk to the PLC s if you are using TCP IP you DO NOT Require the ISO transport Please go to Section 4 Setting up the driver See Installing Siemens H1 ISO transport Not used for TCP IP Copyright www proscada com PSDIRECT driver for CitectSCADA 4 Setting Up the driver Run the Siemens Industrial Ethernet Driver Configurator T Siemens Industrial Ethernet Driver Configuration 2 Hour Demo Mode C Program Files Citect Citect6 O Bin default SIx S R File view Options Help Ol s Rl S Al 2 an Be PLC Device List on Device Name PLC Type Description S7PLC 57 Series 57 Example configuration Primary Device Connection Backup Channel Address Read TSAP Write TSAP onnectio Gane fi 92 168 0 1 R 0 5 2 Not Used device via 2nd Backup Device Connection Optional Ethernet Address Read TSAP Write TSAP Add DISABLED DISABLED DISABLED Enable Ethernet card oon sot ed T ten Te Data Type Exception Type Dead Band 199 200 TF 1 0 Disabled Disabled 0 0 z M219 218 Byte 0 0 300 0 Disabled 0 0 M220 M255 36 Byte 0 0 300 0 Disabled 0 0
13. ciae reece toes teen E E a A 51 Using the IEC 870 Backend with CiTect c csscsesseesseessesseeneeeneeeseeeseeseeeneeeseeesneseneneeenes 52 21 5 Note on installation cc0ccccsesssescsecsseeeeseneeesseectnnenentennees scecesenneseneesenesececonsentenees 52 21 6 CiTect configuration gas ajaaedececsice gaa vets ejeewote epee cote eyes ccc oes nots eoanestewoue oohi eoeeayteguenoeteds 52 21 6 1 Bo rds Objet gsxr unrest eu dou ac EERE OTE 52 21 6 2 Poris Channel a aE E E E EA EET E G 52 21 6 3 IO Devices Utih sisi ca scoala asoaivia aie cnsaaacaaiiepscorac ous R R R ERN aa 52 21 7 TUR Ta vales crisan iaaa r aae a ea a aa a a a aE a aaa 52 21 8 Status data WANS isini arenon neeite ie esite a aaia aaaeei eiei 53 21 9 Tag Setpoints amp COMMONS 55552522 co scoiasatdasseantoansbanhbaahdadssanaegabaoiaeassaoaaasebebhiaantadius 53 Copyright www proscada com PSDIRECT driver for CitectSCADA 1 User information 1 1 Application notes for PSDIRECT CitectSCADA Front end Interface Type Detail Manufacturer www ProSCADA com Device name Siemens S5 and S7 and TI PLCs Communications method Direct DLL interface into driver poll cache The following CitectSCADA Drivers may be replaced by this Driver S7NT Siemens Softnet systems S7NTSP Siemens misaligned real addressing SINEC Siemens TF Systems for S5 Applicom Layer 4 for S5 TINECWIN TINECNT TIDIRECT Simatic TI via CP1434 H1 card SQUARED Square D Ethernet 1 2 Introdu
14. crash 7 Look in the bottom window if there is a message like unable to open Square D adapter that is causing the crash Read in the help file how to fix in the registry 8 If it successfully opened the correct Ethernet card it will not crash again 9 Setup a device with correct Ethernet address amp add a chunk to poll 10 Whenever you make changes here you have to File gt reload yellow pc button 11 When talking you get green tick marks amp polls per second bottom left 12 Now setup CiTect start with the example project 21 2 CiTect channel Form Create one channel object leave the Boards field blank 21 3 CiTect I O Devices Form Set the Protocol Field to PSDIRECT7 set all IO devices to use the same channel only 1 object Copyright www proscada com PSDIRECT driver for CitectSCADA 21 4 Data types Data Types Address Format CitectSCADA Data Type BITS w b DIGITAL REGISTER Sw BCD INT LONG LONGBCD REAL Where is the word number 1 to 32767 the maximum is actually determined by memory constraints of W the O Device b is the bit number 1 to 16 EXAMPLES Data Type DIGITAL Address 01 15 Comment Word Number 1 Bit Number 15 Data Type INT Address S0001 Comment Register Number 1 SY MAX PLCs support remapping reads and writes Copyright www proscada com PSDIRECT driver for CitectSCADA Using the IEC 870 Backend with CiTect The PSDIRECT Frontend emulates the addresses of IEC
15. k MV Time TMV lt Object No gt LONG Represents millisec after midnight MV Float Value FLOAT lt Object No gt REAL MV Float Invalid QFLOAT lt Object No gt INVALID DIGITAL SO TT 2 a BLOCKA SURFS TOPTSINVALDAT MV Float Time TFLOAT lt Object No gt LONG Represents millisec after midnight Bitstring Bit Value BITS lt Object No gt lt bit gt DIGITAL Bits 0 31 as decimal Bitstring Invalid QBITS lt Object No gt INVALID DIGITAL SOV POM Ph 2 Be 8 BLOCK SUBES TOPFSINVAUIDE 72 Bitstring Time QBITS lt Object No gt LONG Represents millisec after midnight IT Value IT lt Object No gt LONG Counter value write to bits 0 7 sends those bits to counter e g reset IT Invalid QIT lt Object No gt INVALID DIGITAL SYS CASS INVALIDNE IT Time TIT lt Object No gt LONG Represents millisec after midnight STP Value MV lt Object No gt TRANSIENT INT DIGITAL Bits 0 6 step value STP Invalid QMV lt Object No gt INVALID DIGITAL UPL eet OB TRANSIENT STP Time TMV lt Object No gt LONG Represents millisec after midnight 21 8 Status data tags Tag Addressing Notation Data Type Comment Master RTU STATUS STATUS 0 INT 0 Successful master polling 1 RTU failure Master RTU reset comms STATUS 0 INT Write 1 Slave RTU is polled timer STATUS 2 INT Decrementing timer reset up on every masterpoll 0 master not polling FORCEGI FORCEGI lt Object No gt INT Triggers interrogate write value is the Interrogate group 20 all 21 9 Tag Setpoints amp Cont
16. lt data block gt lt word gt REAL STRING DIGITALS DX lt data block gt lt word gt lt bit gt DIGITAL Timer TDB lt data block gt lt word gt INT REAL EXAMPLES Data Type DIGITAL Address DO10 001 14 Comment Digital Data Block Number 10 Word Number 1 Bit Number 14 Data Type INT Address D0010 002 Comment Data Word Block Number 10 Word Number 2 8 6 1 2 1 Note on converting SINEC addresses The Sinec TF system has an extra layer of abstraction that names memory objects to TF names Normally in CiTect projects these memory variables are arrays of 16 bit words To convert these addresses e Look in the TF configuration and find the Data block address of each TF array e Search amp replace the VARIABLE DBF file with lt TF array name gt replace with D lt dbn gt lt add DB offset to TF array index gt lt bit gt 8 7 Driver reference Detail Driver name PSDIRECT Maximum array size PSDIRECT1 2048 Bits Maximum array size PSDIRECT6 32 Bits 8 8 Driver generated error codes 7 PROSCADA_ERR_NO_TAGS 0x100 7 PROSCADA_ERR_BAD_OID 0x101 m PROSCADA_COMMS_ERROR 0x102 7 PROSCADA_BAD_DATA_TYPE 0x103 PROSCADA_UNSUPORTED_CITECT_TYPE 0x104 Copyright www proscada com PSDIRECT driver for CitectSCADA PROSCADA_BAD_IOADDRESS 0x105 PROSCADA_BAD_SIGNALCOND 0x106 PROSCADA_BAD_HWOPT 0x107 PROSCADA_DLL_LOAD_FAIL 0x108 PROSCADA_WRITE_FAIL 0x109 PROSCADA_ISO_NOT_CONNECTED 0x10A Backend is not connected to the PLC
17. many polls per sec you get in the configurator status at the bottom After measuring the speed you can calculate the update time of your full configuration e g If you get 10 pps pollblocks per second you can have e 1 pollblock updating 10 times a second or 10 pollblocks updating at 1 0 seconds e 5 pollblocks updating at 1 0 seconds 10 pollblocks updating at 2 seconds If you configure more pollblocks no errors will occur but you are not actually achieving your configuration update time In this case the driver just processes each block in turn This is not a problem most of the time but as you add more blocks your system will slow down amp if you need faster update on a specific block changing its polltime will achieve little 12 3 Optimisation Techniques To make a limited bandwidth system appear faster you have to slow down the updating of less critical data to give more bandwidth to the critical data Increasing the pollrate of a block when the system is already at full stretch will have no effect The basic principle is poll only the data that the operator needs for a given picture amp at the minimum rate he is prepared to accept It is usually better to set slow polltimes at the start of a project which leaves plenty of room to expand this sets a lower expectation and if you need more speed later you have spare bandwidth resources Setpoints Outputs controls or any value that never changes in the PLC only changes when
18. modified from the SCADA can be setup so that they hardly use any channel bandwidth at all Set the polltime to a large value like 60 seconds If a value is written the driver automatically forces the block to update so the user does not notice the slow poll times Prioritize your data find out how fast the data changes in the PLC Do not poll faster than necessary especially while you are constructing your system You can always speed up certain blocks later once your system is fully configured Generally analog values can be polled slower e g 5 sec but Digital Inputs may need 1 sec Copyright www proscada com PSDIRECT driver for CitectSCADA 12 4 PLC Optimisation 12 4 1 Number of Network connection resources CPU properties Resources available for the driver on the S7 300 is Two 2 by default which can be changed this means 2 IO servers can connect but the third will fail unless you change this configuration in Step 7 The S7 400 allows 4 8 connections by default Properties CPU 314 RO S2 J x General Startup Cycle Clock Memory Retentive Memory Interrupts l Time of Day Interrupts Cyclic Interrupts Diagnostics Clock Protection Communication Connection Resources Reserved for PG Communication OP Communication S7 Basic Communication S7 Communication Maximum number of connection resources B 12 1 1 8 2 connections available for SCADA reduce others to provide more headroom Cancel
19. other Citect IO servers From version 7 9 52 performance has been increased substantially over the above numbers the difference is more noticeable for configurations of lots of small blocks The communications are Slow how do make it faster read the section about optimisation of the driver amp try some of the following modifications at the PLC side How do configure communications to an S5 PLC Copyright www proscada com PSDIRECT driver for CitectSCADA A Q This is far more complicated than an S7 PLC Please read the Driver help file SIXHLP CHM section Setting up the hardware for Full instructions In addition there are example S5 PLC programs amp CP card setup files in the backend distribution in the PLC directory keep getting an error Nio niomap different from map popup box You are using more than one IO Channel device on the IO server please put all lO Devices including different PLC types under one single Citect IO Channel object Note as of PSDIRECT 2 3 it is more tolerant of multiple channels With the S7NT driver objects like PID set point sliders operate smoothly however with PSDIRECT it sometimes briefly jumps back to old position before assuming new position The PSDIRECT is actually faster here remember the Display is reading from the PSDRIECT cache amp displaying at the Citect screen refresh rate with S7NT it was actually stalling the screen refresh until the
20. reading from it needs status information about the communincation status of the backend these variables are in the S addresses and are used internally for Unit Status by the front end Now if the driver loses communication to the PLC the Unit status will go bad amp CitectSCADA s redundancy system will switch over to the backup IO Server Note The AlwaysReturnNoError 1 is intended for debugging only When set you will see correct values only if the driver is successfully polling if not INVALID data may be displayed amp no redundancy failovers will occur My communications are Slow WHY Please Note the following typical performance achievable This driver polls as fast as the PLC allows the PLC is the bottleneck slow side the figures below are per PLC the driver performance scales linearly per PLC S7 315 CPU typically achieves 15 20 polls per second We believe it is crippled S7 416 CPU typically achieves upto 150 polls per second 10 x faster This is with 2 IO Devices talking to the same PLC A Vipa PLC typically achieves upto 40 polls per second with default settings if communications resources are increased this can reach 100 The driver has a Built in Limit of 200 polls per second per IO Device so in some cases you can get better performance by splitting your data into 2 IO Devices However we do not recommend this as the spare PLC resources should be reserved for Writing data amp PLC PLC communications amp
21. to name the Local TSAP linking to the IO server name remembering it MUST be 8 chars e g IOSPRIMR IOSPRIMW amp IOSBACKR IOSBACKW 19 1 3 Step 2 Configure the backend driver e The TCP IP version of the CP1434 card is quite rare so most will use the ISO transport MAC address not TCP IP If using TCP IP do not proceed until you can ping the PLC o Setup the Siemens ISO transport in the network settings this is the same as for the S7 amp S5 PLC s described earlier in this document e Set the read amp write TSAP s to the Local TSAP names in the CP1434 config e Check that you have communications you should do this before setting up CiTect Simply setup 1 block of V registers You should see green ticks amp blocks per second at the bottom of the configurator window indicating successful communication 19 1 4 Step 3 Configure the backend blocks e Set the name of the backend IO device the same as the IO device in CiTect e Open the project variable dbf file in excel filter on IO device amp sort on IO Address Then manually add equivalent blocks in the backend Note the backend addressing is slightly different it has between blocktype amp address eg V1000 gt V 1000 e At present there are no Learn address amp variable import features for TI e Any Citect tag accessing data in a block not being polled will cause Nio Address error xxx messages You MUST get rid of these errors by adding poll b
22. 0 2 5 3 JFP With frontend 2 5 3 2 6 JFP Tidy up amp merge added IEC870 chapter Copyright www proscada com PSDIRECT driver for CitectSCADA Contents 1 User informati n se iiecisscamiactniviactestinmsnniateanadinniniamennenaneciienatnennCmaals 6 1 1 Application notes for PSDIRECT CitectSCADA Front end Interface 6 1 2 DIEM METH a cei etc is cic medic ined cineca dada streetscene daseatiaceccedmet deeace 6 1 3 Advantages over the traditional CitectSCADA Drivers cccceceeeeeeeeeeeeeeeeeeees 6 1 4 Advantages over the Siemens Softnet Solutions cceeeceeeeeeeeeeeeeeeeeeeeeeeeeees 7 2 Structure OF the drive a asciceissentssnensieacsicawesavercanustaennsasncecntaantsnnesennineesabiecntsanusascrisinennses 8 3 Set p guide isiin ctswdina hn acne nike dace aaeeea aeea adea cdeananententteaate 9 3 1 Step 1 Install the PSDIRECT CitectSCADA front end driver cccccceeeeeeees 9 3 2 Step 2 Install the Back end Driver ceeeeeeeeeececeeeeeeeeeeeeeeaeeeeeeeeeeeeeeeennaeeees 9 3 3 Step 3 Install Siemens H1 ISO transport Not used for TCP IP 00 9 4 Setting Up the drive r sssssnsnnunennnnnnnnunnunnunnunnnnnnnnnnunnunnunnunnnnnnnnnnnnnun munnum nnmnnn annann nn 10 4 1 Setting Up using the serial MPI ccccccceeeeeeeeeeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaees 12 5 Quick start Simple CitectSCADA Configuration csccsteeeseeetseeen
23. 1 OR simply put the PLC in STOP mode e Set the backend driver s channel protocol to TCP IP e Set the device S7PLC s IP address e File reload the configuration e Check that you have transmits amp receives and the status of the blocks goes good e Import the project into CitectSCADA compile amp run e Open test page 1 The stress test writes huge amounts of data and reads it back comparing it to that written any mismatches increment the error counters Copyright www proscada com PSDIRECT driver for CitectSCADA 14 Setting Up Heartbeat monitoring The S7 driver continues polling normally when the PLC is in Stop mode resulting in frozen values on the screen To force COM s when the PLC is in stop mode requires configuration of the Heartbeat monitoring feature For each IO device Unit configured a parameter of the following form is entered into the Citect INI file HeartBeatAddress lt devname gt lt address gt Where lt devname gt is the name of the IO device in CitectSCADA and in the backend driver And lt address gt is a PLC address of a variable that MUST change very 5 seconds at least if the PLC is running A simple way of achieving this is to increment an integer in OB1 of the PLC scan cycle the address format here is the same as the OPC server so you specify W for Integer amp D for longs etc Examples HeartBeatAddress S7PLC MWO HeartBeatAddress_ PumpHouse DB100 W44 HeartBeatAddress_Furna
24. 52 sssssssssseeerrreesssrsrrrrnrnnesserrrrrnen 34 How to Measure Driver Performance 2 cecceceeeeeeeeeeeeneeeeeeeeeeeeeeeenenneeeeeeeees 34 Optimisation Techniques ccceeccceceeeeeeeeeeeeeaeeeeeeeeeeeeeeeeaaaaaeeeeeeeeeeeeenaaeaes 34 PEC OptimiSatiONs cinneann a aa a a r E E cele testis 35 Number of Network connection resources CPU properties seenen 35 CPU communication load priority CPU properties sssssssssesssesisssissrissreseresisesresriesrresrrssrresereseresens 35 Block size CP card properties aneneen 35 Using the Stress test example project ssussunsneunnnnunnnnnnnnnunnnnnunnunnnnnnnnnnnnnnn nnna 36 Setting Up Heartbeat monitoring s s nsunsunnunenrunnunnunnunennnnnunnunnunnunnunnnnnnnnnnnnnnn nnnm 37 S7 200 SOT p AE E EEE E EEE 38 S7 1200 amp 1500 Setup snssnsusussnnnsnnnnnnnnnnnnnnunununnnnnnnnnnnnnnnnnnnn anann nn nnmn nnnnnnn annman eenen 41 Configuring for Redundancy s sssssneununnunnurennnnunnunnunennnnnunnnnnunnnnnunnnnnnnnn nannan nnnm 42 Standard CiTect redundancy seccccccsissscscsocnscensadaensssesccoondeeseevanascenentedeeeonensnseccdennes 42 N E A A A E E A E A aten cada aaa adeno 42 Using the S7 Simulator application cscceeceeeeeneseeeeeeeeneseeeseeeneeeseeeeeeeeeneeenes 44 Copyright www proscada com PSDIRECT driver for CitectSCADA 18 1 ac call ae ee ne ee ee ee ee ee ee eee 44 18 2 Introduction why a PLC simulator c
25. ABLED DISABLEI _1 0 Bloc Start x End Length Data Typ 7B s0 5199 200 Byte 2A NRINANRAAAN NRINANANA1 217 Rute You can poll the following data from an S7 200 MO M32 S7 200 has very small M area DB1 0 gt x is equivalent to the V mem area e g VW8 CiTect block type INT address DB1 8 10 len 2 Built in I inputs QI len 1 Built in Q outputs Copyright www proscada com PSDIRECT driver for CitectSCADA Alternative S7 200 configuration Configure Connections Copyright www proscada com PSDIRECT driver for CitectSCADA 7 1 so 199 200 Byte gt FF NRINNN RANNA NMRNANANP1 71 Rute Configure Connections x Set Both Local amp remote TSAP s the same 7 1 S0 5199 200 Byte gt FF MARIANA RANA NRMNANRNPW 71 Rute Copyright www proscada com PSDIRECT driver for CitectSCADA 16 7 1200 amp 1500 Setup In TIA Portal PLC Setup check the following e CPU gt Properties gt Protection make sure you TICK the Permit access with PUT GET communication from remote partner and the protection itself must be set to full access PLC_T CPU 1212C AGDGRIy SC General 10 tags System constants tem constants Texts gt General A gt PROFINETin gt DISIDO6 gt gt gt ee Connection mechanisms High speed c Pulse gener Permit access with PUGET communication from remote partner PLC H Startup Cycle Communicati
26. Help 12 4 2 CPU communication load priority CPU properties You can try increasing communication priority Properties CPU 314 RO S2 4 x Time of Day Interrupts Cyclic Interrupts Diagnostics Clock Protection Communication General Startup Cycle Clock Memory Retentive Memory Interrupts r Cycle V Update GB1 process image cyclically Scan cycle monitoring time ms fiso o Minimum scan cycle time ms 0 Scan cycle load from communication lt Size of the process image z OB85 call up at 1 0 access error No 0895 call up w Clock Memory T Clock memory Memory Byte jo 12 4 3 Block size CP card properties Some CP cards not all have an option in the options tab for large PDU block size gt 240 set this option if available Copyright www proscada com PSDIRECT driver for CitectSCADA 13 Using the Stress test example project An example CitectSCADA project installed with the Front end driver in C Program Files Citect CitectSCADA PSDIRECT Sample PROSCADA_test ctz To use this setup you need e AnS7 PLC 400 or 300 with Ethernet CP card e Step 7 with Siemens NCM to configure the PLC CP card e A CitectSCADA machine networked to the PLC NO SIEMENS SOFTWARE Required Probably the easiest protocol to use is TCP IP e Setup the PLC with an IP address and ping to test from the CitectSCADA e NO Step 7 program is required or if one exists it MAY NOT modify m0 m51
27. LC options for S7 300 amp S7 400 what has changed since note that my old configurations still work amp have defaulted to S7 300 A The protocol is identical the S7 400 can handle larger block sizes than the S7 300 and is therefore faster so it is a performance optimisation Copyright www proscada com PSDIRECT driver for CitectSCADA Q A have REAL or LONG tags where some are displaying correctly others not This is a standard CiTect driver issue CiTect always reads arrays of data so if your variables are not aligned to each other on 4 byte boundaries the misaligned tags get invalid data Note this may be random some work some don t usually tag debug works For example DB12 10 DB12 18 are 4 byte aligned however DB12 18 DB12 32 are not The driver has built in an option to read data in blocks of 32 bits which normally solves this issue To apply this simply change the IO device protocol from PSDIRECT1 to PSDIRECT6 then recompile remember to recompile the clients The only disadvantage is that you loose STRING s amp arrays which need to be on PSDIRECT1 on a separate IO device _ F23 X fe VALUE MID D23 8 4 A B G D E M G o J K 19 APA RPXRM_03_APA LONG DB0205 0110 110 27 5 20 RPT RPXRM_03 RPT LONG DB0205 0114 114 28 5 21 RPM__RPXRM_03 RPM LONG DB0205 0118 118 29 5 22 RPMX RPXRM_03_RPMX LONG DB0205 0122 122 30 5 23 RPA RPXRM_03 RPA LONG DB0205 0126 126l 31 5
28. M438 M511 74 Byte 1 0 300 0 Disabled 0 0 D8100 80000 DB100 80219 220 Byte 1 0 300 0 Disabled 0 0 DB100 680220 DB100 80439 220 Byte 1 0 300 0 Disabled 0 0 Channel 1 Device SSPLC 1 Poll Record 2 Failed Communication I Channel 1 Device SSPLC 1 Poll Record 3 Failed Communication I Channel 1 Device SSPLC 1 Poll Record 4 Failed Communication lt TX 0 RX 0 Polls Sec 0 No Citect key 11 56 PM The Default configuration file will open this includes 3 PLC s an S5 S7 amp TI Since you will probably be using an S7 select the S5 PLC amp press delete do the same for the TI PLC The S7 example configuration is setup to poll MO Mg9 this address exists in all S7 PLC s so it should poll correctly without setting up a Step 7 program on the PLC Before setting addresses etc please set the protocol type in the channel settings e Open the channel settings to set the protocol press the saae button Channel 1 Communication Settings Error Handling Reply Timeout Delay Retries Protocol jiso Industrial Ethernet Copyright www proscada com PSDIRECT driver for CitectSCADA You have a choice between TCP IP and ISO If ISO is chosen then the ISO transport must be installed supplied with the driver e Set the PLC s address for ISO this is a 12 digit Hexadecimal MAC address for TCP IP this is of the form 0 0 0 0 e Now press ok to go back to the main device settings The read TSAP se
29. PSDIRECT CitectSCADA Driver for Siemens S5 and S7 and TI PLCs User information and design CGitectSCADA PSDIRECT driver for CitectSCADA Driver version history Version Modified By Details 2 00 JFP 2 0 is the Stable version after Initial development 2 01 JFP Fixed problem with S5 LONGS Fixed S7 PI amp PE addresses Improved some sections amp troubleshooting 22 JFP e Added extra DCB validity checks everywhere amp made sure of potential string overflows e Compiled against the CTDDK V6 dont seem to be any major changes e Added support for Siemens S7 STRING Datatype new feature not supported by S7NT 2 2 1 JFP Added S7 200 support to backend 2 2 2 JFP Added some more FAQ s amp updated status addresses 2 3 JFP e Increased number of IO devices to 128 e Increased blocksize to CiTect max of 2048 bits only useful for those using big arrays e Now allow multiple channels but still recommend only one e New Status register addresses to monitor backend redundant address status e Now allow multiple Citect IO devices connecting to one backend IO Device e Substantial work on the IEC 870 protocol 2 4 JFP e Fixed problem with S7 strings max block length e Fixed problem with S5 strings e Completely re tested amp re vamped the TI profile e Added support for Square D driver 2 4 2 JFP 2 4 3 JFP Added some more troubleshooting items 2 5 14 4 JFP Released with backend 7 10 54 added supportAdded notes for S7 120
30. PSDIRECT driver for CitectSCADA Q A Why do see messages like Nio Address Error DB15 W248 in the bottom window of the configurator This means that CiTect is reading that address however this address is not configured for polling in the backend It is Crucial to Fix this issue before doing any other testing Note that this issue may occur with amp Q addresses where you have many small discontigous poll blocks in the backend What is occurring is that Citect is aggregating address blocks The only possible solution is to use the small blocksize version of the front end driver this means changing the CiTect IO device protocol from PSDIRECT 1 to PSDIRECT6 This change may still not eliminate the reporting of the errors however CiTect will get valid data You only see these errors when CiTect tries to access the data so seldom used addresses may not be noticed There are 2 Semi automatic methods of solving this o By selecting Menu gt Options gt Learn addresses the configurator uses those error messages to stretch existing blocks or add new ones o By selecting Menu gt Options gt Import Addresses The configurator can add stretch blocks by using a VARIABLE DBF or VARIABLE RDB file This works better than the learn address method because you get ALL the addresses in the project If you open a UNITS DBF file it will add IO Devices to the backend Note this only changes the edited file in disk you need to rel
31. SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 QMV amp QIT amp QFLOAT amp QBITS lt OV 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 gt CiTect Tag Addressing Notation CiTect Data Type Comment SPI Value SPI lt Object No gt VAL DIG TAL INT VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7 SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 SPI Invalid SPI lt Object No gt INVALID DIG TAL INT VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7 SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 SPI Time TSPI lt Object No gt LONG Represents millisec after midnight DPI Value BIT 0 DPI lt Object No gt VAL DIGITAL VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7 SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 BIT 1 DPI lt Object No gt 1 DIGITAL VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7 SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 DPI Invalid DPI lt Object No gt INVALID DIGITAL VAL 0 1 1 2 2 3 3 BLOCK 4 SUB 5 TOP 6 INVALID 7 SELECT 7 SPUL 2 LPUL 3 NEGC 14 ISSELECTED 15 DPI Time TDPI lt Object No gt LONG Represents millisec after midnight DPI Value as INT DPI lt Object No gt INT then use Cicode functions to strip amp mask out values e g 0 1 DPI as analogue MV Value MV lt Object No gt INT contains both scaled amp normalised data whatever received MV Invalid QMV lt Object No gt INVALID DIGITAL SONOS Tae BLOCK SUBES TOPESINVALD
32. ant wn s a Select Network Protocol a TF Click the Network Protocol that you want to install then click OK If you have an yi installation disk for this component click Hawe Disk De j A Manufacturers Network Protocol c DECES AppleTalk Protocol Install From Disk Eg i a Insert the manufacturer s installation disk into the drive selected and then click OK PaPa Cancel i Copy manufacturer s files from Clso win2000 3 Browse 7 Press OK Copyright www proscada com PSDIRECT driver for CitectSCADA 8 You will see a prompt ISO transport for Siemens H1 9 Press OK Microsoft Select Network Protocol AppleTalk Protocol Local Area Connection Properties 10 Close and restart the computer Copyright www proscada com PiGBenies PSDIRECT driver for CitectSCADA 21 Using the Square D PLC Backend with CiTect The PSDIRECT Frontend emulates the SQUARED PLC driver 21 1 Installation 1 Install the PSDIRECT front end 2 Install the Square D low level protocol as described in the SDEDIDW HLP help document done in Control panel networking 3 Enable this protocol only on the network adapter you are going to use Disable on all other wireless dialup VPN VMW adapters on the PC 4 Reboot 5 Install the Square D Backend driver setup Exe This may crash just continue 6 Run the driver configurator part may
33. ccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeeeeeee 44 18 3 RAD OO MMNSS scascp hota neta ates vec eti E ie ceth eee eie estes ate 44 18 4 ViPS NN siisii anaie en o paataan a iaa aain a aaaeei aai 44 18 5 Forced variable S o iiirircensinnnnniun ninais a 44 19 Setting up the Simatic l nunsnnnnnnnennnnnunnunnnnennnnnunnunnunnunnnnnnnunnnnnunnnnnnnnnnnnnnn nannan 46 19 1 1 Step 1 Adding peer peer jobs to the PLC CP card setup sssssssssrsisrsissrissriesisesrseriserissrrssrrssersseresees 46 19 1 2 Configuring Redundant SCADA Servers sssssssrsissrissrressssseeressrissrrssrreseresereserusresnresnresnresrresereseresees 47 19 1 3 Step 2 Configure the backend drittens 47 19 1 4 Step 3 Configure the backend bIOtRS sssssssssssessessserississsissrrssersrersseerresrissrrssrreserenerenereneessresrreseresee 47 19 1 5 STEP iNT 10 ecient sceials uta saeco it otep ah st oatcnens A EA RS 47 20 Installing Siemens H1 ISO transport Not used for TCP IP csscsseee 48 21 Using the Square D PLC Backend with Cite ct csscsssesseseeseeeseeeseeseeeneeenes 50 21 1 Installation eeccstecetecaciosticciecatnecsastacs Cadatndliasdbcitieili adie ctdhoiies dimitri Mac tes deiiecttiets 50 21 2 Citect channel FOrm ccccccceeceeeeeeeeeccceeeeeeeeeeeeecaaaeeeeeeeeeeeeaaaaaaaaeeeeeeeeeeeneneaaaees 50 21 3 Citect I O Devices FOrm cccceeeeeeeeccceeeeeeeeeeeeeaaeeeeeeeeeeeeeeeeaaaaaaeeeeeeeeeeeeennaaeaes 50 21 4 D ta type S sanee ana eres
34. ce2 DB130 D44 long integer Copyright www proscada com PSDIRECT driver for CitectSCADA 15 S7 200 Setup 1 Run the Micro Win Ethernet Wizard 2 we recommend that the CP243 be installed in position 0 3 Set the CP243 s Ethernet address 4 Configure a New connection amp set it as follows Configure Connections You have requested 1 connection s For each connection specify whether the connection should act as a client or server and configure its associated properties Connection 0 1 connections requested AREE This is a Client Connection Client connections request data transfers between the local PLC and a remote server This is a Server Connection Servers respond to connection requests from remote clients Local Properties Serve Remote Properties Client s TSAP IV This server will connection with an Operator Panel OP IV Accept all connection requests ACCEL connection requests trom the following Clients only co IV Enable the Keep Alive function for this connection jon Your program can reference this connection In the Driver polling configuration set the Read TSAP field to CP243 PLL Device List Device Name Descriptior PACK Packing F Primary Device Connedtion Address Write TSA 127 0 0 1 Not Used Backup Device Connection Owens Address Read TSAP Write TSA Add Delete 0 0 0 0 DIS
35. ction In large applications where CitectSCADA has to talk to many Siemens PLC s a need has arisen to have a higher performance Siemens Driver interface Simatic Net has a lot of limitations on the number of PLCs it can connect to and also the performance of the Siemens API has been an issue CitectSCADA also needed a way to optimise the way it communicates to the PLCs particularly if the user attempted to poll large configurations of Function block instance DB s directly User Defined types The PSDIRECT CitectSCADA direct interface driver is a front end back end driver meaning that the driver consists of two parts z The back end server polls the data from the PLC s at configurable intervals The back end puts the data in a memory cache m The front end is a native CitectSCADA driver that reads the data from the cache instantly with O delay does not poll the PLC s 1 3 Advantages over the traditional CitectSCADA Drivers This has the following advantages 1 The Polling of the data is completely de coupled from the rate at which the clients are requesting it which means the clients cannot choke up the IO server with requests no matter how badly the system is configured 2 With a traditional CitectSCADA Driver all polling is Dynamic amp client driven With this driver each block of data has an individual poll time This allows each block of data to be optimised to poll as SLOW as is acceptable for that sub application
36. dbieondabnws 26 8 8 Driver generated error codes ennenen 26 Copyright www proscada com PSDIRECT driver for CitectSCADA 8 9 8 9 1 8 9 2 9 10 10 1 1 10 2 11 11 2 11 2 1 1122 12 12 1 12 2 12 3 12 4 12 4 1 12 4 2 12 4 3 13 14 15 16 17 17 1 17 1 1 17 2 17 2 1 18 Parameters Options and Settings cccccccccccccccccceceeeeeeeeececeeeeceeeeeeeeeeeeeeeeeeees 27 Sandara Raramen S annann n a a aa a aaa E E 27 Driver Specific Paramete sssrinin 27 Analysis amp Trouble Shooting sssssnsunnunnunnunenrnnnunnunnunnnnnnnnnnnnnunnunnunnnnnnnnnnnnnnnnnn nnen 29 Using the Special Debug addresses cssscsscseseneseeesneeseesseeseneneeeseeeseeeenenenenes 30 Redundancy tOntfolsssssessesnsnsnsnsnsensnnsttisititiisistiisrstiistrstiisistrtsress 30 For the S5 amp TI PLC the Status addresses are as follows 0 eeeeeeeeeeeeeeeeees 30 Migration from S7NT driver systems s nunsunenennnunnunnunennnnnunnunnunnunnununnnnnnnnnn nunna 32 Communication TONS acrssttesice Penta innesta ianaeaieo aieiaa Meet ats 32 Back end Configuration sisccs viseseceespseeeselesenacecelieuteie ieee minesteyielecee eu liensn tule eeeea 32 Backend TO demies asenensnicioncitnidi aea a EEan E aE EL EA SAES 32 Backend TO Blik isione E EEEE EEEE EEEE EEEREN 32 Communication Optimisation ccsccsecssesseeseeeseesseseeeseeeneeeseesseeeseesseeseeeseeennes 34 note on performance in new version 7 9
37. dex gt 1s T lt index gt 10s Z lt index gt TDB lt no gt lt index gt TDl lt no gt lt index gt TM lt index gt SDB lt no gt lt index gt string len V lt index gt lt bitno gt CitectHMI SCADA Data Type Digital Byte INT BCD LONG LONG_BCD REAL STRING Digital Byte INT BCD LONG LONG_BCD REAL STRING INT BYTE Digital INT BYTE Digital INT BYTE Digital INT BYTE Digital Digital Byte INT BCD LONG LONG_BCD REAL STRING INT BYTE Digital INT BYTE Digital INT BYTE Digital INT BYTE Digital BCD PLC s5time format BCD PLC s5time format BCD PLC s5time format BCD PLC s5time format BCD REAL INT PLC s5time format See note 1 below REAL INT PLC s5time format See note 1 below REAL INT PLC s5time format See note 1 below Siemens STRING datatype See note 5 below string len compulsory S7 200 V memmory area see S7200 Syntax The syntax is defined as follows case insensitive DB lt no gt lt index gt Dl lt no gt lt index gt lt bitno gt Copyright www proscada com PSDIRECT driver for CitectSCADA Where DB or DI data block or instance block lt no gt number of the data block or instance block lt area gt A output Q output E input input M bit memory PE peripheral input PI peripheral input PA peripheral output PQ peripheral output lt index gt element number relative to start of block lt bitno gt bit within the element number
38. dress PSDIRECT6 S7 ETHERNET N name Same as PSDIRECT1 with 32 bit blocksize S7NTSP replacement PSDIRECT6 S7 MPI N name Same as PSDIRECT1 with 32 bit blocksize S7NTSP replacement PSDIRECT7 Blank Square D emulates SQUARED PSDIRECTS8 Blank GE Aritech Fire Panel PSDIRECT1 S7 ETHERNET STAT N name Use to read Status variables that never show COMM PSDIRECT2 S5 SERIAL N name S5 using 3964R serial protocol The Address field is used to specify which backend driver to use amp which protocol The N xx is optional do not type and if this parameter is supplied the xx must be the IO device name in the backend The Name of the IO device is by default used to connect to the backend device of the same name Unless the N xx parameter is supplied in which case THIS overrides the name The N xx may therefore be used if IO device names Longer than 11 characters are required OR Multiple Citect IO devices connected to 1 backend IO device are required 8 4 Driver Caching This driver has its own cache it is therefore not necessary to cache data on CitectSCADA side The recommended cache enabled setting is FALSE default is blank which is TRUE This setting is not critical but performance will be at least 300 ms faster than the defaults Copyright www proscada com PSDIRECT driver for CitectSCADA 8 5 I O Devices form settings Field Name Number Address Protocol Port name Comment Enable Caching Cache time
39. e S5 amp TI PLC the Status addresses are as follows ST1 Conn State 0 means trying to connect to PLC 2 means Connected ST12 Reconnections Increments every time the driver attempts to reconnect after the connection a failed If this is going up you have a bad network ST13 Pollrecs per sec Poll rate for this PLC useful for checking optimisation The rate in mission control should be the sum of these ST14 Disconnect Req s Increments when PLC sends Disconnect Request This Means that your Network is OK but the CP 143 setup is not The PLC is refusing connection requests ST21 Write Connection state 2 means connected Copyright www proscada com PSDIRECT driver for CitectSCADA Copyright www proscada com PSDIRECT driver for CitectSCADA 11 Migration from S7NT driver systems This is a brief summary of the steps required to migrate an existing S7NT system to the PSDIRECT Ethernet driver Note Citect s behaviour is undefined if you forget to compile ALL clients to PSDIRECT to avoid this issue change the IO Device numbers as part of the upgrade 11 1 Communication forms No Boards form required Delete all but 1 ports set all fields to blank address to 0 In IO devices UNITS DBF e Make sure name is less than 11 characters limitation of backend Set port name to the 1 port e Set Protocol to PSDIRECT1 or PSDIRECT6 for S7NTSP Set Address to S7 Ethernet 11 2 Back end Config
40. ecause it is reading instantly from a cache Please note this includes the case where you have both S7 amp S5 PLC s Only use one Channel If you use Both the Ethernet amp Serial drivers put the serial devices on a separate port Note from V2 3 the driver no longer reports errors when multiple channels are used however we still recommend using only 1 channel Field Default Allowable values Port Name This field is user defined and is not used by the driver Port number 0 Any value other than Board name Leave blank Board is not required Baud rate Leave blank Data bits Leave blank Stop bits Leave blank Parity Leave blank Special Opt Leave blank Comment This field is user defined and is not used by the driver Copyright www proscada com PSDIRECT driver for CitectSCADA 8 3 I O Devices Form The Address AND Protocol refers to the Address format of the tags amp also specifies the type the combination is used to decide which Driver DLL to load amp what address format to Use The following table lists the allowable combinations PROTOCOL Address Comment PSDIRECT1 S7 ETHERNET N xx Siemens Industrial Ethernet S7 PLC s PSDIRECT1 S7 MPI N xx Siemens Serial MPI PSDIRECT2 S5 ETHERNET N xx Siemens Industrial Ethernet S5 PLC s PSDIRECT3 Conet N xx OmniFlex Conet with timestamping PSDIRECT4 TI N xx Texas Instruments H1 PSDIRECT5 IEC lt common addr gt N name IEC 870 5 101 with common ad
41. eeeeeeeeees 13 6 Frequently asked questions amp troubleshooting csscssecesseesseesseeeseeesseeeneees 14 7 Reference Required components csscseccseeseneseeeseeeseeeseeseesseeseeeseeeseesseesenenes 20 7 1 GiteciSCADA eres re eo ee ea 20 7 2 Operating SYSUGING isinne nieri aioa aa tea aaa aa aan aa ae Era EEEa E 20 7 3 Recommended System ccccccceeeeeeeeeecceeeeeeeeeeeeeeeaeeaeeeeeeeeeesseeeeaeeeeeeeeeeeeees 20 7 4 ERWINIA ocd tascsevabeseenneeediecocbesuneoidepiew acd notes cadesievac ddecortegieeetdeglacceeediteoatedi 20 8 Reference COMMUNICATIONS FOrmS c ceecceeeeeeseneseeeneeeseeeeeseneneeeseseeseneneeenes 21 8 1 Boards Formiassa R E eas aasmugsscdsieweennamuteeiseensuedauas 21 8 2 Ports Form Channel sirenen neniatn ainnean enanat er ener eee ane ere 21 8 3 VO D vic s FOrnMhitsesisesrsesise sinestun lca leveyiuedtcey dee dbvaySvautueulacdeenyiee vue uSuadeeay ica saii 22 8 4 Driv r Cachi gessisse dadandan aai ida daadaa daeadenn iaaa 22 8 5 VO Devices form SettinGS cccccccceeeeeseeecceeeeeeeeeeeeeeeaaeeeeeeeeeeeeessenaaeeeeeeeeeeeeene 23 8 6 Reference Data types c cccccceeeeeeeseeeeeceeeeeeeeeeeeneaaaeeeeeeeeeeeeesecaaeeeeeeeeeeeeenea 23 8 6 1 Reference Tag Addressing scssssssssscsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssesessssssssssssssssssessees 23 8 7 Driver reference ciisiccsnctcccccnnadaviienntensdededinedecssasedonhdndbewndaysdedednnndeonmphtaiede
42. ences to standard CiTect Drivers the main difference is when switching over the pollblock is in the mode on the standby IO server the every first scan of CiTect data may contain data up to 60 seconds old until the driver polls the new data lt 1 second typically e Redundant load balance with only one PLC If you have a configuration with 1 BIG PLC and a redundant pair of SCADA IO Servers you may run into speed problems For this reason you may want to load balance the communications between the servers to do this setup as follows o Create one backend IO Device called PLC1 both IO Servers use the same o Create Two 2 CiTect IO devices call them something like PLC1_P amp PLC1_S o Set PLC1_P to primary on IO Server 1 amp PLC1_S to Standby Vice versa on IO Server 2 o Set both IO Device Address fields to S7 Ethernet N PLC1 the sets the backend link to the N PLC1 o Split the tag database in 2 using PLC1_P amp using PLC1_S 17 2 Using Backend redundancy with S7 400H systems OR gt 1 CP card in the PLC The driver at the backend level has a backup address per IO Device typically on a S7 400H system you setup as follows Note redundancy at the backend level means a single Citect level IO device Primary address IP 192 168 0 1 Read TSAP R 0 S 3 Backup address IP 192 168 1 1 Read TSAP R 1 S 3 check enable backup address Device Name PLC Type Description S7PLC 7 300 z 57 Example configurati
43. es on the screen To force COM when the PLC is in stop mode requires configuration of Heartbeat monitoring read more about it in Heart beat monitoring section of this document To add these parameters to the CITECT INI file use the following format PSDIRECT AlwaysReturnNoError 1 Note setting the AlwaysReturnNoError to 1 like this is only useful for testing or engineering purposes Copyright www proscada com PSDIRECT driver for CitectSCADA 9 Analysis amp Trouble Shooting Things to do on a call out to the IO server 7 Check to see if there are any popup dialogs from CitectSCADA or the Driver indicating a problem if so write down the message displayed m Open the kernel amp View the Driver s page m Check the Driver Errors amp Timeouts counters m If these two counters are incrementing then CitectSCADA variables are addressing variables not configured in the back end driver 7 Check which IO devices PLC s are offline in CitectSCADA m Open the CitectSCADA kernel and go to the IO Servers page 7 The statuses on the left indicate what is happening on this IO server the statuses on the right indicate the status of the IO Server currently in use Copyright www proscada com PSDIRECT driver for CitectSCADA 10 Using the Special Debug addresses This driver is a cached Front End Back End driver so the standard CitectSCADA driver statistics are not very useful This section de
44. essfully tested CitectSCADA V6 1 has been successfully tested CitectSCADA V7 0 has been successfully tested CitectSCADA V7 2 has been successfully tested CitectSCADA V7 4 has been successfully tested Operating Systems Windows 9x Millennium NOT SUPPORTED for ISO protocol Windows NT4 SP4 or later Windows 2000 Pro or Server Windows XP SP1 amp 2 Windows 2003 Server R2 Windows Vista Windows 2008 Server R2 NB at this time 64 bit systems cannot use ISO Windows 7 Windows 8 Windows 2012 Recommended System CiTect recommendations Network Card Any NDIS compatible card should work Named brands are recommended for best performance NOTE NO SIEMENS SOFTWARE OR HARDWARE REQUIRED NOTE when using the ISO protocol DO NOT install any Siemens software on the machine NOTE Some problems have been encountered with Broadcom cards recommend Intel Copyright www proscada com PSDIRECT driver for CitectSCADA 8 8 1 8 2 Reference Communications Forms Boards Form This driver does not require a BOARDS object for Later versions of CiTect Some people have reported problems omitting the board on this driver if they use other drivers that require boards Note Adding The Board object WILL NOT cause problems however you may see error messages at startup these can be ignored Ports Form channel Note Unlike the S7NT driver only 1 port is compulsory on the IO server performance is just as good with only 1 b
45. increments up infinitely every 10msec DB15 1 increments to pi 1000 DB15 2 is sin DB15 1 DB1 is in S7 format DB1 2 increments up to 100 every 10msec DB1 0 increments every time DB1 2 gets to 100 approx every second STRING SDB1 128 32 contains Hello there Copyright www proscada com PSDIRECT driver for CitectSCADA Pseudo code for S7 IF DB1 4 0 1 THEN DB1 5 6 1 ELSE DB1 5 6 0 END IF DB1 4 1 AND DB1 4 2 THEN DB1 5 7 1 ELSE DB1 5 7 0 END DB1 4 3 blink every 1 sec Pseudo Code for S5 IF DB15 4 0 1 THEN DB15 4 14 1 ELSE DB15 4 14 0 END IF DB15 4 1 AND DB1 4 2 THEN DB15 4 15 1 ELSE DB15 4 15 0 END DB15 4 3 blink every 1 sec Copyright www proscada com PSDIRECT driver for CitectSCADA 19 Setting up the Simatic TI The PSDIRECT Driver replaces the TINECNT amp TINECWIN Drivers The TINEC drivers use the Siemens TF interface via the CP1413 card The ProScada Ethernet backend can talk to the PLC via ISO or TCP IP protocols however note that it does NOT support TF The Siemens TF system is little more than an unnecessary abstraction layer and in reality it is quite easy to transfer the system The PSDIRECT Installation installs a example project in Citect bin PSDIRECT samples The steps to migrating an existing system are as follows 19 1 1 Step 1 Adding peer peer jobs to the PLC CP card setup You can leave the old TF Jobs in place simply add these new Peer Services
46. ind PLC s like old S5 models We soon realised that others would also find it useful for quick test amp setup without having to have to setup a real PLC As such it lowers the barriers to using the PSDIRECT Driver We would not want to pretend that it is a Full emulation in particular it has not been tested against Siemens software like the OPC server or WinCC It certainly does not emulate the protocol fully but is sufficient for the ProScada Siemens Driver It is a low priority project for us with minimal support 18 3 Capabilities e Emulates Both S5 amp S7 PLC s TI sort of e Only Supports TCP IP e Automatically emulates any data block you poll with the DB s initialised to O any data written is stored like a PLC with no program running Emulates 4kb DB s up to DB 1999 M I Q memory areas are emulated as DBO e Supports 2 incoming connections so you can setup a redundant pair of SCADA IO Servers e Only Supports Rack 0 Slot 2 deliberate for training purposes e DB1 amp DB15 contain some forced values 18 4 Installation Run from the command line or explorer there are no parameters The program simply listens for Incoming connections Being a TCP IP server you need to unblock any firewall systems Note it is receiving connections on TCP port 102 When run on the same PC as the IO Server you can use the IP address 127 0 0 1 local loop back in the driver 18 5 Forced variables DB15 is in S5 format DB15 0
47. lecting Learn Addresses from the options menu This only functions while CiTect is running and the Address errors are flooding the bottom window e Note that to make the new added or stretched blocks active you need to save amp reload the configuration Copyright www proscada com PSDIRECT driver for CitectSCADA e When this is done there may still be address errors select Learn Addresses again amp reload again e This process is not perfect you may still have to edit some manually To achieve optimum performance you may still need to optimise the poll times of each block see next section You should at least sort the poll blocks in excel to tidy up Copyright www proscada com PSDIRECT driver for CitectSCADA 12 Communication Optimisation 12 1 note on performance in new version 7 9 52 This version can reads multiple block simultaneously and when upgrading you should notice an improvement in the backend driver poll rate This new version requires no additional changes it will open existing configuration files To take full advantage of this the only change to the configuration required is to set the PLC type to S7 400 in the PLC type The greatest performance improvement will be seen with configurations with large numbers of small poll blocks 12 2 How to Measure Driver Performance Create a minimal backend configuration with 1 poll block 1 variable and a poll time of 0 0 seconds Note how
48. locks e Note Changes to the back end only activate after File gt Reload 19 1 5 STEP 4 Configure Citect e Remove all TINECNT ports Just add 1 port channel for PSDIRECT I use PSPORT e Inthe IO Device fields o Set PROTOCOL to PSDIRECT4 o Set address to TI o Set ALL IO devices port to the common port for PSDIRECT PSPORT Copyright www proscada com PSDIRECT driver for CitectSCADA 20 Installing Siemens H1 ISO transport Not used for TCP IP This step is optional depending on the protocols used to talk to the PLC s if you are using TCP IP you DO NOT Require the ISO transport Please go to Section 4 Setting up the driver Now you need to install the low level Siemens H1 ISO transport This installation is only required for the Siemens Ethernet Driver 1 Open the Settings Control Panel Open the Local Area Network Properties Settings Go to the Protocols tab Press Add Press Have Disk Enter or browse to the following path lt Install disk gt ISO WIN2000 amp XPV O gr oe oe Ie Local Area Connection Prop 21x General Connect using 59 Realtek RTL8029 AS PCI Ethernet Adapter Configure Components checked are used by this connection v E Client for Microsoft Networks M5 File and Printer Sharing for Microsoft Networks X Internet Protocol TCP IP Select Network Compo 21x 4 Click the hina nf notwerl onmnnn
49. oad a to make it active in the Background polling program Then you should see fewer address errors you then need to Learn addresses again Read more Why do see Nio Address Error DB15 W248 in the bottom window when DB15 W248 is not used in any tag You have tags above amp below DB15 W248 and the CiTect block optimiser is aggregating them The PSDIRECT Driver is unable to figure out which addresses are used amp which not You have to build backend blocks spanning the entire DB not missing a single byte This may be a problem with amp Q addresses which cannot span unconfigured IO A Partial solution is to use the 32 bit PSDIRECT6 protocol am unable to get communication what are the most common problems If using ISO protocol Check that the Siemens ISO transport is installed if you see the message in the bottom window failed to open ISO channel 1 then the ISO transport is not correctly installed OR there may be a problem in the registry and the driver is not using the correct Ethernet card The read TSAP setting defaults to R 0 S 2 which means read the CPU in Rack 0 Slot 2 This is Correct for an S7 300 On a S7 400 with 2 slot power supply meaning the CPU is in Slot 3 this should be R 0 S 3 Note the Slot is the slot number of the CPU NOT the CP 443 card If you have 2 CitectSCADA s communicating to a S7 300 the third CitectSCADA connection will fail By default the S7 300 has 8 communication channel
50. on E Primary Device Connection Backup Channel Address Read TSAP Write TSAP 192 168 0 1 R 0 5 3 Not Used Backup Device Connection Optional Address Read TSAP Wa TSAR OOOO O O m 192 168 1 1 R 1 5 3 NoT USED Enable Note the Rack number of the backup CPU is 1 note specifically gave the IP addresses different subnets Ethernet cards in the IO server you probably have twin Ethernet networks Copyright www proscada com PSDIRECT driver for CitectSCADA 17 2 1 Notes e A potential issue is that the CiTect Frontend IO device takes 2x longer to failover while the Backend is doing its failover sequence The timers that affect this are the settings in the channel setup backend We recommend settings do not set any lower o timeout time 3 sec o Delay 30 sec o Retries 1 e You can monitor which connection the backend is using via the debug addresses e Unfortunately you cannot at present force the backend to switch over manually e Read more about monitoring the status in Using the Special Debug addresses Copyright www proscada com PSDIRECT driver for CitectSCADA 18 Using the S7 Simulator application 18 1 What is it The small console application S7simulator exe may be downloaded from a link on http www proscada com Citect htm 18 2 Introduction why a PLC simulator We originally wrote this as a simple application to regression test the driver particularly to test hard to f
51. protocol Siemens H1 ISO Transport This protocol is supplied with the driver No Siemens hardware or software is required at the CitectSCADA side The Polling of Blocks of data from the PLC is performed by the hidden application lt Xxx gt SPOLL EXE This application is started whenever client applications request data On start up the last configuration file used is opened The application copies the configuration file into a memory mapped file MMF CACHE and then updates all polled data to the MMF The tag interface DLL SIXSTSR DLL converts IO address strings into internal references to find the data in the MMF The PSDirect DLL is a standard CitectSCADA Array block driver which reads the tags using Native PLC address references This means you can configure an IO Server with a minimal Comms project and run different tag projects on the Display Clients as per normal CitectSCADA conventions Copyright www proscada com PSDIRECT driver for CitectSCADA 3 3 1 3 2 3 3 Setup guide Step 1 Install the PSDIRECT CitectSCADA front end driver This is provided as a standard CitectSCADA Driver install package just run the Setup exe provided and make sure you choose the correct install directory for the version of CitectSCADA Note After installing It is recommended that you copy CitectSCADA Bin PROTDIR DBF to both the user lt project gt Include AND the main or Comms Projects ref KB Q2546 Step 2 Install the
52. readback occurred have redundant PLC s can configure redundancy at a lower level than the Citect level ie use a single Citect IO device but 2 IP addresses in the backend OR Does the driver support the S7 400H hotstandby PLC Yes simply configure the second IP addresses amp rack amp slot in the Backup fields read more in Configuring for Redundancy How do I debug the operation of the low level backend redundancy read the section on Using the Special Debug addresses Is the PSDIRECT Configurator designed to import addresses from arrays E g in Citect you can define an integer tag array with an address that looks something like DB10 0 20 However the import functionality does not work with arrays in the back end Arrays are supported the data has to be polled in the backend so if DB10 0 20 is a LONG or REAL all examples assume 32bit the poll block has to be at least DB10 0 to DB10 79 As of Backend 7 9 51 005 the database import now supports Arrays You can however solve this problem online in seconds during runtime e if you open the Driver configurator while Citect is running amp open a page with address references that are not currently being polled you will see in the bottom window messages like NIO Address error DB10 D4 NIO Address error DB10 D8 e Now off the options menu select Learn Addresses you should see DB10 0 to DB10 3 change to DB10 0 to DB10 79 you may have to go to another PLC amp back
53. rols CiTect Tag Addressing Notation CiTect Data Type Comment SPI Select ON Long Pulse SPI lt Object No gt INT Write 137 SPI Select OFF Long Pulse SPI lt Object No gt INT Write 136 SPI Execute ON Long Pulse SPI lt Object No gt INT Write 9 SPI Execute OFF Long Pulse SPI lt Object No gt INT Write 8 SPI Selected Feedback SPI lt Object No gt SELECTED DIGITAL Indicates after RTU has replied to Select command SPI Negative Acknowledgement feedback SPI lt Object No gt NEGC DIGITAL Indicates after RTU has replied to Select command DPI Select ON Long Pulse DPI lt Object No gt INT Write 138 DPI Select OFF Long Pulse DPI lt Object No gt INT Write 137 DPI Execute ON Long Pulse DPI lt Object No gt INT Write 10 DPI Execute OFF Long Pulse DPI lt Object No gt INT Write 9 DPI Selected Feedback DPI lt Object No gt SELECTED DIGITAL Indicates after RTU has replied to Select command DPI Negative Acknowledgement feedback DPI lt Object No gt NEGC DIGITAL Indicates after RTU has replied to Select command Copyright www proscada com PSDIRECT driver for CitectSCADA 21 10 Time Stamped Alarms This Driver supports RTU generated timestamps to use this feature use Configure Time stamped Alarms Configure the Variable Tag typically this is a Digital addressed to the VAL bit e g SPI lt n gt VAL for analogs you will need to define your alarm in a Cicode function tha
54. rs Copyright www proscada com PSDIRECT driver for CitectSCADA 5 S7 STRING datatype is supported using the SDB address The values may be written from CiTect amp the string length byte in the PLC will be set by the driver The string will only read write upto the max string len in the PLC There are serious limitations however a ONLY 1 STRING is supported per DB or at least block size apart 1 byte amp last byte of adjacent strings must be gt 256 bytes apart b The CiTect array size MUST be lt 127 bytes Always set CiTect Array size PLC string len 6 The following addresses are not supported m T Siemens Timer a C Siemens Counter Note Siemens Timer amp counters in TM amp TDB memory IS supported An Additional Address the SW addresses is available for status amp debugging please read Using the Special Debug addresses Copyright www proscada com PSDIRECT driver for CitectSCADA 8 6 1 2 Siemens S5 Addressing The Siemens S5 Addressing is designed to emulate the SIEMENS DBF protocol This may differ from the TF Sinec or applicom addressing The address format is almost identical to that used in the Step 5 programming software Data Types Address Format CitectHMI SCADA Data Type DATA BCD DIGITAL INT LONG LONGBCD WORDS D lt data block gt lt word gt REAL STRING DIGITALS D lt data block gt lt word gt lt bit gt DIGITAL DATA BCD DIGITAL INT LONG LONGBCD WORDS DX
55. s 2 for step 7 2 for SCADA 4 for PLC PLC This configuration can be changed in later model CPU s The S7 400 seldom encounters this problem because it has 8 connections How do update the configuration after making changes Or Why do newly added blocks show a status Copyright www proscada com PSDIRECT driver for CitectSCADA A Remember the configurator is not actually polling the PLC s The background polling program sixspoll exe is doing that Save the file then Select File Reload off the menu or press 2 This saves the configuration and tells the background polling program to stop amp reload it s configuration into memory During this process you may see COM in Citect have problems reading Direct S7 IO 1 Q PI etc what do do You need to make sure that the poll blocks exactly match the configuration in the PLC The PLC WILL NOT allow you to poll across an address for which no IO cards exist You need to break this up into smaller blocks Note Citect Does not recommend writing directly to outputs for safety reasons How do setup the IO server to enable redundant CitectSCADA IO Servers The driver behaves like all Citect drivers in this regard eg The same as S7NT Set the INI file parameter AlwaysReturnNoError 0 this is default so this parameter need not exist The poll block SO gt S199 must be defined in the driver backend poll configuration Being a frontend backend driver
56. scribes the Special Tag addresses available for debugging purposes All datatypes are INT STO Connection current connection number an internal value this is normally static is only meaning full when backup addresses are used ST2 Conn State 0 means trying to connect to PLC 2 means Connected ST24 Reconnections Increments every time the driver attempts to reconnect after the connection failure If this is going up you have a bad network ST26 Pollrecs per sec Poll rate for this PLC useful for checking optimisation The rate shown at the bottom status block of the configurator should be the sum of these ST28 Disconnect Req s Increments when PLC sends Disconnect Request This Means that your Network is OK but the CP 143 setup is not The PLC is refusing connection requests ST32 PDU size PLC request block size 240 or 480 bytes ST40 Primary connection Connection number ST42 Primary connection state 2 means connected ST80 Backup connection Connection number of backup connection ST82 backup connection state 2 means connected 10 1 1 Redundancy control When using the Backup IP address the following logic may be used to indicate which connection is active ST0 ST40 means that the Primary IP address is being polled ST0 ST80 means that the Backup IP address is being polled Writing 1 to STO causes the driver to connect to the Backup connection Writing 2 to STO causes the driver to connect to the Primary connection 10 2 For th
57. t returns a Digital The Timer Expr Field MUST be set to a LONG tag addressed to one of the T addresses e g TSPI lt n gt Where lt n gt is the same in both Fields Note this CITECT INI setting Alarm HresType 7 Copyright www proscada com
58. tting defaults to R 0 S 2 which means read the CPU in Rack 0 Slot 2 This is Correct for an S7 300 On a S7 400 with 2 slot power supply meaning the CPU is in Slot 3 this should be R 0 S 3 Note the Slot is the slot number of the CPU NOT the CP 443 card For the S7 200 PLC Set the read TSAP to CP243 because the S7 200 does not comply with the rack amp slot system Now Reload the configuration by pressing the 2 button This is IMPORTANT always reload any configuration change changes The configurator works on the configuration file on disk the reload command loads that into memory briefly interrupting the polling as it does so Now check that you have communications The transmit and receive counters at the bottom of the window should increment The Status of the MO block should change toa Y Copyright www proscada com PSDIRECT driver for CitectSCADA 4 1 Setting Up using the serial MPI The Serial S7 Driver uses a different Backend driver to the Ethernet however the configuration is almost identical The main difference is the Channel settings where you setup the com port amp baud rates The Local MPI address is normally 1 if you have 2 SCADA s on the network then you need to set SCADA a to 1 amp SCADAB to 2 No PLC may then use 2 amp enable the Multi master setting Channel 1 Communication Settings Hardware Setup Error Handling Port com Reply Timeout 5 0 Baud Rate 19200 Delay 1 0
59. uration 11 2 1 Backend IO devices The Back end configuration may be edited in bulk using excel amp File Save As CSV Save the default configuration to CSV and then edit it in Excel and copy data from the UNITS DBF file above From the Options Menu Select Import Variables In the file dialog select the user lt comms project gt directory and open UNITS DBF If you have a redundant CiTect system it will have imported 2 devices per PLC delete all duplicates Make sure each Device has a STO to ST200 IO block THIS IS NOT A PLC ADDRESS it is internal driver status used by the front end to check unit status You will need to manually set the network Addresses for each PLC Remember to Save amp Reload to make the configuration active 11 2 2 Backend IO Blocks Each CiTect tag must be contained inside a backend poll block The data type of each block is BYTE any CiTect data type tag can be read from these blocks If CiTect attempts to read from an address that is not currently polled you will get an NIO IO address error in the bottom window of the configurator There are 2 methods of semi automatically creating these blocks From the Options menu select Import Variables e Inthe file dialog select the user lt root project gt directory and open VARIABLE DBF or _VARIABL RDB e Remember to Save amp Reload to make the configuration active 2 After creating the Backend devices you can remove any address errors by se
60. very tedious Multiple IO servers have to be used to communicate to more than 20 PLC effectively The PSDIRECT driver will take 5 minutes to install The driver works with any standard 10MB 100MB or 1GB Ethernet card To date more than 50 PLCs on a single system have been tested with one standard 100Mb card Multiple Ethernet cards can be used to communicate to PLCs however there are no real performance or reliability gains The driver works equally well sharing CitectSCADA Windows workgroups amp Siemens ISO thru 1 Ethernet card A good Ethernet switch handles different link speeds amp network node isolation amp redundancy The PLC s are the bottlenecks amp the total Ethernet bandwidth used by the Ethernet card is lt 5 typically This driver maximises the communication to all the PLC s on you network by implementing a multithreaded parallel polling strategy This driver supports up to 128 PLC s on one Network It has been proven on a system with 50 PLC s amp 80 000 IO Copyright www proscada com PSDIRECT driver for CitectSCADA 2 Structure of the driver The different protocol levels are displayed in the table below Citect82 EXE PSDirect DLL standard CiTect driver lt xxx gt STSR DLL depends on protocols Driver Poll Cache Memory mapped file SIXSPOLL EXE back end polling Siemens H1 ISO Transport OR TCP IP The flow of information in the driver starts at the network

Driver User manual Document

Contents

Download Pdf Manuals

Related Search

Related Contents