LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

limitation of program size

Hi,
I always get this really nasty error about the "load.cpp", line 6345 failure when I try to save my vi.
I found out that this error is relayed to my big main vi. it's size is about 31mb. when I reduce the program (below 30mb) the problem disappear. but this can't be the solution 'cause I need to expand my program further. I have also created a lot of subvi but on the point I am I can't create anyother.
Is there another solution? (I'm working with lv7.1.1 and have also tried to save the project on another computer. the same error occured.)
Thanks for all answers.
Yves
0 Kudos
Message 1 of 8
(3,332 Views)
Hi Yves,

how do you get a single vi to a size of more than 30MB? How large is it and how much do you need to scroll around when editing?
- You mentioned you already use subVis, but nevertheless I suggest use even more!
- Do you have big constants on your diagram (or big controls (i.e. arrays, graphs) with large amount of default data in it? Try to load this at runtime from files.


Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 8
(3,322 Views)

Why can't you create additional subVIs?

And why is your VI so big?
I had VIs which were several MBs (including pictures) and even they had a lot of code in them, so it sounds like something with 30 MBs would be almost impossible to handle (unless you have a lot of data saved in constants or as default, in which case, the solution is probably to change that).


___________________
Try to take over the world!
0 Kudos
Message 3 of 8
(3,322 Views)

Hi Yves,

there is a link about managing large datasets in LV, maybe it can help.

http://zone.ni.com/devzone/conceptd.nsf/webmain/6A56C174EABA7BBD86256E58005D9712

 

Regards ThomasD

0 Kudos
Message 4 of 8
(3,314 Views)
Hi GerdW

Thanks for your answer.
- Well my front panel is just 2mb. (a lot of controls and some tab control)
- Yes, of course I need to scroll around. but it doesn't matter because the program needs to be varied quite often. (new parts are added and older loops are deleted again.)
- I have build some subvi's. every subvi that I could build now has some reference and I had been teached that reference uses alot of memory and cpu.

Yves

0 Kudos
Message 5 of 8
(3,303 Views)

I'm not sure whether you properly understand the reasons for using subVIs. The reason is usually to have reusable pieces of code which allow you to save diagram space and to make the modifications easier (you only need to modify in one place). Another reason for having subVIs is sometimes just to clear the diagram space, even if the code is not reused.

Using subVIs does make LV create copies of your data in memory, but usually, there are very few applications in which the memory requirements will be so demanding that you would want to do without subVIs.

There are various ways to deal with performace in LV. To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here and here are a couple you can start with. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf). In the bookshelf you should also find articles about performance in LV.


___________________
Try to take over the world!
0 Kudos
Message 6 of 8
(3,296 Views)
Hello Yves,

probably the way you built those subvi's is the problem. From your description I think you marked an area and used "Edit->create subVi". This way all selected controls/indicators are converted to references in the subvi. Create subvi's without selecting any terminals of controls/indicators to overcome this.
Another problem is "new parts are added and older loops are deleted again". LabView tends to show errors (load.cpp and other) when a vi is very big and you often delete big structures and create new ones.

What kind of controls do you use to get 2MB only of controls? In a rough estimation this should far more than 400 (128 simple numeric controls take ~150kB). No way to reduce the number of controls?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 8
(3,288 Views)
Thanks to all for your precious help.
Actually I solved the problem. I have just downloaded the new LV 8 and THE PROBLEM IS GONE!!! yipiieSmiley HappySmiley Happy. the vi is even smaller (10mb) and the compiled code is 5mb. I guess NI managed to work out there memory ressource concept.

merry christmas, joyeux noël, schöne weihnachten from the beautiful switzerland

yves


0 Kudos
Message 8 of 8
(3,250 Views)