550 likes | 1.54k Views
Overview of the DCS Systems. Electronics Week – DCS Review. J. Varela, May 6th 2004. Experiment Controls. Run Controls (RCS): Configure and operate all local/global data taking sessions Monitor and protect the measurements and the data flow
E N D
Overview of the DCS Systems Electronics Week – DCS Review J. Varela, May 6th 2004
Experiment Controls Run Controls (RCS): Configure and operate all local/global data taking sessions Monitor and protect the measurements and the data flow Based on the CMS online software framework (XDAQ, RCS) and commercial products (DBs, SOAP, XML, e-tools etc.) Detector Controls (DCS): Setup and monitor the detectors and the environment Monitor and protect the apparatus equipment Based on industry standards (PLC, field buses, PVSS and JCOP tools)
Detector Control (DCS systems) • Detector subsystems • HV/LV • Fluids and environment • Cooling • Racks/Crates • Temperatures • Infrastructures • Test systems (Laser, LED, alignment camera etc..) • Experiment supervision • DCS Resources handling • Alarm and loggings • History data base • External systems communication. TPG Trigger Primitive Generator RTP Regional Trigger Processor LV1 Level-1 Trigger Processor GTP Global Trigger Processor TTC Timing, Trigger Control sTTS synchronous Trigger Throttle System aTTS asynchronous Trigger Throttle System FES FrontEnd System FED FrontEnd Driver FEC FrontEnd Controller D2S Data to Surface RU Readout Unit BU Builder Unit FS Filter Subfarm EVM Event Manager RM Readout Manager BM Builder Manager EVB Event Builder RCN Readout Control Network BCN Builder Control Network CSN Computing Service Network DCN Dtector Control network DSN DAQ Service Network DCS Detector Control System RCS Run Control System Supervisor structure etc.
JCOP Framework • New Framework released on 16th January 2004 • Version includes: • Core: Device Editor/Navigator, FSM • Devices: CAEN, Wiener, ISEG*, ELMB, Analog/Digital, Accelerator Data Server • Tools: Trending, Installation, Configuration Database • FW Driver: DIM
Local DCS root node Central RCMS Central DCS Integration DCS – RCS Under discussion: Data taking – DCS Local nodes are integrated in the Run Control tree No beam periods – Central DCS takes control of DCS tree DCS services Sub-Detector Controller Local XDAQ Nodes (DAQ & DCS) Interfaces already existing: - RCS – DCS : commands and status ownership - XDAQ – PVSS: data exchange Electronics Setup, etc. Local DCS tree for HV, LV, P, T, etc. Plans to install and test RCS-DCS demonstrator in PC farm at CERN in 2004
DCS Supervisor Demonstrator Distributed FSM Hierarchy Global State Central Control Panel SubDetector States Graphical visualization of CMS detector states Services States SubDetector Control Panel Graphical visualization of subsystem states Detector Subsystems
PVSS Scaling Up • System with 130 PVSS projects each with 40k dpes (variables) was built in 15 machines • Start-up time for a project ~ 30 secs • Memory usage for a project ~ 80 MB • Additional memory per connection ~ 3 MB • On-going tasks: • Alarm handling • Throughput • Parallelisation of start-up • Building a representative system hierarchy • Project behind schedule • Measurements (memory, throughput) are essential to define physical DCS architecture (machines, network)
DCS and Online Data Bases • DCS environmental data is stored in PVSS Archive or in external Oracle DB (not yet available in PVSS) • DCS configuration data can be stored/ retrieved from DCS Oracle DB: • Test new Framework interface to Configuration DB • Build interface between Framework and CMS Equipment Management DB: • Already done for Rack Control Application - CMS • General hardware configuration (HV, etc.) – JCOP Delivery • Integration issues with RMCS, XDAQ, DCS, Sub-detector DBs
Interface to DSS • JCOP/DSS system for CMS delivered and installed • No equipment is connected presently • Version 2.0 of the JCOP/DSS S/W is being completed • More powerful PLCs will probably allow integration of DSS and RSS in a single system • Can JCOP/DSS technology be used to implement Sub-detectors Safety Systems (SSS)? Too late? • Define DSS alarm/action matrix and DCS comand/statesand make sure they are compatible • Interface DCS-DSS needs to be implemented (manpower issue)
High Voltages • CAEN power supplies are fully integrated in the DCS Framework • CAEN power supplies already used by ECAL in Test Beam • CMS request for new CAEN boards to be supported in the FW is accepted: • CAEN EASY System • CAEN DT High-Voltage • ECAL Endcap Power Supplies: • ISEG? Considering now CAEN option • Problems with ISEG OPC Server
Low Voltages • Two solutions for Control and Monitoring of AC-DC Converters: • - Proposal from CAEN (GECO Board), integrated in overall solution for LV distribution. • - Atlas ELMB (provided dedicated CMS production can be organized) • Both solutions are supported by JCOP software
Rack Control • Rack Control is a JCOP project with multiple components: • Rack mechanics and cooling (EST/LEA) • Rack power and control (ST/EL) • Rack monitoring hardware (EP/ESS) • Smoke detection (ST/MA) • Rack Control Software (CMS) • JCOP Rack Application is being developed by CMS (R. Gomez-Reino): • Specification document discussed in JCOP framework • First prototype was implemented • Configuration using Equipment Management DB • Interface to Monitoring Board is working • Discussion with ST/EL on communication with power control PLC (draft doc) • Interplay with RSS/DSS is better understood now • Complete rack prototype suitable for software test is being installed by EP/ESS and ST/EL
Rack Control Application EMDS Interface FW Device Editor Rack Monitoring Rac 3D View (in development)
Detector Environment Monitoring Need to review sub-detector hardware plans and find common solutions (sensors, readout) Define plans for usage of ELMB (Atlas Embedded Monitoring Board): Used by Rack System, ECAL and Alignment RPC is considering it Others? Do we need a dedicated production of ELMBs?
Gas Control Model • Experiment Gas Systems have a common implementation (provided by CERN Gas Group & JCOP) • All the sub-detector Gas Control Systems are supervised by a single PVSS system (redundancy is foreseen) • All gas parameters are made available to Central DCS or Sub-detector DCSs. • Sub-detector panels may display any gas parameters. These panels will not allow any actions. All actions must be performed from the Gas System panels. • Pannels in the Gas System will be developed and maintained by the GCS team. These can be accessed from any DCS station. Actions can be performed by shift operator and/or sub-detector gas expert (different users have different permissions) • A central gas support team, including piquet service, will be provided for all the experiments. Approved by CMS DCS Board
LHC Data Interchange Protocol • DIM chosen as the middleware for DIP • Abstract API on top of DIM • Implementations for the various domains expected in Q2 04 • Possibly available for test-beams in 04 ( access to SPS data )
JCOP Deliverables Hierarchy Control (4Q 2003) ok Configuration Tools (4Q 2003)ok HV Control (4Q 2003)ok Detector Safety System (4Q 2003)ok Data visualisation (4Q 2003)ok Web Access (4Q 2003)ok Gas Control (2Q 2004) Crate Control (2Q 2004) Rack Control (2Q 2004) Cooling and Ventilation Control (3Q 2004) Interface to Conditions Data Base (3Q 2004) Interface to Technical Services (1Q 2006) Interface to LHC Accelerator (3Q 2006)
Subdetector DCS Milestones DCS Project Planning (April 03):
Central DCS Milestones DCS Conventions and Interfaces Q2 03OKNaming scheme, Commands, States Data Bases Specification Q3 03OKConfiguration, Conditions, Equipment, Archive Demonstrator Central DCS Q4 03OKIncluding scaling tests First prototype of complete DCS system Q4 04Integration of subdetectors (Slice test) Configuration Database DAQ interface Integration with Dedicated Systems Gas, Cooling, Racks, DSSQ1 05Magnet, Technical servicesQ1 06