LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Memory is full

I can't figure out the issue I've got : Memory is full

 

 

error.png

When I click on OK, the following table is blinking :

 
 

NI-error.PNG

 

Anyone knows how to solve this issue?

 

Thanks

 

 

 

0 Kudos
Message 1 of 4
(1,191 Views)

You are taking some integer and dividing it by a double.  What is the result of that division?  You are feeding that into Initialize Array.

 

I think it is pretty likely that math is creating a large enough number that you don't have the memory to create an array of that size.

0 Kudos
Message 2 of 4
(1,182 Views)

@RavensFan wrote:

You are taking some integer and dividing it by a double.  What is the result of that division?  You are feeding that into Initialize Array.

 

I think it is pretty likely that math is creating a large enough number that you don't have the memory to create an array of that size.


To add insult to injury, that Initialize Array is not actually needed.  Since you are initializing it to all 0, and then adding the 0, you can eliminate that Addition inside of the loop as well.  So the loop should just reduce down to the multiplication result autoindexing an array.  I will also do so far as to say that the loop could be replaced with Ramp Pattern.vi (Signal Processing->Signal Generation).


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 4
(1,162 Views)

We typically cannot debug truncated code pictures, but this case is more glaring and I agree with Ravens. Most likely your are dividing by zero, giving you ~2^31 iterations.

 

You really should go back to the LabVIEW tutorials (an even maybe math class!), because most of your code makes no sense.

 

(It is not necessary to wired N when autoindexing. Adding zero to a scalar over and over seems useless. You just get the scalar back. You can avoid the addition if you would initialize the array with your scalar instead of zero. It seems you want to create simple ramps. there are tools for that! Typical ramps have a multiplier and offset but then the addition should be after the multiply. Please check the math. Shouldn't the two FOR loops be more similar?)

 

Please attach your entire VI and make sure that all controls have typical default values so we can run it without having to guess (do you know how to do that?). We can point you to significantly better solution quickly!

0 Kudos
Message 4 of 4
(1,155 Views)