UNICOS PVSS (WinCC OA) Project Maintenance

Transcription

1 CERN CH1211 Geneva 23 Switzerland EDMS NO. REV. VALIDITY DRAFT REFERENCE XXXX Date : EN-ICE Workshop 2012 UNICOS PVSS (WinCC OA) Project Maintenance Proposal of guidelines DOCUMENT PREPARED BY: DOCUMENT CHECKED BY: DOCUMENT APPROVED BY: UNICOS core team EN-ICE BOCCIOLI Marco

2 Page 2 of 22 HISTORY OF CHANGES REV. NO. DATE PAGES DESCRIPTIONS OF THE CHANGES all Creation

3 Page 3 of 22 TABLE OF CONTENTS 1. Introduction Instructions for developers of EN SCADA applications How to manipulate Managers, open Project Administrator or Project Console Using the UNICOS HMI On the Data Server... Error! Bookmark not defined. 3. UNICOS System Integrity Operation UNICOS System Status Alarm archive parametrization UNICOS System Integrity Configuration Open front end diagnostic S7 PLC front-end Timing error SOFT_FE front-end UNICOS archive System Integrity Modifying the system integrity configuration on the archive Disabling the system integrity configuration on an archive Enabling the system integrity configuration on an archive UNICOS PVSSDB internal configuration References... 22

4 Page 4 of Introduction This document is a selection of maintenance instructions taken from the CERN-EN-ICE Standby Service Wiki pages (for internal use see References). In some cases, they might apply only to the specific setup made at CERN.

5 Page 5 of Instructions for developers of EN SCADA applications This page provides the information for the developers of EN/ICE SCADA applications using PVSS/WinCC-OA. Note that these are internal procedures, specific to the EN/ICE SCADA Application environment (ie. PVSS running on the Linux data servers) and should not be considered as applicable for any general use out of the scope of EN SCADA Application Service. 2.1 How to manipulate Managers, open Project Administrator or Project Console To administer the managers of PVSS/WinCC OA there are three options 2.2 Using the UNICOS HMI start/stop/ etc. unicos_scripts, undevicelistupdate, unbackup: (local, remote, scattered): start unicoshmi, click on the system status box, select an application name in the list, double click on one of the three box, you can start, etc. you need to be loged in with admin priviledge start/stop/etc. driver of a dedicated front-end: click on the front-end tool (front-end icon on the top of the unicoshmi), select the system and the front-end, click on the driver box like S7, MODBUS, CMW, etc. and same interface as above, you also need to be logged in as admin

6 Page 6 of 22 start/stop/etc. the dist manager on the local system only: click on the unicos icon (top left of the panel), then see picture, you also need to be logged in as admin start/stop/ etc. System Integrity script (unicos_scripts.lst) on local system only: click on the unicos icon (top left of the panel), then see picture, you also need to be logged in as admin

7 Page 7 of 22 start/stop any manager on local/remote system, local UI/scattered UI: click on the unicos icon (top left of the panel), then see picture, you also need to be logged in as admin, select the system, if you right click on a line in the driver or control table you can start/ etc., if you select a manager in the combo box and put the correct command line syntax you can also add/start, etc. (see picture) since unicos_framework-5.2.2, when a unicos ctrl scripts starts you have in the bottom of the page

8 Page 8 of 22 (message text, a kind of logging) the version of the component loaded for a given script: you can also online get the system integrity component running in the server (running in the CTLR script, not in the UI): click on the unicos icon, see picture, select a system and a component, and click on the button version 3. UNICOS System Integrity Operation To open the System Integrity panel: click on the icon of the application (top left corner) select Management->Diagnostic->System Integrity (local)

9 Page 9 of 22 select the system name and the component in the System Integrity operation panel Note: this panel cannot be opened at the same time as the System Integrity Operation panel to enable or disable an alarm double click on a line and right click, select Enable or Disable from the pop-up menu (appropriate user access right are needed) Each System Integrity component instance provides systemalarm (DP Type: _UnSystemAlarm). An instance can be: enabled: green, red or orange colour, the systemalarms are evaluated, the PVSS alert_hdl are activated. disabled: yellow colour, all PVSS alert_hdl of the systemalarm instances are de-activated. There is no alarm evaluated and produced. The alarm can be raised for alarm value >= 10 or < 10, this depends on the configuration. 4. UNICOS System Status To open the system status panel:

10 Page 10 of 22 double click on the system status box (top centre) click on the button System Integrity Alarm List (top right corner of the system status panel) 5. Alarm archive parametrization To open the alarm parametrization panel: click on the icon of the application (top left corner) select Management->Diagnostic->Utilities (local)->alarm archive

11 Page 11 of 22 Alarm parametrization panel: to modify the alarm file switch setting: configure the File cycle frequency and the deletion cycle frequency and click on the Activate button (top part of the panel) to do an alarm file switch, click on to set a periodic alarm file switch o o o o set the File cycle frequency set the deletion cycle frequency unselect the check box Delete only archived files automatically click on the Activate button (top part of the panel)

