1. RPC Detector Control System
Pierluigi Paolucci - I.N.F.N. of Naples
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

2. CMS Experiment Control
I.N.F.N. Naples
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) ad commercial products (DBs, SOAP, XML.....)
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)

3. Pigi Paolucci, I.N.F.N. of Naples
JCOP framework
I.N.F.N. Naples
New Framework released on 16th January 2004  installed and working in Naples
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
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

4. Pigi Paolucci, I.N.F.N. of Naples
Integration DCS - RCS
I.N.F.N. Naples
Central
DCS
Central
RCS
Under discussion:
Data taking – States, Local and Central DAQ/DCS
No beam periods – Central DCS takes control of DCS tree
DCS services
Sub-Detector
Controller
Local DCS node
Local
XDAQ nodes
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
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

5. RCMS  DCS XDAQ  DCS (anyclient  PVSS)
PVSS SOAP Interface
RCMS  DCS
XDAQ  DCS
(anyclient  PVSS)
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

6. Pigi Paolucci, I.N.F.N. of Naples
SOAP Motivation
I.N.F.N. Naples
RCMS communication with DCS
CMS DAQ (RCMS/XDAQ): SOAP messages (over http)
 SOAP talker/listener
as decoupled as possible (avoid dependencies)
 run on the side of PVSS
no native support in PVSS for external communication
solution: SOAP listener running as PVSS API manager
PSI = PVSS SOAP Interface
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

7. Pigi Paolucci, I.N.F.N. of Naples
PSI communication
I.N.F.N. Naples
CMS RCMS
TK RCMS
HCAL RCMS
ECAL RCMS
EVB RCMS
MUON RCMS
ECAL DAQ
ECAL DCS
XDAQ
BARREL
ENDCAP
BARREL
ENDCAP
XDAQ
XDAQ HV LV
XDAQ
XDAQ
XDAQ
XDAQ
XDAQ
XDAQ
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

8. Pigi Paolucci, I.N.F.N. of Naples
SOAP requirements
I.N.F.N. Naples
SOAP messages over http
read/write access (read for all)
logical (Command  DP+value) and raw interface
multiclient operation
synchronous operation (hide asynchronous PVSS)
sync GET
command sync with states
identification, authentication, security
performance: from few/sec to maybe ~thousands/sec (?)
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

9. Pigi Paolucci, I.N.F.N. of Naples
PVSS II and JCOP
I.N.F.N. Naples
Channel DB Manager to define your hardware and software variables, define alarm, connect to hardware..
Panel Editor  to create/modify your panels
Alarm Handling  to generate/monitor alarms
Electronic Logbook  operation logbook
Archiving  to archive your data
In the future it will be correlated to the Oracle CMS database.
State Machine (SMI)  JCOP tool
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

10. Pigi Paolucci, I.N.F.N. of Naples
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
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

11. DCS and Online Data Bases
I.N.F.N. Naples
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
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

12. Pigi Paolucci, I.N.F.N. of Naples
Rack Control
I.N.F.N. Naples
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)
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

13. Rack Control Application
I.N.F.N. Naples
EMDS Interface
FW Device Editor
Rack Monitoring
Rac
3D View (in development)
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

14. Pigi Paolucci, I.N.F.N. of Naples
Gas Control Project
I.N.F.N. Naples
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
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

15. DCS overview The RPC Detector Control System schema RPC DCS HV LV temp
I.N.F.N. Naples
The RPC Detector Control System schema
RPC DCS HV LV
temp
FEB
Gas
Cooling
From other
DCS node
12 crates
80 boards
480 ch.
20 crates
60 boards
720 ch.
300 sensors
10 ADC
About
5000
FEBs
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

16. Pigi Paolucci, I.N.F.N. of Naples
Some DCS numbers
I.N.F.N. Naples
BARREL + ENDCAP
HV system  ch. = boards
LV system  ch. = boards
Temperature  ? ch. = ? boards
Front End  FEBs
Gas
Cooling
Rack, crate
Ventilation
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

