LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

10803, deallocate memory

Hi

I'm getting this nasty 10803 error:
Warning 10803 occurred at AI Group Config

>Possible reason(s):
>
>NI-DAQ LV: The on-going transfer has been stopped. >This is to prevent regeneration for output >operations, or to reallocate resources for input >operations.

What can I do against it? Maybe deallocate memory from time to time. I have set my buffer to 50000.

Any help would be great.

Yves
0 Kudos
Message 1 of 9
(4,035 Views)
Hello,
I suppose you are doing a buffered analog input operation when the error occurs. Please hava a look at this link:
http://digital.ni.com/public.nsf/websearch/86ADA76BA62BC9A6862562B30079A121?OpenDocument
Hopefully it contains the information you need to get rid of the error.
If you are still experiencing the problems, please give me some more information what you are about to do and on the hardware you are using.

Ingo Schumacher
National Instruments
0 Kudos
Message 2 of 9
(4,035 Views)
Thanks fo your answer, but I guess that I need to explain my case more deeply.
I use nidaq 7.1.
I have suvbi where a buffered continuous data acquisition is done. (ai-config, daq-occurence-config,ai-start and in a loop ai-read).
after some time the user can stop acquisition (ai-clear) and start the measurement. the measurement is done in another subvi. again I have ai-config, daq-occurence-config,ai-start and in a loop ai-read for the acquisition.
after a data analises the user comes back to the the first window, and so on. this "loop" is done 30 times.
on the 20 loop the ai-read gives NaN, depending how big te buffer of the ai-config has been set.
0 Kudos
Message 3 of 9
(4,035 Views)
I am not sure if I really understand what you are trying to do. I guess it would be easier if you could reduce your program to just a few VIs showing the problem and post them in the thread.
This would help me to understand the situation and to give some advices.

Ingo Schumacher
National Instruments
0 Kudos
Message 4 of 9
(4,035 Views)
thanks for your help.
here it is. (LV7)
as you see I clear the daq everytime I run this vi. and I also allocate a buffer of 50000 every time I run this vi. and I'm running this type of vi 60 times or more in one measuring loop.
Yves
0 Kudos
Message 5 of 9
(4,035 Views)
I just made a test and was running the VI 150 times in a row - the error did not occure. Please let me know which OS and which NIDAQ driver you are using.
0 Kudos
Message 6 of 9
(4,035 Views)
OS: Win2k, SP4, 512MB RAM
NIDAQ: 7.2.0f1
DAQCard: 6024E PCMCIA, 200kS/s
MAX: 3.1.0.3021
0 Kudos
Message 7 of 9
(4,035 Views)
I just tested with the same setup (one difference: I used a laptop with XP). I adjusted the timeout value of the wait on occurence vi to 2000 ms. After that i could run the vi 200 times in a row without experiencing the mentioned error. Did you watch the memory in the task manager while the VI runs? Is the amount of used memory increasing?
0 Kudos
Message 8 of 9
(4,035 Views)
Ok for the 2000ms. I will try this. But it is still odd that the timeout occurs with a timeout of 1000ms.
thanks for your help.
yves
0 Kudos
Message 9 of 9
(4,035 Views)