RPC Detector Control System Pierluigi Paolucci - I.N.F.N. of Naples http://www1.na.infn.it/wsubnucl/accel/cms/cms.html

What we want to monitor: Detector Control System I I.N.F.N. Naples What we want to monitor: HV and LV values  OPC server  30 Kbytes; FEB disc. Thresholds I2C  100 Kbytes; FEB pulse width I2C  100 Kbytes; FEB temperature I2C  25 Kbytes; Single Counting Rate I2C  to be calculated; Cooling system  ?  ? ; Gas system  ?  ? ; Ambient parameters  ?  ? . All data have to be logged into the Databases We can use different monitor rates to minimize the DB data rate 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

What we want to control: Detector Control System II I.N.F.N. Naples What we want to control: HV and LV systems; Cooling system; Gas system; What we want to load from the configuration DB: HV/LV setpoints FEB disc. thresholds; FEB pulse width; Status ON/OFF… Voltage V0/V1set Current I0/I1set Rump-up Rup Rump-down Rdown Trip time Trip How many subsets of HV setpoints do we need ? 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Pigi Paolucci, I.N.F.N. of Naples RPC HV-LV connections I.N.F.N. Naples RB3/RB4 ALV1 DLV1 ALV2 DLV2 HV1 HV2 Bigap ALV1,ALV2,ALV3 DLV1,DLV2,DLV3 Bigap RB2 reference plane RB1/RB2in Bigap ALV1 DLV1 ALV2 DLV2 HV1 HV2 HV1 HV2 HV3 Two non adjacent gaps will be connected to the same HV channel in order to halve the # of HV channels “without” reducing the trigger efficiency. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

SASY2000 project for RPC II Detector region Electronic house 256 I.N.F.N. Naples Detector region Electronic house 4 8 … 16 HV #1 HV #2 Branch controller #1 Complex ch. 1 256 Remote boards LV #1 LV #6 Branch controller #2 HV #1023 HV #1024 Complex ch. 512 LV #3071 LV #3072 … 256 Branch controller #16 What do we need ?? 26 ch * 12 sect * 5 wheels = 1560 LV 17 ch * 12 sect * 5 wheels = 1020 HV One mainframe is enough for the barrel

HV-LV architecture for a barrel sector I.N.F.N. Naples 26 LV channels 4 Remote Boards 17 HV channels 2 LV + I2C lines RB4 1 cc  4 LV 2 bi-gaps 2 bi-gaps 4 HV ch  2 cc 1 RB 2 LV + I2C lines 2 RB RB3 2 bi-gaps 2 bi-gaps 4 HV ch  2 cc 1 cc  4 LV 3 LV + I2C lines 1 cc  6 LV ch 3 bi-gaps 3 HV ch  1 cc RB2 1 RB 1 RB 2 LV + I2C lines 1 cc  4 LV ch 2 bi-gaps 2 HV ch  1 cc 2 LV + I2C lines 1 cc  4 LV ch 2 bi-gaps 2 HV ch  1 cc RB1 1 RB 1 RB 2 LV + I2C lines 1 cc  4 LV ch 2 bi-gaps 2 HV ch  1 cc Total Number 1560 LV channel 1020 HV channel 480 complex ch. 240 remote boards LVD channel HV channel LVA channel cc = complex channel RB = remote board EACH SECTOR 17 HV ch + 26 LV ch 8 complex ch. 4 remote boards 2 bigaps = 96 strips = 6 febs

Barrel HV-LV schema LV HV 26 LV ch/cable + 17 HV ch/cable per sector 1 I.N.F.N. Naples 26 LV ch/cable + 17 HV ch/cable per sector LV-HV 1 2 LV-HV LV-HV 3 4 LV-HV Settore -4 Settore -5 LV-HV Muon racks 2 RPC HV-LV crates Settore –6 LV HV 26 LV ch/cable 26 LV 17 HV LV-HV 5 6 LV-HV 7 8 Elect. house 17 HV 26 LV 17 HV ch/cable LV 48 remote boards/wheel  240 Remote Board 1 crates/rack  8 crates/wheel  40 crates 26 ch * 12 sect * 5 wheels = 1560 LV 17 ch * 12 sect * 5 wheels = 1020 HV HV

