How to use enable trigger (aigate) on PCI-6115?

[LSM_Dan]

My PCI-6115 seems to ignore a pause trigger.  I get a start pulse to begin a measurement sequence (my trigger).  There is a UUT provided sample clock that I use for my scan clock.  However, the analog data is only valid when a "data valid" signal from the UUT is high.  I've set up a triggered continuous acquisition task, and tried to use the trigger property node to set the "pause digLvl source" and "pause when" properties.  When I run the vi, I get no errors and it triggers and acquires data continously without regard to the pause trigger level.  The documentation for the PCI-6115 indicates that it supports AIGATE which I believe is the same as pause trigger.  Any suggestions as to what I'm doing wrong?

Thanks in advance!
Dan

[reddog]

Make sure you also set the "Pause TrigType" property to Digital Level.  If you don't, the default value of None will be used and none of the other trigger parameters will be applied.

[LSM_Dan]

Thanks for the reply.  Where do I set this property?  As I drill down through the property list I see More->Pause->Trigger Type->Digital Level, but I can't select this as a property.  All I can do is select "source", or "pause when".   For reference I'm using NI-DAQmx 7.4.0f0 and LabView 7.1.

[Ryan_V[DE]]

Dan,

In order to set up a digital pause trigger, you must set the Pause.TrigType property to Digital Level, the Pause.DigLvlSrc property to the PFI line you want to use, and finally the Pause.DigLvlWhen property to either high or low. What do you mean when you say "I can't select this as a property?" Is it greyed out? Perhaps you should try starting with a shipping example. Please have a look at Cont Acq&Chart Samples-Int Clk-Pause Trigger.vi available in the NI Example Finder (Help->Find Examples). It can be found by searching for "pause." Please let us know if you are not able to get this example up and running.

Good Luck!

[LSM_Dan]

Thanks to reddog and Ryan V.  It is now functioning.  The Pause TrigType property was the key.  During a momentary lapse of consciousness I was interpreting "Trigger Type" as a sub-menu title rather than a selectable entity.  I just needed to be astute enough to select it.

Thanks Again
Dan