TkPhase2TBFirst16CBC3 < Sandbox

---+!! 16-CBC3 module

This section is dedicated to the 16CBC3 module received from KIT

%TOC%

---+ Set-up

---++ Description

---+++ 2S Module

| Main components: <ul> <li>2 parallel strip sensors (2 x 1016) <ul> <li>1.8mm sensor spacing</li> <li>5cm x 90&mu;m cell size</li> <li>sensors are read out by the CMS Binary Chip (CBC). Each CBC reads out 254 strips (2 x 127) and performs hits correlation (stubs) and sends the stub data out at each BX.</li> </ul></li> <li>2 Front-end hybrids (FEH): <ul> <li>Right and Left FEH <ul> <li>8 x CBC3 (Right FEH, FeId ="0") + 1 x CIC2 mezzanine card</li> <li>8 x CBC3 (Left FEH, FeId ="1") + 1 x CIC2 mezzanine card</li> </ul></li> <li>CBCs send data to CIC that performs data sparsification, formats the output data, and sends them to the service hybrid (via GBT transmitter)</li> </ul></li> <li>Service hybrid (SEH): <ul> <li>Power distribution (DC-DC converters)</li> <li>Data serialization</li> <li>Opto-electrical conversion</li> <li>VTRx (VersatileTransceiver, operating at up to 10 Gb/s in the upstream and up to 5 Gb/s in the downstream directions)</li> <li>GBT (Giga-Bit Transceiver)</li> <li>GBT-SCA (Slow Control Adapter)</li> </ul></li> </ul> | <img alt="FullModule.png" height="350" src="%ATTACHURLPATH%/FullModule.png" /> |
More details can be found in [[https://indico.scc.kit.edu/event/766/contributions/6764/attachments/3224/4682/8CBC3-Module-StrasbourgHighRateTests.pdf][slides]] and [[https://espace.cern.ch/Tracker-Upgrade/System_tests/SitePages/Getting%20started%20with%208CBC3.aspx][share point]]. Bonus: [[https://indico.cern.ch/event/891171/contributions/3786676/attachments/2006138/3350412/20200319-OT_System_Test_Meeting_Braach.pdf][KIT set-up]], [[https://indico.cern.ch/event/889565/contributions/3754565/attachments/1992647/3323055/20200224_testbeam.pdf][DESY set-up]]

---+++ DAQ system

*MicroTCA crate*: backplane which can accommodate up to 12 Advanced Mezzanine  Card  (AMC)  modules  along  with  up  to  two  &mu;TCA  Carrier  Hub  (MCH) modules.

Current configuration:
   * FC7 ACM card
      * FPGA, Micro SD card slot, 2 FMC connectors:
         * FMC (FM-S14)
         * DIO5
   * MCH:
      * system management and data transfer to the PC (Ethernet)

| <img alt="uTCA_crate.png" height="200" src="%ATTACHURLPATH%/uTCA_crate.png" /> | <img alt="FC7_card_2sides.png" height="200" src="%ATTACHURLPATH%/FC7_card_2sides.png" /> |
<!--External trigger (synced with 42.5 MHz): Scintillators -&gt; NIM Logic (Discriminator + Coincidence) -&gt; DIO5 (FC7)-->


| <img alt="DAQexplanation.png" src="%ATTACHURLPATH%/DAQexplanation.png" width="800" />  |
<!--credit to saskia-->

---++ Powering

---+++ Low Voltage

<table class="twikiTable" width="80%" bgcolor=#f5f5fa  border=1 cellpadding=40 cellspacing=40>
<tr>
<td bgcolor=#eeeeee  align="center"> 
     <br> %NAVY%Channel 1 (*12V*)%ENDCOLOR%: fan for DC-DC cooling (testbench), %NAVY%Channel 2 (*10V*)%ENDCOLOR%: module powering + *grounding* (black cable)<br />
     <img src="%ATTACHURLPATH%/New_LV.jpeg" alt="New_LV.jpeg" width="330" height="200" />
     <img src="%ATTACHURLPATH%/New_LV_front.jpeg" alt="New_LV_front.jpeg" width="330" height="200" />
</td>
<td align="center">
<br> Power distribution on the SEH (2S module)</br>
     <img src="%ATTACHURLPATH%/LV_DC-DC.png" alt="LV_DC-DC.png" width="330" height="200" />
</td>
</tr>
</table>
%RED%WARNING%ENDCOLOR%: For the module, the current must be *<1.3A* otherwise the SEH will turn off by itself.
 

---+++ High Voltage

<table class="twikiTable" width="50%" bgcolor=#f5f5fa  border=1 cellpadding=40 cellspacing=40>
<tr>
<td bgcolor=#eeeeee  align="center"> 
     <img src="%ATTACHURLPATH%/isegHV.jpg" alt="isegHV.jpg" width="330" height="200" />
</td>
<td align="center">
<br> Grounding: SHV shielding has to be connected directly with the black cable to the LV Power supply GND </br>
     <img src="%ATTACHURLPATH%/grounding.png" alt="grounding.png" width="330" height="200" />
</td>
</tr>
</table>
%RED%WARNING%ENDCOLOR%: the bias voltage should be negative, make sure the blue led on the right side are on (not the red one).

---+++ Remote control

* *XDAQ* application: already installed on sbgat209 machine (%H% contact Christian Bonnin for details)
   * Point your browser to <verbatim>http://sbgat209.in2p3.fr:1973</verbatim> and click on *ChrominiSupervisor*
   * if it does not respond, login to sbgat209 and do the following
      * <verbatim>cd ~/TriDAS/pixel/PixelRun</verbatim>
      * <verbatim>./run.sh --xml ~/TriDAS/pixel/PixelRun/telescopeIphc.xml</verbatim>
      * leave the terminal open

* *LV*: the NGP800 power supply can be controlled via XDAQ web interface
   * go to XDAQ web interface(http://sbgat209.in2p3.fr:1973) &gt; Device Under Test &gt; LV control
* *HV*: the ISEG power supply can be controlled via XDAQ web interface as well
   * go to Device Under Test &gt; HV (control)
   <!--* Point your browser to <verbatim>http://192.168.7.69/</verbatim>
   * Note that the IP address 192.168.7.69 is shown on the ISEG device-->

   * <br /> <img alt="New_LV_front.jpeg" height="300" src="%ATTACHURLPATH%/XDAQ_DUT.png" />"
   * %RED%N.B%ENDCOLOR%: to unlock do Ctrl+Click (Click only won't work)

Some reference plots from calibration runs.  
<br />
     <img alt="" src="%ATTACHURLPATH%/current_vs_voltage.png" width="350" />
     <img alt="" src="%ATTACHURLPATH%/noise_vs_voltage.png" width="350" />

---+++ X-Y Table

%TWISTY{mode="div" showlink="Operate the x-y table" hidelink="Operate the x-y table"  firststart="hide" showimgright="%ICONURLPATH{toggleopen-small}%" hideimgright="%ICONURLPATH{toggleclose-small}%" class="twikiHelp"}%
<verbatim>
1. CONNECTION :

	Ouvrir MCS2ServiceTools
		Dans "selectMCS2" mettre l'adresse "network:192.168.7.117"
		Puis connect.
	On doit trouver "MCS2M-D-3C"

	Verifier que pour les modules parameters on est bien pour channel 1 et channel 2 en INVERTED
		et que le Default MAx CLF a pour valeur 1000
    Si OK,on peut déconnecter 

ET passer à la suite: 
	Ouvrir MCS2DemoGUI
	Dans "MCS2 Locator" mettre l'adresse "network:192.168.7.117"
	Selectionner "Movement"
	Choisissez le mode "manual" (cliquant sur "slider")

RAPPEL : X positif vers le mur de la salle. X: canal 0 ("Channel 0")
	 y positif vers le haut		    Y: canal 1 ("Channel 1")
	 z positif

2. POSITIONS :
	A priori, en (X=0,Y=0) le centre du DUT devrait etre dans l'axe du faisceau.
	Limites :	vers le mur :   X = +66 mm 
			vers la salle : X = -55 mm
			vers le haut : Y = 89 mm
		  	vers le bas :  Y = -7 mm (si X=0, on bute sur le bas du support DUT)
						  (si = -55 mm, on peut descendre plus bas...)
	Si le système perd son 0 :
		aller à fond en X positif et setter X=66 mm
		aller à fond en Y positif et setter Y = 89 mm
       NE PAS TENTER DE DESCENDRE A VIDE : IL FAUT UNE MASSE DE 300 GRAMMES...

	DONC : Positionpour monter le DUT : à fond en haut     (Y = 89 mm)
					    a fond vers le mur (X = 66mm)</verbatim>

Documentation: [[%ATTACHURL%/MCS2_SERVICE_TOOL.pdf][MCS2 SERVICE TOOL]], [[%ATTACHURL%/MCS2UserManual.pdf][MCS2 User Manual]], [[%ATTACHURL%/Precision_Tool_Commander_Manual.pdf][Precision Tool Commander Manual]]

%ENDTWISTY%

---+ Ph2_ACF

Ph2_ACF is the [[https://cms.cern][CMS]] Tracker Phase2 Acquisition & Control Framework.

<!--The code is already installed on sbgat231 from [[https://gitlab.cern.ch/cms_tk_ph2/Ph2_ACF][https://gitlab.cern.ch/cms_tk_ph2/Ph2_ACF]].-->

---++ Get started

<!--I recommend to use the code  installed on sbgat231-->

1. First of all login to sbgat209 (or sbgat 419, sbgat231 has internet issue) and chose your working directory.

2. Then get the current being used code (at CYRCé):
    <verbatim>
    git clone -b StrasBugFix https://gitlab.cern.ch/cms-iphc/Ph2_ACF.git
    </verbatim>

   For the official code, do
   <verbatim>
   git clone --recurse-submodules https://gitlab.cern.ch/cms_tk_ph2/Ph2_ACF.git
   </verbatim>

  <!--Note that the compiled code already exist on sbgat209: /home/xtaldaq/enibigir/Ph2_ACF-->

3. Setup (every time you login):
   <verbatim>
   cd Ph2_ACF
   source setup.sh
   </verbatim>

4. Compile the code:
<verbatim>
   cmake3 -S . -B build
   cmake3 --build build -j 4
   </verbatim>

5. Optional: chose a running directory
<verbatim>
   mkdir rundir
   cp settings/D19CDescription_iphc*.xml rundir/
   </verbatim>

You will have 2 files: *D19CDescription_iphc_calib.xml* and *D19CDescription_iphc_data.xml*.

<!--
---+++ Your working directory

Make sure you are in *your working directory*

<verbatim>cd ~/cms_tk_ph2</verbatim> 
<verbatim>mkdir <your username></verbatim>

In order to be able to run the code from your directory your need to do the following 

<verbatim>
cd <your username>
ln -s ../Ph2_ACF/settings .
ls -l
</verbatim>
The later command will print out: *%GRAY%settings -> ../Ph2_ACF/settings%ENDCOLOR%* (symbolic link).

Important: To remove the symbolic link use: *rm -i settings* (for safety)

%X%: Never use rm -r or rm -f or settings/ (with slash), this will remove the directory or the contents of ../Ph2_ACF/settings.
-->

---+++ Parameter setting

<!--Copy the *settings/D19CDescription_iphc.xml* to your running directory, it should look like [[https://gitlab.cern.ch/enibigir/Ph2_ACF/-/blob/MultiLink_2S/settings/D19CDescription_iphc.xml][https://gitlab.cern.ch/enibigir/Ph2_ACF/-/blob/MultiLink_2S/settings/D19CDescription_iphc.xml]]-->
You can look at *D19CDescription_iphc_calib.xml* or *D19CDescription_iphc_data.xml**D19CDescription_iphc_calib.xml* or *D19CDescription_iphc_data.xml*

---++++ Useful settings

Open %NAVY%D19CDescription_iphc.xml%ENDCOLOR% with your favorite editor and have a look

   * Address: %GREEN%uri=%ENDCOLOR%%RED%"chtcp-2.0://sbgat209.in2p3.fr:10203?target=192.168.7.170:50001"%ENDCOLOR%

   * Optical link: %BLUE%&lt;GBT%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;phaseTap=%RED%"7" %ENDCOLOR%%GREEN%enable=%ENDCOLOR%%RED%"1"%ENDCOLOR%%BLUE%/&gt;%ENDCOLOR%

   * Events: %BLUE%&lt;Setting%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"Nevents"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 20%ENDCOLOR%
   * Config files path: %BLUE%CBC_Files%ENDCOLOR% %GREEN%path=%ENDCOLOR%%RED%"./settings/CbcFiles/%ENDCOLOR%
      * To be update after calibration
   * Clock: %BLUE%&lt;Register%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"ext_clk_en"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 0 %BLUE%</Register>%ENDCOLOR%
      * 1 -&gt; enable external clock
      * 0 -&gt; disable external clock
   * Trigger: %BLUE%&lt;Register%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"trigger_source"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 3 %BLUE%</Register>%ENDCOLOR%
     &lt;/verbatim&gt;
      * 1 -&gt; TTC
      * 2 -&gt; Stubs
      * 3 -&gt; Internal trigger (oscillator)
      * 4 -&gt; TLU
      * 5 -&gt; External trigger
      * 6 -&gt; Test Pulse (charge injection)
   * DIO5: %BLUE%&lt;Register%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"dio5_en"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 1 %BLUE%</Register>%ENDCOLOR%
      * 1 -&gt; enabled
      * 0 -&gt; disabled
   * Sparsfication: %BLUE%&lt;CIC2%ENDCOLOR% enableBend="1" enableLastLine="0" &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;enableSparsification=%RED%"1" %ENDCOLOR% clockFrequency="320"/%BLUE%&gt;%ENDCOLOR%
   * Hit comparator mode: %BLUE%&lt;Misc%ENDCOLOR% analogmux="0b00000" &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;pipelogic=%RED%"0"%ENDCOLOR% %GREEN%stublogic=%ENDCOLOR%%RED%"0" %ENDCOLOR%or254="1" tpgclock="1" testclock="0" dll="0"/%BLUE%&gt;%ENDCOLOR%
      * 0 -&gt; sampled
      * 1 -&gt; OR
      * 2 -&gt; HIP
      * 3 -&gt; latched

[[https://gitlab.cern.ch/cms_tk_ph2/Ph2_ACF/-/blob/Dev/HWInterface/CbcInterface.cc#L254]]

---++++ xml file testing

Test the parsing of the %NAVY%D19CDescription_iphc.xml%ENDCOLOR% file
<verbatim>
systemtest -f D19CDescription_iphc.xml</verbatim>

---++ Run the code

*At each new terminal* enter Ph2_ACF directory and setup the code environment

<verbatim>
cd <path-to>/Ph2_ACF
source setup.sh</verbatim>

Then go to your running directory

---+++ FC7 configuration

Check if the FC7 is connected

<verbatim>ping -c 3 192.168.7.170</verbatim>

List all available firmware images on the FC7 FPGA
<verbatim>fpgaconfig -c D19CDescription_iphc.xml -l</verbatim>

Add a new firmware image on the FC7 FPGA
<verbatim>fpgaconfig -c D19CDescription_iphc.xml -f <your image> -i <name without .bin> </verbatim>

"name" you chose must be not too long, otherwise you receive error "TextExceedsSpaceAvailable":
<verbatim>terminate called after throwing an instance of 'uhal::exception::TextExceedsSpaceAvailable'
  what():  Text exceeds space available for it in the MMC (no additional info)
Aborted (core dumped)
</verbatim>

Load firmware image at each FC7 reboot (current firmware)
<verbatim>fpgaconfig -c D19CDescription_iphc.xml -i uDTC_2S_CIC2_3Links</verbatim>

**Note**:  first run after loading not good




---+++ Before data-taking

---++++ Pedestal equalization and noise measurement (CBC)

Change trigger settings: %BLUE%&lt;Register%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"trigger_source"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 3 %BLUE%</Register>%ENDCOLOR%

%RED%Important%ENDCOLOR%: Make sure both Test Pulse and Sparsification are disabled:
 %BLUE%&lt;TestPulse%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;enable=%RED%"0"%ENDCOLOR% polarity="0" amplitude="0x3F" channelgroup="0" delay="0" groundothers="1"/&gt;

How to run *pedestal equalization and noise measurement*
<verbatim>
feh_2s_test -f D19CDescription_iphc.xml --withCIC -t -m [-a] [-b] --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202"</verbatim>

   * -t : tune offset
   * -m: measure noise
   * -a: all channels at once
   * -b: batch mode

*Calibration files* are produced in the Results folder.  Change the config files path in %NAVY%D19CDescription_iphc.xml%ENDCOLOR% in other to use the obtained ones for data taking.

<br /> If you do not run with the -lvps "..." option, you will notice that you need to control the power supply to the service hybrid during the power-cycling . At the moment it is done manually (Ph2_ACF pauses to let you do that)
<br />
<img alt="manual_power-cycle.png" height="100" src="%ATTACHURLPATH%/manual_power-cycle.png" width="500" />

<br /> Under Results folder you will find a ROOT file



<table class="twikiTable" width="80%" bgcolor=#f5f5fa  border=1 cellpadding=40 cellspacing=40>
<tr>
<td bgcolor=#eeeeee  align="center"> 
     <br> Noise distribution in the two FEHs <br />
     <img src="%ATTACHURLPATH%/FE0_Noise.png" alt="FE0_Noise.png" width="330" height="200" />
     <img src="%ATTACHURLPATH%/FE1_Noise.png" alt="FE1_Noise.png" width="330" height="200" />
</td>
<td bgcolor=#eeeeee align="center">
<br> SCurve for a given CBC </br>
     <img src="%ATTACHURLPATH%/FE0CBC0_SCurve.png" alt="FE0CBC0_SCurve.png" width="330" height="200" />
</td>
</tr>
</table>

---++++ Hit and Stub latency scan with Test Pulse

   First of all change trigger settings: %BLUE%<Register%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"trigger_source"%ENDCOLOR%%BLUE%>%ENDCOLOR% 6 %BLUE%</Register>%ENDCOLOR%

Make sure Test Pulse is enabled:
 %BLUE%<TestPulse%ENDCOLOR% %GREEN%enable=%ENDCOLOR%%RED%"1"%ENDCOLOR% polarity="0" amplitude="0x3F" channelgroup="0" delay="0" groundothers="1"/>

To run *Hit latency scan*, do:

<verbatim>
commission -f D19CDescription_iphc.xml --withCIC -l -m 0 -r 512 --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" -b
</verbatim>

   * -m : minimum value
   * -r : range in clock cycles (max=m+r)
   * -l : latency (hits)

To run *Stub latency scan*

1. add the hit latency found previously under <Module>
%BLUE%<Settings%ENDCOLOR% %GREEN%threshold=%ENDCOLOR%%RED%"550"%ENDCOLOR%%BLUE% latency="104"/>%ENDCOLOR%

2. Then run
<verbatim>
   commission -f D19CDescription_iphc.xml --withCIC -s -m 0 -r 512 --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" -b
   </verbatim>

   * -m : minimum value
   * -r : range (max=m+r)
   * -s: stub latency

3. After you've found the stub latency, add it to
%BLUE%<Register%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"common_stubdata_delay"%ENDCOLOR%%BLUE%>%ENDCOLOR% 5 %BLUE%</Register>%ENDCOLOR%

For test pulse: hit latency = 104 and stub latency = 35.

---++++ Hit and Stub latency scan with source or beam

Change trigger settings: %BLUE%<Register%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"trigger_source"%ENDCOLOR%%BLUE%>%ENDCOLOR% 5 %BLUE%</Register>%ENDCOLOR%

Make sure Test Pulse is disabled:
 %BLUE%<TestPulse%ENDCOLOR% %GREEN%enable=%ENDCOLOR%%RED%"0"%ENDCOLOR% polarity="0" amplitude="0x3F" channelgroup="0" delay="0" groundothers="1"/>

To run *Hit latency scan*, do:

<verbatim>
commission -f D19CDescription_iphc.xml --withCIC -l -m 0 -r 512 --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" -b
</verbatim>

   * -m : minimum value
   * -r : range in clock cycles (max=m+r)
   * -l : latency (hits)

To run *Stub latency scan*

1. add the hit latency found previously under <Module>
%BLUE%<Settings%ENDCOLOR% %GREEN%threshold=%ENDCOLOR%%RED%"550"%ENDCOLOR%%BLUE% latency="104"/>%ENDCOLOR%

2. Then run
   <verbatim>
   commission -f D19CDescription_iphc.xml --withCIC -s -m 0 -r 512 --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" -b
   </verbatim>

   * -m : minimum value
   * -r : range (max=m+r)
   * -s: stub latency

3. After you've found the stub latency, add it to
%BLUE%&lt;Register%ENDCOLOR% &lt;span class='WYSIWYG_COLOR' style='color:#008000'&gt;name=%RED%"common_stubdata_delay"%ENDCOLOR%%BLUE%&gt;%ENDCOLOR% 5 %BLUE%</Register>%ENDCOLOR%

With CYRCé beam: hit latency = 119 and stub latency = 48.

   * icon:led-red to find stub latency faster, you can play with external trigger delay %BLUE%<Register%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"ext_trigger_delay_value"%ENDCOLOR%%BLUE%> 100 %BLUE%</Register>%ENDCOLOR%.
   * Currently, for external trigger delay = 100, hit latency = 119 and stub latency = 48.

---++++ DLL scan with source or beam

At the end of the %NAVY%D19CDescription_iphc.xml%ENDCOLOR% file, you will find DLL configuration:

%BLUE%<Setting%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"StartVcth"%ENDCOLOR%%BLUE%>%ENDCOLOR% 590        %ENDCOLOR% %BLUE%</Setting>%ENDCOLOR% </br>
%BLUE%<Setting%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"EndVcth"%ENDCOLOR%%BLUE%>%ENDCOLOR% 540         %ENDCOLOR% %BLUE%</Setting>%ENDCOLOR%  </br>
%BLUE%<Setting%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"StartLatency"%ENDCOLOR%%BLUE%>%ENDCOLOR% 113   %ENDCOLOR% %BLUE%</Setting>%ENDCOLOR%  </br>
%BLUE%<Setting%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"LatencyRange"%ENDCOLOR%%BLUE%>%ENDCOLOR% 4    %ENDCOLOR% %BLUE%</Setting>%ENDCOLOR%  </br>
%BLUE%<Setting%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"DLLStep"%ENDCOLOR%%BLUE%>%ENDCOLOR% 5             %ENDCOLOR% %BLUE%</Setting>%ENDCOLOR% 


To run *DLL scan*, do

<verbatim>
hit_count_pulse_shape -f D19CDescription_iphc.xml --withCIC -b -o DLL_Scan/
</verbatim>

<img alt="TriggerLatencyns__vs__ThresholdVcth__630kHz_logz.png" height="200" src="%ATTACHURLPATH%/TriggerLatencyns__vs__ThresholdVcth__630kHz_logz.png" />

---+++ Take data with source or beam

Change trigger settings: %BLUE%<Register%ENDCOLOR% %GREEN%name=%ENDCOLOR%%RED%"trigger_source"%ENDCOLOR%%BLUE%>%ENDCOLOR% 5 %BLUE%</Register>%ENDCOLOR%

Make sure you have updated
   * the config files with ones from calibration
   * the latency values

To *take data* and save results in to binary files, run

Using number of events
<verbatim>
miniDAQ -f D19CDescription_iphc.xml --withCIC -e 1000 --dqm --daq --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" </verbatim>

Using data taking duration (in seconds)
<verbatim>
miniDAQ -f D19CDescription_iphc.xml --withCIC -D 30 --dqm --daq --lvps "http://192.168.7.94/scpi_response.txt?request=inst:nsel%202" </verbatim>

   * -e : number of events
   * -D: duration
   * --dqm (-q) : create histograms
   * --daq (-d) : : save the data into a binary  .daq file (another .raw format is also available <!--raw use the phase-2 Tracker data format-->
   * -o: output directory. %RED%WARNING%ENDCOLOR%: the directory must be created before running miniDAQ (to be fixed). Default: Results/

---+++ Reproduce results from binary files

You can still reproduce qdm histograms from the binary file, by running:
<verbatim>
miniSLinkDQM -f file.daq --dqm [--tree] - o output
</verbatim>

Make sure you create "output" directory first!

---+++ Single Event Upset (SEU)

SEU effects: corruption of a single bit in a memory array
   * bit errors (charge deposit in an ASIC (silicon))
   * bit flip in I2C registers (in triplicated cells) bits stay wrong after an SEU until reset

CBC alignment: One need to align the CBC with the beam and have a large beam spot to cover both electronic and strips.

Data taking: long run @ known intensité which is derived from expected occupance (something close to LHC). Number from KIT: 10MHz/cm^2 correspond to 1% occupancy. Never run beyond 720MHz/cm^2.

Within XDAQ there is "Read config" that you can run with "miniDAQ" executable.

Example: [[https://docs.google.com/spreadsheets/d/1eQBiWr5U7twgaRClFvm64MQEX-0TdJ3YfUfkGYrfTP8/edit?usp=sharing][https://docs.google.com/spreadsheets/d/1eQBiWr5U7twgaRClFvm64MQEX-0TdJ3YfUfkGYrfTP8/edit?usp=sharing]]

---+++ KIRA test box

<img alt="" src="%ATTACHURLPATH%/KIRA_test-box_img1.jpg" width="350" />
<img alt="" src="%ATTACHURLPATH%/KIRA_test-box_img2.jpg" width="350" />

---+ Troubleshooting

%TWISTY{mode="div" showlink="Troubleshooting" hidelink="Grounding of the mini module"  firststart="hide" showimgright="%ICONURLPATH{toggleopen-small}%" hideimgright="%ICONURLPATH{toggleclose-small}%" class="twikiHelp"}%

* %RED%Error%ENDCOLOR%
<verbatim>
   Starting back-end alignment procedure ....
   terminate called after throwing an instance of 'std::out_of_range'
   what():  vector::_M_range_check
   Abandon (core dumped)
   </verbatim>

   Check back-end alignment procedure in tools/BackEndAlignment.cc

* %RED%Error%ENDCOLOR%
<verbatim>
   I2C readback failed..  for hybrid 0 register 0xa4 [CIC]
   terminate called after throwing an instance of 'std::runtime_error'
   what():  I2C readback mismatch...
   Abandon (core dumped)
   </verbatim>

   Check if you are using CIC2 configuration in your xml file

* %RED%Error%ENDCOLOR%
<verbatim>
   Reading monitoring values on SEH connected to link 0
 	.... Reading 1.5V monitor on SEH  : 0 V.
 	.... Reading 2.5V monitor on SEH : 0 V.
 	.... Reading Vmin monitor on SEH : 0 V.
 	.... Reading internal temperature monitor on SEH : 0 [ raw reading is 0].
   According to the Firmware status registers, it was compiled for: 6 hybrid(s), 1 CIC2 chip(s) per hybrid
   Enabling FE hybrid : 0 - link Id 0
   Error in read-back of I2C from CBC.. register which failed is 0xc
   terminate called after throwing an instance of 'std::runtime_error'
   what():  I2C error with CBC on front-end hybrid.. 
   Abandon (core dumped)
   </verbatim>
   i. e not able to power the module, check the temperature (in beam test of 12/2020 the 2S module didn't work under -5 degree)

* %RED%Error%ENDCOLOR%
<verbatim>
   ...No data in the readout ... Trigger in counter is 0 asked for 1000 events and have 0 words in the readout... Re-trying point
                             ||I| Failed to readout all events..... Retrying...
                             ||I| Read back 0 from FC7... readout request is 0
   </verbatim>
   i. e you don't have the Trigger. First check the cabling, then check your settings whether the DIO5 is enable

* %RED%Error%ENDCOLOR% (DLL scan):
<verbatim>
   D19cFWInterface has received ... 18 ... events from DDR3.. data size is 1440 32 bit words.
   terminate called after throwing an instance of 'std::out_of_range'
   what():  map::at
   Aborted (core dumped)
   </verbatim>

   ??

* %RED%Error%ENDCOLOR%
<verbatim>
   read back from FC7 with ReadData
                             ||I| Iter#0 5632 words in FIFO.. going to readout data
                             ||I| D19cFWInterface has received ... 387 ... events from DDR3.. data size is 6192 32 bit words.
                             ||I| 387 events read back from FC7 with ReadData
                             ||I| Stopping triggers...
                             ||I| EventType: d19c CIC2
   </verbatim>

   ??

* %RED%Error%ENDCOLOR%
<verbatim>
   terminate called after throwing an instance of 'uhal::exception::ControlHubTargetTimeout'
   what():  The ControlHub did not receive any response from the target with URI "chtcp-2.0://sbgat209.in2p3.fr:10203?target=192.168.7.170:50001"
   ControlHub returned error code 3 = 'no reply to status packet'
   </verbatim>

   Start the ControlHub "sudo systemctl start controlhub" or restart it (if running) "systemctl restart controlhub"

* %RED%Error%ENDCOLOR%
<verbatim>
 ||I| Want to configure CIC to output patterns from readout chips... 
 ||I| CIC output pattern configured by setting MISC_CTRL to 00001010
 ||I| Re-loading original coonfiguration of fast command block from hardware description file [.xml] 
 ||I| Re-loading original coonfiguration of fast command block from hardware description file [.xml] 
 ||I| Resetting all registers on back-end board 0
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check
   </verbatim>

%ENDTWISTY%

---+ References

| *Document* | *Link* |
| Workshops | [[https://indico.cern.ch/event/842824/][daq-school-2019 ]], [[https://indico.cern.ch/event/924612/][2S Module]], [[https://indico.cern.ch/event/1014295/][daq-school-2021 (intro)]], [[https://indico.cern.ch/event/986962][daq-school-2021]] |
| 2S Module | [[https://indico.cern.ch/event/396801/contributions/1837404/attachments/795725/1090649/150603_Modules_Approval.pdf][Dimension drawing]], [[%ATTACHURLPATH%/8CBC3-ModuleCarrier-KIT.pdf][8CBC3-ModuleCarrier-KIT]], [[%ATTACHURLPATH%/DUT_KIT_mount.pdf][Dimension drawing KIT]] |
| CBC doc | [[https://indico.cern.ch/event/842824/attachments/1920624/3178069/CBC3_universal_interface_specification_V1_2.pdf][CBC3_universal_interface_specification_V1_2]], [[http://www.hep.ph.ic.ac.uk/ASIC/CBC_documentation/CBC3p1_User_Manual_V1p4.pdf][CBC3p1_User_Manual_V1p4]] |
| FC7 User Manual | [[https://indico.cern.ch/event/842824/attachments/1920624/3177104/FC7_Manual.pdf][FC7 Manual]] |
| Micro TCA | [[https://indico.cern.ch/event/489996/contributions/2299441/attachments/1343873/2025111/Schroff_MTCA_Tutorial_KIT_Karlsruhe.pdf][schroff]] |
| MTCA.4 Tutorial | [[https://indico.cern.ch/event/489996/contributions/2299442/attachments/1345134/2027654/Vollrath_Dirksen.pdf][indico.cern.ch/event/489996]] |
| NAT-MCH | [[https://www.nateurope.com/manuals/nat_mch_man_usr.pdf][NAT-MCH –User’s Manual]] |
| d19c user’s and developer’s manual | [[https://twiki.wigner.mta.hu/twiki/pub/CMS/Phase2InnerTrackerDaqTestSetup/d19c_manual.pdf][d19c_manual]] |
| CERN, Development of DC-DC converter at CERN | [[https://project-dcdc.web.cern.ch][dcdc project]] |
| The VTRx+, an Optical Link Module for DataTransmission at HL-LHC | [[https://s3.cern.ch/inspire-prod-files-f/f2b8685027fa468a7e4d3a6514a3416c][inspire-prod-file]] |
| CBC3 CMSSW | [[https://indico.cern.ch/event/875383/contributions/3689216/attachments/1970750/3278286/cbc3_CMSSW.pdf][cbc3_CMSSW]], [[https://indico.cern.ch/event/637390/contributions/2581859/attachments/1491263/2318119/20170711_Unpacker_and_analysis.pdf][Unpacker_and_analysis]] |
| CYRCe for CMS Test Beam | [[https://indico.cern.ch/event/795718/contributions/3305819/attachments/1792440/2920750/IPHC_TkPII_StatusTestBeamCyrce.pdf][Preliminary]], [[https://indico.cern.ch/event/837126/contributions/3509756/attachments/1886150/3109369/TkUpgradeIPHC_1stTestBeam_25_07_2019.pdf][OT system test meeting]], [[https://indico.cern.ch/event/850820/contributions/3581560/attachments/1919635/3175131/TBFirstIPHC_03_10_2019.pdf][Tracker Plenary during TK Week]] |
| Outer tracker | [[https://indico.cern.ch/event/522485/contributions/2145776/attachments/1282482/1906194/FEE2016_Kloukinas_Kostas.pdf][FEE2016_Kloukinas_Kostas]] |
| CHROMIE tutorial for users | [[https://indico.cern.ch/event/813932][indico]] |
| 2S Module Apps | [[https://indico.cern.ch/event/910751/contributions/3973088/attachments/2086411/3505124/200810_DAQ_Meeting_-_Gipht_Status.pdf][Gipht GUI]], [[https://indico.cern.ch/event/969597/contributions/4080851/attachments/2133064/3592309/20201029-OT_System_Test_Meeting_JB.pdf][KIRA Pulse Generator]], [[https://indico.cern.ch/event/1107277][GUI and KIRA]], [[https://gitlab.cern.ch/smaier/ph2_ot_module_test_manual][GUI Manual]] |
| Thesis | [[http://cds.cern.ch/record/2708026][De Clercq]], [[http://cds.cern.ch/record/2711873][Mykyta]], [[http://cds.cern.ch/record/2707148][Nikkie]], [[http://cds.cern.ch/record/2725964][Stefan (KIT)]], [[https://publish.etp.kit.edu/record/22088][Alexander (KIT)]] |
| Further reading | [[https://cds.cern.ch/record/2702281/files/NOTE2019_006.pdf][CMS NOTE -2019/006]], [[https://www.desy.de/f/students/2019/reports/Robert.Hammann.pdf][H. Robert report 2019]] |
-- Main.EmeryNibigira - 2020-06-08
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	8CBC3-ModuleCarrier-KIT.pdf	r1	manage	107.2 K	2021-03-24 - 17:16	EmeryNibigira
png	ChrominiSupervisor_img3.png	r1	manage	54.9 K	2020-08-30 - 13:18	EmeryNibigira
pdf	DAQexplanation.pdf	r1	manage	29.0 K	2021-11-30 - 14:45	EmeryNibigira
png	DAQexplanation.png	r1	manage	231.6 K	2021-11-30 - 14:50	EmeryNibigira
jpg	DSC_0024.JPG	r1	manage	6488.8 K	2020-06-12 - 23:25	EmeryNibigira
pdf	DUT_KIT_mount.pdf	r1	manage	6390.7 K	2021-07-22 - 16:15	EmeryNibigira
png	FC7_card_2sides.png	r1	manage	420.7 K	2020-08-30 - 19:27	EmeryNibigira
png	FE0CBC0_SCurve.png	r1	manage	24.2 K	2020-09-14 - 21:12	EmeryNibigira
png	FE0_Noise.png	r1	manage	10.0 K	2020-09-14 - 21:12	EmeryNibigira
png	FE1_Noise.png	r1	manage	8.9 K	2020-09-14 - 21:12	EmeryNibigira
png	FullModule.png	r1	manage	451.7 K	2020-06-14 - 15:13	EmeryNibigira
jpg	KIRA_test-box_img1.jpg	r1	manage	4533.2 K	2022-01-21 - 12:11	EmeryNibigira	KIRA â€“ Karlsruhe Infrared Array
jpg	KIRA_test-box_img2.jpg	r1	manage	4053.7 K	2022-01-21 - 12:11	EmeryNibigira	KIRA â€“ Karlsruhe Infrared Array
png	LV_DC-DC.png	r1	manage	20.5 K	2020-06-12 - 23:34	EmeryNibigira
png	LV_DC-DC_monitoring.png	r1	manage	15.4 K	2020-06-13 - 15:06	EmeryNibigira
png	LV_after.png	r1	manage	97.5 K	2020-07-24 - 08:10	EmeryNibigira	LV screenshot after some time
png	LV_start.png	r1	manage	96.2 K	2020-07-24 - 08:09	EmeryNibigira	LV screenshot at the beginning
pdf	MCS2UserManual.pdf	r1	manage	577.2 K	2021-03-08 - 18:16	EmeryNibigira	Table X-Y Doc
pdf	MCS2_SERVICE_TOOL.pdf	r1	manage	426.6 K	2021-03-08 - 18:16	EmeryNibigira	Table X-Y Doc
jpeg	New_LV.jpeg	r1	manage	87.8 K	2020-08-30 - 13:18	EmeryNibigira
jpeg	New_LV_front.jpeg	r1	manage	77.3 K	2020-08-30 - 13:18	EmeryNibigira
pdf	Precision_Tool_Commander_Manual.pdf	r1	manage	1025.6 K	2021-03-08 - 18:16	EmeryNibigira	Table X-Y Doc
png	TriggerLatencyns__vs__ThresholdVcth__630kHz_logz.png	r1	manage	15.0 K	2021-11-26 - 14:16	EmeryNibigira
png	XDAQ_DUT.png	r1	manage	222.9 K	2021-07-13 - 11:43	EmeryNibigira
png	_FC7_card.png	r1	manage	420.7 K	2020-08-30 - 19:25	EmeryNibigira
png	current_vs_voltage.png	r1	manage	9.9 K	2020-07-25 - 16:38	EmeryNibigira
png	grounding.png	r1	manage	52.0 K	2021-03-07 - 23:42	EmeryNibigira
jpg	isegHV.jpg	r1	manage	2192.4 K	2021-03-07 - 23:41	EmeryNibigira
png	manual_power-cycle.png	r1	manage	9.3 K	2020-06-13 - 15:06	EmeryNibigira
png	noise_vs_voltage.png	r1	manage	8.8 K	2020-07-25 - 16:39	EmeryNibigira
png	uTCA_crate.png	r1	manage	678.1 K	2020-08-30 - 12:36	EmeryNibigira
Topic revision: r89 - 2022-02-01 - EmeryNibigira
Account
- Log In
- Cern Search
- TWiki Search
- Google Search
Sandbox All webs
Edit
Attach
Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback