02-27-2013 08:58 AM - edited 02-27-2013 09:06 AM
Fab,
A while back Sean popped the hood on DAQmx and state transitions in this post.
Since seeing that I realized that DAQmx tasks need only be created once....preferably during development. Use Control Task.vi to commit and unreserve in your set-up and cleanup (or as needed) and many of your worries will leave you.
And do upgrade to the latest DAQmx.... Some of those really low level bugs have been hanging in way too long but it seams like NI has been stomping them pretty hard lately.
02-28-2013 10:18 AM
Hi Jeff,
Thanks for giving me some homework, that post looks very interesting and I will study it.
Unfortunately for this application, they do need to create the task at run time, because the hardware used might change. The good news is that this only happens at the beginning when the program is launched and then the task stays the same the rest of the program.
I will look into the code to see when is it that the DAQmx Start is called and look into Sean's post to see what else we can do.
Thanks,
Fab