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!!!!!
DHCP Range: 192.168.0.200 to 239
DNS Server: 192.168.0.254
external IP: 22.214.171.124 (für diverse Port Forwardings)
Manuell vergebene IP Adressen bitte unbedingt Benni mitteilen oder/und in der folgenden Tabelle eintragen!
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
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
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
FIR filer and ADC delay with all sensor and telescope.
telescope n-side switched.
room temp max subevent at 2. with lat = 96
lat = 97 to a greater range of lat scan
lat = 98
Calibration Run with +- 50V Bias with higher compliance since the p-side draws more current than expected (23muA by the MAMBO)
room temp, FIRRun002, PedestalRun005, room temp
target: FW, pos 9 (p-0, n-128*4)
0 offset (at the beginning)
Started APVDAQ and waited till 600 were taken then started EUDAQ
EUDAQ Run 24
Mimosa Thresholds lvl 7
FIRRun002, pedestalrun006; temp see attachment in pedestalrun006
FIRRun002, PedestalRun006 (temp enty)
target: BW, pos 1
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
cooled (see attachment) in -21.24 out -18.54
cooling supply emty at ~24:00 ie first 30k is cooled.
target: BW, pos 5