Trigger Howto

Version 17.1 by sndueste on 2020/01/21 13:04

Introduction (user panel)

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 (Design Paper).

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.

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) 

Trigger_scheme.gif

Different trigger events (starting points)

one can configure each channel for an individual trigger event

FLASH1

trigger No

function

16

the MCA trigger 3.11 ms before the Flash1 pulses (same as A6 but more stable)

166

A6 event. still possible to use but less precise than 16

162

A2 event as earliest ( 24 ms before the FEL)

224

E0 event of the BL fast shutter ( 19 ms before the FEL)

225

E1 event of the PG fast shutter ( 19 ms before the FEL)

21

Trig16 + first bunch of FLASH1 - this trigger is shifted when FL1 starts later than "700"



FLASH2

trigger No

function

22

Trig116 + first bunch of FLASH2 - this trigger is shifted when FL2 starts at a different start time

181

shifts with the start time of FLASH2 as event 22 but comes 22 ms ! before the FEL

from this trigger as starting point one can shift the timing in 9 ns steps first and finally in 0.9 ns steps for fine adjustment.


Expert panels


image2019-9-17_13-10-56.png    image2019-9-17_13-8-46.png

With the "Expert overview" one gets the overview over all channels available on the timing card and can configure the card. This is useful to look what channels are using clock settings or burst mode settings that one wants to change ... and using the other tabs one can set parameters for clocks and bursts (see below)


For each trigger channel there is in addition an "Expert panel" to set the properties of THIS channel

image2019-9-17_13-14-52.png  image2019-9-17_13-15-38.png



Set a constant frequency to a channel


image2019-9-17_13-18-9.pngimage2019-9-17_13-18-37.png


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 !!

Since our main FEL frequency is 100.31 MHz the dividers are not straight forward:

image2019-9-17_14-22-29.png


Clock frequency

Divider to be set

"1 MHz" (1000.31 kHz)

53

"500 kHz" (501.5 kHz)

107

"250 kHz" (250.8 kHz)

215

"200 kHz" (200.6 kHz)

269

"100 kHz" (100.3 kHz)

539


General FLASH frequencies:


Name

Frequency

Divider

1.3 GHz

1300.000000 MHz


108 MHz

108.333333 MHz

12

9 MHz

9.02777777 MHz

144

4.5 MHz

4.513888 MHz

288

1 MHz

1.003086 MHz

1296


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.

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 ...

This results in a continuous train of pulses with the set trigger width.

Creating an (own) burst trigger

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,

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.

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).

To get from the clock to the burst trigger one has to:

  • set the  "2nd source select" to the gate trigger ( here FRONT.TRG2) - this defines a second source to considder for the trigger output.
  • 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.


image2019-9-17_14-35-5.png                        image2019-9-17_14-34-38.png



Real bunch trigger  - get a trigger for each FEL pulse


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.

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)

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.

image2019-9-17_14-51-28.pngimage2019-9-17_14-47-15.png


In the expert panel one can now choose the configured "Bunch Pattern" as "Input source select"

NOTE: To shift the burst in time one can no longer use the delay of the individual channel BUT the delay in the "Bunch pattern" tab in the expert overview! This now shifts all bursts ... so you better know what you are doing. typically the burst is already shifted to the actual FEL timing ... Shifting the timing should be discussed with the beamline scientist / local contact ...


image2019-9-17_15-4-47.pngimage2019-9-17_14-52-40.png