Changes for page Trigger Howto
Last modified by sndueste on 2023/07/07 11:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,19 +2,18 @@ 2 2 3 3 {{toc/}} 4 4 5 -= Introduction (user panel) 6 - = 5 += Introduction = 7 7 8 -The MTCA based triggers have a jitter in the few ps range, the delay can be shifted in 1 ns steps (over many ms), one can choose between 10 Hz triggers, frequencies locked to the pulses (e.g. 1MHz) and the actual bunch patterns. A detailed description can be found in [[x2Timer manual>>attach:x2Timer.pdf]] ([[Design Paper>>url:http://ttfinfo2.desy.de/doocs/Timing/CDRv2.2short.pdf||shape="rect"]]).7 +The MTCA based triggers have a jitter in the few ps range, the delay can be shifted in 1 ns steps (over many ms), one can choose between 10 Hz triggers, frequencies locked to the pulses (e.g. 1MHz) and the actual bunch patterns. A detailed description can be found in [[x2Timer manual>>attach:x2Timer.pdf]]. 9 9 10 10 in short: the triggers are for low impedance (~~50 OHM terminated ?? ), 5V triggers with an adjustable width. The main control panel for the x2 timer has the control options for the 3 front modules (connected with a RJ45 cable - connecting to a "trigger box" with 2 trigger exits (Lemo) each) and 8 Lemo exits at the back of the crate. in the BL-beamline case these triggers are connected to the BNC (patch panel) ports at the rack. 11 11 12 -The main control can be done with a simplified user panel which can handle the timing in respect to the FEL pulses and not in respect to some (arbitrary) reference time ( Event) 11 +The main control can be done with a simplified user panel which can handle the timing in respect to the FEL pulses and not in respect to some (arbitrary) reference time ( Event)[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/TriggerHowto/Trigger_scheme.gif~|~|alt="Trigger_scheme.gif" width="800"~]~]>>attach:Trigger_scheme.gif]] 13 13 14 - [[image:attach:Trigger_scheme.gif]]13 + 15 15 \\ 16 16 17 -= Different trigger events (starting points) =16 += different trigger events (starting points) = 18 18 19 19 one can configure each channel for an individual trigger event 20 20 ... ... @@ -102,21 +102,19 @@ 102 102 103 103 \\ 104 104 105 - = Set a constant frequency to a channel =104 +\\ 106 106 107 -= 106 += Set a constant frequency to a channel 108 108 [[image:attach:image2019-9-17_13-18-9.png||height="250"]][[image:attach:image2019-9-17_13-18-37.png||height="149"]] = 109 109 110 110 \\ 111 111 111 +\\ 112 + 112 112 The timer card provides the option to generate frequencies that are synched to the FEL reprate on the ps level. One can set 3 Clocks by deviding the reference frequency of 54.2 MHz by n.** Please check (using the Expert overview ) before changing a frequency of it is used for some other channel !!** 113 113 114 114 Since our main FEL frequency is 100.31 MHz the dividers are not straight forward: 115 115 116 -[[image:attach:image2019-9-17_14-22-29.png||width="450" align="right"]] 117 - 118 -\\ 119 - 120 120 (% class="wrapped" %) 121 121 |=((( 122 122 Clock frequency ... ... @@ -149,121 +149,30 @@ 149 149 539 150 150 ))) 151 151 152 -\\ 153 - 154 -== General FLASH frequencies: == 155 - 156 -\\ 157 - 158 -(% class="relative-table wrapped" style="width: 19.422%;" %) 159 -|(% class="highlight-grey" title="Hintergrundfarbe : Grau" data-highlight-colour="grey" %)((( 160 -(% style="color: rgb(0,0,0);" title="" %)**Name 161 -** 162 -)))|(% class="highlight-grey" title="Hintergrundfarbe : Grau" data-highlight-colour="grey" %)((( 163 -(% style="color: rgb(0,0,0);" title="" %)**Frequency 164 -** 165 -)))|(% class="highlight-grey" title="Hintergrundfarbe : Grau" data-highlight-colour="grey" %)((( 166 -(% style="color: rgb(0,0,0);" title="" %)**Divider** 167 -))) 168 -|((( 169 -1.3 GHz 170 -)))|((( 171 -1300.000000 MHz 172 -)))|((( 173 -\\ 174 -))) 175 -|((( 176 -108 MHz 177 -)))|((( 178 -108.333333 MHz 179 -)))|((( 180 -12 181 -))) 182 -|((( 183 -9 MHz 184 -)))|((( 185 -9.02777777 MHz 186 -)))|((( 187 -144 188 -))) 189 -|((( 190 -4.5 MHz 191 -)))|((( 192 -4.513888 MHz 193 -)))|((( 194 -288 195 -))) 196 -|((( 197 -1 MHz 198 -)))|((( 199 -1.003086 MHz 200 -)))|((( 201 -1296 202 -))) 203 - 204 -\\ 205 - 206 206 Once a clock is configured with the right frequency one can choose in the "expert panel" of the according channel the "FPGA clock" in the "input source select" chooser. 207 207 208 -One has to set the delay to values less than the repetition rate ... (so for 1 MHz between 0 and 990 µs) and the trigger width also less than the rep rate ...151 +One has to set the 209 209 210 -This results in a continuous train of pulses with the set trigger width. 211 - 212 -= Creating an (own) burst trigger = 213 - 214 -One can use now a SECOND trigger channel which is set to a regular 10 Hz trigger and gate the clock output to create a burst with defined start point and length, 215 - 216 -For the example we use the FRONT.TRG2 (BL3 Trg5) as gate pulse which defines the length of the burst (set with the trigger width) and the (rough) starting point of the burst. This trigger is only used as gate and the physical trigger output is NOT used. 217 - 218 -The second channel (here FRONT.TRG3 (BL3 Trg6) which is set to the clock frequency defines the reprate (by the FPGA clock setting) , the exact starting point of the first trigger ( by the delay ) and the width of the MHz/kHz triggers (width). 219 - 220 -**To get from the clock to the burst trigger** one has to: 221 - 222 -* set the "2nd source select" to the gate trigger ( here FRONT.TRG2) - this defines a second source to considder for the trigger output. 223 -* and the "output source select" to "AND 2nd Ch." this finally only sends a trigger if on both inputs (clock and gate) we have a high signal. 224 - 225 225 \\ 226 226 227 -[[image:attach:image2019-9-17_14-35-5.png||height="250"]] [[image:attach:image2019-9-17_14-34-38.png||width="400"]] 228 - 229 229 \\ 230 230 231 - \\157 +This results in a continuous train of pulses with the set trigger width 232 232 233 -= Real bunch trigger - get a trigger for each FEL pulse = 234 - 235 235 \\ 236 236 237 -Sometimes it is convenient to get a trigger pulse for each pulse in the FEL. thus if the FEL number of bunches or reprate are changed, the trigger adapts accordingly. 238 - 239 -For this one has to select the source of interest in the expert overview panel (tab: "Bunch pattern") ... well for us this is FLASH1 (FL1D) or FLASH2 (FL2D) 240 - 241 -There are 6 different bunch pattern "channels" one can configure. Typically only 2 are needed ... And in each one there are 6 selectors to choose sources . We only need one - it does not matter in which one is used. 242 - 243 -[[~[~[image:attach:image2019-9-17_14-51-28.png~|~|height="250"~]~]>>attach:image2019-9-17_14-51-28.png]][[image:attach:image2019-9-17_14-47-15.png||thumbnail="true" height="199"]] 244 - 245 245 \\ 246 246 247 -In the expert panel one can now choose the configured "Bunch Pattern" as "Input source select" 163 +* in order to generate a stable frequency one has to set the input source to FPGA clock (and use dividers to get the desired frequency) 164 +* to generate the burst patterns of the FEL one has to choose a trigger event (best 116 for FLASH 2 and 16 for FLASH1) and activate Destination 1 for FLASH1 and Destination 2 for FLASH2 . finally one has to assign the activated Bunch pattern mask to the trigger channel of choice . now the pattern can be shifted and the trigger width can be changed as with the 10 Hz triggers. **IMPORTANT: to move the bunchtrain to the desired starting point the DELAY in the expert panel (see below) has to be used. The Trigger in the user panel (see above) has to be set to 0 !!!** 165 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/TriggerHowto/mtcatrigger2k.png~|~|alt="mtcatrigger2k.png" width="607" height="458"~]~]>>attach:mtcatrigger2k.png]] 248 248 249 - **NOTE: To shift theburst in timeone cannolongeruse thedelay oftheindividual channelBUTthedelay in the "Bunch pattern"tab in the expert overview! This now shifts all bursts ... soyou betterknow what you are doing. typically the burst is already shifted to the actualFELtiming ...Shiftingthe timing shouldbe discussed with the beamlinescientist/ local contact ...**167 +here an example defining the bunch pattern for FLASH1 to mask 1 250 250 251 251 \\ 252 252 253 -[[i mage:attach:image2019-9-17_15-4-47.png||height="250"]][[image:attach:image2019-9-17_14-52-40.png||height="250"]]171 +[[here is a link to the old VME trigger system>>doc:FLASH.VMETrigger]] 254 254 255 255 \\ 256 256 257 257 \\ 258 - 259 -\\ 260 - 261 -\\ 262 - 263 -\\ 264 - 265 -\\ 266 - 267 -\\ 268 - 269 -\\