17. Pigi Paolucci, I.N.F.N. of Naples
DCS status overview I
I.N.F.N. Naples
HV channels (80 boards) placed in the 16 crates;
Tender is started in December 03 and is finished on May 04
Easy Prototype in July 04;
Prototype Test in Naples/ISR from Sept 04;
20% of the system in Dec 04;
Board test at CERN from Jan 05;
Full system in Sept 05;
Installation and commissioning 06.
LV channels (60 boards) placed in the 20 crates;
CMS found a common solution;
A3009 board with 12 ch., 2-8, V - 9A, 45 W, 5 boards/crate
Tender at CERN 04;
Full system available in Dec 05;
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

18. Pigi Paolucci, I.N.F.N. of Naples
DCS status overview II
I.N.F.N. Naples
Temperature probes  readout 10 ADC boards;
100 probes installed (on the chambers); 250 probes ready at the assembling sites;
An ADC/DAC board with 128 ch. is under design for ATLAS & CMS by the CAEN company;
The board will be integrate in the EASY crate;
Prototype and test in the 2004;
Full production in the 2005.
Front-end Front End Boards 800 Link boards in 60 crates
Control/monitor width, threshold and temperature
monitor the RPC/FEB performances (occupancy, rate, noise….)
Racks and crates, gas, cooling and ventilation: will be developed using a common solution/tools for the CMS sub-detectors.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

19. Pigi Paolucci, I.N.F.N. of Naples
DCS connection Schema
I.N.F.N. Naples
Control
Room
SY1527
20 Bus lines
12 Bus lines
splitter
HV crates
LV + Temp
LB crate
Detector
LV + Temp
LB crate
300 Optical 1.6 Gbit/s
LV + Temp
LB crate
LV + Temp
LB crate
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

20. Temperature sensor
I.N.F.N. Naples
Our goal is to measure the iron gap temperature with a precision of 1oC in order to:
compensate the HV working point in case of a large gradient of the temperature e/o atmospheric pressure;
study the RPC aging and the current/noise behaviors taking into account this crucial parameter;
Switch off the chamber/sector/wheel in case of “high” temperature.
We have decided to use
the Analog Device
AD592BN transducer,
after having tested
different sensors.
AD592 temperature transducer
High Pre-calibrated Accuracy: 0.5oC +25oC
Excellent Linearity: 0.158C max (0oC to +70oC)
Wide Operating Temperature Range: –25oC to +105oC
Single Supply Operation: +4 V to +30 V
Excellent Repeatability and Stability
High Level Output: 1 mA/K
Two Terminal Monolithic IC: Temperature In/Current Out
Minimal Self-Heating Errors
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

21. Pigi Paolucci, I.N.F.N. of Naples
Front End Board I
I.N.F.N. Naples
The front end electronic boards communicate with the Link Board through the I2C bus;
Each Slave LB receives data from up to 6 FEBs  96 strips;
Each Master LB is connected to, not more, than 2 SLB;
MLB transmits data to the control room via optical fiber;
Each LB crate house up to 8 LBs and has 1 Control Board (CCU);
The RPC continuous monitoring (noise rate, occupancy…) will have a refresh rate of 10 sec;
For each strip the events before and after windowing are counted during a defined period of time. That allows plotting of rates and efficiency;
There are two 32-bit counters for each group of 128 channels/strips;
The amount of data to be sent is 2*32*128 = 8 Kb/10s/LB/plot.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

22. Pigi Paolucci, I.N.F.N. of Naples
Link Board Schema
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

23. Front End Board II
I.N.F.N. Naples
Additionally for the orbit synchronization there are ca bit counters (1 for each bunch crossing) producing ca. 128 Kb of data / plot. But these probably can be read less often.
The theoretical throughput of a CCU chain (up to 27 CBs) is 4 MB/s.
The theoretical throughput of a LB box is 4 MB/s / 27 = 152 KB/s.
The theoretical throughput of a Link Board is 152 KB/s / 8 = 19 KB/s.
Required throughput for a continuous monitoring of one RPC is:
128 strips * 2 counters * 32 bits = 8 Kb/10s = 100 Bytes/s.
The I2C communication does not contribute significantly to the total CCU load.
The total bandwidth depends on the number of CB's in single CCU chain (serviced by a single FEC).
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

