Test Beam Facility For hIgh Rate STudies (TB.First) @IPHC

This page contains instructions and illustrations on how to run the test beam facility at Strasbourg. The page is under construction and for the moment contain only relevant information for the test of a tracker phase 2 2S mini module (2CBC3). FIXME add documentation about CBC2/3 calibration

USEFUL CONTACTS Hide 'USEFUL CONTACTS '

Description of the current setup, installation

ping 192.168.7.230 // ping FC7 ping 192.168.7.221 // ping GLib

Description of the functionalities of the ChrominiSupervisor

Test of the CMS Phase-1 Pixel modules with Digital Test Board (DTB)

To operate the DTB the most commonly used user interface is Pixel eXpert Analysis & Readout (pXar) which implements the full test suite required for module calibration and qualification. Or else more flexible scripting capabilities using the Python interface can be provided by the pxarCore library.

Useful contact

• pXar developer : Urs Langenegger (PSI), urs.langenegger@psiNOSPAMPLEASE.ch
• DTB expert : Danek Kotlinski (PSI), danek.kotlinski@psiNOSPAMPLEASE.ch

Useful documentation

• user manual : https://github.com/psi46/pxar/blob/master/main.pdf
• CERN note about the low-level libray pxarCore : http://cms.cern.ch/iCMS/jsp/openfile.jsp?type=NOTE&year=2016&files=NOTE2016_001.pdf

pXar installation

The compilation of pXar source code requires ROOT installation (recommended to build ROOT from the source), the libusb 1.0 library to communicate with the DTB (libusb-1.0-0-dev on Linux), and the FTDI library for FTDI chips (libftdi-dev on Linux).

Download the latest version of the code from github repo :

git clone https://github.com/psi46/pxar.git pxar

Create and work into build directory :

cd pxar/ && mkdir build && cd build 

Run CMake (that searches for all required packages and verifies all dependencies) :

cmake ..

Compile code :

make [-j4] install

At this stage, if compilation errors related to ROOT appear, ensure that pXar uses the same C++ standard version as the one with which ROOT was built. To know ROOT C++ standard version config :

root-config --cflags

Then remove all files in the build directory and re-run CMake to build with the same standard (C++17 as example) :

rm -rf build/* && cmake -D CMAKE_CXX_STANDARD=17 ..

First DTB connection try

In pxar/ directory :

cd ../main
./mkConfig -d testModule -t TBM10D -r proc600v3 -m
../bin/pXar -d testModule -g -v DEBUG

USB device error

If problem of USB connections with the DTB, try these magic lines (on Linux) :

sudo mount --bind /dev/bus /proc/bus 
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices 
sudo chmod 666 /proc/bus/usb/00*/* 
sudo modprobe -r ftdi_sio 

Re-run these commands before each USB connection to the DTB.

DTB firmware loading

To properly operate the DTB, you also need to have the matching firmware loaded onto that device. The firmware can be obtained by downloading from github repo (in pxar/ directory) :

git clone https://github.com/psi46/pixel-dtb-firmware.git 

Then download the firmware :

./bin/pXar -f ../../pixel-dtb-firmware/FLASH/FLASHFILE

The download can take a while. Don't turn off the power until the 4 LEDs are on ! After that power-cycle the DTB.

New L1 modules

Information provided by D. Kotlinski after the laboratory tests carried out at PSI before sending the modules :

Link to the summary : http://dkotlins.web.cern.ch/dkotlins/CMS/V3/l1_2019_modules_v3.pdf

The folders containing the settings (in pXar format) and the results of these preliminary tests are on lxplus (CERN server) : /afs/cern.ch/work/d/dkotlins/public/v3/

Preparation of pixel module

Setup of the environment : make sure root is sourced. Then to allow the usb port to be accessible (under linux) :

 sudo mount --bind /dev/bus /proc/bus ; 
