clara gaspar, november 2012 experiment control system ls1 plans…

Clara Gaspar, November

2012

Experiment Control System

LS1 Plans…

Clara Gaspar, November 2012

ECS Infrastructure❚Current Control PCs are old, so:

❙New, more powerful machines❘Virtual machines x group projects

❙New Operating Systems:❘Windows 2008S-R2 64 bits only❘Linux SLC6 64 bits only

❙New WinCC-OA 3.11❘No more PVSS…

➨ Need to “move” and “upgrade” ALL PVSS projects

2

2


ECS Interfaces❚Effects on Hardware Interfaces

❙PCI slots no longer available❘SPECS -> New ethernet based SPECS

(coming…)❘Peak CAN Interface -> ?

❙Virtual Machines -> no direct HW connections❘Systec CAN-USB (direct USB cables)

-> New box USB to ethernet (under discussion)

❘Ethernet: Ok

❙Other Hardware?

3

3


New SPECS

4

4

Fan

Sub Detector

Master cards

Master Ports

New Module

s

ECAL 6 22 2

HCAL 2 7 1

PRS 4 10 1

IT 2 6 1

TT 2 4 1

OT 6 24 2

VELO 2 21

TPU 1 1

RICH1 4 14 1

RICH2 5 19 2

Total 34 109 12

❚ Preliminary…

❚ Run Specs Server in CCPC❚ PVSS Project in Control PC


Ethernet to USB

5

5

❚ Simplified block diagram - Preliminary…

❚ Use PVSS “Scattered” Systems:❚ Run OPC Server & PVSS OPC Client in each CCPC❚ PVSS Project away on Control PC


ECS Interfaces❚Effects on Hardware Interfaces

❙In general for HW access from virtual machines:❙Separate the HW access & the supervisory

layer➨ By making more use of scattered projects /

distributed DIM Servers…

❙Software: New 64 bit OSs:❘New drivers (SPECS, Systec)❘New OPC Servers:

〡CAEN, WIENER, ISEG, ELMB

➨ Working versions exist

6

6


WinCC-OA 3.11❚Siemens Strategy:

❙Base all their SCADA products on the PVSS core (i.e. Event Manager,Data Manager, etc.)❘Simatic WinCC (Their old product)❘Simatic WinCC Open Architecture (old PVSS)

❚Implications:❙Installation directory changes❙Manager names change

❘WCCILpmon, WCCILevent, etc.❘WCCOActrl, WCCOAui, etc.

7

7


WinCC-OA 3.11❚Implications (continued):

❙New JCOP framework:❘All CERN managers re-built:

〡WCCOAdim, WCCOAdip, WCCOAsmi, etc.

❙Luckily stay the same:❘The Project directory structure❘All functions used in Ctrl scripts and User

Interfaces❘The C++ API for managers and ctrl extensions

❙In general: everything still works!(and we can mix projects of different versions)

8

8


WinCC-OA 3.11❚Improvements

❙Several, reported here:❘ http://www.etm.at/index_e.asp?id=&sb1=&sb2=&sb3=&snam

e=div_nw_0212_3_11_e.asp&sid=&seite_id=

❘They claim better performance…❘Otherwise I found nothing really useful for

us…

❚But we need to install it:❙Because we need the support for the new

PCs, operating systems, 64 bits, etc.

9

9

http://www.etm.at/index_e.asp?id=&sb1=&sb2=&sb3=&sname=div_nw_0212_3_11_e.asp&sid=&seite_id

http://www.etm.at/index_e.asp?id=&sb1=&sb2=&sb3=&sname=div_nw_0212_3_11_e.asp&sid=&seite_id


Migration Strategy❚Procedure (draft):

❙Keep the old PCs up.❙Copy project to new machine❙“Upgrade” Project❙Test project➨ We will try to create tools to ease the

procedure and of course document the exact detailed procedure to follow.

10

10

To be done by Sub-system Teams


Migration Strategy (detail)

❚Current plan:❙Old PCs will be renamed prefix with “old”

❘ Ex.: r2dcs02w (running Windows 2003 SP2, PVSS 3.8 SP2) r2dcs02w (running Windows 2008 SP2, WinCC 3.11) old PC will be kept as oldr2dcs02w

❘ Auto-start of DIM and PVSS will be disabled

❙New PC with the same name and new OS prepared

❘ New WinCC installed, all configurations, privileges etc. ported over (to the extent possible)

❘ Projects will also be copied over

❙New and old computers can run in parallel, but the WinCC projects and some DIM stuff can not!

❘ This allows manual going forth and back in case there is a need to check

11

11


Migration Strategy❚“Details” to be sorted out:

❙“PVSS” Archive❘WinCC-OA 3.11 needs a new schema version

(Once upgraded old project can not use archive anymore)

➨ Clone archive?

❙Project Upgrade x Project Recreation❘Projects seem to “age” (get heavier and

slower)➨ Create new ones and (ascii) import all

dps?

❙Projects in PCs with HW (Specs for ex.)❘If HW replacement not available yet➨ Leave DIM/OPC Server there, migrate

project

12

12


Manpower & Responsibility

❚Each sub-system:❙Is responsible for upgrading and testing

their projects (there will be docs and tools)

❙Should give us their preferred schedule, so that we can give support…

❙Can give us comments and requests for (central) improvements, we are open…

❙Can discuss with us all other upgrades in their sub-systems, we would like to help…

13

13


Conclusion❚No PVSS projects after LS1…

❚We need your collaboration…

14

14

clara gaspar, november 2012 experiment control system ls1 plans…

Documents