1. André Augustinus 16 June 2003 DCS Workshop Detector DCS status Overview and news

2. André Augustinus 16 June 2003DCS Workshop 2 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations

3. André Augustinus 16 June 2003DCS Workshop 3 Acknowledgements and apologies  Thanks to all detector groups that provided me with input for this overview  Apologies for the very short notice

4. André Augustinus 16 June 2003DCS Workshop 4 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations

5. André Augustinus 16 June 2003DCS Workshop 5 User Requirements  Status of the URDs and other sources of information URD ITS-pixel Recent URD; regular information exchange ITS-drift  Basic URD, no recent update ITS-strip  Basic URD, no recent update. No recent news TPC Regular information exchange TRD Recent URD; regular information exchange TOF  Some information, lack of written information HMPID Regular information exchange

6. André Augustinus 16 June 2003DCS Workshop 6 User Requirements  Status of the URDs and other sources of information URD PHOS  Incomplete URD PHOS-CPV  Basic URD Muon-Trk Recent URD; regular information exchange Muon-Trg Regular information exchange FMD  No URD (yet), but information exchange T0  No URD (yet), some information since last WS V0  No URD (yet), good contact since last WS

7. André Augustinus 16 June 2003DCS Workshop 7 User Requirements  Status of the URDs and other sources of information URD PMD  No URD, very limited contact ZDC  No URD, very limited contact ACORDE  Early stage, limited contact EMC  Early stage, regular contact Infrastructure  Basic URD, central team

8. André Augustinus 16 June 2003DCS Workshop 8 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations

9. André Augustinus 16 June 2003DCS Workshop 9 Overview of detector sub-systems  Will try to go quickly, concentrate on things that might need clarification  Will use overview drawings as last meeting  Included all drawings for reference

10. Detector CAEN CAEN OPCserver PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet User interface Database(s) OPC client DIM client 201201..4 PVSS II Cooling Plant PLC Schneider OPCserver 114 High VoltageLow VoltageDetector Cooling PVSS II OPC client PVSS II OPC client ITS-pixel EC HVLV E [FSM?] Control room (ACR) Detector 10 PCI-VME DIMserver FEE On-detector electronics VME (wiener?) 2 PCI-VME Optics PCI-CAN Wiener OPCserver PVSS II OPC client C 1 or 2360 Crate Control DDL 16/06/03 VR board (12 VR each) 240 LV 20 JTAG 20? Number of CAN busses will depend on performance [to be tested]

11. Detector CAEN CAEN OPCserver PVSS II Detector AREM DIM or OPCserver Ethernet User interface Database(s) OPC client DIM client 288520 PVSS II Cooling Plant PLC Schneider OPCserver 166 High VoltageLow VoltageDetector Cooling PVSS II OPC client PVSS II OPC client (?) ITS-drift E HVLV E [FSM?] Control room (ACR) Detector ? DIMserver FEE On-detector electronics 72*12 10/03/03 E PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) 2..4 DDL Optics VR ? CAEN can be moved to CR; at the cost of longer HV cables [cost issue] Where does these twisted pair go? To VME? Crate Control

12. Detector CAEN CAEN OPCserver PVSS II Detector CAEN(?) CAEN OPCserver Ethernet User interface Database(s) OPC client DIM client 450144 PVSS II Cooling Plant PLC Schneider OPCserver 115 High VoltageLow VoltageDetector Cooling PVSS II OPC client PVSS II OPC client ITS-strip EE HVLV E [FSM?] Control room (ACR) Detector ? ? DIMserver FEE On-detector electronics PCI-CAN Wiener OPCserver PVSS II OPC client C ?? Crate Control FEROM (VME? wiener?) 8+ ? ? OPCserver PVSS II OPC client I/O device (PLC,Wago,ELMB?) Detector Temp. monitoring ?? DDL 28/02/03 No comments so far Can these CAEN be moved to CR? LV: Is Arem-Pro still an option?

