Hardware run with FEI4, Telescope and FW&BW Modules
Pos 10: x= 136.08mm, y=68.9 mm (narrow side down)
Bilder: Hitmap FE-I4 und Correlation zw. Mimosa und FE-I4
Apparently every problem can be attributed to a misalignment problem. The telescope has troubles with heavily misaligned DUTs. Was resolved by creating different gear-files for each run with pretty precise coordinates of the DUT position calculated for the telescope coordinate system.
Additionally one has to watch out for misaligned planes of the telescope itself. It was required to allow for more than 2mm offset for the telescope planes behind the DUTs. This can be easily checked by looking at the PreAligner plots in the -hitmaker-histo.root file.
It look something like this:
and not like this:
RUN WITH SVD3, telescope and FEI4
EUDET Run 61
Mimosa Threshold 6
Pos 2: x=69.3 mm, y=79 mm (Hits in APV 3-4 und 8-9 in p-Seite und 13 und 18 in n-Seite)
a working version of the EUDET online monitor (which works also with the FE-I4) is at the following location
~/BELLETEST/eudaq-neu/build/monitors/onlinemon$ ./OnlineMon.exe -sc 0 -f /home/telescope/eudaq/data/run000060.raw
EUDET Run 62
Pos 3: x=38.6 mm, y=84 mm
EUDET Run 63
Pos 4: x=130.7 mm, y=84 mm
EUDET Run 64
Pos 5: x=30.5 mm, y= 99.74 mm (wide side top)
TLU DuT interface:
Trying to get a nice plot of the beam profile by only using the vertical PMTs (number 0 and 2) see http://elog.hephy.at/testbeam-SPS2015/66 for details.
Producer.TLU Config Change:
Trying to get a nice plot of the beam profile by only using the PMTs 1 and 3 (horizontal) see http://elog.hephy.at/testbeam-SPS2015/66 for details.
Trying to get a nice plot of the beam profile by only using the vertical PMT 0 (upstream vertical, the long one) see http://elog.hephy.at/testbeam-SPS2015/66 for details.
EUDET Run 68
Pos 8: x=136.08 mm, y= 79 mm (narrow side center)
There are two planes, one fixed upstream and one fixed downstream.
CIS3WII_6 upstream and CIS2WI_IBL2 downstream.
They are configured using the pc in H6B which can be accessed via microsoft remote desktop from the network 192.168.5.x using the ip 192.168.5.6.
The configuration files can be found in the folder "E:\ConfigurationCMS\" on the server and are named after the modules.
Only one of the FEI4 detectors can be used at a time since they are of different generations (FEI4A and FEI4B) which can't be used at the same time with the available USB board. vnc
The configuration for EUDAQ needs to be adapted for the used module by changing the name of the configuration file.
SRAM_READOUT_AT = 5
SkipConfiguration = no
UseSingleBoardConfig = no
boards = 230
modules = 1
config_file = E:\ConfigurationCMS\CIS3_W11_06_thr1600_7to21ke_modified.cfg.root
#config_file = E:\ConfigurationCMS\CIS2_W02_IBL1_thr1600_7to14_modified.cfg.root
fpga_firmware = E:\icwiki_svn\USBPixI4\host\tags\release-5.3\config\usbpixi4.bit
lvl1_delay = 16
tlu_trigger_data_delay = 10
In my experience switching between the planes also requires a restart of the USBPix DAQ because apparently something is not working with the reload of a different config file afterwards. I had the phenomenon that the DAQ responded like it was working but the datastream was empty. Therefore always check the online monitor for hitmaps.
EUDET Run 71
Pos 1: x=100 mm, y=79 mm (Hits in APV 3 und 8-9 in p-Seite und 14 und 17 in n-Seite )
Downstream FEI4 used
Trying to get a nice plot of the beam profile by only using the and 3 (horizontal) see http://elog.hephy.at/testbeam-SPS2015/66 for details.
EUDET Run 73
Pos 7: x= 30.5 mm, y= 79 mm (wide side center)
Upstream FEI4 used, checking if alignment change helped
EUDET Run 74
Upstream FEI4 used
Testrun to see how the telescope behaves without a DUT to test if there is an increased amount of multiple scattering after the aluminum planes of the FW and BW module.