...

• 288 bits of "event codes":
  • some have well-defined meanings (in progress)
  • 16 highest bits are hutch specific for sequences (272-287)
  • DAQ readout groups are "extra bits" included at end of timing frame
• timing frames have "destinations": e.g. bykiks, and bykikh both go to "bsy" dump
• unlike LCLS1 we will not be using event-codes to understand when bykiks has fired: use destinations instead
• To trigger on "every shot" with beam (the equivalent of LCLS1's eventcode 140) use "Mode=FixedRate:1MHz, Destination=Include:DumpSXR" (without the "destination" field I believe you will just get a pure 1MHz trigger).  Another method is to use an event-code generated by ACR (see Control Sequence Bit for current examples).  It is also import to set the "select" field to "Inclusive".

Trigger Types

Timing receivers share a common logic module for generating triggers.  They consist of the logical AND of two components, a rate component and a beam destination component.

• Rate component.
  • sequences / event code
  • ac-line rate (1,5,10,30Hz...) + timeslot mask
  • fixed-rate patterns (1H, 10H, 100H, 1kH, 10kH, 71kH, 1MH)
• Beam destination component
  • "Dont Care" : beam or no beam, we don't care
  • "Inclusive" : specify a set/mask of destinations to which the beam must be destined; see the table below
  • "Exclusive" : specify a set/mask of destinations to which the beam must not be destined; see the table below.

DumpBSY corresponds to dropped-shots.

...