Retriggerable Task Support on PXI-5922?

[nld]

Is there a retriggerable Task support on PXI-5922 like for 633xx X Series DAQ boards?

[Duffy2007]

Hello nld,

have you take a look into this example

niScope EX Multi Record Fetch More Than Available Memory.vi

How internal triggering works:

SMC-Based Digitizers Acquisition Engine State Diagram

http://zone.ni.com/reference/en-XX/help/370592N-01/digitizers/5122_state_model/

In your case you have to use a reference trigger.

In the documentation are three main types of triggers,

1. Start Trigger – Controls when the first record’s pre-trigger samples are acquired

2. Advanced Trigger – Controls when all other records’ pre-trigger samples are acquired

3. Reference trigger – Determines when post trigger samples are acquired

According to the Help documentation for the niSCOPE Configure Trigger VI

“When you initiate an acquisition, the digitizer waits for the start trigger, which is configured through the Start Trigger (Acq. Arm) Source property. The default is immediate. Upon receiving the start trigger, the digitizer begins sampling pretrigger points. After the digitizer finishes sampling pretrigger points, the digitizer waits for a reference (stop) trigger that you specify with a Configure Trigger VI. Upon receiving the reference trigger, the digitizer finishes the acquisition after completing posttrigger sampling.”

From this statement, through the trigger VI, you are configuring the reference trigger and the device is waiting for the reference trigger before it can complete each record’s acquisition.

Some things you have to look into:

The Read function is reading one record at a time because of the Fetch Record Number property. Therefore, it may appear that the digitizer is still acquiring when the trigger signal stops because the Read function is fetching one record at a time and this appears to be slower than the acquisition.

In the niScope Ex Multi Record Fetch More Than Avialable Memory.vi, there is an indicator that shows the number of records acquired this should show you how many triggers are sent to the device.

Hope this helps a little bit.