1 / 11

RPC D etector C ontrol S ystem: towards the final system

RPC D etector C ontrol S ystem: 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. Requirements. DCS Items:

noura
Télécharger la présentation

RPC D etector C ontrol S ystem: towards the final system

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. 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

  2. Requirements • DCS Items: • to monitor detector and environmental parameters, calibrate, set and maintain the configuration • take appropriate corrective and immediate actions to protect the equipment, maintain detector stability and reliable performance, and alert on any malfunctions. • The RPC DCS system have to control and monitor: • ~ 800 HV channels • ~1500 LV Feb channels • ~350 LBB channels • 320 T sensors • ~30 MAO channels • ~10 RH sensors Giovanni Polese

  3. Architecture RPC Barrel Hardware Endcap COMMANDS Actions Wheel Disk UXC_b/e USC_b/e … … Sector Ring … Wheel Rack … … … Chamber Chamber … … BC BC T Device Unit board board HV HV SY1527 SY1527 LV feb LV feb rack rack LV LBB LV LBB Giovanni Polese

  4. FSM Schema TOP • DCS States: ON, OFF, STANDBY,ERROR • RPC States: ON, OFF, STANDBY, RAMP1STEP, • RAMP2STEP, ERROR Wh,Dis • STANDBY: HV ON @ intermediate voltage, • LV ON; • ON: HV ON @ nominal voltage, LV ON; • RAMP1STEP: from OFF to STANDBY; • RAMP2STEP: from STANDBY to ON; Sec,Ring Ch OK • Hardware descrition status and summary of all possible error and warning condition, each device level offer major details about error message Hardware Error NOT_OK RDW • Logical Description of the channels behavior: • (ON,OFF, RAMPING,AND DIFFERENT • SEVERITY ERROR CONDITIONS) ON OFF Hv STB RUP Giovanni Polese

  5. HW PVSS GUI System Overview Giovanni Polese

  6. RPC DCS during MTCC • The system was successfully integrated in the central DCS at the middle of July • During the MTCC the system worked well; it was stable, robust and has never crashed. • The FSM has never crashed and has followed correctly the logic behavior of the entire system. • The GUI has been proved to be user friendly and used easily from the shifters and no wrong actions have been performed by them. • All data has been properly stored during the MTCC on the OMDS db from barrel and endcap PCs. Giovanni Polese

  7. New feature for final system • We have performed a positive test in 904 using the final hardware for one wheel. • Additional Panel for Hardware tree, more detailed features for all components (boards, temperature and humidity sensors, MAO, rack and BCs). • At Wheel level, we add the possibility of monitoring up to 6 plots for worst chambers. • Improved the plot manipulation. It’s now possible to scaling axis, zooming and moving time interval. • Additional information about the status of cooling, cavern environmental conditions and magnet status. Giovanni Polese

  8. Alarm Handling • The alarm handling uses different severity level and manages the main working parameters (Imon and main alarm channel conditions). • All alarm conditions are sent to GUI and visualized in a dedicated panel • We add the possibility to send the alarm condition to the expert CERN mobile between SMS and also the possibility to acknowledge it. Giovanni Polese

  9. Access Mode • Different access level: user, operator and expert with different privileges granted. • Every user must login in in the system with NICE password and must to be registered into DB for defining the access level. Low level access (shifter) can just switch on/off chamber and LV/LBB channels, but CANNOT change chamber values (V0,I0) Giovanni Polese

  10. Databases • Configuration DB: A version of Configuration PVSS db with all hardware structure and working parameter has been created on development DB. Next step is to move on OMDS db • Condition DB: During the MTCC the db connection worked well and we was able to store all information from channels behavior (Vmon, Imon, I0,V0,status,temp) and from hardware component (Board temperature, FSM status, HW status) • PVSS DB manager requires many simultaneous connections, so as done by all the other subdetector, we have to move to an adhoc tablespace only for PVSS data. • PVSS use a native schema to write and read data from DB (automatic mode) • We are developing a set of tables to complete the hardware description. Giovanni Polese

  11. Conclusion • We are now migrating to final system, redesigning and optimizing the resources management, starting from the lessons learnt during the MTCC. • Improved the FSM and inserted additional component (Temperature, Mao, Rack). • Migrate to the final db schema on OMDS machine for Configuration and Condition DB. • A working version for Barrel will be ready at the end of May, in time for the DCS commissioning. • Regarding Endcap, we need people to update the system developed by Anna Cimmino for the MTCC. • The entire system fully responses to the last version of the official CMS DCS guidelines, required for the integration to the Central DCS. • PVSS-XDAQ communication and integration in the Run Control. Giovanni Polese

More Related