02-15-2008 06:29 AM
02-15-2008 06:09 PM
Hi Jim,
It could simply be that this version of LabVIEW and the DAQ driver were not written to operate on a core duo computer. A way to test this might be opening the Windows Task Manager>> Selecting the Process tab>> right click on LabVIEW >> clicking Set Affinity>> and then removing one of the CPUs. You can then see if the program runs without error.
If you still get errors, I might be able to try and recreate the issue.
Regards, Mallori M.
02-18-2008 07:51 AM
02-19-2008 11:12 PM
Hi lmtis
Did you try the suggestion that Mallori suggested? If so, how did it work?
It sounds to me that you are just running this program in the background while you acquire data with another application. If this is correct, and you are not using the on the fly updating functionality of this VI, then you may want to consider creating another output application that is not system dependent. Have a look at the following example programs that are available on our website.
Chris_K
02-22-2008 12:08 PM
Hi Chris,
As I indicated in my last post, I don't want to limit LabVIEW to running on one CPU because I need to increase data rates. The 6110 card is capable of 5 MS/s, and with 8 channels of data I need all of the processor I can get. Actually I may have solved the problem. I experimented around with the Set DAQ Device Information VI that Vanessa suggested for using DMA. I finally tried setting the "data transfer mode for analog output group 1" to "interrupts", and I have not had the error now for almost 5 days. I have no idea what the default configuration is or what this new setting does to prevent the overrun (I would have assumed that with an 8k buffer and a 220k waveform that it had always been using interrupts). Enlightenment on this would be welcomed if you know the answer, but in the absence of enlightenment I will gladly settle for my problem being solved. Thanks.