sudo ln -s /sys/kernel/debug/usb/devices /proc/bus/usb/devices ; 
sudo chmod 666 /proc/bus/usb/00*/* ;
sudo modprobe -r ftdi_sio ;

First to test the programmability of the module :

FIXME add link to the github branch, create the git branch:

https://github.com/clgrimault/pxar/tree/iphc

Information on the pixel module

Installation of the DUT (pT mini module)

Grounding of the mini module

Grounding of the mini module Grounding of the mini module

Cabling and setting of the LV (UIB)

Cabling and setting of the LV (UIB) Cabling and setting of the LV (UIB)

Cabling and setting of the HV

Cabling and setting of the HV Cabling and setting of the HV

Preparing the CRATE :

Fixme add picture, with a description of all the element in the crate, how the FC7 connect to the UIB, etc... Describe powering up, cheks and these sort of stuffs.

Trigger system with scintillators

• 2 beam scintillators for coincidence, each 2mm thick, size of pixel module (≈ 40x67mm2)
• Hamamatsu small PMTs H10721 with low voltage control
• In special housing to allow mounting without heavy scotch tape in beam but testing in lab
• Flexibility of changing scintillator
• All mecanical parts of housing produced by 3D printer (Thierry G.)
• First tests were done with 90Sr beta source
• Very fast signals

• information on operation from Ulrich

Trigger supervisor on GLib

Trigger logic

Cabling

Synchronisation with the beam

The telescope

The Motherboard and the connected pixel modules

	Set up with 6 Modules connected

Proposition for the Cyrce configuration : check the fiber association

important associated file: /home/xtaldaq/TriDAS/Config/nametranslation/0/translation.dat

Remark : Before the first calibration, we need to take the files obtained from the DTB measurements using Pxar and convert them from Pxar to POS, following the recipe on the page from Nikkie. Make sure in the DAC file the following two lines are added:

VIbias_bus:    30      # Under the VcThr parameter
TempRange:     60      # Under the CalDel Parameter

Older set-ups Hide 'Older set-ups '

Set up with 6 Modules connected

Pixel Number	Name	Hub address	Slot on the MB	Position on the FMC8SFP	Fiber color (number)	TBM channels	Comments
M3558	BPix_BmO_SEC1_LYR3_LDR2F_MOD4	29	211	B	white (6)	11 and 12
M3211	BPix_BmO_SEC1_LYR3_LDR1F_MOD1	31	221	G	green (3)	5 and 6	Troubles with ROC 8, 9 and 10 (noisy) and ROC 11 (empty sometimes) and 15 (empty always)
M3028	BPix_BmO_SEC4_LYR3_LDR1F_MOD4	25	212	E	blue (1)	1 and 2
M3704	BPix_BmO_SEC1_LYR3_LDR4F_MOD1	4	222	F	aqua (12)	23 and 24
M4643	BPix_BmO_SEC1_LYR3_LDR2F_MOD1	15	223	D	pink (11)	21 and 22	Clement: problem of config if no HV, Chromini : no data at all. On a connector with a red point
M3672	BPix_BmO_SEC1_LYR3_LDR3F_MOD1	30	214	C	purple (10)	19 and 20	Troubles with ROC 14 (noisy) and 15 (empty always). On a connector with a red point

Set up with 4 Modules connected

Pixel Number	Name	Hub address	Slot on the MB	Position on the FMC8SFP	Fiber color (number)	TBM channels	Comments
M3704	BPix_BmO_SEC1_LYR3_LDR4F_MOD1	4	223	D	white (6)	11 and 12	on a connector with a red point, some ROC have strange behaviour for the VcThrCalDel calibration
M3672	BPix_BmO_SEC1_LYR3_LDR3F_MOD1	30	214	C	aqua (12)	23 and 24	on a connector with a red point
M3558	BPix_BmO_SEC1_LYR3_LDR2F_MOD4	29	211	B	blue (1)	1 and 2
M3028	BPix_BmO_SEC4_LYR3_LDR1F_MOD4	25	213	H	green (1)	5 and 6

important associated file: /home/xtaldaq/TriDAS/Config/nametranslation/0/translation.dat

It is very important to have modules connected on the connectors with a red point. If not, we do not succeed in configuring correctly the other modules connected on the motherboard : the I_ana current does not rise after many (!) configurations.

Order to respect to turn it on

• Start the crate
• Start the Magma Box (the button on the back side of the box and the button on the front end)
• Start the PC sbgat209 (if the magma box is off and is connected to the PC via fibers and transiver, then the PC will stop during his boot, without any message on the screen, and nothing will work)
• Open the different windows with running the script

  ./terminalTabs.sh 

  in ~/TriDAS/pixel/ChrominiSupervisor/script/

• sudo ./useFTDI

  to re-initialize correctly the link with the i2c master (from the TriDas/pixel/PixelRun directory)
• Start the PoS :

Done by .bashrc start script Hide

cd /home/xtaldaq/TriDAS
source setenv.sh

cd pixel/PixelRun/
./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml

• Ping the different boards in the crate by clicking the TeleMCH link in ChrominiSupervisor (re-click if red) or running the script

   ./pingAllHosts.sh 

  in ~/TriDAS/pixel/ChrominiSupervisor/script/
• Modify the status of some registers on the FED by clicking the Reset GTX ... link in ChrominiSupervisor or see Chromie instructions here
• Put the low voltages on the motherboard
• To get the FerolSource in green, we need to make the link first with one loop-back configuration of the ferol.
• The arduino should be launched automatically with the ChrominiSupervisor, and the Time Series DataBase shoud be filled with values (login: xtaldaq (xtaldaq1)).

Environmental measures

Check the version of firmware/configuration :

• Firmware FED 18.7, FEC 1.2, triggerSupervisor v21
• trigger delay = 30 in the triggerSupervisor

LV and Current info

For a setup with all the 6 modules connected on the MB (with the new LV, configurable from PC!):

	Before Chromini6ModulPhysics configuration -- note that the LV were not perfectly adjusted to MB requierements at the time of the screenshot
	After Chromini6ModulPhysics configuration

It seems that when the CalDel parameters are not well determined, we need to configure several time the MB and the pixel modules to achieve the target current on I_ana.

LV configuration for older set-ups Hide 'LV configuration for older set-ups '

For a setup with 4 modules connected on the MB (M3704, M3672,M3558 and M3028):

	Before Chromini4ModulPhysics configuration
	After Chromini4ModulPhysics configuration

For comparison, with 3 modules connected on the MB (M3704, M3672 and M3558):

	Before Chromini3ModulPhysics configuration
	After Chromini3ModulPhysics configuration

For comparison, with the setup with 2 modules connected on the connectors with the red points (M3704 and M3672):

After Chromini2RedPointsPhysics configuration

Low voltage on MB:

• stored values on the 1st recall set on the 3 LV : for the 2 module configuration
• stored values on the 2nd recall set on the 3 LV : for the 3 module configuration
• stored values on the 3rd recall set on the 3 LV : for the 4 module configuration

HV info

NEVER TURN THE HV ON IF THERE IS NO LV APPLIED ON THE MODULES !!!

Keep the modules in the dark when HV is on, and use the air conditioning (and if not, use a table fan) !

The HV can be controled from the PC. Use -130 V. Check the current over time, for 6 modules it is about 44 to 51 microA (depending on the time).

Set up with 6 Modules connected

HV configuration for older set-ups Hide 'HV configuration for older set-ups '

Set up with 4 Modules connected

	Measurement of I vs HV
	Measurement of I vs time for HV=130V, time is in minutes and time=0 means 14:00. The variation observed for the 3 first measurements (<=30 min) is directely related to the change of light in the room (impact of the sun outside)! After that, we close the window blinds. But then with time the temparture of the modules started to rise and we observed a higher current on the HV.

Take a physics run

Use the new ChrominiSupervisor

• Start the PoS and the fedKit with:

  cd /home/xtaldaq/TriDAS/pixel
  ./runFedKit.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml
       

--autorun {nb of wanted events}

• On the xdaq page on a web browser
  • click on Initialize
  • select the configuration "Cyrce4ModL34Physics" in the menu
  • click on Configure
  • then check on the bottom of the page that you see the FED phases as on the example or on the ChrominiSupervisor image linked above.

Done by runFedkit script Hide 'Done by script '

• Select the trigger configuration (Scintillators (or internal), check that the Reset button is not pressed, and that we see the counter changing when pushing the Read button)
• Click on the AMC13 picture on the ChrominiSupervisor and remove the command "lt 1000 1" and validate. This action will allow the events to be send to the ferol and then gets the events written on disk.

• Start the run
• Halt the run on the ChrominiSupervisor
• Stop the ferol by clicking the Quit link at the bottom of the page

old procedure Hide 'Old procedure '

Here is the procedure to take a physics run with Chromini, based on what is done for Chromie 25 Easy Steps To Data Taking.

• Start the PoS :

cd /home/xtaldaq/TriDAS
source setenv.sh
cd pixel/PixelRun/
./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml

• On the xdaq page on a web browser --> sbgat209:1973 :
  • click on Initialize
  • select the configuration "PhysicsChromini"
  • click on Configure
  • then check on the PoS window that you see the FED phases example
• Start the ferol

  • cd /home/xtaldaq/TriDAS/pixel
    python fedKit.py -r 

  • Type "4" for the mode, "1" for the FED ID, "Yes" to write on disk, and "/tmp" for the directory where to write the data, and write also the correct run number.

You can run without the "-r" option if you are sure that the run number is already correctly synchronised between the ferol and the pos. see the corresponding doc for chromie

• Prepare the AMC13

  •  /opt/cactus/bin/amc13/AMC13Tool2.exe -c /home/xtaldaq/TriDAS/pixel_debug_tools/TTSStateCheck/address_tables/amc13/connectionSN43iphc.xml 
    rd
    rg
    en 9 f t 

• Start the run on xdaq
• Start the trigger on the AMC13

  •   lt c 

    or

      lt 1000 1 

    for 1000 triggers
• Stop triggering on the AMC13

  •   lt d 

• Halt the run on xdaw
• Stop the ferol by pressing "q"

The data taken are stored on "/tmp" as selected on the ferol step.

Take a calibration run

• Create a new calibration: modify the script "mkNewConfigChromini.sh" in /home/xtaldaq/TriDAS/Config, as suggested by the Chromie documentation Config And Calibration.

• Start the PoS :

cd pixel/PixelRun/
./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml

• On the xdaq page on a web browser
  • click on Initialize
  • select the configuration "Chromini6ModulCalDel" in the menu
  • click on Configure
  • then check on the bottom of the page that you see the FED phases
  • switch to the PixelSupervisor
  • start the run
  • decide if you want to upload the new measurements (if yes, this will create a new dac directory with the new files, and uplaod the aliases.txt and configuration.txt files)
  • halt the run

• List of the calibrations already performed:
  • Delay25 (not working)
  • TBMDelay25 (to be done only once)
  • CalDel
  • VcThrCalDel (the one we do each time before a beam test --- dependence with respect to the temperature ?)
  • PixelAlive
  • SCurve_faster
  • GainCalibration
  • PLL calibration to synchronize pixel modules among each other : 3 calibrations have to be performed one after the other. The list of PLL calibrations : TBMPLLNoTokenPass, TBMPLL, ROCPLL. What we did : run the 1st one, store the new values ; re-run the 1st one to check that the values are still the same ; if not, store and re-run ; if yes, run the 2nd calib, store, check ; then run the 3rd calib. when this loop is done, start again the full loop. In principle this calib is already done with the DTB but it seems that it is really needed to be performed with the final cabling scheme. If we don't change the cabling, we don't need to redo this calibration one more time. After that loop of calibrations, the pixel modules should be synchronized and correlations among them should be visible in DQM root file).

• Analysis of calibration runs:
  • For PixelAlive, SCurve_faster and GainCalibration, we need to run the reco before getting a root file to analyse:

$BUILD_HOME/pixel/PixelAnalysisTools/test/bin/linux/x86_64_centos7/PixelAnalysis.exe $BUILD_HOME/pixel/PixelAnalysisTools/test/configuration/PixelAliveAnalysisTelescope.xml 100475
$BUILD_HOME/pixel/PixelAnalysisTools/test/bin/linux/x86_64_centos7/PixelAnalysis.exe $BUILD_HOME/pixel/PixelAnalysisTools/test/configuration/GainAnalysisTelescope.xml 100198
$BUILD_HOME/pixel/PixelAnalysisTools/test/bin/linux/x86_64_centos7/PixelAnalysis.exe $BUILD_HOME/pixel/PixelAnalysisTools/test/configuration/SCurveAnalysisTelescope.xml 100201

• • There exists in /home/xtaldaq/TriDAS/pixel/PixelRun/Runs/Run_0 an interesting file called plot_Nmodules.C which allows to plot the results for several ROC on one histogram, for a given run.

root -q -l -e "r=151;n=1011;t='C';" plot_Nmodules.C
root -q -l -e "r=246;n=110110;t='C';" plot_Nmodules.C

n = (1/0 for SEC4 2F, 1/0 for SEC4 1F, 1/0 for SEC1 4F, 1/0 for SEC1 3F, 1/0 for SEC1 2F, 1/0 for SEC1 1F), 

C = 2D CalDel, 
G = 1D slope for Gain, 
H = 2D intercept for Gain, 
I = 1D intercept for Gain, 
P = 2D PixelAlive, 
N = 1D noise for SCurve, 
S = 2D noise for SCurve,
R = 1D threshold for SCurve, 
T = 2D threshold for SCurve, 
V = 2D VcThrCalDel.

• • Observation with HV : some results for CalDel, VcThrCalDel and PixelAlive runs with 6 modules

Old procedure Hide 'Old procedure '

cd /home/xtaldaq/TriDAS
source setenv.sh
cd pixel/PixelRun/
./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml 

 
cd /home/xtaldaq/TriDAS/Config
/home/xtaldaq/TriDAS/pixel/bin/PixelConfigDBCmd.exe --insertVersionAlias calib 50 ChrominiDelay25 

/home/xtaldaq/TriDAS/pixel/bin/PixelConfigDBCmd.exe --printVersionAliasList calib

 
cd /home/xtaldaq/TriDAS/pixel
bin/PixelConfigDBCmd.exe --insertVersionAlias calib 51 ChrominiTBMDelay25
PixelConfigDBCmd.exe --printVersionAliasList calib
bin/PixelConfigDBCmd.exe --insertVersionAlias calib 52 ChrominiCalDel
PixelConfigDBCmd.exe --printVersionAliasList calib
bin/PixelConfigDBCmd.exe --insertVersionAlias calib 53 ChrominiVcThrCalibration    

 
find . -name delay25.dat
cd /home/xtaldaq/TriDAS/Config/calib/
mkdir 50
cp 2/delay25.dat 50/

Do the reconstruction

At the monent, the reco is working in Caroline's directory on ui6 under CMSSW_10_1_11 release

Installation recipe Hide 'Installation recipe '

cmsrel CMSSW_10_1_11 cd CMSSW_10_1_11/src # at this stage this is empty cmsenv git cms-init git remote add CHROMIETeledaq https://github.com/CHROMIETeledaq/cmssw.git git fetch CHROMIETeledaq git cms-merge-topic CHROMIETeledaq:chromie git checkout CHROMIETeledaq/chromie git cms-checkdeps -a scram b clean scram b -j10 cd Geometry/PixelTelescope/test # Then you can copy paste the files you want: # /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/DQMTelescope/PixelTelescope/plugins/AnaChromini.cc /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/data/tuneParameters.xml /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/data/telescope.xml /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/plugins/DDTelescopePlaneAlgo.h /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/plugins/DDTelescopePlaneAlgo.cc /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/SiPixelLorentzAngle.db /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/SiPixelLorentzAngleSim.db /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/pixel_telescope_beamspot.db /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/pixeltelescope_v1_cabling.db /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/PixelTelescope_BeamData_RECO.py /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_16dec19/CMSSW_10_1_11/src/Geometry/PixelTelescope/test/Chromini/PixelTelescope_RAWDataCollector_185.py

 
cmsRun PixelTelescope_RAWDataCollector.py
cmsRun PixelTelescope_BeamData_RECO.py

It is very important to know which fiber is associated to which module to make identify the detID. See table here

Older association of modules to detID Hide 'Older association of modules to detID '

Old configuration with 4 modules connected to the MotherBoard

Pixel Number	Slot on the MB	Fiber color (number)	detID	Chromie Module Name	Chromie Position
M3704	223	white (6)	344463364	M3175	Layer 2 [O]
M3672	214	aqua (12)	344724484	M3009	Layer 1 [I]
M3558	211	blue (1)	344725508	M3057	Layer 1 [O]
M3028	213	green (1)	344462340	M3082	Layer 2 [I]

Latency scan for the pixel commissionning

Recipe to take change the latency and run a physics run

Here is the list of script to run frm the sbgat209, with some actions to be tacken simultaneaously withe the xdaq web interface

• go the the directory /home/xtaldaq/TriDAS/Config
• to change the value of the WBC (latency in bunch-crossing unit (so 25 ns) ) ./changeValue.py WBC 21 -d dac/19/
• go the the directory /home/xtaldaq/TriDAS/pixel
• launch fedtkit applications python /opt/xdaq/bin/fedKit.py -q
• launch cross daq application
  • in the director =/home/xtaldaq/TriDAS/pixel/PixelRun
  • launch xdaq ./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml (check the "ready" statement on the screen)
• initialize
• select Cyrce4ModL34Physics
• configure , for the first switch on, configure without LV, and halt and reconfigure until the power consumption is reasonnable,
• select run number and Start
• click on AMC13 picture and hit space then OK
• in the directory /home/xtaldaq/lcharles/trigSupervisor do python ctrl_trig_ext_bunch.py
• check number of trigger in Ferol->Ferol Controller->Monitoring
• click Halt
• click QUIT (at bottom of page)

Next step:

• Check "Write data to": /home/xtaldaq/datata
• You should find a directory with run number

Do the simulation

Ongoing....

The recipe is under development and can be read in /opt/sbg/cms/safe1/cms/ccollard/TrackerTelescope/ui6/Chromini_simu/info_caro.txt

The code is compiling. The first step is running but somewhere in the code there should be a threshold which prevent to have SimHit for 25 MeV protons. It works for 120 GeV protons. The step to produce digis is crashing. To be continued....

Next steps :

• Work on the simu...
• Upgrade the telescope with new MB and new pixel modules.

To-Do List :

• Par rapport aux nouvelles MB :

• • Mettre une protection sur les chips pour modules L1, une fois bondés, de type résine globtop si les MB sont ok.

• • comment protéger les modules L1 pour les tests ou les poser sur les cadres en alu (pas d'oreilles!)?

• • utiliser les nouveaux cables "capton" longs de 1 m.

• • Commander des DOH carriers de spare avec le quartz classique (clock LHC) s’il en existe quelque part en stock.

• • Possibilité de se procurer une nouvelle carte i2c ?

• • tester les nouveaux modules avec la DTB

• • tester les modules avec la nouvelle MB...

• • mettre le telescope 2.0 dans la nouvelle boite à cyrcé

Installation of the DAQ software (Ph2_ACF)

The DAQ PC is sbgat231, login xtaldaq, password xtaldaq.

The description and instalation of the DAQ soft is shown in the gitlab https://gitlab.cern.ch/cms_tk_ph2/Ph2_ACF

Here is some description of the framework https://indico.cern.ch/event/842824/contributions/3538260/attachments/1921782/3179353/DAQWorkshop_HandsOn.pdf from the tracker phase 2 DAQ workshop https://indico.cern.ch/event/842824/timetable/?view=standard

for setting up the FC7 : https://indico.cern.ch/event/842824/attachments/1920624/3177632/PreparingFC7.pdf

and for installing soft

https://gitlab.cern.ch/fravera/Ph2_ACF/tree/daqWorkshop

on CC7

 sudo yum install boost
sudo yum install boost-devel

create a file (touch) sudo nedit sudo /etc/yum.repos.d/ipbus-sw.repo &

and add the following lines in that file

[ipbus-sw-base]
name=IPbus software repository
baseurl=http://www.cern.ch/ipbus/sw/release/2.5/centos7_x86_64/base/RPMS
enabled=1
gpgcheck=0

[ipbus-sw-updates]
name=IPbus software repository updates
baseurl=http://www.cern.ch/ipbus/sw/release/2.5/centos7_x86_64/updates/RPMS
enabled=1
gpgcheck=0
sudo yum clean all
sudo yum groupinstall uhal
sudo yum install root
sudo yum install root-net-http root-graf3d-gl root-physics root-montecarlo-eg root-graf3d-eve root-geom libusb-devel xorg-x11-xauth.x86_64
 sudo yum install cmake
git clone https://:@gitlab.cern.ch:8443/fravera/Ph2_ACF.git
mkdir Ph2_ACF/build 
cd Ph2_ACF/build 
sudo yum install pugixml
sudo yum install pugixml-devel
cmake ..
make
cd ..
source setup.sh

./bin/fpgaconfig -c settings/IphcDescription.xml -l

To load another firmware :

./bin/fpgaconfig -c settings/IphcDescription.xml -f d19c_8cbc3-1_8cbc3-2.bin -i d19c_8CBC3_workshop.bin

to determine the firmware version to use :

./bin/fpgaconfig -c settings/IphcDescription.xml -i d19c_8CBC3_workshop.bin

to push into gitlab on the branch JAFromDAQWorkshop :

 git push --set-upstream https://gitlab.cern.ch/jandrea/Ph2_ACF.git JAFromDAQWorkshop

To load a new firmware, use the fbgaconfig binary:

 ./bin/fpgaconfig -h 

To get the list of available firmware :

  ./bin/fpgaconfig -c settings/IphcDescription.xml -l

and load that onto the sd card with

 ./bin/fpgaconfig -c settings/IphcDescription.xml -f firmware/d19c_2cbc3_none.bin -i d19c_2cbc3_none

then load the image to the fpga with

  ./bin/fpgaconfig -c settings/IphcDescription.xml  -i  d19c_2cbc3_none

Instructions for calibrating the system (CBC3 mini module for the moment)

• start by verifying that the box of the mini-telescope is close and light tight. Deplete to -10 V and verify the current on the HV power supply. It should remain well below the microA. Once verified, you can set the HV to 400V, the full depletion being around 300V. After stabilizing, the current consumption of current at 400V should be (KIT double mini module) : 0.1377 microA, 0.4368 microA. This is tested within the casemate. Could be different in the lab.

The following calibration (offset and noise) can be done with external clock (if available)

 <Register name="ext_clk_en"> 1 </Register>   <!-- the external clock should be at 42.5 MHz (85/2) -->  

But the internal trigger should be used

 <Register name="trigger_source"> 3 </Register> <!-- default value is 3 --> 

to do : add pictures illustrating the results of the calbiration

offset calibration offset calibration

bin/calibrate -f settings/IphcDescription.xml    

Noise scan Noise scan

 bin/calibrate -f settings/IphcDescription.xml -n 

Latency scan with pulses Latency scan with pulses

  <TestPulse enable="1" polarity="0" amplitude="180" channelgroup="0" delay="0" groundothers="1"/>

   <Register name="ext_clk_en"> 0 </Register> 

  <Register name="trigger_source"> 6 </Register> <!-- default value is 3 -->

  <Register name="data_handshake_enable"> 1 </Register>

Latency scan with signal particles latency scan with signal particles

<TestPulse enable="0" polarity="0" amplitude="230" channelgroup="0" delay="0" groundothers="0"/>

<Register name="ext_clk_en"> 1 </Register>

<Register name="trigger_source"> 5 </Register> <!-- default value is 3 --> 

 <Settings threshold="420" latency="68"/> 

Latency scan with signal particles, for stubs Latency scan with signal particles, for stubs

 bin/commission -f settings/IphcDescription.xml -m 0 -r 400 --notdc -s
  <Register name="common_stubdata_delay"> 194 </Register>  

16CBC3 module

Link to twiki 16-CBC3 module

Elog

Installed on xtaldaq, connect, open firefox and go to http://sbgat231:8080/TB.First/

How to take a combined run (with the telescope and the 2S module) ?

Information taken from this google sheet.

Before starting a combined run, the telescope should already have been configured until the expected I_ana value is obtained. Otherwise making several configuration in combined mode will generate errors.

• Start the PoS and the fedKit with:

  cd /home/xtaldaq/TriDAS/pixel
  ./runFedKit.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml
       

  * Start the miniDAQ of the 2D module with the option "-s" + a duration option "-D" (units= second). The option "-e" allows to choose a fixed number of events to be taken, in placed of a fixed time for the duration of the run :

  miniDAQ -f tb_july/D19CDescription_iphc_data.xml -D 30 --withCIC -q -d --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" -s
       

• In the ChrominiSupervisor : click on "initial" for the DUT
• In the ChrominiSupervisor : click on the boxes for the telescope and the DUT and then click on "Initialize"
• In the ChrominiSupervisor : click on "Configure"
• In the ChrominiSupervisor : When the 2 setups are configured, we can start the run. The run number can be selected for the telescope, but the one for the DUT is automatically increased with respect to the previous DUT run number.
• In the ChrominiSupervisor : click on the AMC13 and launch an empty command. This will release the triggers both for the telescope and the DUT.
• If the -D option was set to 30 seconds for the DUT, the DUT run will stop after that time, but we need to manually stop the telescope run.

• Note about the DUT clock : The following connections have to be made:

  On the Trigger board :
      1- Trigger input
      2- Clock input from the FC7 of the DUT
      3- Trigger output to the FC7 of the DUT
  On the FC7 of the DUT :
      2- Trigger input from the TriggerSupervisor (or from Ulrich trigger)
      5- Clock output (coming from the DUT) that we can use in the TriggerSupervisor  
       

  Then a run with the module 2S has to be launched in order to activate the clock output (there is some parameter set in that sense in the xml run with miniDAQ). When it is activated, we can switch within the triggerSupervisor to the External Clock option. If it is in green, then it is fine.

List of known issues

Within the Box

• Opening the air extraction will increase the temperature and the humidity in the old box. Don't open it too large, just what is needed to get the correct pressure within the box.

• Loss of connection with the LV of the DUT or the telescopre (firmware bug by the onstructor). Solved by resetting manually the LV.

Configuration of the pixel

• Before starting a combined run, the telescope should already have been configured until the expected I_ana value is obtained. Otherwise making several configuration in combined mode will generate errors related to the FEC.

Trigger, delays, latency, ...

• Check the value of the trigger delay in the ChrominiSupervisor, if this value is not equal to 30, the pixel modules will not be synchronized with the trigger arrival. The value in the box on the top right corner of the ChrominiSupervisor should be 66, for the same reason. If this is not the case, you have to update the latency in the pixel config files ./changeValue.py WBC 66 -d dac/19/ where the dac directory (here taken as 19 in the example) should correspond to the one used in physics run.

• Don't forget to send the empty command on the AMC13 to allow the telescope (and the DUT in case of combined run) to recieve the triggers.

• In case of tests with the internal trigger from the TriggerSupervisor, choose a small value of rate (in kHz).

• Don't forget to validate any change done within the TriggerSupervisor.

• Trigger rate read on the TriggerSupervisor : the determination of the rate takes some time, it needs to stabilize, especially after a reset of the trigger. be patient... Clicking several times on the read button could help to increase the stat for the measurement.

• The 2S module does not work properly if the rate is too low (to be check with the latest version of the code).

• Observed problem without solution : sometimes the latency seems to drift. We have observed a few runs for which the <#clusters/event> in the telescope suddenly falls to very small values, while nothing has changed with comparison to good runs...

Ferol

• In case of probem with the ferol, close all the windows on sbgat209 and start a new session. If this does not cure the problem, reboot pc and ferol (follow carefully the procedure written above on this twiki)

• Problem with the EVM unit during a run with the pixels : mismatch between the run numbers (behind the output directories in datata). Solved by increasing manually the run number in the ChrominiSupervisor.

Data taking program and analyses

test beam of the 17th of July 2019

test beam of the 17th of July 2019 test beam of the 17th of July 2019

bin/calibrate -f settings/IphcDescription.xml -n

<Register name="trigger_source"> 3 </Register> <!-- default value is 3 -->

./bin/miniDAQ --dqm -f settings/IphcDescription.xml -e 500000 --daq output.dat

<Register name="trigger_source"> 5 </Register> <!-- default value is 3 -->

./bin/miniDAQ --dqm -f settings/IphcDescription.xml -e 500000 --daq output.dat

test beam of the 19th of November 2019

test beam of the 19th of November 2019 test beam of the 19th of november 2019

test beam of February 2020

test beam of February 2020 test beam of February 2020

test beam of October 2020

test beam of October 2020 test beam of October 2020

test beam of December 2020

test beam of December 2020 test beam of December 2020

test beam of January 2021

test beam of January 2021 test beam of January 2021

test beam of March 2021

test beam of March 2021 test beam of March 2021

test with source of March 2021 : First correlation between the two planes of the telescope, with source

test with source of March 2021 test with source of March 2021

test beam of April 2021 : First correlation between the two planes of the telescope, with beam

test beam of April 2021 test beam of April 2021

test beam of June 2021

test beam of June 2021 test beam of June 2021

test beam of July 2021

test beam of July 2021 test beam of July 2021

google sheet

Restart : November 2021

test beam of November 2021 test beam of November 2021

test beam of January 2022 : First correlation between the telescope and the DUT, with beam

google doc

test beam of End of June 2022 : First Test beam with the new box !

google doc

-- JeremyAndrea - 2019-07-17 -- CarolineCollard - 2021-01-18