1 / 24

ATLAS DCS

ATLAS DCS. Overview Logical Organization Technical Implementation Front-End Back-End Connection to DAQ Requirements on JCOP Conclusions. Scope of DCS. Included Supervision and operation of all subdetector hardware Supervision of common experimental infrastructure

monte
Download Presentation

ATLAS DCS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATLAS DCS • Overview • Logical Organization • Technical Implementation • Front-End • Back-End • Connection to DAQ • Requirements on JCOP • Conclusions JCOP External Review, March 10th 2003, H.J.Burckhart

  2. Scope of DCS • Included • Supervision and operation of all subdetector hardware • Supervision of common experimental infrastructure • Connection to the CERN infrastructure services • Interaction with the LHC accelerator • Excluded • Global safety • CERN Safety System • Detector Safety System • Subdetectors have internal HW interlocks • Any contact with physics data (“events”) • DAQ Run Control • Data quality monitoring • Data flow control JCOP External Review, March 10th 2003, H.J.Burckhart

  3. ATLAS Detector • Inner Detector • Pixel • SCT • TRT • Calorimeter • Liquid Argon • TileCal • Muon system • CSC • TGC • MDT • RPC JCOP External Review, March 10th 2003, H.J.Burckhart

  4. Detector ATLAS Detector Inner Detector Pixel Si Strips TileCal Muons Common Infrastructure LAr TRT HC EMC EC Barrel EC Ext Barrel Disks Cylinders Barrel EC FW Barrel Detector HT Laser Cs S. CSC MDT RPC TGC Gas Barrel EC EC Racks Crates Cooling Env. Gas sys Temp Magnetic field Alignment LV & HV Power Supplies Cryo Purity Temp. Position, Strain Rad Env. Cooling LV & HV Frontend boards Cooling Power Supplies Temp. Cooling HV & LV Gas Ctrl Gas dist. Temp Mixing Purifiying External Systems DAQ CERN LHC Magnet Information System Message Report System Run Ctrl, DB Op . Param Acess Ctrl Electr. Distrib. Cooling Ventilation Cryo Safety Ctrl Room Bckgnd Luminosity Injection Inhibit Beam Dump BT Solenoid ET Logical Organization JCOP External Review, March 10th 2003, H.J.Burckhart

  5. CFS Test HV Rack PC Rack PC Barrel Fieldbus 200m DCS HW Architecture Local Area Network SCX1 Operation Alarms Server Local Control Stations (LCS) Back-End System Expert Workstations Subdetector 1 Subdetector 2a Common Infrastructure Subdetector n USA15 Electronic Rack ELMB Detector Sub-system ELMB ELMB Front-End System Power Supply ELMB UX15 ELMB Sensors Interlock Box Actuators Cooling Supervisory only Partition 1 Partition 2 Partition 3 Partition m JCOP External Review, March 10th 2003, H.J.Burckhart

  6. Back-End • Based on PVSS • Functionality (to be) added by JCOP • FSM • DB interface(s) • Visualization package • … • Organized in 3 layers • Supervisory Level (Control Room) • Subdetector Level (Subdetector Control Station SCS) • Subsystem Level (Local Control Station LCS) JCOP External Review, March 10th 2003, H.J.Burckhart

  7. DSS Operator IF Data Viewer Alarm IF DAQ IS LHC DAQ MRS Magnet DIP DAQ RC CERN Global Control Station (GCS) DCS_IS Config DB Conditions DB Subdetector Control Stations (SCS) CIC Tile Pixel SCT TRT MDT TGC RPC (CSC) LAr Local Control Stations (LCS) OPC LCS EB- LCS B- LCS B+ LCS EB+ LCS LCS PC LCS LCS OPC OPC OPC OPC OPC HEC HV Temp Purity ISEG HV FE Crates HV/ LV Cooling LV HV Misc. CAN • EMBA 32 ELMB • EMBC 32 ELMB • ECA 26 ELMB • ECC 26 ELMB • HV/LV 10 ELMB • ECA 8 ELMB • ECC 8 ELMB • EMBA 4 ELMB • EMBC 4 ELMB • ECA 4 ELMB • ECC 4 ELMB PVSS DDC OPC Back-End Hierarchy JCOP External Review, March 10th 2003, H.J.Burckhart

  8. Front-End • HT/LT systems • Commercial Devices (e.g. CAEN 1527, ISEG, WIENER) • Purpose-built, controlled by ELMB • Gas systems • Subdetector specific systems (standard interface to PVSS) • Alignment systems • FE electronics • Analyzers • General purpose Embedded Local Monitor Board (ELMB) JCOP External Review, March 10th 2003, H.J.Burckhart

  9. General Purpose Front-End JCOP External Review, March 10th 2003, H.J.Burckhart

  10. Reasons for ELMB • Experience from LEP: flexible I/O system needed • Homogenous solution for all of ATLAS • save development effort • ease integration • reduce maintenance effort • No commercial solution exists for usage in cavern • radiation tolerance • magnetic field • Cost (several 100k channels) JCOP External Review, March 10th 2003, H.J.Burckhart

  11. Features of ELMB • Flexible I/O functions • multiplexed ADC, 16 bit, 64 channels with signal adaptation • 8 input, 8 output and 8 definable I/O ports • SPI bus • low power consumption, opto-isolated • add-ons: DAC, 12 bit, 16-64 channels; interlock facility • Radiation tolerant for usage in cavern outside of the calorimeter • 0.5 Gy and 3*1010 neutrons per year • Operation in field of 1.5 Tesla • Remote diagnostics, loading of SW, SEE detection and recovery • Low cost (2 CHF per ADC channel) JCOP External Review, March 10th 2003, H.J.Burckhart

  12. ELMB on Motherboard ELMB Adapters JCOP External Review, March 10th 2003, H.J.Burckhart

  13. ELMB Motherboard (connector side) JCOP External Review, March 10th 2003, H.J.Burckhart

  14. Resolution and stability of ELMB 1uV JCOP External Review, March 10th 2003, H.J.Burckhart

  15. Radiation Tolerance ELMB JCOP External Review, March 10th 2003, H.J.Burckhart

  16. Read-out Chain ELMB PC (Windows) PC (Windows) xx PVSS ELMB GP SW OPC Client OPC Server CANbus Ethernet • Conversion to physical units • Network management • Signal adaptation • Raw calibration • Send data on request • Send data on change • Fine calibration • Warnings/alarms • Actions • Archiving • Data visualization • Data exchange with DAQ JCOP External Review, March 10th 2003, H.J.Burckhart

  17. Status Read-out Chain • Final elements • ELMB (1000 pieces produced) • CAN interface card (Kvaser) • OPC server (CANopen) • PVSS • Realistic system successfully operated • CAN Branch 300m long (powering, data transmission) • 32 ELMB * 6 branches (12k analogue and 5k digital channels) read into PVSS in 30 seconds (8 seconds with buffering) • 2-level PVSS system • Long term experience • 2 months operation in radiation environment • Automatic SEE recovery JCOP External Review, March 10th 2003, H.J.Burckhart

  18. Data DAQ Messages Commands ATLAS DAQ_IS DAQ_MRS LAr Tilecal … TileDCS EB- B-+ B+ EB+ ROD ... DAQ Partition Connection to DAQ DCS Global Operation ATLAS Subdetector CIC Pixel Tilecal MDT … Subsystem EB- B- B+ EB+ Cooling LV HV SAlone JCOP External Review, March 10th 2003, H.J.Burckhart

  19. Continuation of JCOP Sharing of work: • Experiment DCS team is responsible to provide the DCS to the collaboration • Support of subdetector DCS teams • Connection to DAQ • Control of common experimental infrastructure • Overall detector supervision • IT/CO is responsible for commonly used SW • PVSS support • Tools and libraries (including maintenance) • User Training • Common applications • Help experiments to use JCOP SW JCOP External Review, March 10th 2003, H.J.Burckhart

  20. Request to JCOP(IT/CO) (1) • Continuation of PVSS support PVSS is a versatile product and a good basis for DCS • General user support • Consultancy • Training • Problem shooting • Coordinate with PVSS provider ETM • Enhancement requests • Bug reporting and fixes • Administration (distribution, licenses) JCOP External Review, March 10th 2003, H.J.Burckhart

  21. Request to JCOP(IT/CO) (2) • JCOP Framework Here only main points, for all details see WG documentation • Tools for Controls Hierarchy • Tools for handling a big number of channels in PVSS • configuration • operation (e.g. alarming, masking) • Tools for data handling (Data Bases) • Configuration DB Experiments use probably different DB, provide interface • Conditions DB Full connection to the (hopefully) LHC experiment-wide DB • Data visualization The functionality of the PVSS tool is quite limited. Either substantial upgrade need (JCOP or ETM?) of connection experiments tool (e.g. ROOT?) • Alarm system Access to data would be much easier if PVSS would use a standard DB instead of its own internal one JCOP External Review, March 10th 2003, H.J.Burckhart

  22. Request to JCOP(IT/CO) (3) • Connection of Front-End equipment • HT (CAEN, Iseg, …) • LT (Wiener, …) • Crates (Wiener, … • PLC (Siemens, Schneider) • Data Interchange Protocol (DIP) • Provide tool • Application for exchange of data with LHC accelerator • Application for interaction with CERN services • Electricity • Cooling/Ventilation • Safety JCOP External Review, March 10th 2003, H.J.Burckhart

  23. Request to JCOP(IT/CO) (4) • Common Applications • Gas systems • Rack Control • Cooling systems • … • Develop Detector Safety System (DSS) • Direct Interactions with end users • Help with first usage of a building block • Help in final installation • Configuring • Commissioning • Trouble shooting JCOP External Review, March 10th 2003, H.J.Burckhart

  24. Conclusions JCOP very useful and it works quite well, but we leave now the design and prototype phase and enter the production phase. Some adjustments needed: • Clear definition is needed concerning the Responsibilities experiments  IT/CO • ATLAS TC wants a written work package agreement with JCOP (IT/CO) about deliverables an time scale (like with JCOV) • Revision of of Program Plan • Organizational structure ok, but Steering Group too big • Proposal: one person from each experiment (e.g. Technical Coordinator) plus one person from EP and IT each JCOP External Review, March 10th 2003, H.J.Burckhart

More Related