CREATION AND CONFIGURATION OF A PVSS (WINCC...

93
LHC Project Document No. LHC-UNICOS CERN Div./Group or Supplier/Contractor Document No. EN/ICE EDMS Document No. Date: 2012-SEP-21 the Large Hadron Collider project CERN CH-1211 Geneva 23 Switzerland INSTALLATION SPECIFICATION CREATION AND CONFIGURATION OF A PVSS (WINCC OA) - UNICOS APPLICATION Abstract This document details the procedure to develop a PVSS-UNICOS application, the installation in new computer at CERN and the integration with a running PVSS-UNICOS application. Prepared by: UNICOS core team EN-ICE BOCCIOLI Marco Checked by: Approved by:

Transcript of CREATION AND CONFIGURATION OF A PVSS (WINCC...

LHC Project Document No.

LHC-UNICOS

CERN Div./Group or Supplier/Contractor Document No.

EN/ICE

EDMS Document No.

Date: 2012-SEP-21

the

Large Hadron Collider project

CERN CH-1211 Geneva 23 Switzerland

INSTALLATION SPECIFICATION

CREATION AND CONFIGURATION OF A PVSS (WINCC OA) - UNICOS

APPLICATION

Abstract

This document details the procedure to develop a PVSS-UNICOS application, the

installation in new computer at CERN and the integration with a running PVSS-UNICOS

application.

Prepared by:

UNICOS core team EN-ICE

BOCCIOLI Marco

Checked by:

Approved by:

LHC Project Document No.

LHC-UNICOS

Page 2 of 93

History of Changes

Rev. No. Date Pages Description of Changes

1.1 Draft

1.2 Draft

1.3 Draft

1.4 Draft

1.5 Draft

1.6 Draft

1.7 Draft

1.8 Draft

1.9 Draft

1.10 Draft

1.11 Draft

1.12 Draft

1.13 Draft

1.14 Draft

1.15 Draft

1.16 Draft

02-Jul-2003

14-Jul-2003

06-Aug-2003

18-Sep-2003

11-Mar-2004

25-Mar-2004

27-May-2004

22-Nov-2004

30-Mar-2005

05-Jul-2005

29-Aug-2005

14-Jan-2006

18-Jul-2006

21-Apr-2008

22-Sep-2012

First draft

Correction

Add: be in administrator group when creating starting a PVSS

project.

Add comment from developers and the trend tree part

Update to unicos-jcop-2.1

Update to unicos-jcop-2.2

Update to unicos-jcop-2.3

Update to unicos-jcop-3.0

Update to unicos-jcop-3.1

Update to unicos-jcop-3.3

Update to unicos-pvss-3.4

Update to unicos-pvss-3.5

Update to unicos-pvss-3.6

Update whole document for unicos-pvss-3.8 (BF and BB)

Update the whole document for unicos-pvss-3.8-SP2. Add S7

LHC Project Document No.

LHC-UNICOS

Page 3 of 93

Table of Contents

1. INTRODUCTION ....................................................................................... 5

1.1 PURPOSE OF THIS DOCUMENT .................................................................. 5

1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ......................................... 5

1.3 CONTACT AT CERN .................................................................................. 5

1.4 NAMING CONVENTION ............................................................................. 5

2. HARDWARE PLATFORM............................................................................ 6

3. SOFTWARE NEEDED ................................................................................. 6

4. DEVELOPMENT PROCEDURE .................................................................... 6

4.1 PROCEDURE ............................................................................................ 6

4.2 INFORMATION TO COLLECT FOR THE PROJECT ............................................ 7

4.3 CONFIGURING THE WINCC OA UNICOS PROJECT ........................................ 7 4.3.1 FILE SWITCH OF THE ARCHIVE ........................................................................... 11

4.4 SET UP OF THE UNICOS-S7 COMMUNICATION........................................... 12

4.4.1 PROCEDURE ..................................................................................................... 12 4.4.2 FRONT-END DIAGNOSTIC ................................................................................... 13

4.5 SET UP OF THE UNICOS-MODBUS COMMUNICATION .................................. 13 4.5.1 PROCEDURE ..................................................................................................... 14 4.5.2 TYPICAL ERRORS .............................................................................................. 15 4.5.3 FRONT-END DIAGNOSTIC ................................................................................... 18

4.6 VALIDATION OF THE UNICOS DEVICES .................................................... 18

4.7 SYNOPTICS AND WINDOWTREE ............................................................... 20

4.8 TRENDTREE CONFIGURATION ................................................................. 31

4.9 SYSTEMINTEGRITY CONFIGURATION ....................................................... 44

4.10 APPLICATION CONFIGURATION ............................................................... 56

4.11 MODIFICATION OF THE CONFIGS OF THE DEVICE ..................................... 62

4.12 CONFIGURATION OF EMAIL..................................................................... 64

4.13 MESSAGETEXT ...................................................................................... 65

4.14 ALARM ARCHIVE CONFIGURATION ........................................................... 67

4.15 PACKAGING TO THE TARGET APPLICATION ............................................... 68

5. INSTALLATION IN A NEW DS ON CERN SITEERROR! BOOKMARK NOT DEFINED.

6. INSTALLATION IN A RUNNING DS ......................................................... 68

6.1 DEVELOPMENT OF THE APPLICATION ....................................................... 68

6.2 DESCRIPTION OF THE PROCEDURE .......................................................... 69

6.3 BACKUP OF THE RUNNING CONFIGURATION ............................................. 70

7. BEHAVIOUR OF THE DEVICE IN A DISTRIBUTED ENVIRONMENT ........... 74

7.1 BEHAVIOUR OF THE DEVICE ANIMATION .................................................. 74

7.2 PROCEDURE .......................................................................................... 75

8. MODIFY THE DEVICE TYPE DATA OR ADD A NEW DEVICE TYPE ............. 76

8.1 MODIFYING THE DEVICE TYPE FUNCTIONS ............................................... 77

8.2 MODIFYING THE FRONT-END DEVICE TYPE FUNCTIONS ............................. 77

LHC Project Document No.

LHC-UNICOS

Page 4 of 93

8.3 MODIFYING THE SYSTEMINTEGRITY DEVICE TYPE FUNCTIONS ................... 78

9. OTHER UTILITIES .................................................................................. 79

9.1 EXPORT OF THE UNICOS DEVICE ............................................................. 79

9.2 EXPORT OF TRENDTREE/WINDOWTREE .................................................... 80

9.3 IMPORT OF TRENDTREE/WINDOWTREE .................................................... 80

9.4 USER DEFINED POP-UP PANEL ................................................................ 82

9.5 MASKING OF EVENT ............................................................................... 82

9.6 DEVICE LINK ......................................................................................... 85

9.7 ANADIG/ANALOG DEVICE ....................................................................... 85

9.8 BACKUP OF THE APPLICATION................................................................. 86

APPENDIX A: WIDGET CONVENTION ............................................................ 87

APPENDIX B: FACEPLATE AND CONTEXTUAL BUTTON ................................... 90

APPENDIX C: LIST OF FIGURES ..................................................................... 92

LHC Project Document No.

LHC-UNICOS

Page 5 of 93

1. INTRODUCTION

1.1 PURPOSE OF THIS DOCUMENT

This document details the step by step procedure on how to develop a PVSS-UNICOS

application. It is a natural following of the document CREATION OF A WINCC OA - CPC

6 APPLICATION. The content of that document is intended as already executed before

following the content of this document. Procedure on creating a WIN CC OA project

and importing CPC devices can be found in the mentioned document.

1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

From this point onwards, the following acronyms will be used:

Ev: PVSS Event Manager.

Db: PVSS Database manager.

Arch: PVSS Archive manager, archiving of the values.

Ctrl: PVSS Control script manager.

Drv: PVSS Driver manager, e.g.: UNICOS-MODBUS driver.

DS: Data Server. This is a computer running the PVSS core managers: Ev,

Db, Arch, Ctrl, Drv

Quantum: PLC.

Premium: PLC.

OWS: Operator Workstation.

DPT: PVSS data point type

DPE: PVSS data point element

Device: UNICOS object, this is a DPT

Panel: PVSS panel

Synoptic: PVSS panel

Hierarchy: this is a way of classifying the elements and accessing them via a top

bottom link (parent-child).

Node: virtual folder of a hierarchy, for example a folder on a disk is a node.

However all the folders of the disk are not represented as node in the hierarchy

View: top hierarchy, for example the C disk in a computer is a view

Trend: PVSS trend containing maximum 8 curves

Plot: container of one trend

Page: container of maximum 6 plots

1.3 CONTACT AT CERN

Any problem during installation or development can be reported to the following email

address: [email protected].

1.4 NAMING CONVENTION

As a general rule, the following characters must not be used to name folders, files,

panels, DP, DPE, device name, device type, PVSS system name and PVSS project

LHC Project Document No.

LHC-UNICOS

Page 6 of 93

name: ' ', @, #, $, %, ^, &, *, (, ) [, ], {, }, :, ", <, >, `, ~, !, /, ?, |, \, +, =, and ,.

Use instead _.

2. HARDWARE PLATFORM

For the development of the PVSS-UNICOS application the following hardware will be

needed:

WindowsXP, Windows2003, Windows7, Windows2008 computer with minimum

800Mhz Pentium III CPU, 1Gb of RAM

Screen resolution: 1280x1024 minimum.

3. SOFTWARE NEEDED

The following software must be installed:

Excel and Internet Explorer.

PVSS 3.x and the latest patches installed.

Please note that if PVSS is already installed, it is better to de-install it, re-install it

again and apply the patches.

Do not use the „ ‟ and „-‟ character In reply to: the folder and path name of the PVSS

installation folder, use instead the „_‟ character or the capital letters. E.g.:

C:\ETM\PVSS2

The UNICOS core team will provide the following zip files:

Latest UNICOS-PVSS version : unicos-pvss-x.x.zip

The component installer must be downloaded from the EN/ICE web site:

http://www.cern.ch/wikis/display/EN/PVSS+Service+Download+3.8SP2

4. DEVELOPMENT PROCEDURE

4.1 PROCEDURE

The Windows computer will act as a DS1 and OWS.

To develop the application the following procedure can be applied:

1. Collect information on the project: Section 4.2

2. Create a PVSS project, set up the PLCs and install the components refer to

document CREATION OF A WINCC OA - CPC 6 APPLICATION.

3. Set-up the UNICOS-S7 communication: Section 4.4

4. Validate the UNICOS devices: Section 4.6

5. Develop the synoptics and configuration of the WindowTree: Section 4.7

6. Configure the TrendTree: Section 4.8

7. Configure the systemIntegrity: Section 4.9

8. Configure the application security: Section 4.10

9. Modify if necessary the configs of the devices: Section 4.11

10. Configure the email: Section 4.12

11. Configure the alarm archive: Section 4.13

1 For Linux DS computer, contact the UNICOS support.

LHC Project Document No.

LHC-UNICOS

Page 7 of 93

12. Package the development to the target application: Section 0

4.2 INFORMATION TO COLLECT FOR THE PROJECT

The following information must be decided before starting the PVSS-UNICOS:

The PVSS system name and PVSS system number

The PLCs and DS hostnames

The PLCs modbus slave address (or unit address)

The ip numbers2 of the DS and PLCs can be the one used at consortium site.

4.3 CONFIGURING THE WINCC OA UNICOS PROJECT

13. Start the manager running unicos_scripts.lst. Add the created PLC into the

systemIntegrity (from the configuration menu, Figure 1 and Figure 2). Select the

unicosS7PLC option from the list (left side), select the PLCs, the add option and press the

proceed button. A click on the refresh button shows the list of the PLCs that are included

into the systemIntegrity. The time out delay to send the DS ip number (IP Sending delay

in msec.), synchronized the PLC date and time (PLC Time Synchro delay in sec.) and the

checking of the PLC state (PLC Checking delay in sec.) can also be modified. Default

settings can be restored.

2 Temporary IP numbers can be given for the development of the application in LAB, they can

be replace afterwards on the production site by re-importing the communication file (without

the Delete keywork) or by changing the IP number of the PLCs.

LHC Project Document No.

LHC-UNICOS

Page 8 of 93

Figure 1: Configuration menu.

LHC Project Document No.

LHC-UNICOS

Page 9 of 93

Figure 2: systemIntegrity configuration for unicosS7PLC.

14. From the systemIntegrity run-time panel disable the PLCs (from the Diagnostic

menu, Figure 3 and Figure 4). Select unicosS7PLC option from the list (left side). Select

the line with the text Communication PLCname by double click and then right click.

LHC Project Document No.

LHC-UNICOS

Page 10 of 93

Figure 3: Diagnostic menu.

LHC Project Document No.

LHC-UNICOS

Page 11 of 93

Figure 4: systemIntegrity run-time panel for unicosS7PLC.

15. From the PVSS Console, stop the simulation driver.

4.3.1 FILE SWITCH OF THE ARCHIVE

This step has to be done whenever the characteristics of the archive are modified.

1. From the menu Utilities (Figure 3), select Value archive.

2. Select an archive from the list and click on the Activity buttons.

3. Do the file switch (Figure 5)

LHC Project Document No.

LHC-UNICOS

Page 12 of 93

Figure 5: Archive file switch.

4.4 SET UP OF THE UNICOS-S7 COMMUNICATION

4.4.1 PROCEDURE

1. if the DS is in a local network and there is no DNS defined in the environment,

define each PLCs in the file C:\wnt\system32\drivers\etc\hosts

2. Start the S7 driver: PVSS00S7

3. Enable the PLC (if there is more than one PLC, enable one PLC at a time): Figure

4.

4. Open the Front-end diagnostic; select the PLC by double click on a PLC (Figure 3

and Figure 6). The behaviour shall be:

– The DS comm. Alarm must disappear after 30sec.

– The sent frame counter must increment

– The counter must increment, the invalid must not be set, and the time must be

more or less the current time of the DS (at least no less than 300 sec. in the past

or in the future)

– The ip number must be equal to a value and 0 every 4.5 sec.

LHC Project Document No.

LHC-UNICOS

Page 13 of 93

– The receive frame counter must increment

– The device data (from the device overview panel) must not be invalid (cyan

colour)

Figure 6: Front-end diagnostic.

5. If there is PLC-PLC communication: text of type Communication plc->plc, the

alarm state should be green (Figure 6).

4.4.2 FRONT-END DIAGNOSTIC

From the Front-end diagnostic (Figure 6), it is possible to force a synchronization of

the PLC time to the DS time, to reset the S7 error, to request all the PLC data except

the event data and to delete un-used PLC applications.

4.5 SET UP OF THE UNICOS-MODBUS COMMUNICATION

Note: this section is only for connection with Schneider PLCs. For Siemens PLC, refer

to section 4.4.

LHC Project Document No.

LHC-UNICOS

Page 14 of 93

4.5.1 PROCEDURE

6. if the DS is in a local network and there is no DNS defined in the environment,

define each PLCs in the file C:\wnt\system32\drivers\etc\hosts

7. Start the modbus driver: PVSS00mod

8. Enable the PLC (if there is more than one PLC, enable one PLC at a time): Figure

4.

9. Open the Front-end diagnostic; select the PLC by double click on a PLC (Figure 3

and Figure 6). The behaviour shall be:

– The DS comm. Alarm must disappear after 30sec.

– The sent frame counter must increment

– The counter must increment, the invalid must not be set, and the time must be

more or less the current time of the DS (at least no less than 300 sec. in the past

or in the future)

– The ip number must be equal to a value and 0 every 4.5 sec.

– The receive frame counter must increment

– The device data (from the device overview panel) must not be invalid (cyan

colour)

LHC Project Document No.

LHC-UNICOS

Page 15 of 93

Figure 7: Front-end diagnostic.

10. If there is PLC-PLC communication: text of type Communication plc->plc, the

alarm state should be green (Figure 6).

4.5.2 TYPICAL ERRORS

To find the default in the communication with the PLC use the Front-end diagnostic

panel (Figure 6) and the PVSS console log.

The MODBUS error codes (ModPlc run-time data) are:

11. 1: the PLC is not reachable (Figure 8)

12. 2: there is a timeout in the connection with the PLC, the PLC is considered as

dead.

For these two errors, the systemIntegrity handles the re-connections and reset the

error code. These errors means that the PLC is not started or not well defined in the

hosts file. Figure 9 is a typical error when the PLC is not defined in the hosts file.

LHC Project Document No.

LHC-UNICOS

Page 16 of 93

Figure 8: PLC not reachable.

Figure 9: PLC not defined in the hosts file.

13. 4 to 6: MODBUS errors. These errors are not reset by the systemIntegrity. This

must be done from the Front-end diagnostic panel by clicking on the enable/disable

button and the reset modbus error (Figure 6).

The typical errors are:

14. the Ip number is sent (every 4.5 sec. the Ip is set to a value and then to 0) the

sentFrame counter is incremented but no data are received:

– check the receiveFrame counter: it should increment

– check the counter, it should increment every 10 sec.

– check the time of counter, this is the time of the PLC, it should be the time of the

DS

– check any PLC alarms, they should be all green

– check the PLC unit modbus address (Figure 10). If the modbus PLC address is

wrong (Figure 11), the DS will reject all the received frames. The modbus address

can be changed (Figure 10) from the Utilities menu.

LHC Project Document No.

LHC-UNICOS

Page 17 of 93

Figure 10: MODBUS parameterization.

15. The colour of the events in the eventList is cyan or the time of the counter in the

Front-end diagnostic is the DS time +1msec. or the invalid is set and there is an alarm

Time synchronisation (Figure 6).

– Check the date and time of the PLC

– The data and time of the PLC must be UTC time.

16. The counter is not changing

– Start the PLC

LHC Project Document No.

LHC-UNICOS

Page 18 of 93

– The memory location of the counter may be used by something else than the

UNICOS middleware

– Check the modbus unit address (modbus slave configuration address) in the

specification and in PVSS (Figure 10). Figure 11 is a typical example of a wrong

definition of the modbus address in PVSS, in this example the Modbus address or

Unit address is in the PLC set to 4 and in PVSS set to another value.

– Check if the PLC hostname is defined in the hosts file of the DS.

Figure 11: Wrong modbus address.

In some cases it is better to restart the modbus PVSS driver.

Each PLC is also checking the state of the connections of the other PLCs it is in

communication with. For example for a Quantum communicating with a Premium, two

additional alarms will be in the Front-end diagnostic panel (Figure 6):

17. Communication Premium -> Quantum

18. Communication Quantum -> Premium

These alarms are evaluated by each PLC and reported to PVSS, this is to report that

the PLC has detected a communication problem with its partner. They should be

green, however if they are red it should not prevent the PLC-DS communication to

work fine.

4.5.3 FRONT-END DIAGNOSTIC

From the Front-end diagnostic (Figure 6), it is possible to force a synchronization of

the PLC time to the DS time, to reset the modbus error, to request all the PLC data

except the event data and to delete un-used PLC applications.

4.6 VALIDATION OF THE UNICOS DEVICES

There is no need to do a synoptic to validate the UNICOS devices.

1. Set the time-out of the automatic deselection: open the Select/deselect diagnostic

panel (Figure 12) from the Diagnostic menu (Figure 3), and set the time out of the

automatic deselection (Figure 12).

LHC Project Document No.

LHC-UNICOS

Page 19 of 93

Figure 12: Select/deselect diagnostic panel.

2. From the unicosHMI panel open the Device Overview panel (Figure 13)

3. Select the PLC, the application, the device type and press the Apply button (Figure

13). In the tree device overview, the filtering criteria can be modified by clicking on the

Filter button (Figure 14).

4. If there are more devices than free space in the screen, one can navigate between

devices of the same type by selecting the range number of devices to show (Figure 13)

5. Select the device, the contextual buttons of the device is shown in the contextual

area in the bottom left side (Figure 13)

6. If the device state is not changing according to the requested action check:

– The PLC state, PLC-DS communication into the systemIntegrity (Figure 2 and

Figure 4) or Front-end diagnostic (Figure 6).

– Check the data inside the PLC.

LHC Project Document No.

LHC-UNICOS

Page 20 of 93

Figure 13: Device tree overview.

Figure 14: Tree device overview extended filter.

4.7 SYNOPTICS AND WINDOWTREE

The synoptic can be created from the WinCC OA Graphical Editor (Gedi):

LHC Project Document No.

LHC-UNICOS

Page 21 of 93

1. Start the Gedi

2. To create a new panel

– from the PVSS00NG create a new panel, set the width to 1270 and the height to

835 and the backcol to unSynopticBackground.

– from the PVSS00NG open the template_panel.pnl located in the

installed_components/panels/vision folder and save it as the new panel

The newly created panel is saved in the current application folder.

To add widgets in the synoptic:

1. Drag/drop widgets (refer Appendix A: Widget convention for more detail) from

the UN_OBJECTS catalogue of the installed_components folder (Figure 15, and Figure

98)

2. Assign it to a device (Figure 15): systemName:Alias_of_the_device, e.g.:

qscc_p8_1:ATVAC_Q180_Analog1. The device name can be assigned later by clicking

on the ReferenceEditor: Figure 16 or entering directly the name of the device: Figure

17.

3. Drag and drop lines of fluid, arrows and static objects respectively from the

catalogue UN_LINES, UN_ARROWS and UN_STATICS (Figure 15). These objects can be

resized if necessary.

Figure 15: Drawing a synoptic.

LHC Project Document No.

LHC-UNICOS

Page 22 of 93

Figure 16: Change the device– 1.

Figure 17: Change the device – 2.

4. Any JPEG, GIF, BMP, XPM and WMF (EMF) picture format can be used, the files

must be in the picture folder of the project or of the project paths. The XPM, WMF (EMF)

can be set as shared.

5. If it is necessary, one has access to the PVSS graphical elements to its event

scripts and to the panel event scripts. Library files can be created; library function call

can be added. The new library must be added in the config file manually.

The WindowTree is created and configured during the installation. New tree view can be

created if needed, however they will not be accessible via the WindowTree icon. New tree

view can be created from the Tree Management of the Configuration menu (Figure 1 and

Figure 18)

LHC Project Document No.

LHC-UNICOS

Page 23 of 93

Figure 18: Tree management.

Hierarchy, folder, as well as panel, plot and page can be deleted from the PVSS database

(Figure 19) from the Manage Tree Deletion button accessible from the UNICOS System DPs

(Figure 18).

LHC Project Document No.

LHC-UNICOS

Page 24 of 93

Figure 19: Delete panel, plot, page, node and views.

The WindowTree configuration tool (Figure 20) is based on the Windows Internet

Explorer:

– left side: hierarchy space browser, right click menu are available

– right side: the content of the selected node, right click menu are available.

– hierarchy and panel top menu: act on the selected node on the left side

To populate the WindowTree:

1. Create a new folder: from the hierarchy top menu or via mouse right click on the

right side either into the WindowTree (Figure 21), either a given folder (Figure 22) or

either in a given panel (Figure 23).

2. Create a new panel (an empty panel will be physically created on the disk) or add

an existing panel (already created on the disk): from the hierarchy top menu or via

mouse right click on the right side either into the WindowTree (Figure 21), either a given

folder (Figure 22) or either in a given panel (Figure 23).

3. A folder can be linked to a panel: from the panel top menu, PVSS $-parameter

(Figure 24) can be entered at this time.

4. A panel can be unlinked: from the panel top menu (Figure 23).

5. If a folder or a panel is copied: the copy goes to the clipboard. It can be pasted

afterwards anywhere in the hierarchy. All its children and the children of its children are

also copied with the configuration. If the current folder or panel is modified afterwards,

the modification is not propagated to all the copied instances.

A panel of the WindowTree can be configured:

6. PVSS $-parameter (Figure 24) can be given to each child panel:

LHC Project Document No.

LHC-UNICOS

Page 25 of 93

– double click on a child in the right area in.

– from the panel top menu.

– from the right click menu.

7. The horizontal navigation (Figure 27): reference to a node of the WindowTree,

panel, plot or page can be configured for each navigation button. The horizontal

navigation can be saved into the WindowTree3 in order to be able to make reference on it

from another place of the WindowTree.

The configuration of the panel can be modified (Figure 25):

– double click on a child in the right area in.

– right click on a selected panel.

– from the panel top menu (Figure 23).

– click on a panel with no child on the left side, the configuration is on the right side

(Figure 23).

Figure 20: WindowTree configuration.

3 The navigation configuration can be saved into the WindowTree. A panel can have a link to a

another panel configured in the WindowTree. For instance, this allows to have contextual

button linked to the same panel but with different dollar parameter for each panel in the

WindowTree. A typical example is the cell of the sector where a unique panel with dollar

paramters is used to show the content of the cell, each cell of a sector can be linked to the

same panel (to another position into the WindowTree) but with different dollar parameters.

The contains is that each link must be to a panel included into the WindowTree.

LHC Project Document No.

LHC-UNICOS

Page 26 of 93

Figure 21: Hierarchy and panel top menu and right click for the WindowTree.

LHC Project Document No.

LHC-UNICOS

Page 27 of 93

Figure 22: Hierarchy and panel top menu and right click for the folder.

LHC Project Document No.

LHC-UNICOS

Page 28 of 93

Figure 23: Hierarchy and panel top menu and right click for the panel.

Figure 24: PVSS $-parameter for a panel.

LHC Project Document No.

LHC-UNICOS

Page 29 of 93

Figure 25: Configuration of a panel.

To test the WindowTree:

8. Open the panel via the WindowTree (Figure 26) from the unicosHMI panel, the

contextual button of the panel are shown in the contextual area and the panel is shown

in the central area.

9. Test the behaviour of the devices from the panel with the contextual button of the

device or the faceplate.

10. Test the navigation by click on the panel buttons in the contextual area (Figure

28).

LHC Project Document No.

LHC-UNICOS

Page 30 of 93

Figure 26: WindowTree.

LHC Project Document No.

LHC-UNICOS

Page 31 of 93

Figure 27: Panel navigation configuration.

Figure 28: Panel contextual button.

4.8 TRENDTREE CONFIGURATION

The TrendTree configuration tool (Figure 29) is based on the Windows Internet

Explorer:

– left side: hierarchy space browser, right click menu are available

– right side: the content of the selected node, right click menu are available.

– hierarchy and plot/page top menu: act on the selected node on the left side

The behaviour is similar to the one of the WindowTree.

The TrendTree, the Predefined_Trends and User_DefinedTrends folder are created and

configured during the installation,. New tree view can be created if needed, however

they will not be accessible via the TrendTree icon. New tree view can be created from

the UNICOS System DPs of the Configuration menu, Figure 1 and Figure 18)

LHC Project Document No.

LHC-UNICOS

Page 32 of 93

To populate the TrendTree:

1. Create a new folder from the hierarchy top menu or via mouse right click on the

right side either into the TrendTree (Figure 30), either a given folder (Figure 31), either a

given plot (Figure 32) or either in a given page (Figure 33).

2. Create a new plot or a new page (an empty plot or an empty page will be created)

or add an existing plot or page (a plot or page already configured) from the hierarchy top

menu or via mouse right click on the right side either into the TrendTree (Figure 30),

either a given folder (Figure 31), either a given plot (Figure 32) or either in a given page

(Figure 33).

3. A folder can be linked to a plot/page: from the plot/page top menu. The folder

name is renamed to the plot/page title.

4. A plot/page can be unlinked: from the plot/page top menu (Figure 32 and Figure

33).

5. If a folder, a plot or a page is copied: the copy goes to the clipboard. It can be

pasted afterwards anywhere in the hierarchy. All its children and the children of its

children are also copied with the configuration. If the current folder, plot or page is

modified afterwards, the modification is not propagated to all the copied instances.

A plot and a page of the TrendTree can be configured:

6. plot configuration (Figure 32), page configuration (Figure 33)

– double click on a child in the right area in.

– from the panel top menu.

– from the right click menu.

7. The horizontal navigation (Figure 34): panel, plot or page can be configured for

each navigation button.

The configuration of the plot/page can be modified (Figure 32 and Figure 33):

– double click on a child in the right area in.

– right click on a selected panel.

– from the plot/page top menu (Figure 32 and Figure 33).

– click on a panel with no child on the left side, the configuration is on the right side

(Figure 32 and Figure 33).

LHC Project Document No.

LHC-UNICOS

Page 33 of 93

Figure 29: TrendTree configuration.

LHC Project Document No.

LHC-UNICOS

Page 34 of 93

Figure 30: Hierarchy and plot/page top menu and right click for the TrendTree.

LHC Project Document No.

LHC-UNICOS

Page 35 of 93

Figure 31: Hierarchy and plot/page top menu and right click for the folder.

LHC Project Document No.

LHC-UNICOS

Page 36 of 93

Figure 32: Hierarchy and plot/page top menu and right click for the plot.

LHC Project Document No.

LHC-UNICOS

Page 37 of 93

Figure 33: Hierarchy and plot/page top menu and right click for the page.

LHC Project Document No.

LHC-UNICOS

Page 38 of 93

Figure 34: Plot/page horizontal navigation.

8. Configure the plot (Figure 32). Select the device data, the colour, range, visibility,

curve type and scale visibility. Save the configuration by a click on the apply button. The

selection of the device (DP element) can be done either via the default PVSS DP selector

(Figure 35) or the UNICOS device selector (Figure 36). The setup is done by a click on

the Set PVSS DP Selector/Set UNICOS DP Selector button.

9. Configure the page (Figure 33): Add/remove plot in a page, select the plot to be in

the page by clicking on the OK button (Figure 37), a click on the None button will empty

the plot cell of the page. A plot can also be viewed, copied, edited and created. Save the

configuration by a click on the apply button.

LHC Project Document No.

LHC-UNICOS

Page 39 of 93

Figure 35: PVSS DP Selector.

LHC Project Document No.

LHC-UNICOS

Page 40 of 93

Figure 36: UNICOS DP Selector.

LHC Project Document No.

LHC-UNICOS

Page 41 of 93

Figure 37: Selection of a plot.

To test the TrendTree:

1. Open the panel via the TrendTree (Figure 26) from the unicosHMI panel), the

