Changes for page Gotthard related stuff

Last modified by sndueste on 2023/09/25 09:36
From version 19.1
edited by sndueste
on 2023/09/25 09:36
Change comment: There is no comment for this version
To version 1.1
edited by sendels
on 2019/05/08 15:17
Change comment: There is no comment for this version

Summary

Details

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