LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

dynamic calls (subpanel)

Hi all,

In my app I open VI-References to submodules. Over these references I run
the VIs (Invoke node) and load them into a subpanel. When I execute the
main VI in the development system all works fine, but when I build an
application the VIs don't run. A property node that shows the execution
state says they are bad.

One submodule that contained only controls, but no code worked. I think, the
VIs are bad because, the subVIs cannot be found (vi.lib, llbs, ...).

Has anyone an idea?

Thanks,
Marko
0 Kudos
Message 1 of 4
(3,148 Views)
Hi,

If you include the sub vi's in the executable, make sure the panels are not
removed. They are removed by default, unless the vi has locals, property
nodes or a panel that opens when run. Set remove panel to no in the third
tab of the application builder.

Also make sure the paths are correct. Only way to find out is to debug the
executable (a.go. by include popups with error messages, or a status
indicator).

Regards,

Wiebe.


"Marko Aschoff" wrote in message
news:c9204k$nhs$1@news.eastlink.de...
> Hi all,
>
> In my app I open VI-References to submodules. Over these references I run
> the VIs (Invoke node) and load them into a subpanel. When I execute the
> main VI in the development system all works fine, but when I build an
> application
the VIs don't run. A property node that shows the execution
> state says they are bad.
>
> One submodule that contained only controls, but no code worked. I think,
the
> VIs are bad because, the subVIs cannot be found (vi.lib, llbs, ...).
>
> Has anyone an idea?
>
> Thanks,
> Marko
0 Kudos
Message 2 of 4
(3,148 Views)
Hi,

following I want to add:

If I add the dynamically called SubVI to the build options it works, but at
build time I do not know, whick SubVIs (Modules) will be loaded, some
Modules are also to be build in the future.

Thanks,
Marko
0 Kudos
Message 3 of 4
(3,148 Views)
Marko,

It's generally a good idea to add the SubVIs you want to use as dynamic VIs, keep in mind that just because you add it as a dynamic VI doesn't mean you have to use it. Alternately, you could be sure to add all the vi.lib files and SubVIs which will be called by your dynamic VIs, but this would be tricky if they aren't developed yet. If neither of those would work then you will need to distribute the dynamic VIs along with all of their dependencies(SubVIs you've written and vi.lib files). One way to make sure you have all the dependencies is to save each SubVI as an Application Distribution (llb with all of it's dependencies and vi.lib files included).

Regards,
Ryan K.
0 Kudos
Message 4 of 4
(3,148 Views)