Information concerning the SVD3 setup during a beam test

In the beam area setup the whole crate and the power supply with the usual spider cable and the two Keithly 2410 high voltage supplies. Monitoring of the 2410 happens via a NI MAX interface that connects to the GPIB-Ethernet interface and needs to be configured there. The IP and password are noted on the device. The software can be found on heros in medialib/LONGTERM/longterm R3.1_doubleSided as a normal *.vi file. 

Default adresses 16 and 17 as defined in labview, need to figure out on site which is which, if the voltage selected (e.g. 100V) is applied as +50/-50 or if it is applied as +100/-100 before connecting the cables. 

Take a run without dut as well to check the telescope integrity. Without dut in beamline!!!!!

WLAN Router:

SSID: Hephy

password: 20supersecret14

DHCP Range: 192.168.0.200 to 239

Netmask: /24

DNS Server: 192.168.0.254

Gateway: 192.168.0.254

external IP: 128.141.174.109 (für diverse Port Forwardings)

Manuell vergebene IP Adressen bitte unbedingt Benni mitteilen oder/und in der folgenden Tabelle eintragen! 

IP/MAC Zuweisung:

Admin Zugang Wlan Router:

IP: 192.168.0.254

Username: admin

password: Hephy2014

x-Achse: positiv Richtung Saleve (counting room)

y-Achse: positiv Richtung UNTEN!!

position of laddertestbox xy stages:

Rev. Pos (BWD Sensor, BWD, Oben) x= 82.3, y=110.6

Mitte Sensor:

Pos 1: (mitte BWD sensor): x=144.74, y=80.8

Pos 2: (mitte Origami -z): x=269.62, y=80.8

Pos 3: (mitte Origami ce): x=394.42, y=80.8

Pos 4 (mitte FWD Micron Sensor): x=517, y=80.8

Ecke:

Pos 5 (Ecke BWD sensor): x=92.3, y=105.6

Pos 6 (Ecke Origami -z): x=217.18, y=105.6

Pos 7 (Ecke Origami ce): x=342.06, y=105.6

Pos 8 (Ecke FWD sensor): x=467,62, y=56,3 

Pos 9 (Ecke FWD sensor): x=568,33 y=64,48

Coordinate system:

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

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:

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. 

FIR filer and ADC delay with all sensor and telescope.
telescope n-side switched.

FirRun001, room temp
telescope n-side switched.

PedestalRun001, FIRRun001, room temp
telescope n-side switched.
In order to correct the position change the

room temp max subevent at 2. with lat = 96

room temp, FIRRun001, pedestal run 003

lat = 97 to a greater range of lat scan

Cooled!
FIRRun002, pedestalrun006; temp see attachment in pedestalrun006
 

firrun003, room temp
 

CE. pedestal run 003. Fir run 002. Room temp