24. First examples Clusters Size Distribution
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

25. Pigi Paolucci, I.N.F.N. of Naples
Front End Board - XDAQ
I.N.F.N. Naples
The Warsaw people are working on the FEB monitorig and control and on the integration of it in the XDAQ framework
They already have a lot of work done  see Wrochna talk
We have an official meeting during the CMS week to discuss and organize the DCS trigger/RPC system and the Online Monitoring and the Offline Monitoring.
Some test periods are scheduled for the next 3 month in which we will test the Link Board system with the barrel/endcap RPC  I2C functionalities
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

26. Pigi Paolucci, I.N.F.N. of Naples
RPC Configuration
DataBase
Pierluigi Paolucci - I.N.F.N. of Naples
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

27. Pigi Paolucci, I.N.F.N. of Naples
RPC Barrel
I.N.F.N. Naples
HV system  ~ 480 channels
config. param. = 8
cond. param. = 11
LV system  ~ 750 channels
Temperature  ~ 300 channels
Front End  ~ 4680 Front-End Boards
config. param. = Threshold & Width
cond. param. = Rate/Occupancy histograms
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

28. 9.360 Threshold + 9.360 width + 4.680 temp.
Front-End Board Data
I.N.F.N. Naples
Barrel FEB is equipped with 2 front-end chips (8 strips each) and 1 temperature sensor. For each chip there are:
2 threshold value (hardware defaults of 200 mV);
2 width values (hardware defaults of 100 ns);
1 temperature value.
How many operations/bytes do we need to read/write this parameters ??
Read width/thresh.  2 write + 1 read  5 bytes
Read temperature  2 write + 1 read  5 bytes
Write width/thresh.  3 write  6 bytes
TOTAL number of FEB parameters are
9.360 Threshold width temp.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

29. RPC Barrel configuration Data
I.N.F.N. Naples
Barrel RPC detector is equipped with 480 HV channels and with 780 LV channels.
To configure the detector we need to set:
Vset, Vmax, Iset, Imax, Trip, Rup, Rdown, On/Off.
HV & LV configuration requires about
1260 ch * 8 par. = par * 2 bytes = 20 KB
FEB configuration requires about
3.4 Kbytes per Link Board
corresponding to 2 MB.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

30. RPC configuration states
I.N.F.N. Naples
The RPC detector will have 4 different states (run, calibration, “injection/safe” and off);
RUN  LVON && HVON (status = = working voltage) && FEBThresholdLoaded && NoiseRateOK
SAFE  HVON (status = = safe voltage)
CALIBRATION  LVON && FEBThresholdLoaded && NoiseRateOK && different voltages.
“Plateau calibration” needs 5-7 runs with different configuration parameters (HV set-points) when the others muon systems are working/triggering in “normal mode”.
RPC must be in local mode and the RPC Local DAQ will take data.
Offline monitoring to calculate the efficiency curves.
Noise calibration runs needs few runs with different FEB thresholds but fixed HV set-points.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

31. Front End Board Summary
I.N.F.N. Naples
RPC/FEB monitoring requires about
100 Bytes/s per Link Board
corresponding to 60 KB/s in the barrel.
FEB configuration requires about
3.4 Kbytes/s per Link Board
corresponding to 2 MB/s in the barrel.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples

32. Pigi Paolucci, I.N.F.N. of Naples
Conclusions
I.N.F.N. Naples
The HV tender is finished; a prototype will be ready in July 04. The production will finish in September 05.
The CMS LV project is almost ready. The tender will start in a couple of months. The CAEN has a LV board designed for RPC.
100 out of 300 temperature sensors (AD592BN) have been installed on the chambers and tested at the ISR.
The Link Board test-beam project is going on. New check/results during the next test beams (June-Endcap/July-Bari/October-Barrel).
The histograms and snapshots work well and have proved their usefulness in testing the performance of chambers.
A full time student from Naples is working on the RPC DCS and we will have a first complete prototype (HV-LV-Temp) at the end of the 2004.
14/01/2019
Pigi Paolucci, I.N.F.N. of Naples