12 Page 12 of 22 to check the periodicity of the alarm file switch: make the time difference between two consecutive files 6. UNICOS System Integrity Configuration To open the System Integrity Configuration panel: click on the icon of the application (top left corner) select Configuration->System Integrity (local)

13 Page 13 of 22 select the component in the System Integrity configuration panel Note: this panel cannot be opened at the same time as the System Integrity Operation panel Each System Integrity component instance provides systemalarm (DP Type: _UnSystemAlarm). An instance can be: enabled: systemalarm are evaluated, PVSS alert_hdl are activated disabled: all PVSS alert_hdl of the systemalarm instances are de-activated. There is no alarm evaluated and produced. The alarm can be raised for alarm value >= 10 or < 10, this depends on the configuration. 7. Open front end diagnostic To open a front-end panel: click on the icon of the application (top left corner) and select Management->Diagnostic->Front-End

14 Page 14 of 22 or click on (top centre area), select a DS and a front-end in the list 8. S7 PLC front-end To open the S7_PLC front-end panel: Procedure Open front end diagnostic (Section 6) and select the S7_PLC front-end or right click on the S7_PLC front-end widget and select Front-end diagnostic, or double click on the S7_PLC front-end widget S7_PLC front-end panel: Note: the S7_PLC front-end on remote can be accessed via the front-end panel In the PLC->DS communication (centre left side of the S7_PLC front-end panel)

15 Page 15 of 22 invalid check box: set=timestamp invalid, false=timestamp valid counter value time stamp: counter value time stamp In the PLC alarm (centre right side of the S7_PLC front-end panel), the types of alarms are: Communication alarm (TSPP watchdog): alarm raised if the counter value is not updated or not updated faster than the checking delay (see below) Time synchro alarm: alarm raised if the time stamp is too far in the past (10 min. in the past compared with current time) or the time stamp of the counter value is invalid (see also below) S7 driver TSPP/polling connection alarm: alarm raised if the S7 polling or TSPP is not connected or if there is a S7 error code for the PLC (connected state and error code in the Polling run-time data and TSPP run-time data) import file version alarm: if the PLC and PVSS version, if the version are different an alarm is raised Communication alarm: PLC system alarm produced by the PLC, this type of alarm is used to show communication problem between PLC or with fieldbus node front-end system alarm. Note: if the front-end System Integrity status is disabled, the alarms colour are yellow. In the TSPP and Polling run-time data (bottom right side) error code: S7 error code connected: state of the conection to the PLC, true (set)=connected, false (not set)=not connected Se.F: number of send frame of the S7 connection Re.F: number of received frame of the S7 connection Rj.F: number of rejected frame of the S7 connection In the Vers. (bottom centre side) the PLC version the PVSS version of the PLC In the S7 static data (bottom left side) TSPP and Polling device number TSPP and polling timeout: transaction timeout, timeout between the S7 request and the S7 response in milliseconds Global information (top left side) PLC type: S7-400 or S7-400 PLC name _S7_Conn DP: internal S7 DP driver: S7 driver number send ip: if the state is enabled, the send ip switch periodically (IP Sending delay (msec) in the S7 PLC System Integrity panel) from 0 to a number. DS ip: data server IP number import version Last GQ: time of the last GQ set for the PLC (this does not mean that a Request all PLC data was requested) The following actions are available:

16 Page 16 of 22 synchronize the PLC date and time: click on the Synchronize the PLC date and time button (top centre side of the MODBUS front-end panel), no action, just for backward compatibility request a get all data: click on the Request all PLC data button, the GQ for the PLC is set and the PLC will send all its current data To open the S7 PLC System Integrity configuration (Procedure UNICOS System Integrity Configuration, Section 6) and click on unicoss7plc the PLC Checking delay (sec.) can be modified: periodically every PLC Checking delay (sec.) the PLC front-end counter is checked, an alarm is raised if the counter was not updated if the time stamp of the counter is invalid or too far (10 min.)in the past, a time alarm is raised IP Sending delay (msec): alternatively the DS IP and 0 is sent to the PLC every IP Sending delay PLC Time Synchro delay (sec): every PLC Time Synchro delay the current DS time is sent ot the PLC, this is to periodically syncrhonize the time and date of the PLC PLC GQ (nb checking delay): every PLC GQ time of PLC Checking delay a GQ for the PLC is set (this is not a Request all PLC data was requested), -1 means no GQ. 8.1 Timing error. The S7_PLC PLC clock is synchronised by NTP, the S7_PLC clock time is always UTC. The PLC program cannot start if the clock is not synchronised via NTP (the NTP must be correctly configured in the PLC). Note: the PLC time must be UTC time, because the PLC program sends to PVSS the data with the time of acquisition, and this timestamp must be in UTC. When the PLC is reloaded (full reload of the program) the PLC clock is synchronised by NTP.. If there is still some data which are not updated, one has to issue a get all data from the S7_PLC front-end panel (see above). 9. SOFT_FE front-end To open the SOFT_FE front-end panel:

