12-21-2005 01:28 AM
12-21-2005 02:28 AM
12-21-2005 02:33 AM
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).
12-21-2005
03:45 AM
- last edited on
11-25-2025
12:14 PM
by
Content Cleaner
Hi Yves,
there is a link about managing large datasets in LV, maybe it can help.
https://forums.ni.com/t5/Example-Code/Managing-Large-Data-Sets-in-LabVIEW/ta-p/4100668
Regards ThomasD
12-21-2005 05:33 AM
12-21-2005
05:59 AM
- last edited on
11-25-2025
12:14 PM
by
Content Cleaner
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.
12-21-2005 06:48 AM
12-23-2005 12:35 AM