Skip to Content

Wiki source code of Gotthard related stuff

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