Labview 10.0 "There was not enough memory to compile this VI"

[Questionmarker]

Hello,

I am using Labview 10.0,  32 bit (German, please be gentle with my translations) with a Win XP system on Dual-Core with 4 GB RAM. I have wired a quite small program for my measurements; sadly since few days the execution of this program is not possible anymore (I added a new state for my consumer event). None of my VIs should be memory intensive as they basically just ask for a data set or send a text command. Could it really be the case, that my tiny bit of code exceeds my available Memory? Or is this like the bug in Labview 8.2?

Help would be great, I have no clue how to go on and I do not want to rewire everything again from the very beginning while hoping for the best...

I am looking forward to your replies,

?

[GeorgJ]

Hi!

Since you said your VI is very small, maybe you can post it here, so I can have a look and see what the problem is?

[Questionmarker]

Sure! Only some sub-vis will not be readable for you as they are not from labview originally. They mainly trigger another RT-Engine to move Axis around or record data.

"Very small" is to be understood in comparison to the size of some programs made by my colleagues... Anyhow we all cannot figure out why it refuses to work; every state on its own seems to work. And we never encountered this error message before.

I admit it is a bit messy here and there as I am "learning on the job" (as most LabVIEW users I guess ). I included the whole project. As you see, its few 100 KB. MainFrame_MSC.vi should be the most interesting part.

Are there more efficient ways to implement the states (e.g. by sub-VIs)? Is my Computer limiting? Any hint is very velcome.

Regards, ?

[GeorgJ]

I had a look at your code. Unfortunately since some sub-VIs are missing I could not try to run it and see the error. I have two suggestions, though:

1. Try to isolate the problem by gradually reducing your VI (delete parts of the VI till it starts working). When your VI successfully compile, try to add in the functionality again and see when exactly the error occurs again. I know this is some work, but we have to isolate the problem before we can solve it.

2. Install the latest patch for LabVIEW: Currently this is LV 2010 f4: http://joule.ni.com/nidu/cds/view/p/id/2226/lang/en

[Questionmarker]

Dear GeorgJ,

Thank you for your time and your hints!

I started off with the VIs you probably could not see, especially with those that had a dependency to data outside of my project. As they are exactly the same VIs as the ones I imported to this project there were some warnings due to same naming, that I ignored until now. I started by exchanging them with their counterparts from within the project and miracly after the last dependency was solved I was immideately able to compile and run the program.

Funny: Actually the very first of my VIs of this program was one of these VIs I replaced now. Thus I guess this warning cannot be the whole story as it worked in the beginning and refused to do so later...

I consider this as a working solution to my problem, though it would be nice to understand why this causes so much trouble:

1. have a Sub-Vi somewhere

2. create a project

3. copy this Sub-Vi to the LabVIEW user folder to easily access it in the drop-down library

4. use both of them in the project (actually, I even did not use both, but the presence of the stand-alone sub-vi seemed to be enough)

This seems to have caused the crash for me. Well - lets keep our projects tidy from now on...

[GeorgJ · Accepted solution]

Questionmarker,

I am glad to hear that you could solve the problem.

By the LabVIEW user folder do you mean the user.lib Folder?

by the drop-down library do you mean the function-palette?

I was a little confused by these terms. However, I tried to do (from my understanding) what you were describing and it worked without any errors.

Maybe you should consider to repair your LabVIEW installation if the problem continues to exist.

Greetings

[Questionmarker]

Hey GeorgJ,

Yes, I mean the user.lib folder.

Yes I mean the function palette.

It is my bad translation that does not match the english nomenclature, as I have german labview and even not on this PC but downstairs...

I am installing the latest LabVIEW at this moment.

Greetings ?

[Questionmarker]

Hey again,

the error occured again. After phoning the support, they told me another way to get rid of this - a forced new compilation of the VI. To do so press Ctrl + Shift + leftklick the run arrow.

I think this forces labview to write new metacode before compilation and the metacode might become too big / bugged due to numerous iterations of placing and removing VIs.

You can also do a mass compile of your whole project by right klicking it.

I hope this will help someone.