LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

load VI in subpanel with compilated application

I use subpanel to load VIs into my application.

 

I have an executable created using the LabVIEW Application Builder. But i have some problem to load previous VI.

 

The error message when i run executable is :

 

Error 1003 occurred at Nœud de méthode dans LoadAndRun.vi->RMP_main_interface.vi

 

Possible reason(s):

LabVIEW:  Le VI n'est pas exécutable. Selon toute probabilité, le VI est brisé ou l'un de ses sous-VIs est introuvable. Sélectionnez Fichier>>Ouvrir pour ouvrir le VI, puis vérifiez que vous pouvez l'exécuter.

Chemin du VI : d:\Documents and Settings\T0108265\Bureau\builds\Projet_RMP\RMP_main_interface2\Plugin_RMP_1.vi

 

i join some screenshot to show front panel and diagram.

 

Thank you in advance  

Download All
0 Kudos
Message 1 of 8
(4,020 Views)

Hi,

 

When you're building an application, the path changes from dir-name\vi-name to dir-name\appname\vi-name.

 

If I look at your images, you take the "current VI path" and strip it once.  But it would mean that you would still be in the app part of the path.  If you strip it once more you will get to the dir-part.

 

This is different between running code in development mode and in app runtime mode.

 

That is why I allways use the next when working with paths in LabVIEW

 

Runtime_Development.png

 

Runtime_Development.png

Kind regards,

- Bjorn -

Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's 😉
LabVIEW 5.1 - LabVIEW 2012
Message 2 of 8
(3,997 Views)

Thank you for your answer.

 

I have modified my project, make a new executable  but i always have same problem.

 

I join my project and executable into two zips files.

 

I must make an executable with application builder et install it into another computer as a stand alone application only with run time.

 

I hope you find answer to this problem.

Download All
0 Kudos
Message 3 of 8
(3,974 Views)

John,

 

if it's not answered by the time I get to the office, I will check it then and will supply an answer then 😉

Kind regards,

- Bjorn -

Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's 😉
LabVIEW 5.1 - LabVIEW 2012
0 Kudos
Message 4 of 8
(3,970 Views)

Sorry,

 

I convert project into labview 8.6

 

Have nice day

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

Hi John,

 

Seems to be that the sine pattern VI's from NI_AALBase.lvlib can not be found while running it in the application.

 

If you change those by a different algoritm, e.g. a random number then it works fine.

 

Missing.JPG

Kind regards,

- Bjorn -

Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's 😉
LabVIEW 5.1 - LabVIEW 2012
0 Kudos
Message 6 of 8
(3,941 Views)

Hello johndays,

 

I am doing tests since yesterday and I'm afraid that you won't be able to use the functions which need of the NI_ALLBase.lvlib and NI_AALPro.lvlib protected libraries. Because they are protected by a password, they can't be used in applications. I found many cases where people have the same problem as you and the only way to fix your problem should be to know the password of the librairy or use other functions in the plugin21.vi, plugin22.vi, plugin31.vi and plugin32.vi. Use functions as random number or any else than the ones which use protected librairies.

 

Il you want to know if you use functions that need protected librairies, add your VIs in the project window like this :

 

Project Window.jpg

 

... And check in your dependencies if you see protected library icon :

 

Protected Librairies.jpg

 

I added modifications on your main VI because I think calling the VI ref is useless. Moreover, you had an error in the Abort Method (just before closing the reference). I saw it in debugging mode. I also added modifications on your "LoadAndRun.vi" beacause you weren't testing if the plugins files were already running or not.

 

Please find my VIs as attachment and let me know if they are compatible with you LabVIEW's version.

 

Regards

Jérémy C.
NI France

0 Kudos
Message 7 of 8
(3,927 Views)

IIn my case, the lite LabVIEW run-time engine was installed before the Full version of the LabVIEW run-time engine...

 

I just uninstall everything and reinstall with the Full version of the LabVIEW Run-time engine

 

Hope this helps,

 

Vincent

Vincent Carpentier, Ing./Eng.
CLA, CPI
Neosoft Technologies
www.neosoft.ca
DQMH Trusted Advisor
0 Kudos
Message 8 of 8
(3,830 Views)