Changes for page Gotthard related stuff

Last modified by sndueste on 2023/09/25 09:36
From version 10.1
edited by palutke
on 2023/06/24 16:11
Change comment: There is no comment for this version
To version 6.1
edited by palutke
on 2022/10/07 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,8 +11,8 @@
11 11  Ethernet connections:
12 12  
13 13  (% style="list-style-type: square;" %)
14 -* gbit port  <~-~-->  Server PC (hasfl2det01 at FLASH2, no server currently at FLASH1)
15 -* base-T     <~-~-->  Office net
14 +* gbit port <~-~--> Server PC (hasfl2det01 at FLASH2, no server currently at FLASH1)
15 +* base-T <~-~--> Office net
16 16  
17 17  == How to use the Detector and save in DAQ ==
18 18  
... ... @@ -33,33 +33,11 @@
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 -
51 -Using burst mode (standard operation as of June 2023)
52 -
53 -(% style="list-style-type: square;" %)
54 -* 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
55 -* Exposure range is 100ns <  Exposure < ~~1/3 * Frame periode
56 -* The periode is: 9968ns for 100kHz,
57 -
58 58  == Modules and their exchange ==
59 59  
60 60  Two (Three) modules available (physically at FLASH):
61 61  
62 -(% class="wrapped relative-table" style="width: 64.2451%;" %)
40 +(% class="wrapped" %)
63 63  |=(((
64 64  hostname
65 65  )))|=(((
... ... @@ -66,8 +66,6 @@
66 66  Status
67 67  )))|=(((
68 68  Sensor
69 -)))|=(% colspan="1" %)(((
70 -Sensor image
71 71  )))|=(((
72 72  config file
73 73  )))
... ... @@ -74,17 +74,9 @@
74 74  |(((
75 75  cfeld-gotthard02
76 76  )))|(((
77 -**standard**/online/working
53 +standard/online/working
78 78  )))|(((
79 -(% class="content-wrapper" %)
80 -(((
81 81  two small areas of damaged pixels
82 -)))
83 -)))|(% colspan="1" %)(((
84 -(% class="content-wrapper" %)
85 -(((
86 -[[image:attach:cfeld-gotthard02.jpg||height="250"]]
87 -)))
88 88  )))|(((
89 89  bchip_mpc1922Receiver.config_cfeld-gotthard02
90 90  )))
... ... @@ -94,11 +94,6 @@
94 94  working
95 95  )))|(((
96 96  first 1/3 is blind, strong base line offset in the center and a further blind bunch and the end
97 -)))|(% colspan="1" %)(((
98 -(% class="content-wrapper" %)
99 -(((
100 -[[image:attach:hasdslabgh.jpg||height="250"]]
101 -)))
102 102  )))|(((
103 103  bchip_mpc1922Receiver.config
104 104  )))
... ... @@ -108,8 +108,6 @@
108 108  was working (2018), backilluminated! the sensor front is Al-shielded for x-rays
109 109  )))|(((
110 110  ?
111 -)))|(% colspan="1" %)(((
112 -\\
113 113  )))|(((
114 114  bchip_mpc1922Receiver_petra.config
115 115  )))
... ... @@ -116,7 +116,7 @@
116 116  
117 117  \\
118 118  
119 -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/**
80 +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.) The config files are located at the **hasfl2det01: /export/doocs/server/gotthard_server/cfgs/**
120 120  
121 121  \\
122 122  
... ... @@ -123,101 +123,3 @@
123 123  == GOTTHARD Server ==
124 124  
125 125  The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**
126 -
127 -\\
128 -
129 -== Main Parameters and limits ==
130 -
131 -(% class="wrapped" %)
132 -|=(((
133 -Parameter
134 -)))|=(((
135 -Design
136 -)))|=(% colspan="1" %)(((
137 -Real /tested
138 -)))
139 -|(((
140 -Max Frames
141 -)))|(((
142 -125
143 -)))|(% colspan="1" %)(((
144 -120
145 -)))
146 -|(((
147 -Max. exposition time
148 -)))|(((
149 -~~2/3 of period time
150 -)))|(% colspan="1" %)(((
151 -\\
152 -)))
153 -|(((
154 -Min. period time
155 -)))|(((
156 -ca. 930 ns
157 -)))|(% colspan="1" %)(((
158 -\\
159 -)))
160 -|(((
161 -Max repetition frequ.
162 -)))|(((
163 -1 MHz
164 -)))|(% colspan="1" %)(((
165 -833 kHz (software limited)
166 -)))
167 -
168 -\\
169 -
170 -== Soft reset a GOTTHARD Module ==
171 -
172 -(% style="list-style-type: square;" %)
173 -* Open console on Linux PC (connected to DESY net)
174 -* write "telnet cfeld-gotthard02" (or the respective Host name or IP of the module)
175 -(% style="list-style-type: square;" %)
176 -** you should be connected to the GOTTHARD onboard system → </root:
177 -* type: "reboot"
178 -(% style="list-style-type: square;" %)
179 -** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.
180 -
181 -\\
182 -
183 -== Triggering the Gotthard with a burst trigger ==
184 -
185 -it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger
186 -
187 -here are some Info from PIS (June 2023)
188 -
189 -
190 -
191 -{{view-file att--filename="Flash_G1.pdf" height="250"/}}
192 -
193 -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).
194 -
195 -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.
196 -
197 -Regarding the detector setting (assuming it is 200 kHz pulse rate, 100 pulses per train):
198 -
199 -* timing mode: trigger
200 -* number of frames: 1
201 -* 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)
202 -* 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)
203 -* exposure time: > 93 ns and smaller than period
204 -
205 -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.
206 -
207 -\\
208 -
209 -by:
210 -
211 -Dr. Jiaguo Zhang
212 -
213 -Paul Scherrer Institut
214 -
215 -Forschungsstrasse 111
216 -
217 -5232 Villigen PSI
218 -
219 -Switzerland
220 -
221 -\\
222 -
223 -\\