LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic VI Istance

Thank you Jean-Pierre,
as usually your answers are exaustives.

Golzio

"Jean-Pierre Drolet" ha scritto nel messaggio
news:3b8bbd67@newsgroups....
> I have done some tests and found a workaroud. Here is a summary:
>
> Include Master.vit as Dynamic VI:
> the VIT is not included in the internal LLB of the executable. Error 7
> generated at run-time
>
> Include Master.vit as Top Level VI:
> generates a building error at "Librarian Get Info.vi" - file not found
>
> Include a Dynamic VI that calls Master.vit:
> It works provided you change Master.vit settings to save the front panel.
> To make Master.vit a subVI of another VI without creating a new instance,
> open Master.vit front panel and drag and drop its icon in the diagram of
t
he
> calling VI. You can also include Master.vit as a Dynamic VI to force it
into
> the internal LLB when you compile with an external LLB
>
> Jean-Pierre Drolet
>
>
0 Kudos
Message 11 of 13
(819 Views)
Hi Golzio
I can't really add anything to the answers you have already other than to add that I had already come up against this problem tonight & arrived at the same conclusion - that you need a seperate .llb containing the *.vit files with your application. If I find a better solution I will post an answer - it's a shame really as the concept as outlined in the latest LTR was a really neat solution to our problem.
Lets hope someone from NI reads this stuff!!
Regards

Tim Overfield
0 Kudos
Message 12 of 13
(819 Views)
I have explained a workaround in a previous post; maybe I was not clear enough of how to include a VIT in an executable.

1. Put your templates VIT on the diagram of a dummy caller VI. To avoid to create a new instance of the VIT on the diagram, drag the icon of the VIT and drop it on the caller diagram. A blue "T" should appear on the VIT icon to indicate that it is a template.

2. Include this dummy VI as a Dynamic VI in the build settings

3. Change the VIT settings to include their front panels.

4. If you build a single EXE, the VITs are now saved into the EXE. If you build with an external LLB, include the VITs as Dynamic VIs to force them to be saved in the EXE.

The bug is that when you include VIT as a Dynamic VI without a caller
, the VIT is not saved in the EXE internal LLB.

Jean-Pierre Drolet


LabVIEW, C'est LabVIEW

0 Kudos
Message 13 of 13
(819 Views)