Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Buliding Exe file

I have many Labview 500 pcs .llb file,totol have 500 Mega, I use Labview Apllication builder6.1 to complier to exe file,It file have 90 Mega,when our customer open the system must spend 5 min. because our system include many picture,How can I improve it.
I use application Building 6.1 have building in slow speed computer function,exe file=125Mega,

Why standard complier file = 90M for slow computer complier=125M.
Please help me
0 Kudos
Message 1 of 4
(3,452 Views)
Cheryl,

Here is a basic picture of how LabVIEW works. If all of your subVIs are called directly from the block diagram, then all subVIs will be loaded into memory when the top level VI is loaded into memory. So, if you have a lot of pictures, all 90+ MB of memory will need to be used. This will probably involve using some virtual memory for currently running programs. I would actually expect this kind of behavior from a system designed this way.
There are many ways to improve it. First, call many of your VIs dynamically using the Call by Reference Node (see the LabVIEW User's Manual, Online help, and shipping examples for a starting point). Calling your VIs dynamically will only load that VI when you are ready to run it. This should speed up your program a goo
d deal. However, if you still have a lot of pictures in those subVIs, then it will still take a little while to load and run.

As for your question on the different file sizes, the slow computer version does not compress the files so they are bigger. We suggest this for slower computers because the slow computer can just run the program and not decompress it first.

Lastly, this type of question should probably be posted in the LabVIEW category and not the Serial Interfaces category. You will get more answers in the LabVIEW category.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 2 of 4
(3,452 Views)
Dear Sir,

Thank you for your suggestion. I did as your advice. The problem is solved.

But unfortunately that there is a new problem happened. The customers will see displaying data, source coding in VI file. There are tables and data at the front page of the diagram. These situations are not our desirous. We do not want the customers realizing our data.


How to comply?


Please help us ASAP.



Cheryl

Email: icm@icm.com.tw
0 Kudos
Message 3 of 4
(3,452 Views)
Cheryl,

If you are saving most of your VIs in an external LLB to be used by your application, then you can use an Application Distribution from the Save with Options menu in the File menu. This will allow you to save the VIs without a block diagram so that no one can see your code. Make sure that you back the VIs up first or you will loose your block digrams as well and you will never be able to change the code of the VI. This sort of process can also be done in the Application builder. In VI Settings, you can remove the block digrams of all of the VIs and this should solve your issue as well.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 4 of 4
(3,452 Views)