Classification
Revision
Public
PA6
Document Number
Date
17-1957
2018-06-07
•
ADQUpdaterGUI (Windows only application) is not supported.
Important
ADQ7-FWATD is not supported by LabView, ADCaptureLab or the ADQUpdaterGUI.
3.2
Collecting Data
The FWATD C-example is provided together with the SDK. For Windows it is located in
<Path to installation directory>/C_examples/ADQAPI_FWATD_example
after installing the SDK, and for Linux in the
examples/fwatd_example
directory of the SDK archive. This example illustrates the capabilities of ADQ7-FWATD, and can be used
as-is. However, the example is primarily intended to be used as a guide for creating use case specific
applications.
4
Detailed System Description
This section provides additional details on important system features.
4.1
Trigger Setup
There are four available trigger sources: software-, level-, internal- and external trigger. The trigger
source is selected with
SetTriggerMode()
. Please refer to the ADQAPI reference guide [
3
] for informa-
tion on the argument list.
4.1.1
Software Trigger
The software trigger is issued by calling the API function
SWTrig()
and its main purpose is debugging.
One call to the function will generate exactly one trigger event on the digitizer. Multiple calls to the function
in rapid succession will
not
result in a trigger pattern with a well- defined period due to the non-real-time
behavior of most modern operating systems.
4.1.2
Level Trigger
The level trigger takes a 16-bit ADC code and an edge polarity as inputs and considers the first sample
after threshold has been crossed as the trigger point. To guard against false triggers caused by noise,
a
reset level
has to be specified. This reset level is specified in absolute ADC codes and is used to arm
the level trigger mechanism by mandating that the data visits ADC codes below/above this level before
a new rising/falling trigger event may be generated. The level trigger achieves a resolution equal to the
sample rate.
ADQ7-FWATD User Guide
www.teledyne-spdevices.com
Page 7 of 26
