Changes for page Gotthard related stuff

Last modified by sndueste on 2023/09/25 09:36
From version 9.1
edited by sndueste
on 2023/06/20 12:33
Change comment: There is no comment for this version
To version 5.1
edited by palutke
on 2022/10/07 14:49
Change comment: There is no comment for this version

Summary

Details

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