10-29-2018 03:30 AM - edited 10-29-2018 03:35 AM
Hi Kevin,
I seperated DAQmx Write, start task and clear, each function in VI and i timed only the call DAQmx Write the same problem.
I tried to update the frimware of cDAQ, to connect the cDAQ directly with another PC (Windows 7) and i still have the same issue.
10-29-2018 10:29 AM
You're still measuring the overhead of all the config operations because you're feeding in a Global channel. Use the technique you showed in msg #5 where you explicitly configure and start the task *before* you start measuring execution time.
-Kevin P