Numbers below follow the numbering you have on your questions in the most recent post.
1. One disadvantage is the extra overhead time involved in gettting the task fully configured before running it. Some apps are not particularly senstiive to this overhead though, and it might be a reasonable option for you.
However, a second-level issue is that I *think* I recall some kind of memory-leak issue that comes with creating new tasks frequently. Hang on while I search... Ah yes, here's a related thread.
But as a matter of proportionality, you probably shouldn't need to worry too much about the memory leak unless you're recreating tasks 1000's of times or more. Certain kinds of "best practices" matter more in some situations than others.
2. I'm honestly not 100% sure. I suspect it might just stay at whatever voltage it was already at before the call to DAQmx Start. But maybe it defaults to 0 V? I'm also not around hw I can test with.
3. I don't have extremely thorough low-level knowledge about this. But I feel very confident that with a PXIe device, by the time DAQmx Write returns and before you could do a confirmation with any kind of DAQ AI measurement, the new output voltage *WILL* be set. I'd be less confident if you were using a USB device, but wouldn't be surprised if it were true there as well.
4. For many common devices (including yours), I'm quite sure the last generated voltage remains at the output pin when the task is stopped. I'm "pretty sure" it would also remain after the task is cleared. Exceptions I know of would be the much less common Delta-Sigma output devices which would revert back to 0.0 V output very soon after stopping the task.
-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.
