LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Executable with missing VI´s

I am trying to build an executable in LV 2011 which is dynamically able to load other VI´s. During development this work´s fine, but after creating the exe one of the vi´s  (Kundensignalgenerator) which should be loaded is not able to execute due to missing VI´s. In the projet which i use to build the executable this missing VI´s could be seen. This is the first time im trying to build an executable so any hint could be usefull. Thanks in advance

Download All
0 Kudos
Message 1 of 9
(3,002 Views)

Have you set these VIs to be always included within your build specification?

0 Kudos
Message 2 of 9
(2,997 Views)

Yes i did. But even if i do not hte behaviour is allways the same. One loaded Vi is runnung the other is not.

Enclosed is the project which i made out of the three VI´s.

0 Kudos
Message 3 of 9
(2,994 Views)

You didn't enclose the VIs in your zip file. Would it be possible to do so? Without seeing how they are called, it makes it difficult to determine the problem. My guess is the build is not actually putting the VI where the code is looking for it. Also, do you know how to make a debuggable executable? This may be helpful for this situation.

0 Kudos
Message 4 of 9
(2,991 Views)

The Vi´s where included in my question but is it all again in the ZIP file. Thanks.

0 Kudos
Message 5 of 9
(2,987 Views)

You should be using relative paths. Right now your paths are hardcoded in. Try building your paths based off the "application directory" which is an available primative in LabVIEW.

0 Kudos
Message 6 of 9
(2,980 Views)

Sorry Greg,

 

i did not see the second part of your question. Unfortunattely i have no idea how to build a debuggable executable? This is is my first time with the application builder. Thanks.

0 Kudos
Message 7 of 9
(2,979 Views)

I understand what you mean, but what i don´t understand is, why one VI works and the other does not.

0 Kudos
Message 8 of 9
(2,978 Views)

Can we revisit this issue?  I am having a similar problem.  I have a project that uses 18 different VIs.  Everything works fine inside Labview, but as soon as I try to build the project, the executable can't find a bunch of SubVis.  It works if I put every VI in the "start up VIs" in the source file tab, but this loads every VI up when I run the program.  If I put the subVI's in the "always included" section, all the run arrows break again (from missing subVIs).

 

Was a solution ever established for this problem?

 

Thanks.

0 Kudos
Message 9 of 9
(2,919 Views)