Controlling the trigger blocking feature involves three functions in the ADQAPI: SetupTimeStamp-
Sync(), ArmTimeStampSync() and DisarmTimeStampSync(). The timestamp reset feature can be con-
figured in two modes:
First event
Once the timestamp reset engine is armed, the first event observed on the timestamp reset source
will reset the timestamp.
Every event
Once the timestamp reset engine is armed, all subsequent events observed on the timestamp
reset source will reset the timestamp.
4.4.2 Trigger Blocking
The trigger blocking function generates a blocking window that may be used together with the timestamp
reset feature to ensure that the digitizer does not create records with unsynchronized timestamps.
The trigger blocking engine listens for external events on either the external trigger connector (TRIG)
or the synchronization connector (SYNC). The selected source will be referred to as the trigger blocking
source throughout this section. The trigger blocking engine uses the global edge specification set by
calling SetTriggerEdge().
Controlling the trigger blocking feature involves three functions in the ADQAPI: SetupTriggerBlock-
ing(), ArmTriggerBlocking() and DisarmTriggerBlocking(). The blocking function can be config-
ured in four modes:
Once
Once the trigger blocking engine is armed, this mode inhibits the creation of records until the first
event on the trigger blocking source has been observed. At this point, the blocking is disengaged
and all subsequent triggers are allowed to propagate.
Window
Once the trigger blocking engine is armed, this mode inhibits the creation of records until an event
on the trigger blocking source has been observed. Following an event, the blocking is disengaged
for a fixed duration (the window length) and triggers are allowed to propagate. Any additional
events on the trigger blocking source that occurs during the window are ignored, i.e. they do not
reset the window.
Gate
Once the trigger blocking engine is armed, this mode inhibits the creation of records until an event
on the trigger blocking source has been observed. Following an event, the blocking is disengaged
for as long as the trigger blocking source signal remains 'logic high' or 'logic low' (depending on
the source's edge specification) and is reengaged once an event of the opposite type is detected.
Inverse window
Once the trigger blocking engine is armed, this mode allows triggers to propagate until an event
on the trigger blocking source has been observed. Following an event, the blocking is engaged
ADQ14-FWPD – User Guide
www.teledyne-spdevices.com
Classification
Revision
Public
PA1
Document ID
Print date
18-2074
2018-04-06
Mode index 0
Mode index 1
Mode index 0
Mode index 1
Mode index 2
Mode index 3
Page 13 of 28
Need help?
Do you have a question about the ADQ14-FWPD and is the answer not in the manual?