Page History
...
- 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 (in particular DumpBSY, as described below)
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)
...
. See table below where DumpSXR destination corresponds to destination bit 4. 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.
...
Overview
Content Tools