Wiki source code of Gotthard related stuff

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