Changes for page Gotthard related stuff

Last modified by sndueste on 2025-08-22 10:41

From version 19.4
edited by rangeadm
on 2025-04-23 15:10
Change comment: Update document after refactoring.
To version 20.1
edited by sndueste
on 2025-08-22 10:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FLASHUSER.Additional helpful things.jddd-linked help pages.WebHome
1 +FLASHUSER.Misc.jddd-linked help pages.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rangeadm
1 +XWiki.sndueste
Content
... ... @@ -1,13 +1,8 @@
1 -=== page content: ===
1 +== page content: ==
2 2  
3 -== ==
4 -
5 5  {{toc maxLevel="2"/}}
6 6  
7 -\\
8 8  
9 -----
10 -
11 11  == Info collection related to the Detector ==
12 12  
13 13  * [[Data sheet of a macro objective>>attach:MP-E_65mm_F2.8_1-5x_Instruction_DE.pdf]]
... ... @@ -15,13 +15,13 @@
15 15  * [[attach:READ_ME_GOTTHARD_detector.pdf]]: READ_ME_GOTTHARD_detector.pdf (Server information is outdated, see below)
16 16  * some investigation related to read out noise for different exposure times [[attach:GOTTHARD noise evaluation and exposure time dependence (002).pdf]]
17 17  
18 -\\
19 19  
14 +
20 20  Ethernet and trigger  connections:
21 21  
22 22  [[image:attach:20230922_161707_resized.jpg||thumbnail="true" height="250"]]
23 23  
24 -(% style="list-style-type: square;" %)
19 +(% style="list-style-type:square" %)
25 25  * trigger at port 1
26 26  * gbit port  <~-~-->  Server PC (hasfl2det01 at FLASH2, no server currently at FLASH1)
27 27  * base-T     <~-~-->  Office net
... ... @@ -30,34 +30,30 @@
30 30  
31 31  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"
32 32  
33 -\\
34 34  
35 35  * Main Gotthard panel for users :
36 36  
37 37  [[image:attach:Clipboard05.gif||height="400"]]
38 -\\
32 +
39 39  
40 -\\
41 41  
42 42  * Exp2 DAQ RC gui for recording Gotthard data. EXPERIMENT_GOTTHARD has to be included
43 43  
44 44  [[image:attach:Clipboard01.gif||height="400"]]
45 45  
46 -\\
47 47  
48 -\\
49 49  
50 50  == Operation hints (June 2023): ==
51 51  
52 -(% style="list-style-type: square;" %)
43 +(% style="list-style-type:square" %)
53 53  * **Where is the GOTTHARD GUI:** FLASH2 - Panel: Infrastructure tab → Miscellaneous tab → FLASH2 GOTTHARD ctrl button
54 54  * **Never change a running system:** Do not change parameters while the Detector is running/taking data, The detector will crash.
55 55  * Furthermore the module will crash if recieving to much light (e.g. illuminating with flash light during data dating.
56 56  * **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)
57 57  
58 -(% style="list-style-type: square;" %)
49 +(% style="list-style-type:square" %)
59 59  * **Robooting the GOTTHARD** (if it has crashed): 
60 -(% style="list-style-type: square;" %)
51 +(% style="list-style-type:square" %)
61 61  ** 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
62 62  ** hard reset: power down the GOTTHARD, wait some seconds, Repower the module, wait for reconnection to server/GUI
63 63  * **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
... ... @@ -66,11 +66,11 @@
66 66  
67 67  Using burst mode (standard operation as of June 2023)
68 68  
69 -(% style="list-style-type: square;" %)
60 +(% style="list-style-type:square" %)
70 70  * 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
71 71  * Exposure range is 2**00ns <  Exposure < ~~1/3 * Frame periode**
72 -* The periode is:** 9968ns for 100kHz, 4984 for 200kHz, 1993 for 500kHz**
73 -* The number of** frames must be lower than 125, for stable operation 120**
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**
74 74  * Number of Shots: Number of trigger events before self stopping, select large number for permanent operation
75 75  
76 76  == Modules and their exchange ==
... ... @@ -77,7 +77,7 @@
77 77  
78 78  Two (Three) modules available (physically at FLASH):
79 79  
80 -(% class="wrapped relative-table" style="width: 64.2451%;" %)
71 +(% class="relative-table wrapped" style="width:64.2451%" %)
81 81  |=(((
82 82  hostname
83 83  )))|=(((
... ... @@ -135,24 +135,22 @@
135 135  )))|(((
136 136  ?
137 137  )))|(% colspan="1" %)(((
138 -\\
129 +
139 139  )))|(((
140 140  bchip_mpc1922Receiver_petra.config
141 141  )))|(% colspan="1" %)(((
142 -\\
133 +
143 143  )))
144 144  
145 -\\
146 146  
137 +
147 147  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/**
148 148  
149 -\\
150 150  
151 151  == GOTTHARD Server ==
152 152  
153 -The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**
143 +The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**
154 154  
155 -\\
156 156  
157 157  == Main Parameters and limits ==
158 158  
... ... @@ -176,7 +176,7 @@
176 176  )))|(((
177 177  ~~2/3 of period time
178 178  )))|(% colspan="1" %)(((
179 -\\
168 +
180 180  )))
181 181  |(((
182 182  Min. period time
... ... @@ -183,7 +183,7 @@
183 183  )))|(((
184 184  ca. 930 ns
185 185  )))|(% colspan="1" %)(((
186 -\\
175 +
187 187  )))
188 188  |(((
189 189  Max repetition frequ.
... ... @@ -193,21 +193,21 @@
193 193  833 kHz (software limited)
194 194  )))
195 195  
196 -\\
197 197  
186 +
198 198  == Soft reset a GOTTHARD Module ==
199 199  
200 -(% style="list-style-type: square;" %)
189 +(% style="list-style-type:square" %)
201 201  * Open console on Linux PC (connected to DESY net)
202 202  * write "telnet cfeld-gotthard02" (or the respective Host name or IP of the module)
203 -(% style="list-style-type: square;" %)
192 +(% style="list-style-type:square" %)
204 204  ** you should be connected to the GOTTHARD onboard system → </root:
205 205  * type: "reboot"
206 -(% style="list-style-type: square;" %)
195 +(% style="list-style-type:square" %)
207 207  ** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.
208 208  
209 -\\
210 210  
199 +
211 211  == Triggering the Gotthard with a burst trigger ==
212 212  
213 213  it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger
... ... @@ -232,7 +232,6 @@
232 232  
233 233  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.
234 234  
235 -\\
236 236  
237 237  by:
238 238  
... ... @@ -246,13 +246,11 @@
246 246  
247 247  Switzerland
248 248  
249 -\\
250 250  
251 251  == Using the Spectralyzer together with Gotthard ==
252 252  
253 253  one needs spectralyzer 0.2.4 or newer
254 254  
255 -\\
256 256  
257 257  start spectralyzer on one of our consoles ( works for fl24 and fl26user )  (for installing new version or for other users .. ask Christopher Behrens... )
258 258  
... ... @@ -262,16 +262,12 @@
262 262  (spectralyzer) fl26user@hasfcons1:~~$ spectralyzer
263 263  )))
264 264  
265 -\\
266 266  
267 267  [[image:url:https://ttfinfo.desy.de/Flash2_FL26elog/data/2023/06/2023-02-10T16:03:53-00.jpg||height="250"]]
268 268  
269 269  [[image:attach:image2023-9-15_11-16-3.png||height="400"]]
270 270  
271 -\\
272 272  
273 -\\
274 274  
275 -\\
276 276  
277 -\\
259 +