EMS manual: trigger procedures

called with
FSC
???
Immer {<trigger id> [<repetition time>]}
creates a trigger with id <trigger id>, always running, with the possibility to specify a repetition time.
LAM <LAM mask>
creates a LAM trigger with id 1, the content of the LAM register in the CAMAC controller is ANDed with the <LAM mask>, if the result is not 0, the trigger is set.
Multi-Q-Response {<number of triggers> <N> <A> <F> [<N> <A> <F> ...]}
creates a trigger with the id of the entry, whose CAMAC operation (internally a CAMACread with <N> <A> <F>) sets the Q-signal.
Nie
creates a trigger which never fires.
Q-Response {<N> <A> <F>}
creates a trigger with id 1, which is set if the CAMAC operation (internally a CAMACread) with <N> <A> <F> sets the Q-signal.
Rate {<trigger id> <rate>}
creates a trigger which fires with a specific rate (1/sec).
shm <trigger id>
creates a trigger which fires as long the number of generated trigger is lower than the number written into the shared memory section with the key '815'.
Signaltrigger <number of signal handlers> {<list of variable names to contain signal numbers>}
creates a trigger which listens to a list of signals ???.
zel {<device> <master?> <conversion time> <trigger mode> [<flags> [<fast clear acceptance time> [<control variable for testing>]]]}
creates a trigger using the PCI synchronisation module at <device>; the module can acts as master (<master?>!=0) or slave; the conversion time is set to '(<conversion time>-1) * 100ns'; <trigger mode> may have one of three values:
0: polling
1: interrupt driven
2: selection driven;
the bits in <flags> have the following meaning:
0: TINT: use trigger interrupt, not EOC interrupt
1: TAW: use trigger acceptance window
2: T4LATCH: Trigger 4 is latched
3: RAUX0: AUX_IN0 resets trigger
fast clear acceptance time is '<fast clear acceptance time> * 100ns'; what is the use of <control variable for testing> ???