contextual button of the panel are shown in the contextual area and the panel is shown

in the central area.

2. Open the page and plot via the TrendTree (Figure 38) from the unicosHMI panel

(Figure 39 and Figure 40), the contextual button of the plot and page are shown in the

contextual area and the plot or page is shown in the central area (Figure 39 and Figure

40).

For each plot there is a menu: stop/start the trend plot, change the time scale (pre-

defined time scale are given: 10 minutes, 1 hour, 8 hours, 1 day, 8 days), zoom

in/out the time and Y axis (the plot must be stopped), save the current settings

(password protected), export to a csv file, print, open the plot configuration panel,

choose the logarithmic/standard trend type, zoom the plot. The curve of a plot can be

hidden or set to visible: click on the check box below the trend plot. Tooltip text is

displayed on the description of the plot. The time printed below the trend plot is the

time of the last refreshed data of the curve.

For the page, there is a menu: change the time scale of all the plots of the page (pre-

defined time scale are given: 10 minutes, 1 hour, 8 hours, 1 day, 8 days), zoom

in/out the time and Y axis of all the plots of the page (only on the plots of the page

that are stopped), save the current settings of all the plots of the page (password

LHC Project Document No.

LHC-UNICOS

Page 42 of 93

protected), export to a csv file all the data of all the plots of the page, print, and open

