Page History

...

The EventCodes tab is where you can select to record the arrival of various eventcodes and choose the eventcode from which the trigger pulses will be generated.  The Sequencer Codes section is now depreacted and cannot be selected anymore.  An eventcode can be designated as Readout, Command, Control(Transient), and Control(Latch).  An eventcode designated as Readout will generate the trigger pulses on each occurrence.  There should be only one eventcode designated as such.  An eventcode designated as Command will generate a software event which can be used for software command generated readout (like for a Princeton camera).  That software generated event will collected along with the other detectors on the next occurrence of a Readout event.  An eventcode designated as Control(Transient) will be recorded in the datastream for each occurrence with the specified delay and duration (in units of readout occurrences).  This allows a record to track the occurrence of some event triggered from that eventcode elsewhere, like the pump laser for instance. It is also possible to ass add a list of event codes to record in the <hutch>.cnf file, removing the need to set commonly used event codes in the EVR config if they are needed for recording only. An eventcode designated as Control(Latch) will be recorded in the datastream on every readout event following its occurrence until the complementary Control(Latch) code is received.  For example, a pulse picker state can be recorded by the occurrence of the commands responsible for its "Open" and "Close" operation.  For many experiments, only the Readout eventcode needs to be designated.

...

Recovering from errors:

LCLS-1 DAQ Tier-1 Troubleshooting - first level