Pigi Paolucci, I.N.F.N. of Naples HV system Barrel I.N.F.N. Naples The barrel system consists of: wheel 1 2 3 4 5 TOT gaps 408 2040 hv ch. 204 1020 remote board 48 240 crates 8 40 racks 4*1/2 20*1/2 1020 hv channels  1 SY1527 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Pigi Paolucci, I.N.F.N. of Naples HV system Endcap I.N.F.N. Naples Each endcap system consists of: station RE1 RE2 RE3 RE4 TOT # chambers 108 90 468 # hv ch. 216 180 756 # RDB 54 45 189 # crates 6 5 21 # racks 2 8 1512 gaps/hv ch.  1 SY1527 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Pigi Paolucci, I.N.F.N. of Naples LV system description I.N.F.N. Naples BARREL 26 ch/sector * 12 sectors * 5 wheels = 1560 LV ch. 3 RDBs/sector  36 RDBs/wheel  180 RDBs. ENDCAP About 1200 LV ch corresponding to 100 RDBs The LV system needs less Remote Board than the HV system  1 SY1527 Mainframes is OK 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Total number of data to monitor for HV/LV SYSTEM BRL ch. EDC ch. VALUES TOTAL HV 1020 1512 6 15192 LV 1560 1200 4 11040 We need different HV/LV setpoints loaded in the configuration database in order to have different configurations of the RPC system: Different background conditions; Efficiency .vs. HV; Electronic calibration (FEB and trigger) HV OFF. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

More items about the HV/LV I.N.F.N. Naples What do we need to study the RPC efficiency versus the HV (plateau runs): At least 6 runs with the RPC at different HV; A trigger without RPCs (muon trig ?); Load different HV setpoints for each run: Build an automatic way to take these runs from the run control (state machine). Write data and analysis results in the database: Calculate the “new” working point for each RPC; Write them in the configuration database; Write the RPC efficiencies at the working point in the DB in order to use them in the simulation. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

96 channels + 96 channels + 96 channels Electronic architecture for barrel sectors 4-10 I.N.F.N. Naples 5 MasterLinkBoards 10 SlaveLinkBoards 2 SLB 2 SLB RB4 96+96 channels 96+96 channels 1 MLB 1 MLB RB3 96 channels 96 channels 1 SLB 1 SLB 1 MLB 96 channels + 96 channels + 96 channels RB2 1 SLB 1 SLB 96 channels + 96 channels 1 SLB 1 SLB 96 channels + 96 channels RB1 1 MLB 1 MLB 96 channels + 96 channels 5 optical links bi-gap = 48 strips = 3 FEBs 96 channels = 6 FEBs

96 channels + 96 channels + 96 channels Electronic architecture for all the other barrel sectors 5 MasterLinkBoards 8 SlaveLinkBoards 1 SLB 1 SLB RB4 96 channels 96 channels 1 MLB 1 MLB RB3 96 channels 96 channels 1 SLB 1 SLB 1 MLB 96 channels + 96 channels + 96 channels RB2 1 SLB 1 SLB 96 channels + 96 channels 1 SLB 1 SLB 96 channels + 96 channels RB1 1 MLB 1 MLB 96 channels + 96 channels Box MLB SLB Sec 4-10 1 5 10 Other sec 8 Wheel 12 60 Barrel 300 500 5 optical links/sectors 60 optical link/wheel 300 optical link barrel

