1 / 27

ALICE DCS Review Detector applications

ALICE DCS Review Detector applications. for the DCS team. Common solutions. Common solutions for common requirements Many detectors use the same hardware: CAEN HV and LV; ISEG HV; Wiener LV; Wiener VME crates; ELMB monitoring Common access mechanisms, panels, configuration etc.

naida-giles
Download Presentation

ALICE DCS Review Detector applications

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. ALICE DCS ReviewDetector applications for the DCS team

  2. Common solutions • Common solutions for common requirements • Many detectors use the same hardware:CAEN HV and LV; ISEG HV; Wiener LV; Wiener VME crates; ELMB monitoring • Common access mechanisms, panels, configuration etc. • The same class of sub-systems will behave similar:CAEN HV and ISEG HV are expected to behave similarly in operation • Common behaviour programmed in FSM • In many aspects there are similarities in the operation of detectors • Help detectors in defining operation model (as FSM) • Define a set of standard command and states • Provide standard operation panels DCS Review, CERN Geneva

  3. Common solutions • A common solution is a whole package: • Software: set of tools for easy configuration, integration and operation of your device • Tools to ‘populate’ your device, set alarm limits, archiving properties etc. • Pre-defined database structures, and mechanisms to access them • Set of basic panels for operation of your device • Pre-defined FSM for integration in DCS • Hardware: DCS will take care of definition of cabling, connectors, services etc. [for controls part!] • e.g. CANbus cabling, ELMB cabling and power • Support & maintenance by DCS (and JCOP) • Software: assistance to detectors, updates of tools • Hardware: debugging, stock of spares (where possible) DCS Review, CERN Geneva

  4. High Voltage • 2 options: CAEN and iseg • CAEN: • Very well supported in the framework • Stable OPC server provided by CAEN • This covers 12 HV sub systems • Same solution used in 1 LV sub-system (T0) Framework PVSS II OPC client CAEN OPCserver Ethernet DCS Review, CERN Geneva

  5. High Voltage Framework • iseg: • Needs PEAK CANbus interface • PCI or USB • Non CERN standard • Well supported in the framework • ALICE contribution to JCOP • OPC server provided by iseg • Now stable • This covers 4 sub systems PVSS II OPC client Iseg OPCserver Peak CAN-PCI CANbus DCS Review, CERN Geneva

  6. Low Voltage • 2 options: CAEN and Wiener • CAEN Easy3000: • First units being delivered, under test • Now also supported in the framework • Not yet all cards • Stable OPC server provided by CAEN (as for HV) • This covers 8 sub systems • 1 of these (TOF) slightly different (sasy) • Same solution used to supply HV for 1 detector (SSD) Framework PVSS II OPC client CAEN OPCserver Ethernet DCS Review, CERN Geneva

  7. Low Voltage • Wiener PL500F12 • First units being delivered, under test • New version has Ethernet interface • Was CANbus • Will be supported in the framework • New OPC server provided by Wiener under validation • This covers 6 sub systems Framework PVSS II OPC client Wiener OPCserver Ethernet DCS Review, CERN Geneva

  8. VME crate control Framework • 1 single option: Wiener • Comes in many flavours • Control/monitoring identical • Needs Kvaser CANbus interface • Available in 4 port PCI and 1 or 2 port USB • Very well supported in the framework • This covers 14 sub systems PVSS II OPC client Wiener OPCserver Kvaser CAN CANbus DCS Review, CERN Geneva

  9. General Purpose Monitor Framework • 1 single solution: ELMB • ATLAS development, now used by all LHC experiments and services • High density I/O device (64 analog in) • Main use: temperature measurement • Needs Kvaser CANbus interface • Available in 4 port PCI and 1 or 2 port USB • Needs external power • Catered for by central power supplies • Very well supported in the framework • Used in 11 sub systems PVSS II OPC client ELMB OPCserver Kvaser CAN CANbus+ power DCS Review, CERN Geneva

  10. [FED] DIM server Intercom Front End Device – FED Framework • Physical Front-end access in ALICE is implemented in several ways • Ethernet, DDL, CAN, JTAG, custom links… • The Front-end Device (FED) hides the implementation details and provides an uniform way for accessing the FERO • PVSSII to FED communication is based on DIM PVSS II DIM client Ethernet DCS Review, CERN Geneva

  11. FED Architecture PVSSII DB FED Client Supervisory Layer FED API (DIM) Commands Services FED Server Intercom Layer Control Layer FEE Client Device Driver FEE API (DIM) FEE Server Field Layer CE Detector specific functionality implemented in FED server (detector responsibility) FERO FERO DCS Review, CERN Geneva (DCS Board Based)

  12. Serial devices (RS232) • Aim for standard way of interfacing this class • Physical interface (cables and alike) • Needs a COM port on a PC; cable length is limited • A standard (and transparent !) way to use serialover Ethernet overcomes this limit • CERN standard; expertise exists • Examples exist, several detectors start using it • Exist in single and multi-port version • Software interface (transporting the data) • PVSSII has all one needs to ‘drive’ a serial connection • Examples exist • Functional interface (exchange sensible data) • Application dependent • to be developed by the detector (using the above!) DCS Review, CERN Geneva

  13. Detector cooling and gas • Very similar systems across detectors • Build centrally by a single team (TS/CV, GWG) • We will provide a standard way of integrating into DCS • User interface, FSM, database • More details on cooling and gas in next presentation DCS Review, CERN Geneva

  14. Common and Specific solutions • Common solutions described and FED concept cover over 80% of all (approx. 100) sub systems. • The other sub systems are ‘specific’ solutions • Each of them will be quickly presented here DCS Review, CERN Geneva

  15. Specific solutions [SDD] • Low Voltage: AREMpro • Interfaced through Ethernet, using DIM • SDD will have to take care for integration • Would be good if it could mimic standard LV (e.g. Wiener) • DIM server under development (will be in device), no integration in PVSSII yet DCS Review, CERN Geneva

  16. Specific solutions [TPC] • Very High Voltage: Heinzinger • Interfaced through dedicated PLC system • Developed by DCS team • Prototype exists (and tested), next version ready for TPC tests • Working on integration into DCS • Includes current monitoring in resistor rods DCS Review, CERN Geneva

  17. Specific solutions [TPC] • Gating and calibration pulsers • Interfaced through serial interface • Hardware being build, no integration in DCS yet • Laser • Comprising laser, mirrors, cameras • Now interfaced directly to PVSSII (prototype) • Drift velocity monitor • Multi-component system (HV, ELMB, analysis device) DCS Review, CERN Geneva

  18. Specific solutions [TRD] • HV distribution boxes • Control from DCS board, access through FED • Prototype exists, integration into HV DCS by TRD DCS Review, CERN Geneva

  19. Specific solutions [TOF] • LV CAEN “Sasy” system • Or “ALICE-box” • Close collaboration with CAEN • System very similar to CAEN Easy system • Working on integration in JCOP framework DCS Review, CERN Geneva

  20. Specific solutions [HMPID] • Liquid system • Dedicated PLC system • Exists for 1st module, well integrated in DCS • Temperature monitoring • Using liquid system PLCs to connect sensors • More efficient then creating another (ELMB based) system DCS Review, CERN Geneva

  21. Specific solutions [PHOS] • Bias voltage regulation • Control from RCU (DCS board), access through FED • Integration in HV DCS by PHOS • LED calibration system • Current proposal to use CANbus • Non standard CANbus interface, not using FED • Investigating ‘standard’ FED concept with DCS board DCS Review, CERN Geneva

  22. Specific solutions [PHOS] • Temperature monitoring (both PHOS and CPV) • Based on ELMB and Ni100 sensors • Need specific calibration • Current proposal through special non-standard software (Sarov developed) • Investigating standard ELMB solution • Crystal cooling system • PLC-like system (non-CERN standard) • Interface through serial connection • Interfaced to Sarov developed scada (to PVSSII via DIM) • Assessing effort to directly interface to PVSSII DCS Review, CERN Geneva

  23. Specific solutions [µ-trk] • HV distribution (for stations 3,4 and 5) • Interface through serial connection • Integration in DCS by µ-trk • Geometry monitoring system • Specific driver boards, access through FED mechanism DCS Review, CERN Geneva

  24. Specific solutions [T0] • CAEN mainframe shared with V0 • Integration of shared hardware into DCS to be validated • Threshold control • Current proposal ELMB with DAC • Only application in ALICE, exists in ATLAS • Laser attenuator • Interface through serial connection • Prototype (using Digi) exists DCS Review, CERN Geneva

  25. Specific solutions • TRD and μ-trk have a HV distribution ‘box’, PHOS has a HV regulation • Started an effort to see how this can be unified from the controls point of view DCS Review, CERN Geneva

  26. Overview common vs. specific Common solution FED concept Specific solution DCS Review, CERN Geneva

  27. DCS Review, CERN Geneva

More Related