03-26-2014 09:19 AM
Thank you for your explanation, i'll have to read it some more, to really understand it. I'm also going to read the link provided.
Regards,
Thijs
04-22-2025 03:59 PM - edited 04-22-2025 04:00 PM
@JÞB wrote:
Better yet, DAQmx tasks really only need to be created once, Preferably during development and not at run time if you can avoid it at all. Presist them to the project (if you deploy to a debug enviornment) or, to MAX if you deploy exe's. This also lets your tasks be available for troublshooting and integration or even to a "Engineering SFP" for the station. I can't remember the last time I delivered a solution the encluded DAQmx Create Task.vi.
Its pretty easy to write yourself a little utility to abort and Unreserve all DAQmx Tasks.
You can run into a lot of trouble trying stuff like this with DAQmx. The most reliable and pain-free way to change settings is to use Clear Task.
There are a lot of problems you WILL encounter trying to control tasks and modify timing resources yourself. The DAQmx API is terrible in my opinion.