pos x-Direction = Jura side
pos y-Direction = Down
Zero-point is in the top right corner in Beam direction
absolute Position of PI Stages:
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 )
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)
Pos 3: x=38.6 mm, y=84 mm
Pos 4: x=130.7 mm, y=84 mm
Pos 5: x=30.5 mm, y= 99.74 mm (wide side top)
Pos 6: x=136.08 mm, y= 91.49 mm (narrow side top)
Pos 7: x= 30.5 mm, y= 79 mm (wide side center)
Pos 8: x=136.08 mm, y= 79 mm (narrow side center)
Pos 9: x=30.5 mm, y= 60.67 mm (wide side down)
Pos 10: x= 136.08mm, y=68.9 mm (narrow side down)
Something triggered a emergency break. HWRun012 only last 1-10k event has to be discarded.
120GeV hadrons, beam config H6A.BELLE.003
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:
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
TLU DuT interface:
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.