LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

onboard device memory overflow

I was wondering if onboard device memory overflow could be attributed to poor coding style.  I'm currently receiving error -200361 onboard memory device overflow on my usb 6009 DAQ. I did read this link http://digital.ni.com/public.nsf/allkb/611475F9BE62881E86256FDC0062B1BB and was just wondering if it could also be a problem with poor coding style.  I have attached a copy of my code.  I would greatly appreciate if i can get some pointers.
0 Kudos
Message 1 of 2
(2,485 Views)

LabVIEW has parallel processing powers, use these. By wiring up the error wires from channel calculation to channel calculation you force them to be processed one after each other.

Merge the erros and than to the check.

A better approach will beto to the FFT for all channels in one subVI.

Use a different read VI (I don't have daqmx base, but look for someting that outputs an array of waveforms, in daqmx it is called 'Multiple channels->Multiple Samples-> 1D waveforms)

Feed this output (1d array of waveforms) to the FFT power spectrum VI you have, automatically the right instance will be selected and the channels will be processed in one call.

 

The following code you use looks very strange to me.

 

 

What it does is a 'not equal' to two booleans which both are false. So the output will be 'TrueFalse', than you do a case structure which will always be false and do nothing.

Why so hard?

 

Ton

Message Edited by TonP on 10-23-2008 08:31 PM
Message Edited by TonP on 10-23-2008 08:33 PM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 2
(2,473 Views)