LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with dynamic call of sub VI in executable in LV 6

I contacted NI Tech Support several months ago with a problem calling a sub
VI dynamically in an executable using LV 6.

I have a very large application built in LV 5 that uses numerous dynamic
calls to control data acquisition and command handlers. When I ported the
application to LV 6, everything worked fine in the development version, but
the dynamic calls did not work when the application was compiled into an
executable. I know all of the path references are correct since the code
works fine in LV 5.

I sent a very simple example of the problem and my results to NI Tech Support.
After several e-mails and phone calls, they acknowledged that it was a bug
and would be forwarded to the dev
elopment team. Well, 6.0.1 is out and I
tried it again and still no luck.

I was wondering if anyone else has run into this problem.

Alternately, I was wondering if anyone else has successfully called sub VIs
dynamically in an executable in LV 6. If so, I would love to find out how
you did it.

_______________________
Michael Fortenberry
G Systems, Inc.
0 Kudos
Message 1 of 4
(2,369 Views)
Ah,
so it is a bug then - I had wondered. I also ran into problems when trying
to dynamically run a large application. In the end I got around it by decreasing
the number of dynamic calls (and upgrading the control computers spec accordingly),
but that wasn't exactly the ideal solution. I was using LV5, and I would
be curious to hear if there is a fix for this in LV6.
Cheers,
Ben

"Michael Fortenberry" wrote:
>>>I contacted NI Tech Support several months ago with a problem calling
a sub>VI dynamically in an executable using LV 6. >>I have a very large
application built in LV 5 that uses numerous dynamic>calls to control data
acquisition and command handlers. When I ported the>application to LV 6,
everything worked fine in the development
version, but>the dynamic calls
did not work when the application was compiled into an>executable. I know
all of the path references are correct since the code>works fine in LV 5.
>>I sent a very simple example of the problem and my results to NI Tech
Support.> After several e-mails and phone calls, they acknowledged that it
was a bug>and would be forwarded to the development team. Well, 6.0.1 is
out and I>tried it again and still no luck. >>I was wondering if anyone
else has run into this problem. >>Alternately, I was wondering if anyone
else has successfully called sub VIs>dynamically in an executable in LV 6.
If so, I would love to find out how>you did it.>>_______________________>Michael
Fortenberry>G Systems, Inc.>
0 Kudos
Message 2 of 4
(2,369 Views)
I also have had that exact problem. Worked fine in v5.1, but not in 6. Has NI tech support got back to you yet?(I notice this was posted a couple of months back now...)
0 Kudos
Message 3 of 4
(2,369 Views)
I have had the same problem, but managed to run the executable by doing the following:

In application builder you go to the "Source files" tab and add your dynamic VI's with the button "Add Dynamic VI..."

Then you have to go to the "VI Settings" tab and change "Remove Panel" from "Yes" to "No" for the dynamic VI's in the list. You can change the settings by clicking on the row for the right VI and then click on "Edit Build Settings...".

Rolf Weibull
Mecel, Sweden
0 Kudos
Message 4 of 4
(2,369 Views)