13. Chambers ISEG PCI-CAN ISEG OPCserver PVSS II Chambers Wiener PCI-CAN Wiener OPCserver Ethernet User interface Database(s) RCU DIMserver OPC client DIM client 1082881..31..22? PVSS II Chambers, detector ELMB 1..18~400? PVSS II RS232 HVrod Heinzinger 4?1 Cooling Plant (ch) PLC Schneider OPCserver 1?18?3221216 High VoltageLow VoltageFEETemp. MonitorChamber CoolingVery High Voltage PVSS II OPC client PVSS II OPC client PCI-CAN ELMB OPCserver PVSS II OPC client TPC (1) CC HVLV ECE HV S [FSM?] Control room (ACR) 108? Chambers, detector 44 DDL 16/06/03 Ethernet Switch ?? E E ProfiBus is still a possible alternative Controls interface under study

14. Ethernet HVrod “box” ? DIMserver (?) ?12?4 VHV Curr. Monitor TPC (2) Cooling Plant (rods) PLC Schneider/Siemens OPCserver 1 VHV rod Cooling Thermal Screen(s) PLC 18 Schneider/Siemens OPCserver 1? Thermal Screen(s) ? DIMserver (?) ? Laser calibr. syst. PCI-Profibus OPCserver (?) 2? Pulser system PSLaser Mirrors, cameras ? Schneider OPCserver Gas system PLC ELMB Gas EEE C P HVrod 4 Cooling Plant (TS) Detector P Chambers Gating pulser 72? Calibration pulser 16/06/03 216 URD is being written

15. Detector ISEG PCI-CAN ISEG OPCserver PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet User interface Database(s) DCS board DIMserver OPC client DIM client 18*(12+18)10801..101..501 PVSS II 1050540 High VoltageLow VoltageFEE PVSS II OPC client PVSS II OPC client Ethernet Switch 540 Ethernet Switch x Schneider OPCserver Gas system PLC ELMB Gas [FSM?] CCEE E EHVLV TRD Control room (ACR) Cooling Plant PLC Schneider OPCserver 1? Detector Cooling E Detector ? ? DATA 2*540 16/06/03 Distribution Box x Network topology still under study What kind of distribution box is this?

16. Detector CAEN CAEN OPCserver PVSS II Detector CAEN(?) Ethernet Database(s) OPC client DIM client 360?3600184? High VoltageLow Voltage PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EE HV LV TOF Control room (ACR) [FSM?] distribution 180 HV 180 CAEN OPCserver PVSS II OPC client DC-DC LV 360 DIMserver FEE DRM Cooling Plant PLC Schneider OPCserver 1? Detector Cooling ? E Detector ? ? E 72? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) Crate Control ?? DDL 28/02/03 No real comments so far TOF presentation in a moment

17. Detector CAEN CAEN OPCserver PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) Liquid Circulation OPC client DIM client 12649? On-detector electronics 70117 High VoltageLow VoltageLiquid CirculationTemp. Monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client Siemens OPCserver PLC 1? User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EEC HVLV HMPID Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? Cooling Plant PLC Schneider OPCserver 1? Detector Cooling E Detector ? ? ? 10/03/03 VME+NIM PCI-CAN Wiener OPCserver ?1+1 Crate Control PVSS II OPC client C ? Can these CAEN be moved to CR? (were originally projected in CR)

18. Detector CAEN(?) CAEN OPCserver PVSS II Detector Wiener(?) PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client ??? On-detector electronics ??? High VoltageLow VoltageTemp. Monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II EC HVLV PHOS Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? Cooling Plant PLC(?) OPC/DIM server (?) ? Detector Cooling ? E Detector ? RCU PCI-Profibus DIMserver ?10-20 FEE E DDL 28/02/03 ? Can these CAEN be moved to CR? Following activities in TPC

19. Detector CAEN CAEN OPCserver PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client 4016?? On-detector electronics ?15? High VoltageLow VoltageTemp. Monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EC HVLV PHOS-CPV Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? Detector ? 28/02/03 ? Can this CAEN be moved to CR?

20. Detector CAEN PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client 328?? Detector ?28 High VoltageLow VoltageEnvironment monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EC HV LV Muon-Trk Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener) 1 Crate Control 1 Geometry monitor DIMserver (?) ?? Geometry Air/Water cooling PLC(?) OPC/DIM Server (?) ? Detector Cooling E Detector ? ? 16/06/03 ? PCI-CAN CAEN OPC Switch 192 HV C ?1140 Crocus (on-detector crates) DDL 20 repeater 3 C 48 Purpose build HV switch. Need a closer look!

21. Detector CAEN CAEN OPCserver PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client 16100? Detector ?22 High VoltageLow VoltageEnvironment monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EC HVLV Muon-Trg Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? Crate Control Efficiency system Detector ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener) 17? 10/03/03 Can be moved to CR if really needed

22. Detector CAEN ? PVSS II Pre-amps CAEN ? Ethernet Database(s) OPC client DIM client 1407011 High VoltageLow Voltage User interface PVSS II HV LV FMD Control room (ACR) [FSM?] Crate Control CAEN OPCserver PVSS II OPC client CAEN OPCserver PVSS II OPC client FEE Digitizers 10 Air cooling ? Detector Cooling Detector ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) ? 10/03/03 10 FMD-RCU PCI? VME? EE PCI-Profibus DIMserver ? E 20 lvl0 E? 300? DDLTTC 2 Following activities in TPC ? Can this CAEN be moved to CR?

23. Detector (PMT) CAEN(?) PVSS II Detector (shoe box) ? Ethernet Database(s) OPC client DIM client ?24?? High VoltageLow Voltage User interface PVSS II HVLV T0 Control room (ACR) [FSM?] PCI-CAN Wiener OPCserver PVSS II OPC client Crate Control ? ? PVSS II ? ? ? ? DIMserver FEE On-detector electronics ? Laser system ? Laser calibr. syst. Detector ? C VME (wiener?) ?? 10/03/03 Can be shared with V0 Following activities in TOF

24. Detector CAEN PVSS II Ethernet Database(s) OPC client DIM client 144+121 High Voltage User interface PVSS II HV V0 Control room (ACR) [FSM?] 10/03/03 Crate Control DIMserver FEE ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) 4? ? CAEN OPCserver PVSS II OPC client E PMT Optical fibers Front-End electronics Maybe shared with T0

25. Detector ? PVSS II Detector ? Ethernet Database(s) OPC client DIM client 52 ?? High VoltageLow Voltage User interface PVSS II HVLV PMD Control room (ACR) [FSM?] Crate Control ? ? PVSS II ? ? ? ? On-detector electronics 52 Temp. Monitor ? ? OPCserver PVSS II OPC client I/O device (PLC,Wago,ELMB?) ? Schneider OPCserver Gas system PLC ELMB Gas E C P Cooling Plant PLC ? ? Detector Cooling E Detector ? ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) ?? 28/02/03 No comments so far

26. Detector ? PVSS II Ethernet Database(s) OPC client DIM client 50? High Voltage User interface PVSS II HV ZDC Control room (ACR) [FSM?] Crate Control ? ? PVSS II ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) ?? 16/06/03 No comments so far

27. Detector ? PVSS II Detector ? Ethernet Database(s) OPC client DIM client ?128??? High VoltageLow Voltage User interface PVSS II HVLV Cosmics (ACORDE) Control room (ACR) [FSM?] Crate Control ? ? PVSS II ? ? ? ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) ?? 28/02/03 No comments so far

28. André Augustinus 16 June 2003DCS Workshop 28 Summary  For many detectors we have more or less detailed information  For a few detectors we are lacking even very basic information

29. André Augustinus 16 June 2003DCS Workshop 29 Cabling Background:  End of the year the RB26 doors will be closed  Need to know what cables will go through TPC, TRD, TOF  Started an effort to capture cabling information, based on what we know Inspired by pixel cabling overview last meeting

30. André Augustinus 16 June 2003DCS Workshop 30 Cabling  I will present examples for a few sub-systems Question:  Do we think this is a useful activity and should be continued?

31. PC ISEG ECH238 3 EHQ F 020p 18 Magnet Door UX Rack xxx Detector C 1..3 ? m Device TPC; high voltage 10/03/2003 ? m 1..3 CANBus [16 lines per cable, CERN standard. Scem xxx ] 18 E Control PC 1 Ethernet ? m 18 cables CR x Rack xxx Should be some patch panel somewhere…

32. PC Wiener PL500F 3 2..7V / 115A ? Magnet Door UX Rack xxx Detector C 1..22 ? m Device TPC; low voltage 10/03/2003 ? m 1..22 CANBus [under discussion ] 72 E Control PC 1 Ethernet ? m CR x Rack xxx Should be some patch panel somewhere… [under discussion ] 72? 72 bus bars 72(?) sense wires

33. PC Wiener PL500 4 5V / 50A 20 Magnet Door UX Rack xxx 30 m TPC end Detector C 1..4 ? m Device VR board 12060 6 x ITS-pixel; low voltage 10/03/2003 Internal patch panel 6 m 3 m1 m 1..4 CANBus 240 sense wires 180 T signal cables [s = 6 mm 2 ] [s = 1 mm 2 ] [s = 25 mm 2 ] [shared with High Voltage and temperature monitoring] 20 E Control PC 1 Ethernet ? m 60 MCM extenders 20 cables 120 cables (Vdd, gnd) 120 cables (Vmcm, gnd) CR x Rack xxx Vdd, gnd, 2 sense Vmcm, gnd, 2 sense 3 T_mcm 120240180 180 T signal cables ? 18020 JTAG 20 JTAG control cables ?

34. André Augustinus 16 June 2003DCS Workshop 34 Cabling  Can this be useful?  A repository of (DCS related) cabling Can be used as input to the installation team  Needs input from the detectors  ‘Later’ detectors can be inspired by ‘earlier’ detectors

35. André Augustinus 16 June 2003DCS Workshop 35 Cabling Special case: Ethernet at detector level  Some detectors envisage Ethernet on/in the detector: TPC, TRD, TOF, PHOS, FMD, T0 More detail in Peter’s talk  Technical issues Must work in magnetic field and radiation What will be the best topology

36. André Augustinus 16 June 2003DCS Workshop 36 Cabling  “Managerial” issues How to interface with rest of network Who is responsible for what  Many efforts going on in this field to tackle technical aspects When things become more clear we should get IT division involved choice of equipment, managerial aspects

37. André Augustinus 16 June 2003DCS Workshop 37 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations

38. André Augustinus 16 June 2003DCS Workshop 38 Controls Hierarchy ECS DCS DAQTrig ITSTPCTRD… SPDSDDSSD HVLVCool RB24RB26 Sec1 Sec2 Sec3 “Node” = “Control Unit” in FSM

39. André Augustinus 16 June 2003DCS Workshop 39 Controls hierarchy  Reflects the operation of your detector  Each “node” can be operated independently Should define a “node” for each entity that has to be the ability to be operated independently (e.g. in the case of a calibration run)  A “node” contains the logic of interaction between its children

40. André Augustinus 16 June 2003DCS Workshop 40 Controls Hierarchy ECS DCS DAQTrig ITSTPCTRD… SPDSDDSSD HVLVCool RB24RB26 Sec1 Sec2 Sec3 Will there be a reason to operate the ITS as one single entity? and/or Is there a ‘strong’ interaction between the ITS detectors? then this ITS node should be defined

41. André Augustinus 16 June 2003DCS Workshop 41 Controls hierarchy  The lowest node reflects the smallest part of your detector that logically could be operated independently Note that we talk operation here; this is not the smallest part of the detector you can switch off (e.g. in case of a problem); that will always be possible on the channel level !

42. André Augustinus 16 June 2003DCS Workshop 42 Controls Hierarchy ECS DCS DAQTrig ITSTPCTRD… SPDSDDSSD HVLVCool RB24RB26 Sec1 Sec2 Sec3 Does it make sense to operate a single TPC sector; or does one only operate one half of the TPC at the same time?

43. André Augustinus 16 June 2003DCS Workshop 43 Controls hierarchy  One should try to match the ‘smallest operable part’ of your detector for all sub systems, especially if they have to be operated simultanously Chamber HV1aHV1b LV1 If all HV has to be on to operate the chamber; or if LV can only be switched on if both HV is on, it makes no sense to define both HV as individual nodes Better to define all HV as one node

