cooled (see attachment)

FIRRun002, PedestalRun006

target: CE, pos 3

cooling box emergency break ... ie about the last 1-10 k not useable.

cooled (see attachment) in - 20,5 out -7,8

FIRRun002, PedestalRun006

target: fw, pos 4

120GeV hadrons, beam config H6A.BELLE.003

Testrun with the FEI4 working for the first time. 

Lessons learned about the configuration:

EnableDUTVeto needs to be set for the FEI4 to allow it to work

HandShakeMode needs to be enabled for the FEI4 as well

"Enable RJ45 input during scans" needs to be enabled for the USB-controller

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

Room temp, fir002

room temp
FIRRun002,
pedestalrun006;
pedestalrun007
 

Channels:

• Upstream vertical -> channel 0; (bitmask 1)
• Upstream horizontal -> channel 1; (bitmask 2)
• Downstream vertical -> channel 2; (bitmask 4)
• Downstream horizontal ->channel 3; (bitmask 8)

TLU DuT interface:

FIR filer and ADC delay with all sensor and telescope.
Telescope alignment

Room temp, fir004

room temp

FIRRun004, PedestalRun008
telescope alignment

room temp
pedestalrun 008
FIRRun004

max frame pos = 0. frame

[six]
lvl = 20, 30
lat = 95
sam = 20
grp = 8

room temp
pedestalrun 008
FIRRun004

max frame pos = 0. frame

[six]
lvl = 20, 30
lat = 96
sam = 20
grp = 8

room temp
pedestalrun 008
FIRRun004

max frame pos = 1-2-3. frame n side still shifted

[six]
lvl = 20, 30
lat = 97
sam = 20
grp = 8

room temp
pedestalrun 008
FIRRun004

max frame pos = 1-2-3. frame n side still shifted

[six]
lvl = 20, 30
lat = 98
sam = 20
grp = 8

cooled
pedestalrun 008
FIRRun004

max frame pos = 1-2-3. frame n side still shifted

[six]
lvl = 15, 35
lat = 96
sam = 50
grp = 8

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. 

[Producer.USBpixI4]
SRAM_READOUT_AT = 5
SkipConfiguration = no
UseSingleBoardConfig = no
boards = 230
modules[230] = 1
#upstream
config_file = E:\ConfigurationCMS\CIS3_W11_06_thr1600_7to21ke_modified.cfg.root
#downstream:
#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. 

temp: in -22 out -18,
FIRRun004,

cooled
pedestalrun 008
FIRRun004

max frame pos = 1-2-3. frame n side still shifted

[six]
lvl = 15, 35
lat = 96
sam = 50
grp = 8