570 likes | 757 Views
Detector DCS status. Overview and news. 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
E N D
Detector DCS status Overview and news DCS Workshop
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 DCS Workshop
Acknowledgementsand apologies • Thanks to all detector groups that provided me with input for this overview • Apologies for the very short notice DCS Workshop
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 DCS Workshop
User Requirements • Status of the URDs and other sources of information DCS Workshop
User Requirements • Status of the URDs and other sources of information DCS Workshop
User Requirements • Status of the URDs and other sources of information DCS Workshop
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 DCS Workshop
Overview ofdetector 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 DCS Workshop
ITS-pixel 20? 4 1 1 2 20 240 10 1 or 2 360 20 120 1..4 16/06/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II OPC client OPC client OPC client Wiener OPCserver DIMserver Wiener OPCserver SchneiderOPCserver CAEN OPCserver PCI-CAN PCI-VME PCI-CAN E C PCI-VME C E CAEN VME(wiener?) DDL Number of CAN busses will depend on performance[to be tested] PLC Wiener Optics JTAG LV CoolingPlant VR board(12 VR each) HV LV Detector Detector On-detectorelectronics Detector High Voltage Low Voltage FEE Crate Control Detector Cooling
ITS-drift 6 2..4 1 6 72*12 ? 520 288 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet CAEN can be moved to CR; at the cost of longer HV cables [cost issue] PVSS II PVSS II PVSS II OPC client OPC client OPC client (?) Wiener OPCserver SchneiderOPCserver CAEN OPCserver DIM or OPCserver DIMserver PCI-CAN E E C E VME(wiener?) DDL Where does these twisted pair go? To VME? PLC ? Optics CAEN AREM CoolingPlant HV LV VR Detector Detector On-detectorelectronics Detector High Voltage Low Voltage FEE Crate Control Detector Cooling
ITS-strip 1 8+ 1 5 ? 144 450 ? ? 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient No commentsso far User interface Ethernet PVSS II PVSS II PVSS II PVSS II Can these CAEN be moved to CR? Can these CAEN be moved to CR? OPC client OPC client OPC client OPC client DIMserver Wiener OPCserver ? OPCserver SchneiderOPCserver CAEN OPCserver CAEN OPCserver ? PCI-CAN ? E E C E ? ? LV: Is Arem-Pro still an option? PLC CAEN CAEN(?) I/O device(PLC,Wago,ELMB?) FEROM(VME? wiener?) DDL CoolingPlant HV LV Detector Detector On-detectorelectronics Detector Detector High Voltage Low Voltage FEE Crate Control Temp. monitoring Detector Cooling
TPC(1) 108? 1 216 22 3 18? 1? ? ? 1 4? 108 ~400? 44 1..22 ? 288 1..18 1..3 16/06/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet Controls interface under study PVSS II PVSS II PVSS II ProfiBus is still a possible alternative OPC client OPC client OPC client PVSS II ISEG OPCserver Wiener OPCserver ELMB OPCserver SchneiderOPCserver DIMserver PCI-CAN PCI-CAN PCI-CAN RS232 C C C E E S ISEG EthernetSwitch Heinzinger E PLC Wiener EthernetSwitch CoolingPlant (ch) E HV LV ELMB HV DDL Chambers Chambers Chambers,detector Chambers,detector RCU HVrod High Voltage Low Voltage Temp. Monitor Chamber Cooling FEE Very High Voltage
TPC(2) 4 1? 1 ? 216 ? 12? 18 4 72 ? 2? ? 16/06/03 URD is being written Ethernet DIMserver (?) Schneider/SiemensOPCserver Schneider/SiemensOPCserver DIMserver (?) OPCserver (?) SchneiderOPCserver ? ? PCI-Profibus E E P E PLC PLC PLC Calibrationpulser C PS Laser P ELMB Gas CoolingPlant (rods) CoolingPlant (TS) Gatingpulser “box” HVrod HVrod ThermalScreen(s) Mirrors,cameras Chambers Detector VHV Curr. Monitor VHV rod Cooling Thermal Screen(s) Laser calibr. syst. Pulser system Gas system
TRD 10 x 1? 540 x 50 ? 1 1..50 1..10 1080 18*(12+18) 540 ? 16/06/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet Network topology still under study PVSS II PVSS II OPC client OPC client ISEG OPCserver Wiener OPCserver DIMserver SchneiderOPCserver SchneiderOPCserver PCI-CAN PCI-CAN C C E E E ISEG EthernetSwitch PLC PLC What kind of distribution box is this? Wiener E ELMB Gas EthernetSwitch CoolingPlant Distribution Box HV LV E DATA 2*540 Detector Detector DCS board Detector Detector High Voltage Low Voltage FEE Detector Cooling Gas system
TOF 72? 360 1? 180 ? ? 4 360? ? 18 180 ? ? 3600 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient No realcomments so far User interface Ethernet TOF presentationin a moment PVSS II PVSS II PVSS II OPC client OPC client OPC client DIMserver Wiener OPCserver SchneiderOPCserver SchneiderOPCserver CAEN OPCserver CAEN OPCserver PCI-CAN E E E C E E CAEN HV PLC ? distribution CAEN(?) PLC C P LV VME(wiener?) ELMB Gas CoolingPlant HV DC-DC LV Detector Detector DRM Detector Detector DDL High Voltage Low Voltage FEE Crate Control Detector Cooling Gas system
HMPID 1 1+1 1? ? 17 1 ? ? ? 126 ? 70 ? ? 49 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II PVSS II OPC client OPC client OPC client Can these CAEN be moved to CR?(were originally projected in CR) OPC client Wiener OPCserver SiemensOPCserver ? OPCserver Wiener OPCserver SchneiderOPCserver SchneiderOPCserver CAEN OPCserver PCI-CAN ? PCI-CAN E C E C E E ? PLC PLC PLC C P Wiener VME+NIM I/O device(PLC,Wago,ELMB?) CAEN ELMB Gas LiquidCirculation CoolingPlant HV LV Detector Detector Detector On-detectorelectronics Detector Detector High Voltage Low Voltage Liquid Circulation Temp. Monitor Crate Control Detector Cooling Gas system
PHOS ? ? 10-20 ? ? ? ? ? ? ? ? 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II OPC client OPC client Can these CAEN be moved to CR? OPC client Wiener OPCserver DIMserver ? OPCserver OPC/DIMserver (?) CAEN OPCserver PCI-CAN PCI-Profibus ? E C E E Following activities in TPC ? ? PLC(?) Wiener(?) CAEN(?) I/O device(PLC,Wago,ELMB?) CoolingPlant HV LV DDL Detector Detector RCU On-detectorelectronics Detector High Voltage Low Voltage FEE Temp. Monitor Detector Cooling
PHOS-CPV 1 5? ? ? 16? 40 ? ? 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II OPC client OPC client Can this CAEN be moved to CR? OPC client Wiener OPCserver ? OPCserver SchneiderOPCserver CAEN OPCserver PCI-CAN ? E C E ? PLC C P Wiener CAEN I/O device(PLC,Wago,ELMB?) ELMB Gas HV LV Detector Detector On-detectorelectronics Detector High Voltage Low Voltage Temp. Monitor Gas system
Muon-Trk 3 ? 20 140 1 ? 28 1 ? 328 ? ? ? 48 ? 192 1 ? ? ? 16/06/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II PVSS II OPC client OPC client OPC client OPC client CAEN OPC ? Wiener OPCserver Wiener OPCserver ? OPCserver DIMserver (?) OPC/DIM Server (?) SchneiderOPCserver PCI-CAN PCI-CAN PCI-CAN ? E C C C E E Purpose build HV switch.Need a closer look! CAEN PLC HV PLC(?) C repeater P C Wiener VME(wiener) I/O device(PLC,Wago,ELMB?) ELMB Gas Geometrymonitor Air/Water cooling LV Switch HV DDL Detector Detector Crocus(on-detector crates) Detector Detector Detector High Voltage Low Voltage Crate Control Environment monitor Geometry Detector Cooling Gas system
Muon-Trg 2 ? 2 17 ? ? 16 ? ? 100 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II PVSS II OPC client OPC client OPC client Can be moved to CR if really needed OPC client Wiener OPCserver Wiener OPCserver ? OPCserver SchneiderOPCserver CAEN OPCserver PCI-CAN PCI-CAN ? E C C E PLC C P CAEN Wiener VME(wiener) I/O device(PLC,Wago,ELMB?) ELMB Gas HV LV Efficiencysystem Detector Detector Detector Detector High Voltage Low Voltage Crate Control Environment monitor Gas system
FMD 20 1 10 1 2 ? 300? 10 ? ? 140 70 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II Can this CAEN be moved to CR? Following activities in TPC OPC client OPC client OPC client DIMserver Wiener OPCserver ? CAEN OPCserver CAEN OPCserver PCI-Profibus PCI-CAN E E E C ? DDL TTC CAEN ? CAEN ? FMD-RCU PCI? VME? VME(wiener?) LV E? Air cooling lvl0 HV Detector Pre-amps Digitizers Detector High Voltage Low Voltage FEE Crate Control Detector Cooling
T0 ? ? ? 24 ? ? ? ? 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II PVSS II Can be shared with V0 Following activities in TOF ? ? OPC client ? ? DIMserver Wiener OPCserver ? ? ? PCI-CAN C CAEN(?) ? VME(wiener?) Laser system HV LV Detector(PMT) Detector(shoe box) On-detectorelectronics Detector High Voltage Low Voltage FEE Crate Control Laser calibr. syst.
V0 1 4? ? 144+12 ? 10/03/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient User interface Ethernet PVSS II PVSS II OPC client Maybe shared with T0 OPC client DIMserver Wiener OPCserver CAEN OPCserver PCI-CAN E C CAEN HV Front-Endelectronics VME(wiener?) PMT Opticalfibers Detector High Voltage FEE Crate Control
PMD ? ? ? ? ? ? 52 52 52 ? ? 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient No commentsso far User interface Ethernet PVSS II PVSS II PVSS II PVSS II ? ? OPC client OPC client ? ? ? OPCserver Wiener OPCserver ? SchneiderOPCserver ? ? ? PCI-CAN C E E PLC ? ? PLC C P I/O device(PLC,Wago,ELMB?) VME(wiener?) ELMB Gas CoolingPlant HV LV Detector Detector On-detectorelectronics Detector Detector High Voltage Low Voltage Temp. Monitor Crate Control Detector Cooling Gas system
ZDC ? ? ? 50 16/06/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient No commentsso far User interface Ethernet PVSS II PVSS II ? OPC client ? Wiener OPCserver ? PCI-CAN C ? VME(wiener?) HV Detector High Voltage Crate Control
Cosmics (ACORDE) ? ? ? ? ? 128? 28/02/03 [FSM?] Database(s) PVSS II PVSS II PVSS II Control room (ACR) OPCclient DIMclient No commentsso far User interface Ethernet PVSS II PVSS II PVSS II ? ? OPC client ? ? Wiener OPCserver ? ? PCI-CAN C ? ? VME(wiener?) HV LV Detector Detector High Voltage Low Voltage Crate Control
Summary • For many detectors we have more or less detailed information • For a few detectors we are lacking even very basic information DCS Workshop
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 DCS Workshop
Cabling • I will present examples for a few sub-systems Question: • Do we think this is a useful activity and should be continued? DCS Workshop
10/03/2003 18 3 18 1..3 TPC; high voltage CR x Rack xxx UX Rack xxx E PC C ISEG ECH238 EHQ F 020p Should be some patch panel somewhere… ? m ? m ? m 1 Ethernet 1..3 CANBus 18 cables [16 lines per cable, CERN standard. Scem xxx ] ControlPC Device MagnetDoor Detector
10/03/2003 72? 72 3 ? 1..22 TPC; low voltage CR x Rack xxx UX Rack xxx E PC C Should be some patch panel somewhere… Wiener PL500F 2..7V / 115A ? m ? m ? m 1 Ethernet 1..22 CANBus 72 bus bars [under discussion ] 72(?) sense wires [under discussion ] ControlPC Device MagnetDoor Detector
10/03/2003 60 120 180 180 20 240 120 20 20 20 4 1..4 ITS-pixel; low voltage CR x Rack xxx UX Rack xxx Vdd, gnd, 2 senseVmcm, gnd, 2 sense 3 T_mcm 6 x E PC C Wiener PL500 5V / 50A VR board JTAG 6 m ? m ? m 30 m 3 m 1 m 1 Ethernet 1..4 CANBus 120 cables (Vdd, gnd) 60 MCM extenders 20 cables [s = 25 mm2] [s = 6 mm2] [shared withHigh Voltage and temperature monitoring] 120 cables (Vmcm, gnd) ? [s = 1 mm2] 20 JTAG control cables 240 sense wires ? 180 T signal cables 180 T signal cables ControlPC Device MagnetDoor TPCend Internalpatch panel Detector
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 DCS Workshop
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 DCS Workshop
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 DCS Workshop
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 DCS Workshop
Controls Hierarchy ECS “Node” =“Control Unit”in FSM DAQ Trig DCS ITS TPC TRD … SPD SDD SSD HV LV Cool RB24 RB26 Sec1 Sec3 Sec2 DCS Workshop
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 DCS Workshop
Controls Hierarchy ECS 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 DAQ Trig DCS ITS TPC TRD … SPD SDD SSD HV LV Cool RB24 RB26 Sec1 Sec3 Sec2 DCS Workshop
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 ! DCS Workshop
Controls Hierarchy ECS DAQ Trig DCS ITS TPC TRD … Does it make sense to operate a single TPC sector; or does one only operate one half of the TPC at the same time? SPD SDD SSD HV LV Cool RB24 RB26 Sec1 Sec3 Sec2 DCS Workshop
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 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 nodesBetter to define all HV as one node HV1a HV1b Chamber LV1 DCS Workshop
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 DCS Workshop
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 DCS Workshop
Error situationsand 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 DCS Workshop
Error situationsand 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 DCS Workshop
Error situationsand 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… DCS Workshop
Error situationsand 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) DCS Workshop
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 DCS Workshop