17 Page 17 of 22 Procedure Open-front-end-diagnostic (Section 7) and select the SOFT_FE front-end or right click on the SOFT_FE front-end widget and select Front-end diagnostic, or double click on the SOFT_FE front-end widget SOFT_FE front-end panel: Note: the SOFT_FE front-end on remote can be accessed via the front-end panel In the FE->DS communication (centre left side of the CMW front-end panel) invalid check box: set=timestamp invalid, false=timestamp valid counter value time stamp: counter value time stamp In the FE alarm (centre right side of the CMW front-end panel), one type of alarm: Communication alarm: alarm raised if the counter value is not updated or not updated faster than the checking delay (see below) Note: if the front-end system Integrity status is disabled, the alarm colour is yellow.

18 Page 18 of 22 To open the SOFT_FE System Integrity configuration (Procedure UNICOS System Integrity Configuration, Section 6) and click on SOFT_FE the SOFT_FE Checking delay (sec.) can be modified: periodically every SOFT_FE Checking delay (sec.) the SOFT_FE front-end counter is checked, an alarm is raised if the counter was not updated 10. UNICOS archive System Integrity 10.1 Modifying the system integrity configuration on the archive Open the system Integrity configuration panel for the archive: Procedure UNICOS System Integrity Configuration, Section 6, click on archive

19 Page 19 of 22 The following parameters can be modified to avoid the alarm archive errors: alarm file size checking delay (sec.): periodic time at which a check on the alarm folder and file size is done. If the files size or folder is too big an alarm is raised The following parameters can be modified to avoid the valarch archive errors: valarch file switch checking delay (sec.): periodic time at which a check on the periodicity of the file switch is done. If during that time there was a file switch (one or more than one) an alarm is raised Update stats max retry: maximum retry of valarch get statistics Update stats max delay: maximum time to wait to check the result of the valarch get statistics Max missing update: maximum number of consecutive occurence of a bad get valarch statistics. Each valarch file switch checking delay (sec.), a request to get valarch statistics is done, if after Update stats max delay the statistics are not udpated a retry is done until Update stats max retry: if the statistics are still not updated, this is considered as a bad get valarch statistics. If the same occurs consecutively Max missing update (at the file switch checking delay period) an alarm is raised. If at the next file switch checking delay period there is still a valarch get stats error, the valarch is killed. If at the next file switch checking delay period there is still a valarch get stats error and the manager is stopped, it is restarted. And so on indefinitely until the error disapears. Example: valarch file switch checking delay (sec.): 600 Update stats max retry: 3 Update stats max delay: 10 Max missing update: 2 Behaviour: Every 10 min a valarch get stats is issued, if the valarch manager does set the stats in 10 sec. a second valarch get stats is issued, and a third time if the valarch manager does not set the stats: no update of stats in 30 sec. 10 min after, the same process starts, after 30 sec. if the the valarch manager does not set the stats, an alarm is raised 10 min after, the same process starts, after 30 sec. if the the valarch manager does not set the stats, the valarch manager is automatically killed (the pmon should restart it) 10 min after, the same process starts, after 30 sec. if the the valarch manager does not set the stats, is automatically started and so on.

20 Page 20 of Disabling the system integrity configuration on an archive Open the System Integrity configuration panel for the archive: Procedure UNICOS System Integrity Configuration, Section 6, click on archive select the archive name in the list of archives (bottom list) Note: the list of alarm name (upper list) is based on the PVSS valarch DPE select disable in the combo box (just above the proceed button) click on proceed the selected archived will be removed from the list of archive alarm state (top list), this alarm is still existing (in the System Integrity Operation panel: Procedure UNICOS-System Integrity Operation - Section 3, click on archive, systemstatus: Procedure UNICOS-system Status Section 4, etc.) and is masked. there is more checking on this archive, the algorithm described above (in the first section) is disabled for this archive.

21 Page 21 of Enabling the system integrity configuration on an archive Open the System Integrity configurationpanel for the archive: Procedure UNICOS System Integrity Configuration, Section 6, click on archive select the archive name in the list of archives (bottom list) Note: the list of alarm name (upper list) is based on the PVSS valarch DPE select enable in the combo box (just above the proceed button) click on proceed the selected archived will be added in the list of archive alarm state (top list) with Al or Ok state. the algorithm described above (in the first section) is enabled for this archive. 11. UNICOS PVSSDB internal configuration To open the UNICOS PVSSDB internal configuration: Procedure Procedure UNICOS System Integrity Configuration, Section 6 click on the Internal Configuration buttom (top left corner) select PVSSDB in 4. Config Data: o the first parameter is the checking time in sec.

22 Page 22 of 22 o from the second parameter: list of file to check: : periodically a check is done on the size of the files 12. References This document is a collection of maintenance instructions taken from the CERN-EN-ICE Standby Service Wiki pages: