Changes for page Gotthard related stuff

Last modified by sndueste on 2023/09/25 09:36
From version 8.1
edited by palutke
on 2023/06/08 14:23
Change comment: There is no comment for this version
To version 11.1
edited by palutke
on 2023/06/24 16:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,6 +33,32 @@
33 33  
34 34  \\
35 35  
36 +== Operation hints (June 2023): ==
37 +
38 +(% style="list-style-type: square;" %)
39 +* **Where is the GOTTHARD GUI:** FLASH2 - Panel: Infrastructure tab → Miscellaneous tab → FLASH2 GOTTHARD ctrl button
40 +* **Never change a running system:** Do not change parameters while the Detector is running/taking data, The detector will crash.
41 +* Furthermore the module will crash if recieving to much light (e.g. illuminating with flash light during data dating.
42 +* **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)
43 +
44 +(% style="list-style-type: square;" %)
45 +* **Robooting the GOTTHARD** (if it has crashed): 
46 +(% style="list-style-type: square;" %)
47 +** 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
48 +** hard reset: power down the GOTTHARD, wait some seconds, Repower the module, wait for reconnection to server/GUI
49 +* **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
50 +* **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.
51 +* **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)
52 +
53 +Using burst mode (standard operation as of June 2023)
54 +
55 +(% style="list-style-type: square;" %)
56 +* 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
57 +* Exposure range is 100ns <  Exposure < ~~1/3 * Frame periode
58 +* The periode is: 9968ns for 100kHz, 4984 for 200kHz, 1993 for 500kHz
59 +* The number of frames must be lower than 125, for stable operation 120
60 +* Number of Shots: Number of trigger events before self stopping, select large number for permanent operation
61 +
36 36  == Modules and their exchange ==
37 37  
38 38  Two (Three) modules available (physically at FLASH):
... ... @@ -106,6 +106,7 @@
106 106  
107 107  == Main Parameters and limits ==
108 108  
135 +(% class="wrapped" %)
109 109  |=(((
110 110  Parameter
111 111  )))|=(((
... ... @@ -154,3 +154,47 @@
154 154  * type: "reboot"
155 155  (% style="list-style-type: square;" %)
156 156  ** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.
184 +
185 +\\
186 +
187 +== Triggering the Gotthard with a burst trigger ==
188 +
189 +it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger
190 +
191 +here are some Info from PIS (June 2023)
192 +
193 +
194 +
195 +{{view-file att--filename="Flash_G1.pdf" height="250"/}}
196 +
197 +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).
198 +
199 +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.
200 +
201 +Regarding the detector setting (assuming it is 200 kHz pulse rate, 100 pulses per train):
202 +
203 +* timing mode: trigger
204 +* number of frames: 1
205 +* 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)
206 +* 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)
207 +* exposure time: > 93 ns and smaller than period
208 +
209 +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.
210 +
211 +\\
212 +
213 +by:
214 +
215 +Dr. Jiaguo Zhang
216 +
217 +Paul Scherrer Institut
218 +
219 +Forschungsstrasse 111
220 +
221 +5232 Villigen PSI
222 +
223 +Switzerland
224 +
225 +\\
226 +
227 +\\