05-29-2009 01:12 PM
Solved! Go to Solution.
06-01-2009 02:51 PM
Hi talltubatom,
The behavior that you're seeing is due to the nature of the DAQmx driver. This KB explains that behavior for DAQmx 7.4 and higher. If you are looking to reduce CPU usage, you could use"wait" mode, otherwise, if you use "yield" you will still see high CPU usage, but if other programs need to execute, they will be given the necessary CPU. Let me know if you have other questions about that, have a great day!
06-02-2009 08:52 AM
is wait a function of the reader?
I don't understand how this only explains high speed aquisition. Because the sleep timer is increased at low speeds?
06-03-2009 04:43 PM
The KB I linked in my last post states: "However, it should be noted that if data is arriving or space is being made available fast enough such that the NI-DAQmx process does not have to wait for data, then the process will never be put to sleep and no reduction of CPU usage will occur." That statement explains the default sleep behavior- let me know if you have more questions. Take care!