g. dissertori ethz cms electronics 2002 1 ecal dcs : plans for 2003 g. dissertori ethz 27.11.2002

G. Dissertori ETHZ CMS Electronics 2002 1

ECAL DCS : Plans for 2003ECAL DCS : Plans for 2003

G. DissertoriETHZ

27.11.2002


ECAL Electronics, DCSECAL Electronics, DCS

Description of the prototype slow control system

comments regarding each subsystem

Contents



Main DCS console(PVSS, JCOP Framework)Main DCS console(PVSS, JCOP Framework)

HV (PVSS)HV

(PVSS)

LV (?)LV (?)

DSS (PVSS)DSS (PVSS) Cooling (?)

Cooling (?)

Laser (?)

Laser (?)

Temp/Humid.Moni

t. (PVSS)

Temp/Humid.Moni

t. (PVSS)

DAQDAQDB/ ArchiveDB/ Archive

DIM , XDAQ/PVSS

DIM ?DIM ?



HV LV DSS Cooling

TEMP. + HUMID. Monit.

ALARMS

LASER DAQ

Main DCS Console

DB/ARCH



had a meeting recently (HV, LV, TSS, F. Glege)

for mid-2003 (SM0) : first prototype of DCS software system in PVSS should include HV, LV, Temp.Monit., TSS, Cooling?, Framework with FSM, Partitioning,

communication with XDAQ and ECAL DAQ?

test of this prototype during 2003

beg. 2004: production setup for the SM calibration at H4 during 2004, probably all resources needed for calibration

beg. 2005: first tests of a setup for full ECAL (maybe start with reduced size) may have to find a location to do such a test

from mid 2005 on : install equipment and start testing of the full system

beg. 2006 : full system ready

Planning: Software



up to end-2003 : subprojects software covered by responsible groups, framework covered, but I guess with substantial help/input needed (from Frank Glege, I guess)

end 2003 - 2004: have to shift manpower (1 person) to framework, probably from TSS and Temp. monitoring

in 2005 - 2006 : would like to get help for the test and integration of full system, also for the interfacing with the DAQ : 1 person (0.5 FTE ?)

Planning: Manpower



we urge all subitems of DCS to look into PVSS (or a possible interface such as DIM) as soon as possible

when working with PVSS, follow rules when defining data points

please communicate, such as alarm types etc

Wishes/ Request / AOB



HV issues

• they use CAEN PS. Supported by JCOP.

• Rome group will develop the HV PVSS application

• prototype should be ready for SM0• they will have Labview as backup



LV issues

• exact system not yet defined ( in terms of hardware )

• planned to use DCUs (CCUs) to control the LVRs

• therefore: will use XDAQ

• therefore : will need PVSS - XDAQ interface

• hopefully a very first prototype ready for SM0



DSS issues

• a first prototype already used in 2002 (M0’)

• the Belgrade group will build the application

• should be ready for SM0

• need good communication with DAQ, in order to get information from sensors integrated in PCBs

• needs communication with cooling

• sensors: as close as possible to final solution (2 sensors per module)



Temp./Humid. Monit. issues

• a first prototype already used in 2002 (M0’)

• the Protvino group (together with ETHZ) will build the application

• should be ready for SM0

• needs communication with cooling (feedback ?)

• sensors : as close as possible to final solution : • 10 temp.sensors per supermodule (4 on grid, 4 on screen, 2 on IN/OUT pipes).• 1 humidity sensor per module



Cooling issues

• need to start discussion now

• I think at the moment they use Labview



Laser issues

• Need to start discussion now

• I assume they will have their own software (not PVSS)

• but at least we need software communication with the Laser system in order to know hardware status



Communication with DAQ

• first tests for communication ECAL PVSS - XDAQ first half of 2003

• so hopefully ready for SM0

• As long as “J.Fay/J. Bourotte DAQ” is the run controller, have to communicate : best solution: DIM

• the DIM name server would run on the central DCS station• APIs exist for different platforms• in PVSS (JCOP framework) DIM is integrated (as API manager, built in via

particular definition of data points)• DIM could also be a candidate for other communications (eg. with

LASER)



Database/Archiving

• Probably will use PVSS archiving tools

• what other kinds of databases will be used by others?



FRAMEWORK issues

• A. Lister (ETHZ) just started to work on it

• hopefully first prototype ready for SM0

• with FSM, partitioning, alarm handling, XDAQ interface ...

• Note : planned that Alison leaves for CDF end 2003 (for some time). See man power issues....

g. dissertori ethz cms electronics 2002 1 ecal dcs : plans for 2003 g. dissertori ethz 27.11.2002

Documents