the page configuration panel.

Figure 38: TrendTree.

Figure 39: unicosHMI with plot.

LHC Project Document No.

LHC-UNICOS

Page 43 of 93

Figure 40: unicosHMI with page.

The list of device DPE to be trended in a plot and the list of device DPE to be trended

in the faceplate can be configured per device type via the device trend configuration

panel (Figure 1 and Figure 41).

LHC Project Document No.

LHC-UNICOS

Page 44 of 93

Figure 41: Device trend configuration.

4.9 SYSTEMINTEGRITY CONFIGURATION

The systemIntegrity component checks that the PVSS-UNICOS application is running

in good condition:

3. It checks the state of the drivers, the state of the archives, the database size, the

version of the imported file with the version of the front-end software4 and of the state of

the remote PVSS systems

4. It checks the state of the PLCs connected to the DS

5. It sends the DS ip number to the PLCs

6. It checks the state of the PLC-PLC connections

7. It checks if the date and the time setting of the PLCs is coherent with the date and

time settings of the DS.

4 For unicosS7PLC only.

LHC Project Document No.

LHC-UNICOS

Page 45 of 93

1. In the systemIntegrity configuration panel (from the configuration menu, Figure

1):

2. Select archive in the list of components5: value archive and alarm archive. Add the

archives configured for the PLCs (Figure 42). Select the archive, the add option and press

the proceed button. A click on the refresh button shows the list of the archives that are

included into the systemIntegrity

3. Select driver in the list of component. The drivers configured for the PVSS

application (Figure 43). Select the driver, the add option and press the proceed button. A

click on the refresh button shows the list of the drivers that are included into the

systemIntegrity

4. Select dist in the list of component. Any remote PVSS system6 (in case of PVSS

distributed system) into the systemIntegrity (Figure 44). Select remote system, the add

option and press the proceed button. A click on the refresh button shows the list of the

remote systems that are included into the systemIntegrity

5. Add the check of the database size (Figure 45). By default the size of the

db/pvss/alertrr.db is checked every 30 sec. and must be less than 100Mb. New files can

be added in the “Internal configuration setup of the PVSS DB” (click on Internal

configuration button and select PVSSDB (Figure 46). The first entry is the timeout and

the following entries are the files to check.

6. For the S7PLC: add the checking of the versions (Figure 47). If the version read

from the S7PLC and the one read during the import of the device list differs an alarm is

raised.

5 The systemIntegrity for the value archive checks if there are less than two file switch during

the Archive checking delay, if the manager is off, if the archive is offline, in the latter case the

manager is stopped. For the alarm, it checks if there are less than teo file switch during the

alarm checking delay, if the size of the current alarm file is less than 100Mb and if the size of

the overflow alarm file is less than 50Mb. 6 The PVSS local system is never added because this is the one currently running.

LHC Project Document No.

LHC-UNICOS

Page 46 of 93

Figure 42: systemIntegrity configuration for archives.

LHC Project Document No.

LHC-UNICOS

Page 47 of 93

Figure 43: systemIntegrity configuration for drivers.

LHC Project Document No.

LHC-UNICOS

Page 48 of 93

Figure 44: systemIntegrity configuration for remote systems.

LHC Project Document No.

LHC-UNICOS

Page 49 of 93

Figure 45: systemIntegrity configuration for PVSS DB size.

Figure 46: systemIntegrity PVSS DB file list configuration.

LHC Project Document No.

LHC-UNICOS

Page 50 of 93

Figure 47: systemIntegrity configuration for ImportFile.

The state of the different components can be analysed with the systemIntegrity

operation panel (Figure 4, Figure 48, Figure 49, Figure 50, Figure 51 and Figure 52).

Right click operation are allowed. Remote system can be accessed.

LHC Project Document No.

LHC-UNICOS

Page 51 of 93

Figure 48: systemIntegrity operation for archive.

LHC Project Document No.

LHC-UNICOS

Page 52 of 93

Figure 49: systemIntegrity operation for driver.

LHC Project Document No.

LHC-UNICOS

Page 53 of 93

Figure 50: systemIntegrity operation for remote systems.

LHC Project Document No.

LHC-UNICOS

Page 54 of 93

Figure 51:systemIntegrity operation for PVSSDB.

LHC Project Document No.

LHC-UNICOS

Page 55 of 93

Figure 52: systemIntegrity operation for ImportFile.

Action to take in case of alarm:

7. Memory: the DS is running with low memory. Stop any process using too much

memory. PVSS will go to emergency mode if the DS stays too long time with this alarm.

The only way to quit the emergency mode is to stop and start the PVSS project.

8. Disk: the DS is running with too low disk space.

– Remove any big files residing in the DS computer

– Stop the PVSS project and remove the log files of the project

– Delete the old archive files and any archives files copied to the backup area

(Figure 5)

9. Distributed: re-start the remote PVSS system

10. Driver: re-start the driver

11. ValueArchive:

– If the archive is not started re-start it

LHC Project Document No.

LHC-UNICOS

Page 56 of 93

– If the archive is started, check the error in the PVSS console log, check the file

switch frequency and in the value archive activity panel (Figure 5). If this error

does not disappear, stop and restart the value archive manager.

12. AlarmArchive:

– check the error in the PVSS console log, check the size of the current alarm folder

(last line in the left table of Figure 71, the folder name is alxxx where xxx is the

time in second) and db/pvss/aloverflow folder check the file switch frequency and

in the value archive activity panel (Figure 71)

13. PLC:

– Check the modbus error

– Check the date and time synchronisation of the PLC

– Check the PLC-PLC communication error

– Check if the PLC counter is changing

14. PVSSDB:

– The size of one of the file is greater than 100Mb. Contact immediately the UNICOS

support, your system may enter in a critical state and may not be able to re-start.

15. ImportFile:

– Check if this is a S7PLC: the ImportFile check is only supported for S7PLC

– Check the version set from the import file and the one in the S7PLC

4.10 APPLICATION CONFIGURATION

The application state shows the alarm status of the critical components of the UNICOS

application. This is an easy way to know the state of the systemIntegrity alarms of the

PVSS-UNICOS application.

1. Open the Application of Configuration menu (Figure 1 and Figure 53)

2. Add into the Application status, the PLCs imported in PVSS (Figure 55)

3. Add into the Application status, the archives configured for the PLCs (Figure 56)

4. Add into the Application status, the drivers configured for the PVSS application

(Figure 57).

5. Add into the Application status, the remote system if any

6. Add memory and disk space alarm (Figure 58).

7. Other PVSS alarms can also be added (Figure 53)

LHC Project Document No.

LHC-UNICOS

Page 57 of 93

Figure 53: Application configuration panel.

Figure 54: Application setting panel.

LHC Project Document No.

LHC-UNICOS

Page 58 of 93

Figure 55: Add PLC.

Figure 56: Add archive.

LHC Project Document No.

LHC-UNICOS

Page 59 of 93

Figure 57: Add driver.

Figure 58: Add memory and disk space alarm.

8. Configure the synoptic (Figure 53) opened at start-up of the unicosHMI.

9. Configure the GIF logo file and the Application name shown in the header of the

unicosHMI panel.

10. Configure if necessary (Figure 54):

11. Configure the ManReg time-out. This time-out is the length of the pulse sent to the

PLC for the validation of the commands that are sent to the PLC.

LHC Project Document No.

LHC-UNICOS

Page 60 of 93

12. The device prefix, this prefix will be used to create the devices in PVSS during the

import.

13. The manReg timeout: this is the time out used to reset the bit of the manReg

when a command is sent to the PLC.

14. Event16/event32 protocol event type. The UNICOS event protocol support

event16: only the current 16 bits event and event32: old and current 16 bit event value

combined in a 32 bit event value. During the installation of the unicosObjects component,

the event protocol is set to event32.

15. The DPE used in the objectList to get the state of the devices.

16. The DPE used in the eventList to get the list of events of the devices.

17. If the default time shown in the EventList, ObjectList, AlarmList and MessageText

is in UTC or LTI: local time format (the other time format that the one set can be shown

via a right click).

18. The DPE used by the device selector provided by the unicos-pvss package. This

DPE is used to list the device name.

19. The default setting of the hierarchy display can also be modified (Figure 59). These

settings will be the default one used during further installation or update of the

unicosObjects components.

Figure 59: Setting the default hierarchy display settings.

20. The state of the Application alarm is shown in the unicosHMI panel. Open the run-

time panel of the Application (Figure 60) by double-clicking on the System Status of the

unicosHMI panel. Remote system can be accessed.

LHC Project Document No.

LHC-UNICOS

Page 61 of 93

Figure 60: Application run-time panel.

21. A double click on one application name on the left side list and a double click on a

line of the list of alarm of the selected application followed by a right click (Figure 60)

gives access to the detail and the possible actions of the alarm (Figure 61).

Figure 61: Detail and actions of the alarm.

LHC Project Document No.

LHC-UNICOS

Page 62 of 93

4.11 MODIFICATION OF THE CONFIGS OF THE DEVICE

The PVSS configs can be modified online into the PVSS application for fast modification

and to check if the setup is correct:

1. Open the Device configuration from the configuration menu (Figure 1 and Figure

62) and select a device. The current configs can be re-loaded, saved and discarded7.

2. Select the configs to modify. The following configs can be modified:

3. Data point element config: Archive (Figure 63), pv_range (Figure 63), alarm range

(Figure 63), address (Figure 63), and smoothing (Figure 63) on local and remote system.

4. Data point element config: unit (Figure 62), format (Figure 62) and

alias/description (Figure 63) can only be modified on local system.

5. Description, diagnostic, synoptic, html, alias, domain and nature (Figure 62) can

only be modified on local system.

6. Name for the PCO and PID (Figure 62) can only be modified on local system.

7. The Y scale in the faceplate: Faceplate Trend table.

Any modification must be reported into the specification file otherwise the

next time the data will be imported into PVSS the modifications will be lost or

an export of the devices must be done and then report back to the

specifications.

Figure 62: Device configuration.

7 The configuration of the address, smoothing, alias/description, archive, pv_range, and alert

pop-up panels are automatically saved when the Apply button is pressed (Figure 63).

LHC Project Document No.

LHC-UNICOS

Page 63 of 93

Figure 63: Configuration of the alias/description, smoothing, address, archive, pv_range and

alert config.

LHC Project Document No.

LHC-UNICOS

Page 64 of 93

4.12 CONFIGURATION OF EMAIL

Email (and also CERN SMS message sent by email) can be configured (from the Alert

Mails button of the systemIntegrity configuration panel Figure 2). A report for each

category can be sent periodically: the list of DPE to send via the report and frequency

can be configured. The unSystemAlarm category is configured by default: email for

systemIntegrity alarms. Categories can be added/removed/enabled/disabled8 (Figure

64).

An email is sent to all the defined receiver of all categories at startup of the

PVSS00ctrl.

Figure 64: Email configuration.

It is possible to configure an email/SMS for an AnalogInput, AnalogOuput, DigitalInput

and DigitalOutput device from the faceplate (Figure 65 and Figure 66) and for Alarm

device from the right click on the widget (Figure 67). This email configuration can also

be imported and exported into text files.

8 Adding a category will just configure the email sender component it will not send

automatically an email. A mechanism based on PVSS script or PVSS alert class script must be

implemented to send the email message to the email component. The email component will

then send the email.

LHC Project Document No.

LHC-UNICOS

Page 65 of 93

Figure 65: Add email/SMS for AnalogInput, AnalogOutput device alarm

Figure 66: Add email/SMS for DigitalInput, DigitalOutput device alarm

Figure 67: Add email/SMS for Alarm device alarm

4.13 MESSAGETEXT

The unMessageText component (Figure 68) is a kind of log book. Each action on a

device (select/deselect, device button action) and any relevant error of the UNICOS

utilities is reported to the unMessageText. The last messages are visible from the

unicosHMI (bottom-right). Four types of message can be logged: INFO, EXPERTINFO,

ERROR and WARNING. Filters are available to configure which type of message to

show (Figure 69). The history (Figure 70) is accessible from the unicosHMI with a right

click on the unMessageText (Figure 68).

LHC Project Document No.

LHC-UNICOS

Page 66 of 93

Figure 68: MessageText.

Figure 69: MessageText filter.

LHC Project Document No.

LHC-UNICOS

Page 67 of 93

Figure 70: MessageText history.

4.14 ALARM ARCHIVE CONFIGURATION

The alarm must be configured to avoid too large file size:

1. Open the Alarm archive (Figure 71) from the Utilities menu.

2. Set the file switch frequency and number of files to keep.

LHC Project Document No.

LHC-UNICOS

Page 68 of 93

Figure 71: Alarm archive configuration.

4.15 PACKAGING TO THE TARGET APPLICATION

The following data have to be packed

1. The specifications

2. The WindowTree and TrendTree configuration: export9 of the WindowTree and

TrendTree hierarchy and the panel, plot and page navigation.

3. The zip file of all the folders of the project except the db, config, printers and log

folder. This can be done with the online backup of the project (Figure 74 in Section 5.3).

5. INSTALLATION IN A RUNNING DS

5.1 DEVELOPMENT OF THE APPLICATION

During the development of the new application that has to be merged into an existing

one, one should take care of the following:

1. Use the same PVSS system name and system number as the final one

9 The UNICOS core team will provide a tool for the export.

LHC Project Document No.

LHC-UNICOS

Page 69 of 93

2. During the development of the synoptic, do not use the same synoptic name as

the one already existing in the running DS

3. Do not use the same names for the WindowTree configuration:

4. Panel

5. Folder

6. Do not use the same name for the TrendTree configuration:

7. Page

8. Plot

9. Folder

5.2 DESCRIPTION OF THE PROCEDURE

To install the application in the existing DS the following procedure can be followed:

1. From the systemIntegrity run-time panel disable the configured PLCs (from the

Diagnostic menu, Figure 3 and Figure 4). Select the line with the text Communication

PLCname by double click and then right click.

2. Stop all the OWS computers

3. Stop the modbus driver

4. Do an online backup of the current application: Section 5.3

5. Do a zip of all the folders of the project except the db and log folder

6. Extract all the data from the current project and send them to the LHC Logging

7. Unzip the new project folders into the project in the DS computer: panels, etc. are

restored into the DS. Existing files must not be overwritten. In case there is a redundant

or a bad definition into the new project, this shall be corrected before continuing.

8. Collect the info: Section 4.2.

9. Modify the specifications: see document CREATION OF A WINCC OA - CPC 6

APPLICATION

10. Import the specification into the PLCs: see document CREATION OF A WINCC OA -

CPC 6 APPLICATION

11. Import the specifications10 into the PVSS project: see document CREATION OF A

WINCC OA - CPC 6 APPLICATION

12. Set-up the UNICOS-MODBUS communication for all the previous configured PLCs:

Section 4.4

13. Validate the UNICOS devices of all the previous PLCs: Section 4.4

14. Set-up the UNICOS-MODBUS communication for all the new configured PLCs one

per one: Section 4.4

15. Validate the UNICOS devices of all the new PLCs: Section 4.4

16. Restore the WindowTree and TrendTree: import11 of the WindowTree and

TrendTree hierarchy and the panel, plot and page navigation.

17. Configure the systemIntegrity with the new PLCs and archives: Section 4.9

18. Configure the application security with the new PLCs, new archives and new PVSS

remote systems (if any): Section 4.10

19. Modify if necessary the configs of the devices: Section 4.11

20. Configure if necessary the email: Section 4.12

10 The PLC configurations of the previous PLC must not be overwritten. 11 The UNICOS core team will provide a tool for the import.

LHC Project Document No.

LHC-UNICOS

Page 70 of 93

21. Configure if necessary the alarm archive: Section 4.13

22. Modify the WindowTree and TrendTree if necessary, e.g.: do a new hierarchy, mix

in the same hierarchy the synoptics of the old PLCs with the ones of the new PLCs, etc.

23. Do an online backup.

5.3 BACKUP OF THE RUNNING CONFIGURATION

To do an online backup of the PVSS application:

1. do an online backup of the database:

a. Open the Online backup utility (Figure 72) from the Utilities menu.

b. Configure the backup location (Figure 73) and press the Apply button

c. Start the backup (Figure 72)

2. do an online backup of the parametrization of the project (all folders except log,

help, msg, printer and source and an ascii export of all the DPTs and DPs of the project):

a. Open the Online backup utility (Figure 72) from the Utilities menu.

b. Configure the backup location (Figure 73) and press the Apply button

c. Start the backup (Figure 74)

The list of existing backups is accessible by pressing the refresh button (Figure 75).

LHC Project Document No.

LHC-UNICOS

Page 71 of 93

Figure 72: Online backup of the project database.

LHC Project Document No.

LHC-UNICOS

Page 72 of 93

Figure 73: Configuration of the backup location.

LHC Project Document No.

LHC-UNICOS

Page 73 of 93

Figure 74: Online backup of the project folders.

LHC Project Document No.

LHC-UNICOS

Page 74 of 93

Figure 75: List of existing PVSS application online backups.

6. DEVICE IN A DISTRIBUTED ENVIRONMENT

6.1 BEHAVIOUR OF THE DEVICE ANIMATION

The device data widget of devices from different PVSS system can be mixed in the

same synoptic (panel) and plot. If the remote system is not available the device data

colour will set to Device not connected colour (Figure 95). As soon as the remote

system is up and running, the device data will be set accordingly to the current state

of the device.

The configuration of the device name from the PVSS00NG can be done:

LHC Project Document No.

LHC-UNICOS

Page 75 of 93

3. While the remote systems are up and running and therefore the filtering device

selector has access to all the device names of all the PVSS system. Filters on the PVSS

systems are supported: Figure 15, Figure 16 and Figure 17.

4. Even if the remote systems are not connected. The device names of the remote

systems are not available, but the name can be still entered: Figure 17.

Similarly plots can be configured with data from the local system and remote systems

5. While the remote systems are up and running and therefore the filtering device

selector has access to all the device names of all the PVSS system. Filters on the PVSS

systems are supported: Figure 32, Figure 35 and Figure 36.

6. Even if the remote systems are not connected. The device names of the remote

systems are not available, but the name can be still entered: Figure 32.

It is also possible to configure:

7. The list of plots in a page with plots from the local system and remote system.

8. The horizontal navigation of a plot, page and panel can also be configured with

plots and pages from a remote system.

However this is not recommended, the plots and page should always be taken from

the local system. The panel‟s device instances are always taken from the local system.

6.2 PROCEDURE

The PVSS application must have been configured as a distributed system. To declare

the remote systems:

1. Define all the remote PVSS systems the local system is connected to by starting

the Distributed System configuration tool (Figure 1 and Figure 76):

2. the PVSS system name, PVSS system ID.

3. the hostname, post number must be entered, “” are for default value local host

and default port number.

4. Start (stop and restart if it was started before) the PVSS00dist manager from the

PVSS console.

5. Include the remote system into the systemIntegrity (Section 4.8) and into the

application (Section 4.10).

6. Do this configuration in all the other systems.

The state of the remote systems can be monitored (Figure 3 and Figure 77).

LHC Project Document No.

LHC-UNICOS

Page 76 of 93

Figure 76: Configuration of the remote PVSS systems.

Figure 77: Monitoring of the state of the remote PVSS systems.

7. MODIFY THE DEVICE TYPE DATA OR ADD A NEW DEVICE TYPE

The unicos-pvss package allows the creation of new device type and the modification

of:

7. existing device type

8. UNICOS front-end device type

9. systemIntegrity device type.

This must be done in collaboration with the UNICOS core team.

LHC Project Document No.

LHC-UNICOS

Page 77 of 93

To add a new device type:

10. Create a data point of type _UnObject with the name deviceType_unicosInfo.

11. Set the config of the device type (Section 7.1).

To add a new front-end device type:

12. Create a data point of type _UnFrontEnd with the name deviceType_unicosInfo.

13. Set the config of the device type (Section 7.2).

To add a new systemIntegrity device type:

14. Create a data point of type _UnSystemIOntegrity with the name

deviceType_systemIntegrityInfo.

15. Set the config of the device type (Section 7.3).

7.1 MODIFYING THE DEVICE TYPE FUNCTIONS

The following items of the UNICOS device type data can be modified (Figure 1 and

Figure 78):

16. The list of widget

17. The faceplate

18. The contextual menu

19. The select state

20. The functions configured for the device

Figure 78: Modify the device type functions.

7.2 MODIFYING THE FRONT-END DEVICE TYPE FUNCTIONS

The following items of the front-end device type data can be modified (Figure 1 and

Figure 79), the function are called during the import of the devices and the device

configurations:

LHC Project Document No.

LHC-UNICOS

Page 78 of 93

21. The function that check the delete command.

22. The function that executes the delete command.

23. The function that check the front-end settings.

24. The function that executes the import of the front-end settings.

Figure 79: Modify the front-end type functions.

7.3 MODIFYING THE SYSTEMINTEGRITY DEVICE TYPE FUNCTIONS

The following items of the systemIntegrity device type data can be modified (Figure 2

and Figure 80):

25. The function called during the initialization of the systemIntegrity of this device

type.

26. The function called whenever a request is sent to this device type:

add/delete/enable/disable/diagnostic.

27. The function called whenever the config data of this device type are modified.

28. The config data of this device type.

29. The panel to configure the systemIntegrity of the devices of this device type.

30. The panel to show the status of the systemIntegrity of the devices of this device

type.

Figure 80: Modify the systemIntegrity device type functions

LHC Project Document No.

LHC-UNICOS

Page 79 of 93

8. OTHER UTILITIES

8.1 EXPORT OF THE UNICOS DEVICE

The list of devices and their configuration can be exported (Figure 81) to an ASCII file

having the same format as the file to import. The file may contain the following data

#VALUE! when the device data configuration cannot be read, for instance if the device

has no alarm configuration, the HH, H, L and LL value cannot be read and are replace

by #VALUE!.

Figure 81: Export of the devices.

LHC Project Document No.

LHC-UNICOS

Page 80 of 93

8.2 EXPORT OF TRENDTREE/WINDOWTREE

The complete or part of the TrendTree and WindowTree can be exported (Figure 82)

into as ASCII file in the xml format by selecting a tree or a node in the tree. The

current PVSS system is replaced by the keyword “#local” and all the instances of the

„&‟12 character are replaced by the „@‟ character. One can also export a complete tree

without the tree definition (export without tree definition check box) in order to import

later on the complete tree into another tree or into a node.

Figure 82: Export of the TrendTree and WindowTree.

8.3 IMPORT OF TRENDTREE/WINDOWTREE

The complete or part of the TrendTree and WindowTree can be imported into a

running DS (Figure 1, Figure 83 and Figure 84). The keyword “#local” will be replaced

by the PVSS system name in which is imported the file, any „@‟ character are replaced

by the „&‟ character. The WARNING (e.g.: same plot but with different configuration,

part of a tree) can be imported by selecting the Force Import check box. Part of a tree

can be imported into a position in a tree by selecting the Force Import and Import into

selected position check boxes and selecting a node in a tree.

12 The „&‟ is not allowed in an XML file.

LHC Project Document No.

LHC-UNICOS

Page 81 of 93

Figure 83: Import Tree, check data.

-

LHC Project Document No.

LHC-UNICOS

Page 82 of 93

Figure 84: Import Tree, import data.

8.4 USER DEFINED POP-UP PANEL

Since unicos-pvss-3.6 it is possible to configure the main interface and introduce a

user defined panel to be pop-up, the panel name, X and Y position (Figure 53).

8.5 MASKING OF EVENT

Since unicos-pvss-3.6, the masking of event is possible when a device is flipping; this

will result in having no archive history in the event list for this particular device. When

the event is masked an „e‟ letter appears in the top right position of the widget (Figure

85) and the check in the device faceplate (Figure 92). Unmasking will re-enable the

archive on the event, thus resulting in having the event in the event list. The mask

and un-mask is accessible via the right click on the widget (Figure 85). The masking

state of the event is exportable (Section 8.1) and can also be imported. The list of

devices with the event masked can be listed from the Utilities menu as well as the list

of masked alarms.

LHC Project Document No.

LHC-UNICOS

Page 83 of 93

Figure 85: Masking/unmasking event.

Figure 86: Device faceplate.

LHC Project Document No.

LHC-UNICOS

Page 84 of 93

Figure 87: List of device with a masked event.

Figure 88: List of device with a masked alarm.

LHC Project Document No.

LHC-UNICOS

Page 85 of 93

8.6 DEVICE LINK

Since unicos-pvss-3.6, it is possible to link device, the list of linked devices is

accessible from the right click from the widget (Figure 89), the faceplate of the linked

devices can be opened by selecting the device. The linked device can be imported and

is also exported with the device data (Section 8.1). Links can be added dynamically

from the device configuration (Section 4.11).

Figure 89: Device link.

8.7 ANADIG/ANALOG DEVICE

A new feature was introduced in unicos-pvss-3.6 for the AnaDig and Analog device.

When one of the device links is of type Controller and on the same PVSS system a „R‟

letter appears in the bottom right position in the widget (Figure 90) and a new

tabulation appears in the faceplate (Figure 91): Regulation that shows data from the

Controller (maximum four) and the Analog/AnaDig device.

Figure 90: AnaDig/Analog widget.

LHC Project Document No.

LHC-UNICOS

Page 86 of 93

Figure 91: AnaDig/Analog Regulation tabulation.

8.8 BACKUP OF THE APPLICATION

In unios-pvss-3.6 the application backup utility was introduced. It is triggered by the

online backup (Section 5.3). The result is a backup of the PVSS database, panels,

pictures, images, scripts and libs folders of the project without the value archive and

alarm archive. This backup is in the folder configured for the online backup.

LHC Project Document No.

LHC-UNICOS

Page 87 of 93

APPENDIX A: WIDGET CONVENTION

The following convention is used for all the device widgets:

Figure 92: Device widget.

31. Mode

This letter displays current object mode with its associated color. Only one mode could

be active.

Mode Letter Color

Auto None None

Manual M White

Local L White

Forced F Yellow

Regulation R White

Tracking T White

32. Data quality

This letter displays current object warning.

Data quality Letter Color Priority

Invalid N Cyan Highest

Old data O Cyan Highest

IO Error E

Orange

Highest

IO Simulated S High

Forced <> Auto

W Normal Manual <> Auto

Position Warning

If any data of the current object is invalid (PVSS _invalid), a letter N in cyan is

displayed in the warning letter position.

The letter O is shown if the PLC is enabled and the driver handling the communication

with the PLC is running and the PLC counter is changing periodically.

33. Alarm

This letter displays the current object alarm state.

W A

M

Data quality

Alarm

Body

Selection

Mode

Lock Mouse over

R

e Event masked

Regulation (only AnaDig/Analog)

LHC Project Document No.

LHC-UNICOS

Page 88 of 93

Alarm Letter Color Priority

Full Stop Interlock F

Red

Highest

Stop Interlock S High

Start Interlock I Normal

Position Alarm P

Mask Letter Color Priority

Alarm Blocked (in PLC) B Yellow

Highest

Alarm Masked (in PVSS) M High

If no alarm is defined in PVSS (_alert_hdl), for all the AnalogInput and AnalogOutput

devices all the square boxes of the alarms/Limits are in black (Figure 93). For the

DigitalInput/DigitalOutput the alarm square boxes are greyed out (Figure 94).

34. Event masked

This letter shows the mask/unmask state of the event

Event mask Letter Color

Event masked e Yellow

Event unmasked

Figure 93: AnalogInput/AnalogOut device faceplate with no PVSS alarm.

LHC Project Document No.

LHC-UNICOS

Page 89 of 93

Figure 94: DigitalInput/DigitalOut device faceplate with no PVSS alarm

35. Selection

When the object is selected, the selection shape goes white.

36. Body

Body Color Priority

Invalid Cyan Highest

Alarm Unack. Red Blinking High

Alarm Red Normal

Forced Mode Yellow Low

Auto Mode Green Lowest

Figure 95: Device widget examples.

LHC Project Document No.

LHC-UNICOS

Page 90 of 93

APPENDIX B: FACEPLATE AND CONTEXTUAL BUTTON

Each device has a faceplate and associated contextual buttons. The faceplate (Figure

97) shows the detail information of the device. The operation on the device is done via

the contextual buttons in the bottom of the faceplate (Figure 97).

If any data of the current device is invalid (PVSS _invalid), all the displayed data are

in colour cyan in the faceplate (Figure 96).

If the PLC is disabled, or the driver handling the communication with the PLC is not

running or the PLC counter is not changing periodically all the displayed data are in

colour cyan in the faceplate (Figure 96).

Figure 98 shows the list of UNICOS widgets.

Figure 96: Faceplate with invalid/old data.

LHC Project Document No.

LHC-UNICOS

Page 91 of 93

Figure 97: Faceplate in normal condition.

Figure 98: List of UNICOS widgets.

LHC Project Document No.

LHC-UNICOS

Page 92 of 93

APPENDIX C: LIST OF FIGURES

Figure 1: Configuration menu. ........................................................................................ 8 Figure 2: systemIntegrity configuration for unicosS7PLC. ................................................... 9 Figure 3: Diagnostic menu. ........................................................................................... 10 Figure 4: systemIntegrity run-time panel for unicosS7PLC. ............................................... 11 Figure 5: Archive file switch. ......................................................................................... 12 Figure 6: Front-end diagnostic. ..................................................................................... 13 Figure 7: Front-end diagnostic. ..................................................................................... 15 Figure 8: PLC not reachable. ......................................................................................... 16 Figure 9: PLC not defined in the hosts file. ...................................................................... 16 Figure 10: MODBUS parameterization. ........................................................................... 17 Figure 11: Wrong modbus address. ............................................................................... 18 Figure 12: Select/deselect diagnostic panel..................................................................... 19 Figure 13: Device tree overview. ................................................................................... 20 Figure 14: Tree device overview extended filter. ............................................................. 20 Figure 15: Drawing a synoptic. ...................................................................................... 21 Figure 16: Change the device– 1. .................................................................................. 22 Figure 17: Change the device – 2. ................................................................................. 22 Figure 18: Tree management. ....................................................................................... 23 Figure 19: Delete panel, plot, page, node and views. ....................................................... 24 Figure 20: WindowTree configuration. ............................................................................ 25 Figure 21: Hierarchy and panel top menu and right click for the WindowTree. ..................... 26 Figure 22: Hierarchy and panel top menu and right click for the folder. .............................. 27 Figure 23: Hierarchy and panel top menu and right click for the panel. .............................. 28 Figure 24: PVSS $-parameter for a panel. ...................................................................... 28 Figure 25: Configuration of a panel. ............................................................................... 29 Figure 26: WindowTree. ............................................................................................... 30 Figure 27: Panel navigation configuration. ...................................................................... 31 Figure 28: Panel contextual button. ............................................................................... 31 Figure 29: TrendTree configuration. ............................................................................... 33 Figure 30: Hierarchy and plot/page top menu and right click for the TrendTree. .................. 34 Figure 31: Hierarchy and plot/page top menu and right click for the folder. ........................ 35 Figure 32: Hierarchy and plot/page top menu and right click for the plot. ........................... 36 Figure 33: Hierarchy and plot/page top menu and right click for the page. ......................... 37 Figure 34: Plot/page horizontal navigation. ..................................................................... 38 Figure 35: PVSS DP Selector. ........................................................................................ 39 Figure 36: UNICOS DP Selector. .................................................................................... 40 Figure 37: Selection of a plot. ....................................................................................... 41 Figure 38: TrendTree. .................................................................................................. 42 Figure 39: unicosHMI with plot. ..................................................................................... 42 Figure 40: unicosHMI with page. ................................................................................... 43 Figure 41: Device trend configuration. ........................................................................... 44 Figure 42: systemIntegrity configuration for archives. ...................................................... 46 Figure 43: systemIntegrity configuration for drivers. ........................................................ 47 Figure 44: systemIntegrity configuration for remote systems. ........................................... 48 Figure 45: systemIntegrity configuration for PVSS DB size. .............................................. 49 Figure 46: systemIntegrity PVSS DB file list configuration. ............................................... 49 Figure 47: systemIntegrity configuration for ImportFile. ................................................... 50 Figure 48: systemIntegrity operation for archive. ............................................................ 51 Figure 49: systemIntegrity operation for driver. .............................................................. 52 Figure 50: systemIntegrity operation for remote systems. ................................................ 53 Figure 51:systemIntegrity operation for PVSSDB. ............................................................ 54 Figure 52: systemIntegrity operation for ImportFile. ........................................................ 55 Figure 53: Application configuration panel. ..................................................................... 57

LHC Project Document No.

LHC-UNICOS

Page 93 of 93

Figure 54: Application setting panel. .............................................................................. 57 Figure 55: Add PLC. ..................................................................................................... 58 Figure 56: Add archive. ................................................................................................ 58 Figure 57: Add driver. .................................................................................................. 59 Figure 58: Add memory and disk space alarm. ................................................................ 59 Figure 59: Setting the default hierarchy display settings. ................................................. 60 Figure 60: Application run-time panel. ........................................................................... 61 Figure 61: Detail and actions of the alarm. ..................................................................... 61 Figure 62: Device configuration. .................................................................................... 62 Figure 63: Configuration of the alias/description, smoothing, address, archive, pv_range and

alert config............................................................................................................ 63 Figure 64: Email configuration. ..................................................................................... 64 Figure 65: Add email/SMS for AnalogInput, AnalogOutput device alarm ............................. 65 Figure 66: Add email/SMS for DigitalInput, DigitalOutput device alarm .............................. 65 Figure 67: Add email/SMS for Alarm device alarm ........................................................... 65 Figure 68: MessageText. .............................................................................................. 66 Figure 69: MessageText filter. ....................................................................................... 66 Figure 70: MessageText history. .................................................................................... 67 Figure 71: Alarm archive configuration. .......................................................................... 68 Figure 72: Online backup of the project database. ........................................................... 71 Figure 73: Configuration of the backup location. .............................................................. 72 Figure 74: Online backup of the project folders. .............................................................. 73 Figure 75: List of existing PVSS application online backups. .............................................. 74 Figure 76: Configuration of the remote PVSS systems. ..................................................... 76 Figure 77: Monitoring of the state of the remote PVSS systems. ........................................ 76 Figure 78: Modify the device type functions. ................................................................... 77 Figure 79: Modify the front-end type functions. ............................................................... 78 Figure 80: Modify the systemIntegrity device type functions ............................................. 78 Figure 81: Export of the devices. ................................................................................... 79 Figure 82: Export of the TrendTree and WindowTree. ....................................................... 80 Figure 83: Import Tree, check data................................................................................ 81 Figure 84: Import Tree, import data. ............................................................................. 82 Figure 85: Masking/unmasking event. ............................................................................ 83 Figure 86: Device faceplate. ......................................................................................... 83 Figure 87: List of device with a masked event. ................................................................ 84 Figure 88: List of device with a masked alarm. ................................................................ 84 Figure 89: Device link. ................................................................................................. 85 Figure 90: AnaDig/Analog widget. ................................................................................. 85 Figure 91: AnaDig/Analog Regulation tabulation. ............................................................. 86 Figure 92: Device widget. ............................................................................................. 87 Figure 93: AnalogInput/AnalogOut device faceplate with no PVSS alarm. ........................... 88 Figure 94: DigitalInput/DigitalOut device faceplate with no PVSS alarm .............................. 89 Figure 95: Device widget examples. ............................................................................... 89 Figure 96: Faceplate with invalid/old data. ...................................................................... 90 Figure 97: Faceplate in normal condition. ....................................................................... 91 Figure 98: List of UNICOS widgets. ................................................................................ 91