In addition to a property node that can be queried, it'd also be very helpful to add DAQmx Event support for the status of the trigger.
Edge or threshold based triggers would latch their status until queried via property node. For retriggered tasks, the first property node query returning True would then reset the status back to False. (Analogous to the counter property for querying whether terminal count has been reached.)
Each edge trigger would produce one DAQmx Event per trigger edge. So there'd be only one unless the task is retriggerable.
Level or state based triggers (such as the pause trigger) would not latch the property node value, they would return the instantaneous status at the time of query.
Each level trigger would produce a DAQmx event when transitioning into the "trigger active" state. For a digital pause trigger set to pause while high, the event would occur on every rising edge of the trigger signal.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
I did find that this seems to work. The "AvailSampPerChan" is 0 until a trigger has happened. Then it starts counting up as data is collected. So this just asks if it is greater than 0 indicating a trigger event and then waits for the task to complete. It does assume you will never have a task in excess of 5 min. Nothing I do should ever be that long. You can specify -1 for indefinite, but that seems dangerous.
