Data Acquisition Idea Exchange

About Data Acquisition Idea Exchange

Have an idea for new DAQ hardware or DAQ software features?

  1. Browse by label or search in the Data Acquisition Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

Add Triggered Property to DAQmx

I'd like to know if a DAQmx Task has been triggered.  Perhaps via task property?






Steve K

1 Comment
Trusted Enthusiast

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