06-28-2005 04:03 PM
06-29-2005 11:12 AM
06-29-2005 03:00 PM
06-30-2005 12:11 PM
06-30-2005 02:55 PM
07-01-2005 04:09 PM
Hi Stefano-
I am awaiting information from our R&D representative regarding clock behavior in DAQmx Base to verify if the behavior is device-specific or not. I will update you as soon as I get word back.
As for the LabVIEW crashing, there could be a number of causes that may relate to memory utilization issues or a problem that might even be unrelated to your DAQ operations. Are you able to successfully run any DAQmx Base shipping examples? I would suggest running a few example programs of the same type of operation that your program performs to see if you are able to replicate the crash with those. Do you see any error codes when LabVIEW crashes? If not it will be difficult to troubleshoot the problem, but if the examples run well then I would suggest looking at them as references for structuring your own programs.
Thanks-
07-01-2005 04:10 PM
Hi Stefano-
I am awaiting information from our R&D representative regarding clock behavior in DAQmx Base to verify if the behavior is device-specific or not. I will update you as soon as I get word back.
As for the LabVIEW crashing, there could be a number of causes that may relate to memory utilization issues or a problem that might even be unrelated to your DAQ operations. Are you able to successfully run any DAQmx Base shipping examples? I would suggest running a few example programs of the same type of operation that your program performs to see if you are able to replicate the crash with those. Do you see any error codes when LabVIEW crashes? If not it will be difficult to troubleshoot the problem, but if the examples run well then I would suggest looking at them as references for structuring your own programs.
Thanks-
07-05-2005 10:20 AM
07-06-2005 06:35 PM
Hi Stefano-
It sounds like the error you're running into is a DMA buffer error that results from a hardware overrun on the buffer. This makes sense at higher rates and in situations when you temporarily stop removing data from the buffer during file writes because the hardware DMA buffer is being filled faster than you are reading it out with the DAQmx Read VI.
The best solution to avoid this problem is to read more points from the buffer at a time or to read more frequently. The first option is perhaps more useful in your situation because the file writing portion will delay the subsequent read operation significantly. By reading more points at a time you will ensure that there is space to buffer more incoming data at faster rates.
Please verify which DAQ board you are using- it seems the sampling schemes are in fact very device-specific in DAQmx Base.
Thanks-
07-19-2005 01:38 PM