|
The following is intended to give an overview of how timing works in
Mr. Kick. This will explain the interdependencies of data acquisition,
event timing and analog output - and what constrains that implies.
Note: Only internal and external digital triggers are discussed
here! - External analog trig works slightly different…
Any action, i.e. acquisition, trig out (event timing) or analog output
is initiated by an incoming trigger. It may originate from some external
device, e.g. a footswitch (via PFI #1-5), or it may be internal (DIO #7
-> PFI #7).
The incoming trigger is routed to both onboard event timers. They may
be used to delay the action. Each of them will send out a pulse at a specified
delay (may be zero) and with a specified width (duration). Event timer
#1 may be disabled in individual classes - this will suppress the pulse
in that class.
The output pulse from event timer #0 is used to trigger data acquisition.
In this way the acquired sweeps are synchronised to event timing: Time
zero in any sweep is simultaneous with the onset of the event timer #0
pulse. Event timer #0 can not be disabled.
Both analog output channels are trigged by the same signal and will run
in parallel. They can be trigged by event timer #0 (along with data acquisition),
or they can be trigged by event timer #1 (via PFI #6*).
To summarise:
- The output of event timer #0 is locked to time zero in any sweep.
If event timer #0 is delayed, then data acquisition is delayed as well
- and by the same amount.
- Event timer #1 may be set to fire before or after event timer #0 -
or simultaneous with it. Event timer #1 can only fire before #0 if #0
is delayed.
- Event timer #1 may be disabled, #0 cannot.
- Analog output may be trigged by either one of the event timers: The
onset of the analog output may be delayed relative to the chosen event
timer, but cannot precede it.
In principle any TTL compatible signal can be supplied
to the PFI #6, but it has only been tested with event timer #1.
|
