Wiki source code of Gotthard related stuff

Version 9.1 by sndueste on 2023/06/20 12:33
Hide last authors
sendels 1.1 1 == Info related to the Detector ==
2
3 \\
4
sendels 3.1 5 * [[Data sheet of a macro objective>>attach:MP-E_65mm_F2.8_1-5x_Instruction_DE.pdf]]
6 * [[FLASH-GH-Meeting_10.10.2014.pdf by Steffen>>attach:FLASH-GH-Meeting_10.10.2014.pdf]]
palutke 5.1 7 * [[attach:READ_ME_GOTTHARD_detector.pdf]]: READ_ME_GOTTHARD_detector.pdf (Server information is outdated, see below)
sendels 1.1 8
9 \\
10
palutke 5.1 11 Ethernet connections:
sendels 1.1 12
palutke 5.1 13 (% style="list-style-type: square;" %)
palutke 8.1 14 * gbit port  <~-~-->  Server PC (hasfl2det01 at FLASH2, no server currently at FLASH1)
15 * base-T     <~-~-->  Office net
sendels 1.1 16
palutke 5.1 17 == How to use the Detector and save in DAQ ==
18
sendels 2.1 19 for now very short: run the Exp2 DAQ with EXPERIMENT_GOTTHARD included as shown below. AND press the start button in the Gotthard DAQ (you get there from the Gotthard panel lower left button "Gotthard DAQ"
sendels 1.1 20
21 \\
22
sendels 2.1 23 * Main Gotthard panel for users :
sendels 1.1 24
sendels 4.1 25 [[image:attach:Clipboard05.gif||height="400"]]
sendels 1.1 26 \\
27
28 \\
29
30 * Exp2 DAQ RC gui for recording Gotthard data. EXPERIMENT_GOTTHARD has to be included
31
sendels 4.1 32 [[image:attach:Clipboard01.gif||height="400"]]
33
34 \\
palutke 5.1 35
36 == Modules and their exchange ==
37
38 Two (Three) modules available (physically at FLASH):
39
palutke 7.1 40 (% class="wrapped relative-table" style="width: 64.2451%;" %)
palutke 5.1 41 |=(((
42 hostname
43 )))|=(((
44 Status
45 )))|=(((
46 Sensor
palutke 7.1 47 )))|=(% colspan="1" %)(((
48 Sensor image
palutke 5.1 49 )))|=(((
50 config file
51 )))
52 |(((
53 cfeld-gotthard02
54 )))|(((
palutke 7.1 55 **standard**/online/working
palutke 5.1 56 )))|(((
palutke 7.1 57 (% class="content-wrapper" %)
58 (((
palutke 5.1 59 two small areas of damaged pixels
palutke 7.1 60 )))
61 )))|(% colspan="1" %)(((
62 (% class="content-wrapper" %)
63 (((
64 [[image:attach:cfeld-gotthard02.jpg||height="250"]]
65 )))
palutke 5.1 66 )))|(((
67 bchip_mpc1922Receiver.config_cfeld-gotthard02
68 )))
69 |(((
70 hasdslabgh
71 )))|(((
72 working
73 )))|(((
74 first 1/3 is blind, strong base line offset in the center and a further blind bunch and the end
palutke 7.1 75 )))|(% colspan="1" %)(((
76 (% class="content-wrapper" %)
77 (((
78 [[image:attach:hasdslabgh.jpg||height="250"]]
79 )))
palutke 5.1 80 )))|(((
81 bchip_mpc1922Receiver.config
82 )))
83 |(((
84 cfeld-gotthard01
85 )))|(((
palutke 6.1 86 was working (2018), backilluminated! the sensor front is Al-shielded for x-rays
palutke 5.1 87 )))|(((
88 ?
palutke 7.1 89 )))|(% colspan="1" %)(((
90 \\
palutke 5.1 91 )))|(((
92 bchip_mpc1922Receiver_petra.config
93 )))
94
palutke 6.1 95 \\
palutke 5.1 96
palutke 7.1 97 To change a module the respective config file has to be selected. However changing it will crash the server, thus, it is not possible to change on the fly. Connact Sören if there is the need to exchange a module. However, the differences in the configs are only the hostname. (**To be tested: On the fly might work, if one edits the config-file itself after switching of the server instead of selecting another config file in the GUI. But how to transport this information to the GUI? → Display the first line of the config file!**) The config files are located at the **hasfl2det01: /export/doocs/server/gotthard_server/cfgs/**
palutke 5.1 98
99 \\
100
101 == GOTTHARD Server ==
102
103 The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**
palutke 8.1 104
105 \\
106
107 == Main Parameters and limits ==
108
sndueste 9.1 109 (% class="wrapped" %)
palutke 8.1 110 |=(((
111 Parameter
112 )))|=(((
113 Design
114 )))|=(% colspan="1" %)(((
115 Real /tested
116 )))
117 |(((
118 Max Frames
119 )))|(((
120 125
121 )))|(% colspan="1" %)(((
122 120
123 )))
124 |(((
125 Max. exposition time
126 )))|(((
127 ~~2/3 of period time
128 )))|(% colspan="1" %)(((
129 \\
130 )))
131 |(((
132 Min. period time
133 )))|(((
134 ca. 930 ns
135 )))|(% colspan="1" %)(((
136 \\
137 )))
138 |(((
139 Max repetition frequ.
140 )))|(((
141 1 MHz
142 )))|(% colspan="1" %)(((
143 833 kHz (software limited)
144 )))
145
146 \\
147
148 == Soft reset a GOTTHARD Module ==
149
150 (% style="list-style-type: square;" %)
151 * Open console on Linux PC (connected to DESY net)
152 * write "telnet cfeld-gotthard02" (or the respective Host name or IP of the module)
153 (% style="list-style-type: square;" %)
154 ** you should be connected to the GOTTHARD onboard system → </root:
155 * type: "reboot"
156 (% style="list-style-type: square;" %)
157 ** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.
sndueste 9.1 158
159 \\
160
161 == Triggering the Gotthard with a burst trigger ==
162
163 it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger
164
165 here are some Info from PIS (June 2023)
166
167
168
169 {{view-file att--filename="Flash_G1.pdf" height="250"/}}
170
171 I think one does not need to set it in GUI when running in continuous mode. In G1, whether the detector is running in burst or continuous mode depends on the setting of the "number of frames" in trigger mode. If the number of frames sets to 1, it will be in continuous mode (1 trigger -> 1 frame).
172
173 Since G1 accepts triggers from the lemo connector, one can also use the bunch train trigger. The spacing of the trigger train needs to be larger than 3.2 ms, which is the readout time of G1.
174
175 Regarding the detector setting (assuming it is 200 kHz pulse rate, 100 pulses per train):
176
177 * timing mode: trigger
178 * number of frames: 1
179 * number of triggers:  M x N (M is the number of trains and N is the pulses per train, one can also take a bit more frames per train to track the pedestal/dark)
180 * period: < 5 us (1/200 kHz = 5 us, the period needs to be slightly smaller than 5 us since the detection of the trigger only starts after the period is reached)
181 * exposure time: > 93 ns and smaller than period
182
183 Alignment: One of the four lemo connectors on G1 outputs its exposure window. Using an oscilloscope, one can use a photodiode under the beam and align the pulses from the diode and the exposure window of G1 by fine tuning the exposure time of G1 and/or the setting of "delay after trigger" from the detector, or "delay time" of the wave-generator (if a wave-generator is used to generate the triggers for every pulse). After this, one can do a fine scan of trigger delay to find an optimal setting with highest signal after putting G1 under the beam.
184
185 \\
186
187 by:
188
189 Dr. Jiaguo Zhang
190
191 Paul Scherrer Institut
192
193 Forschungsstrasse 111
194
195 5232 Villigen PSI
196
197 Switzerland
198
199 \\
200
201 \\