LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamically loaded VI's and Application Builder

Hi,
Is there a clever way to get around the need to specify the VI's that are to be dynamically loaded when using the Application Builder. In the development environment I routinely add support for new GPIB/serial/USB/enthernet devices to my code by reading a configuration file that associates a device name with a set of VI's. The set of VI's are then dynamically loaded and are ready to use whenever the new device name is specified. This scheme does not work in the standalone application because all of the dynamically loaded VI's need to be specified at build time. It is fairly serious problem to have to go back and create a new executable on the development machine every time a new device is encountered. I work a
t a scientific user facility and users frequently bring their own devices (such as temperature controllers and field generators -- usually with VI's!) and I need to get them going as quickly as possible.
0 Kudos
Message 1 of 3
(1,302 Views)
Hi Lee,
as far as I remember, in LV6 you can do that (to run a non-included VI from your builded application - you have to code a "loader VI" using VIServer's methods). Try to contact Labviewguru ... he is the one to ask for details.

Good Luck!

p.s.: this post may be helpful [http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000DC360000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0]
Message 2 of 3
(1,302 Views)
You do not have to specify the dynamically loaded VIs when building an executable. I am attaching an example that shows how to do this. In this example, this.vi calls that1.vi. I then built this.vi into an executable without specifying that1.vi as a dynamically loaded vi. When you run this.exe, you specify the path to that1.vi and click the run arrow. That1.vi will then show its front panel and run. You can also load and run that2.vi.

Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

Message 3 of 3
(1,302 Views)