RPC Detector Control System: towards the final system Workshop on CMS RPC commissioning and upgrade Pierluigi Paolucci, Anna Cimmino I.N.F.N. of Naples Giovanni Polese Lappeenranta University Giovanni Polese

New feature for final system Improved Hardware description from Hardware tree, more detailed features for all components (boards, temperature, MAO, rack and BCs), easier management of all kind of problem happened during the MTCC . Positive performance tests in 904 using the final hardware for one wheel regarding configuring, starting up and db access operations. Additional feature for each wheel, possibility to plot simultaneously the worst six chamber. Additional information about the status of cooling, cavern environmental conditions and magnet status. RPC DCS is developed as a hierarchy where every object is represented as a node of the tree, following the CMS structure. Control Unit performs as logical decision unit, they can take decisions and act on their children, sending comands, based on their states. The logical behavior of a Control Units is expressed in terms of Finite State Machines States transitions can be triggered by: Command reception, either from its parent or from the operator State changes of its child Each single element of the structure, in the FSM approach, is a different parts of the detectors, structured as logical software units, arranged in a tree-like structure. Each logical unit is characterized by a set of well defined states. Giovanni Polese

DCS news We are migrating the entire structure to the DCS final PCs in P5. All DCS PCs have been put in place, configured and ready for working. From HV/LV point of view, the first step for W+2 test was deeply focused on the hardware setup of the entire system. All chain components has been configured and tested successfully. The HV Mainframe has been installed, configured and now works properly in USC55. This mainframe is temporarily shared with LV to allow testing. The Next step, after creating all the right links and setting the right configuration for HV,LV and T boards, is to upload the setup configuration into Db. Only after this, PVSS is able to retrieve the config from db and start to control the entire system. RPC DCS is developed as a hierarchy where every object is represented as a node of the tree, following the CMS structure. Control Unit performs as logical decision unit, they can take decisions and act on their children, sending comands, based on their states. The logical behavior of a Control Units is expressed in terms of Finite State Machines States transitions can be triggered by: Command reception, either from its parent or from the operator State changes of its child Each single element of the structure, in the FSM approach, is a different parts of the detectors, structured as logical software units, arranged in a tree-like structure. Each logical unit is characterized by a set of well defined states. Giovanni Polese

Databases Configuration DB: A version of Configuration PVSS db with all hardware structure and working parameter has been created on devdb for W+2. Next step is to move on OMDS db. Condition DB: More hardware information added on db from hw point of view, optimized thresholds for main channels parameter (Vmon, Imon, I0,V0,status,temp) and from hardware component (Board temperature, FSM status, HW status) Regarding OMDS db resources, the idea is to use a common db only for PVSS data, both for configuration and condition. Additional table and view to simplify and speed up the communication with external software. RPC DCS is developed as a hierarchy where every object is represented as a node of the tree, following the CMS structure. Control Unit performs as logical decision unit, they can take decisions and act on their children, sending comands, based on their states. The logical behavior of a Control Units is expressed in terms of Finite State Machines States transitions can be triggered by: Command reception, either from its parent or from the operator State changes of its child Each single element of the structure, in the FSM approach, is a different parts of the detectors, structured as logical software units, arranged in a tree-like structure. Each logical unit is characterized by a set of well defined states. Giovanni Polese

Conclusion The entire system fully responses to the last version of the official CMS DCS guidelines, required for the integration to the Central DCS. First PVSS DCS application version for W+2 available when the final hardware configuration will be ready (after cabling T sensor ~ 1 week). Ready to be used from not expert from the second half of May. Global DCS commissioning is foreseen from the half of Jun. Regarding Endcap, no upgrade has been done from the MTCC for qualified manpower missing. RPC DCS is developed as a hierarchy where every object is represented as a node of the tree, following the CMS structure. Control Unit performs as logical decision unit, they can take decisions and act on their children, sending comands, based on their states. The logical behavior of a Control Units is expressed in terms of Finite State Machines States transitions can be triggered by: Command reception, either from its parent or from the operator State changes of its child Each single element of the structure, in the FSM approach, is a different parts of the detectors, structured as logical software units, arranged in a tree-like structure. Each logical unit is characterized by a set of well defined states. Giovanni Polese

HV cabling multiconductor connettorization (600 ch): pretest and fixing: 1 month * 2 people  8 K€ connectorization: 2 months * 2 people  20 K€ HV cable-distrib: 1 month * 2 people  8 K€ people involved up to now: G. Passeggio, F. Cassese, A. Vanzanella A. Cimmino and P. Noli HV Patch Panel connection: 2 weeks * 2 people Giovanni Polese

Giovanni Polese

Giovanni Polese

Giovanni Polese

LV cabling tower and tower-tower cabling installation: (1 week * 2 people)/wh  5 weeks LV test: (1 week * 2 people)/tw  10 weeks temp test: (1 week * 2 people)/wh.  5 weeks Infrastructure cabling and test (1 week * 2 people)/wheel  5 weeks Giovanni Polese

HV & LV components status Log scale Giovanni Polese

Components - numbers modello ordinati consegnati mancanti SY1525 2 A3485 - MACISTE 3 1 A3512N - HV 80 47 33 BC A1676 7 A3000 - CRATE 34 A3000FB - FAN 14 A3486S - MAO 5 A3009 - LV 60 57 Late delivery To modify Late delivery Giovanni Polese