44. André Augustinus 16 June 2003DCS Workshop 44 Controls hierarchy  For operation it would be very convenient to have the same subdivision for DCS and DAQ So that one can ‘partition’ part of your detector and run in stand alone (e.g. for calibration); both DCS and DAQ It is not logical to be able to operate one half of your detector while in DAQ you can only read out the whole detector Or, if the DAQ can run one sector in stand-alone while the DCS is only able to operate half of the detector

45. André Augustinus 16 June 2003DCS Workshop 45 Controls hierarchy  You can define as many intermediate levels in your hierarchy as you need  For each node you will have to define the states it can have, the commands it can accept, the logical behaviour it should have  Giacinto will talk in more detail on Finite State Machines

46. André Augustinus 16 June 2003DCS Workshop 46 Error situations and Interlocks Various levels of protection of your equipment  Inside your equipment (hardware) E.g. a current exceeding a given value will result in switching off that channel (trip)  In the DCS system (software) Program an action on any set of readings (within a sub system or across sub systems) E.g. if HV on one part of a chamber goes off, switch off the rest of the chamber E.g. if a rise of temperature is measured, switch off LV

47. André Augustinus 16 June 2003DCS Workshop 47 Error situations and Interlocks  Interlock (hardware) Can be inside or across sub systems, or even from outside the detector A trip on one channel, force also other channels to trip If the gas system fails, switch off the HV If the cooling system fails, switch of the LV An alarm system can switch off all your systems

48. André Augustinus 16 June 2003DCS Workshop 48 Error situations and Interlocks  Software actions give high flexibility in their implementation (delay’s, special ramp down, can act on the channel level) But: are intrinsically less reliable  Hardware action are less flexible and usually act in a more ‘crude’ way But: are highly reliable  Difficult to get good things of both…

49. André Augustinus 16 June 2003DCS Workshop 49 Error situations and Interlocks This means work for you…  For each event analyse what is the impact on your detector and equipment  Define what action needs to be taken and evaluate the risk if the action is not taken  This gives an indication how the action could be implemented (hardware or software)

50. André Augustinus 16 June 2003DCS Workshop 50 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations

51. André Augustinus 16 June 2003DCS Workshop 51 Prototyping  HV and LV Less than half of the detectors have ‘final hardware’ and started prototyping only few with Framework/PVSS  Gas and Cooling Outsourced to CERN groups (except PHOS cooling) Various stages of progress Some in production, others in design

52. André Augustinus 16 June 2003DCS Workshop 52 Prototyping  Other systems Various stages of progress Concentrating mainly on functionality rather than controls aspects To be followed case by case  As always: Let us know what you are doing, and any remarks you have !

53. André Augustinus 16 June 2003DCS Workshop 53 Detector (DCS) planning  Some information on beam tests etc.  Pre-installation information in central planning  Very little information on DCS needs at the various stages  Please let us know your needs in controls for your beam tests, lab tests, pre-installation etc. So that we can plan our work and your support

54. André Augustinus 16 June 2003DCS Workshop 54 Central team  Good news:  We finally got (temporary…) lab space We will set up all ‘common solutions’ These set-up’s can be used as demonstration and for debugging purposes  Involved in TPC tests  Major ‘proof of concept’ during pre-installation of TPC in 2004

55. André Augustinus 16 June 2003DCS Workshop 55 More news  An effort started to redesign the Framework Simplify the internals (easier maintenance) Simplify for the users (panels etc.) Further integration of FSM  Ready by the end of the year Coincides with a new version of PVSS (version 3)  If you use the framework, it is now to let us know your comments and remarks !!!

56. André Augustinus 16 June 2003DCS Workshop 56 More news  Current framework can still be used Your own created panels will need to be adapted to the new Framework  For FSM, if you can, wait for new Framework It’s configuration and use will be simplified

57. André Augustinus 16 June 2003DCS Workshop 57 Overview  Status of URD’s  Hardware and layout Overview of the detectors sub systems Cabling overview  Operational aspects Control Hierarchy Error situations and interlocks  Future Prototyping in detectors and planning Plans in central team  Other news  Detector presentations