AHCAL Shift Instructions for HGCAL + AHCAL TestBeam at CERN SPS in July 2017
Contents
- AHCAL Shift Instructions for HGCAL + AHCAL TestBeam at CERN SPS in July 2017
during ongoing run
- the box below "Measurement_start" should be bright green and read "Yippie!!"
- the four large displays should be changing all the time (except for periods of ~10 seconds where we do temperature readout, then the little LED below "Temp RO scheduled" should be bright green)
- the table on the right should show 12 rows with 4 chip numbers each
- in the box "Common DAQ" the upper box should be dark green and read "Listen", the lower box should be blue and read "Connected".
when run is stopped
- the box below "Measurement_start" should be dark green and read "Start"
- the four large displays should be not changing
- the table on the right should show 12 rows with 4 chip numbers each
- in the box "Common DAQ" the upper box should be bright green and read "Listening", the lower box should be red and read "Disconnected".
restart the labview
- All labview windows must be closed (including the Labview project assistant, which appears when the last file/project is closed)
The labview control program is located in f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\
Labview is started by double-clicking on the AHCAL_DAQ_xLDA.lvproj file
In the Labview project navigator (not the windows explorer), open main.vi by double clicking
- run the labview program (the icon with arrow pointing right right in the menu bar on the left side
- in tab "2) System Setup" click on "Configure CCC", then "Configure x-LDAs"
- in tab "5) Take Data" click on the "Listen" if it is not switched on already (on = light green)
- Operation of labview program can be checked independently by clicking "Start" in tab 5). after ~20 seconds, A lot of data should come from all 12 layers. Test is stopped by clicking on the gray button with "STOP" label (do not confuse with the blue "STOP" in top left corner). It takes few seconds until it is stopped. If no data arrive, call the expert.
Configure the detector from scratch
After the power cycle of the AHCAL detector, following steps bring AHCAL to a proper configured state.
Power on
Power is connected from dedicated windows PC and controlled via a labview program. This PC is next to the Beam steering PC. If the program is not running (or crashed), the is a shortcut on desktop to the labview project, which is located in D:\MPOD_labview\AHCAL_MPOD.lvproj
- Switch-off procedure:
- first switch off high voltage: u400-u407, u500-u503
- wait for these HV channels to ramp down
- switch off 12V (u100-u107, u300-u303)
- switch off 5V (u0-u7, u200-u207)
- Switch-on procedure:
- first switch on 5V (u0-u7, u200-u207) and ensure they were switched on correctly
- switch on 12V (u100-u107, u300-u303) and ensure they were switched on correctly
- switch off high voltage: u400-u407, u500-u503 and ensure they were switched on correctly
expected currents:
|
4.8V |
12V |
High Voltage |
before initialization |
1.2-1.5 A |
0.1 A |
+-0.002 A |
after configuration |
1.8-2.0 A |
0.1 A |
+-0.003 A |
running |
1.8-2.0 A |
0.1 A |
+-0.003 A |
temperature readout |
1.2-1.6 A (?) |
0.1 A |
+-0.003 A |
Configuration
Configuration and datataking labview is located on a PC in the beam area with IP addresses 192.168.1.11 (AHCAL network) and 192.168.222.42 (HGCAL network). There is dedicated computer (called "onlinemonitoring", the PC with a big screen) for the remote desktop to that PC. To connect, go to directory ~/rdesktop-1.8.3 and start with command ./rdesktop -u calice 192.168.1.11 -g 1900x1100.
If the labview control is not running, start the labview program from f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\AHCAL_DAQ_xLDA.lvproj, then start main.vi from the project explorer
- in tab "2) System setup": (see picture above)
Select CCC config path to following file: f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\ccc_hgcal_together.xml
- select the CCC mode to "HGCAL veto+stop+wait"
- click "Configure CCC"
- switch on the "Timestamps" and click on "Configure LDA" button
- click on the "A)VDAC POWER" "ON" button. after the powercycle, it will take longer and few layers will not respond properly. Try again, until both "set" and "ack" LEDs net to the button stay all green.
- click on the "B)VDDA POWER" "ON" button
- click on the "C)VDDD POWER" "ON" button
- click on the "D)CALIB POWER" "ON" button
click on the "E)OpenColl. Power "ON" button
- click on the "A)ASIC POWER AND RESET" "ON" button
- in tab "3) Slow Control": (see picture above)
fill \AT to the "Add suffix to path" text field
- press "Autopopulate SCs"
- press "Write SC" button. Takes few seconds after all layers are configured.
- in tab "4) Calibration": (see picture above)
- click on "Set" in the "Delay lines" section
- click on "Set" in the "DACs (VCALIB)" section
- switch on the "Pre_Bias 2" in the "Enable Section"
- switch off the "TCALIB1 (5)" in the "Enable Section"
- click on "Set" in the "Enable Section" section
- in tab "5) Take Data": (see picture above)
- click on the "set" in the "Setup Testbeam mode (Auto Trigger)" section. Takes ~5 seconds to finish
- ensure the "Listen" button is switched on and shows "Listening" text.
- System is ready to be started from eudaq.
how to do a LED calibration
First, change the configuration in Labview:
- ensure the detector is stopped (check the color of the "START" button in tab 5).
- go to tab 2 (System Setup).
Select CCC config path to following file: f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\ccc_hgcal_separated.xml
- select the CCC mode "HGCAL Independent"
- click "Configure CCC"
- switch off "Timestamps" in the LDA setup
- click on "Configure x-LDAs"
- go to "3) Slow Control"
fill \ET_IC to the "Add suffix to path" text field.
- press "Autopopulate SCs"
- press "Write SC" button. Takes few seconds after all layers are configured
- go to "4) Calibration"
- switch on the "TCALIB1 (5)" in the "Enable Section"
- click on "Set" in the "Enable Section" section
- Go to tab 5 (Take Data)
- click on the "set" in the "Setup LAB mode" section.
- switch off the "Temperature compensation" LED, so that it shows "no" caption
- ensure the "Listen" button is switched on and shows "Listening" text.
Then the LED is started from a special version of EUDAQ, which loads different configuration files and executes them. This eudaq is located on the "flchcallab4" in the testbeam area with IP addresses 192.168.1.10 (AHCAL network) and 192.168.222.43 (HGCAL network). There is dedicated computer (called "flchcallab6", left from the computer with a big screen) for remote execution of the eudaq. There is already opened terminal in the very right desktop of that PC, which is already connected to the EUDAQ PC, from where a single command is sufficient ./LED_2017 to start the EUDAQ. To start the EUDAQ from a new terminal, or from different computer execute:
ssh -X calice@192.168.1.10 #or 192.168.222.43 from svhgcal01 cd /home/calice/Desktop/EUDAQ1.6/producers/calice/scripts/ ./LED_2017
In EUDAQ:
load a configuration file /home/calice/Desktop/EUDAQ1.6/producer/calice/scripts/conf_dailyLED_July/LED_00.conf
- click "config" and wait. It takes ~20 seconds to finish the config
- check, that there is no hadron beam! Only muon beam is tolerated during the LED calibration
- click on "Start".
- configuration files 01,02,03,04 and 05 will be loaded and executed automatically within ~30 minutes
- if the eudaq doesn't reload and doesn't restart new run, the EUDAQ needs a restart. Then the next configuration file after the last successful configuration file can be loaded and it will automatically continue with running till LED_05.conf.
- When the LED is finished (LED_05.conf was loaded and executed), it is better to terminate the EUDAQ.
How to configure AHCAL for combined physics runs from LED mode
First, change the configuration in Labview:
- ensure the detector is stopped.
- go to tab 2 (System Setup).
Select CCC config path to following file: f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\ccc_hgcal_together.xml
- select the CCC mode "HGCAL veto+stop+wait"
- click "Configure CCC"
- switch on "Timestamps" in the LDA setup
- click on "Configure x-LDAs"
- go to "3) Slow Control"
fill \AT to the "Add suffix to path" text field.
- press "Autopopulate SCs"
- press "Write SC" button. Takes few seconds after all layers are configured
- go to "4) Calibration"
- switch off the "TCALIB1 (5)" in the "Enable Section"
- click on "Set" in the "Enable Section" section
- Go to tab 5 (Take Data)
- click on the "set" in the "Setup Testbeam mode (Auto Trigger)" section. Takes ~5 seconds to finish
- switch on the "Temperature compensation" LED, so that it shows "yes" caption
- ensure the "Listen" button is switched on and shows "Listening" text.
How to make the detector independent
This guide describes how to make the AHCAL detector independent on the HGCAL, which does following things:
- disabling the veto signal to HGCAL
- Ignores the HGCAL WAITING_FOR_TRIG signal
- stops listening the HGCAL triggers.
The procedure:
- ensure the detector is stopped (from EUDAQ usually). If eudaq is crashed, pressing the gray "STOP" with red text should do it. If not, close and restart the labview.
go to tab 2 (System Setup). Select CCC config path to following file: f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\ccc_hgcal_separated.xml
- select the CCC mode to "HGCAL Independent"
- click "Configure CCC"
- Go to tab 5 (Take Data)
How to switch on and of High Voltage (HV)
Whenever is the black clover removed, the high voltage should be switched off, because the detection layers themselves are not light-tight.
- High voltage is switched in the datataking labview in tab "4) Calibration"
- click on the "Pre_Bias 2" in the "enable section" to give it a desired state (light green = on, dark green = off)
- click on on "Set" below.
trouble shooting
- if run in EUDAQ does not start: check that the upper box in the "Common DAQ" area is bright green and reads "Listening". If not, click on it, it should change the status. If the run still does not start, stop and start a new run in EUDAQ. If this does not help, call AHCAL expert (Jiri or Katja).
- if no new events appear in run: check if the four large displays are still moving (they should to that also if there is no beam). If they don't move for more than ~10 seconds, stop and start a new run in EUDAQ. If this does not help, call AHCAL expert (Jiri or Katja)
- Labview does not react on the EUDAQ stop: Eudaq probably crashed and labview is trying to send the data to non-existing connection. Eventually, labview will crash with error message, that it is not able to write to TCP socket. Both EUDAQ and labview needs to be killed and restarted.
- Labview pops up error message: Probably communication with EUDAQ is lost and it won't work properly until restarted. Perform a labview+eudaq restart
- all other cases: call AHCAL expert (Jiri or Katja)