BARREL: ENDCAP: FEB monitor/control data I I.N.F.N. Naples BARREL: 78 FEB/sector * 12 sectors * 5 wheels = 4680 FEBs 9360 Threshold + 9360 width + 4680 temp. 13 I2C lines/sector = 780 I2C lines ENDCAP: 2544 FEBs (4 chips)  336 I2C lines 10176 Threshold + 10176 width + 2544 temp. TOTAL number of FEB variable to monitor: 19536 Threshold + 19536 width + 7224 temp. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

FEB monitor/control data II I.N.F.N. Naples Barrel FEBs are equipped with 2 front-end chips (8 strips each) and 1 temperature sensor corresponding to the following parameters to monitor and control: 2 threshold values (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  5 bytes 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

FEB monitor/control data III I.N.F.N. Naples To monitor all the barrel FEB parameters we need: 46800 bytes (width) 46800 bytes (thresh.) 23400 bytes (temp.) To write a “new” width and/or threshold we need: 46800 bytes (thresh.); How often do we need to monitor them ? We are discussing about  How often do we need to modify them ? High background To reduce the dead time 117 Kbytes 94 Kbytes 50 KB/h  1.2 MB/day 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Pigi Paolucci, I.N.F.N. of Naples More DCS items I.N.F.N. Naples Gas system: The Gas system group will provide us also the slow control system to integrate in our DCS. Cooling: The slow control for the cooling will be developed with the DT people. Ambient: The ambient temperature and pressure will be monitored using the DT system. We are discussing about the humidity monitoring. Single rate (under discussion): Measured by link board, can be monitored per chip (8 strips), per FEB (16/32 strips) per chamber (6/12 FEBs). 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Strip and front-end board summary I.N.F.N. Naples Barrel Sectors RB4 …… 120 chambers RB3 …… 120 chambers RB2 …… 120 chambers RB1 …… 120 chambers Total number of FE Channels: 180 x 192 = 34.560 (RB1i , RB1e , RB2) 60 x 288 = 17.280 (RB2-special) 240 x 96 = 23.040 (RB3, RB4) -------------------------- Total = 74.880/16 Ch. = 4.680 FE boards x 1.2 ( spare)  5.600 FEBs 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Single Rate and strip occupancy I.N.F.N. Naples Strip occupancy: Monitor through histograms the FEB/chip/strip occupancies using the features provided by the LinkBoard. Single rate: The LinkBoard will provide also a single rate monitor per FEB/chip/strip. The histograms parameter and time window will be programmable thought the I2C line. The total number of channels are: 4.700/9.400/80.000 General questions: How many bytes ? What is our monitor rate ? What is our loading rate into the DB ?. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Warning, Alarm and more I I.N.F.N. Naples The monitored channels will be organized in “categories” following a “risk criteria”: High Risk  HV, LV and GAS Medium Risk  Cooling, FEB Temp and Single Rate Low Risk  Ambient param, width and thresh. Every channel will have more warning/alarm levels: … < LL < L < Imon (HV) < H < HH < …. (example) A combination of the warning/alarm level and the “risk category” will generate a different operation to perform during the data tacking. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Warning, Alarm and more II I.N.F.N. Naples EXAMPLE I The HV variables belong to the High Risk category. Suppose that the current drown by a gap (Imon) will have 2 upper limits: A single Imon alarm do not have to stop the run but it has to generate and temporary voltage reduction. If we have (# .gt. X) of Imon alarms we should stop it. EXAMPLE II A LV trip will not stop the runs. An HV/LV RDB crate trip will stop it . warning alarm Imon < 10 mA < 15 mA 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples

Pigi Paolucci, I.N.F.N. of Naples Conclusion I.N.F.N. Naples The HV/LV system prototype is under test in Bari and in Naples (May 2002). A PC running PVSS II is in Naples and we are waiting for a SY1527 mainframes to begin to develop some DCS code. Some items are still under discussion but I hope to freeze them for the september 2002. A collaboration with the DT and CSC group is now very important in order to define a uniform and consistent DCS muon system minimizing the effort of these groups. 01/01/2019 Pigi Paolucci, I.N.F.N. of Naples