Quantcast
Channel: All LabVIEW posts
Viewing all articles
Browse latest Browse all 203763

Re: Dynamically Launch VI Runtime vs Development environment

$
0
0

dkfire wrote:

What is the simple single sub-vi that you are adding doing?
Are the dynamically lainched vi still ending up with a while-loop?

Like any other standalone running vi, a dynamically launched vi need to have something in it that is continueing its execution, else it will stop.

 

A vi in a subpanel that has stop, is not that easy to spot when it is a exe. The front panel is still looking like it is running.
That is because you are runing the exe in RunTime Engine.


The VIs I am launching can run stand alone.  I will attach an example of the VIs I am trying to launch.

 

When I talked about adding a subVI, I meant adding any subVIs to my 'test' VI that I was launching.  I will attach examples of this as well.

 

I don't think it is an issue with the VIs I'm launching not operating properly since they run fine in the development environment.

 

Attached VIs:

 

Change_Password.vi

This VI is one of the VI I am attempting to launch for the application.  It will not run properly for you since you do not have the .ini file I read from or the database, but it should give an idea of the type of VIs I am trying to launch.  This VI runs properly stand alone or when launched dynamically from the Development environment.  When launched from the Runtime environment, the FP loads, but does not run.

 

Test.vi

This is a VI I used to test the functionality of my dynamic launching method.  It works in both the Runtime and Development environments.

 

Test2.vi

This is the Test.vi modified slightly so that it includes an subVI (in this case 'Simple Error Handler.vi').  It works when launched from the Development environment but not from the Runtime.  It, like my Change_Password.vi, only loads the FP but does not run.


Viewing all articles
Browse latest Browse all 203763

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>