Alkeria NECTA Series - Trigger; Trigger Ready; Custom Sources

4. Interfacing to the world 64
Note
The strobe signal is not a generalization of the exposure signal described in
4.5.4.1, but actually a different signal with its own use: both signals originate
from the line start event trigger, so they can have different delays with respect
to it. E.g., starting from a trigger event (e.g. crossing of an encoder target po-
sition), NECTA can start an exposure with a given delay (using the trigger man-
ager) and generate the strobe signal with a shorter delay to pre-trigger the
lighting system.
4.5.4.3 Trigger
Trigger signals generated from input ports and/or internal processing modules (encoder and frequency
multiplier) can be routed to output ports. Each trigger signal rises on the corresponding event trigger
signal (acquisition, frame, line, end-of-exposure – see Chapter 6) and remains active for about 5 µs. Like
the exposure signal, trigger outputs allow synchronizing external devices to the camera trigger events.
Example Code 4.13 | Frame start trigger as P2 source
device.PIOPorts[2].Source = OutputSource.FrameStartTrigger;
4.5.4.4 Trigger ready
The trigger manager module also generates a ready signal for each trigger module (acquisition, frame, line,
end-of-exposure – see Chapter 6), indicating that corresponding trigger module are ready to accept a
trigger signal. Trigger ready signals are normally high (active); theyfall on the corresponding trigger event
and rise again when a new trigger can be accepted. When a trigger ready signal is low, all the related
trigger events are ignored.
Example Code 4.14 | Line start trigger ready as P2 source
device.PIOPorts[2].Source = OutputSource.LineStartTriggerReady;
4.5.5 Custom sources
Additional application-specic output sources can be available on some NECTA models with customized
rmware.
Example Code 4.15 | Custom signal 10 as P0 source
device.PIOPorts[0].CustomOutputSource = 10;
device.PIOPorts[0].CustomOutputSourceEnabled = true;