Wiki source code of Gotthard related stuff

Version 16.1 by sndueste on 2023/09/15 13:46
Show last authors
1 == ==
2
3 {{toc/}}
4
5 == Info collection related to the Detector ==
6
7 * [[Data sheet of a macro objective>>attach:MP-E_65mm_F2.8_1-5x_Instruction_DE.pdf]]
8 * [[FLASH-GH-Meeting_10.10.2014.pdf by Steffen>>attach:FLASH-GH-Meeting_10.10.2014.pdf]]
9 * [[attach:READ_ME_GOTTHARD_detector.pdf]]: READ_ME_GOTTHARD_detector.pdf (Server information is outdated, see below)
10 * some investigation related to read out noise for different exposure times [[attach:GOTTHARD noise evaluation and exposure time dependence (002).pdf]]
11
12 \\
13
14 Ethernet connections:
15
16 (% style="list-style-type: square;" %)
17 * gbit port  <~-~-->  Server PC (hasfl2det01 at FLASH2, no server currently at FLASH1)
18 * base-T     <~-~-->  Office net
19
20 == How to use the Detector and save in DAQ ==
21
22 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"
23
24 \\
25
26 * Main Gotthard panel for users :
27
28 [[image:attach:Clipboard05.gif||height="400"]]
29 \\
30
31 \\
32
33 * Exp2 DAQ RC gui for recording Gotthard data. EXPERIMENT_GOTTHARD has to be included
34
35 [[image:attach:Clipboard01.gif||height="400"]]
36
37 \\
38
39 == Operation hints (June 2023): ==
40
41 (% style="list-style-type: square;" %)
42 * **Where is the GOTTHARD GUI:** FLASH2 - Panel: Infrastructure tab → Miscellaneous tab → FLASH2 GOTTHARD ctrl button
43 * **Never change a running system:** Do not change parameters while the Detector is running/taking data, The detector will crash.
44 * Furthermore the module will crash if recieving to much light (e.g. illuminating with flash light during data dating.
45 * **Checking/switching server:** The server is reachable from the GOTTHARD GUI (lower left corner find the status of the server PC "hasfl2det01") click it to open server/watchdog control. The server is otherwise found under FLASH.SYSTEM → HASFL2DET01.WATCH. Open control of SVR.GOTTHARD (for start/stop/reboot)
46
47 (% style="list-style-type: square;" %)
48 * **Robooting the GOTTHARD** (if it has crashed): 
49 (% style="list-style-type: square;" %)
50 ** soft reboot: 1. open console on linux DESY PC, 2. type "telnet (Hostname/IP)" e.g. "telnet cfeld-gotthard02" , 3. you are logged on the GOTTHARD module as /root, type "reboot", 4. wait until server/GUI has reconnected to the module
51 ** hard reset: power down the GOTTHARD, wait some seconds, Repower the module, wait for reconnection to server/GUI
52 * **In case of a crashes** (no data taking, no reaction on input: Reboot the detector) or if GUI input returns error: Check connection (Power/Data), check GOTTHARD server
53 * **Permantent operation:** Activate check box for continous run to trigger automated restart of the module after reaching the set number of short or after sefl-stopping due to hickups. The restart needs about 1-2 seconds. During this time no data is taken.
54 * **Background**: Check "Take" stores the actual detector image~: Uncheck this again. Than this stored image is online subtracted from all images in the GUI when checking "subtract". The DAQ only stores raw data (NOT the background subtracted images)
55
56 Using burst mode (standard operation as of June 2023)
57
58 (% style="list-style-type: square;" %)
59 * Do not change the delay in the GOTTHARD GUI. The Alignment to the FEL pulses are done by adjusting the FLASH trigger: FL2EXP1/RTM.TRG6, it can be opened from the GOTTHARD GUI or from FLASH2 → Beamlines → FL26 → Exp. control → Patch Panel26-2 → MTCA Trigger 2
60 * Exposure range is 2**00ns <  Exposure < ~~1/3 * Frame periode**
61 * The periode is:** 9968ns for 100kHz, 4984 for 200kHz, 1993 for 500kHz**
62 * The number of** frames must be lower than 125, for stable operation 120**
63 * Number of Shots: Number of trigger events before self stopping, select large number for permanent operation
64
65 == Modules and their exchange ==
66
67 Two (Three) modules available (physically at FLASH):
68
69 (% class="wrapped relative-table" style="width: 64.2451%;" %)
70 |=(((
71 hostname
72 )))|=(((
73 Status
74 )))|=(((
75 Sensor
76 )))|=(% colspan="1" %)(((
77 Sensor image
78 )))|=(((
79 config file
80 )))|=(% colspan="1" %)(((
81 DOOCS address (status 2023)
82 )))
83 |(((
84 cfeld-gotthard02
85 )))|(((
86 **standard**/online/working
87 )))|(((
88 (% class="content-wrapper" %)
89 (((
90 two small areas of damaged pixels
91 )))
92 )))|(% colspan="1" %)(((
93 (% class="content-wrapper" %)
94 (((
95 [[image:attach:cfeld-gotthard02.jpg||height="250"]]
96 )))
97 )))|(((
98 bchip_mpc1922Receiver.config_cfeld-gotthard02
99 )))|(% colspan="1" %)(((
100 FLASH.FEL/GOTTHARD/FL2/
101 )))
102 |(((
103 hasdslabgh
104
105 "gotthard dgt01"
106 )))|(((
107 working
108 )))|(((
109 first 1/3 is blind, strong base line offset in the center and a further blind bunch and the end
110 )))|(% colspan="1" %)(((
111 (% class="content-wrapper" %)
112 (((
113 [[image:attach:hasdslabgh.jpg||height="250"]]
114 )))
115 )))|(((
116 bchip_mpc1922Receiver.config
117 )))|(% colspan="1" %)(((
118 FLASH.FEL/GOTTHARD2/FL2/
119 )))
120 |(((
121 cfeld-gotthard01
122 )))|(((
123 was working (2018), backilluminated! the sensor front is Al-shielded for x-rays
124 )))|(((
125 ?
126 )))|(% colspan="1" %)(((
127 \\
128 )))|(((
129 bchip_mpc1922Receiver_petra.config
130 )))|(% colspan="1" %)(((
131 \\
132 )))
133
134 \\
135
136 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/**
137
138 \\
139
140 == GOTTHARD Server ==
141
142 The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**
143
144 \\
145
146 == Main Parameters and limits ==
147
148 (% class="wrapped" %)
149 |=(((
150 Parameter
151 )))|=(((
152 Design
153 )))|=(% colspan="1" %)(((
154 Real /tested
155 )))
156 |(((
157 Max Frames
158 )))|(((
159 125
160 )))|(% colspan="1" %)(((
161 120
162 )))
163 |(((
164 Max. exposition time
165 )))|(((
166 ~~2/3 of period time
167 )))|(% colspan="1" %)(((
168 \\
169 )))
170 |(((
171 Min. period time
172 )))|(((
173 ca. 930 ns
174 )))|(% colspan="1" %)(((
175 \\
176 )))
177 |(((
178 Max repetition frequ.
179 )))|(((
180 1 MHz
181 )))|(% colspan="1" %)(((
182 833 kHz (software limited)
183 )))
184
185 \\
186
187 == Soft reset a GOTTHARD Module ==
188
189 (% style="list-style-type: square;" %)
190 * Open console on Linux PC (connected to DESY net)
191 * write "telnet cfeld-gotthard02" (or the respective Host name or IP of the module)
192 (% style="list-style-type: square;" %)
193 ** you should be connected to the GOTTHARD onboard system → </root:
194 * type: "reboot"
195 (% style="list-style-type: square;" %)
196 ** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.
197
198 \\
199
200 == Triggering the Gotthard with a burst trigger ==
201
202 it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger
203
204 here are some Info from PIS (June 2023)
205
206
207
208 {{view-file att--filename="Flash_G1.pdf" height="250"/}}
209
210 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).
211
212 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.
213
214 Regarding the detector setting (assuming it is 200 kHz pulse rate, 100 pulses per train):
215
216 * timing mode: trigger
217 * number of frames: 1
218 * 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)
219 * 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)
220 * exposure time: > 93 ns and smaller than period
221
222 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.
223
224 \\
225
226 by:
227
228 Dr. Jiaguo Zhang
229
230 Paul Scherrer Institut
231
232 Forschungsstrasse 111
233
234 5232 Villigen PSI
235
236 Switzerland
237
238 \\
239
240 == Using the Spectralyzer together with Gotthard ==
241
242 one needs spectralyzer 0.2.4 or newer
243
244 \\
245
246 start spectralyzer on one of our consoles ( works for fl24 and fl26user )  (for installing new version or for other users .. ask Christopher Behrens... )
247
248 (% class="code" %)
249 (((
250 fl26user@hasfcons1:~~$ mamba activate spectralyzer
251 (spectralyzer) fl26user@hasfcons1:~~$ spectralyzer
252 )))
253
254 \\
255
256 [[image:url:https://ttfinfo.desy.de/Flash2_FL26elog/data/2023/06/2023-02-10T16:03:53-00.jpg||height="250"]]
257
258 [[image:attach:image2023-9-15_11-16-3.png||height="400"]]
259
260 \\
261
262 \\
263
264 \\
265
266 \\