02-01-2006 04:43 PM
02-02-2006 12:50 PM
If you want to continuously output the data that you originally wrote to the buffer, you can set the DAQmx timing vi to continuous samples. When continuous samples is selected the default the regeneration mode is set to 'allow regeneration'. This means that the samples you originally wrote to the buffer will repeat at the output automatically. You will only need to start and stop the task once. When you select this mode you can use the DAQmx Is Task Done vi inside the while loop. This vi will return the status of your task each iteration of the loop. Your vi has been changed to do this. Also, you can tell the driver to only use memory on the 6534 depending on your sample size. You can find an example in LabVIEW that does this. It is called Cont Gen Voltage Wfm-Int Clk-On-Board Regeneration.vi, and it can be found in example finder.
02-02-2006 02:33 PM
02-02-2006 05:09 PM
Dave,
I took another look at your example program and I was able to recreate the
error. I do not believe this is expected behavior and will let our R
& D department know about it. In the mean time, I was able to get
your application to run by making a minor change. If you
expand your while loop to include the DAQmx create task, DAQmx timing, DAQmx
start and the DAQmx clear task then you will no longer get this error. I
have been able to run the application after making these changes for over 600
iterations. By recreating and clearing the task every iteration of the
while loop the error goes away.
Regards,
Jesse O.
Application Engineering
National Instruments
02-02-2006 05:21 PM
02-03-2006 02:30 PM
Dave,
After further testing of that code, we have been able to find another work
around. Inside the while loop where you have the DAQmx Start, if you
place the DAQmx write before the stop inside the loop the error goes away.
Regards,
Jesse O.
Application Engineering
National Instruments
02-03-2006 02:33 PM