ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

release a vit instance name

Solved!
Go to solution

Hi

 

This is my first serious encounter with vit and I'm in doubt already.

I have a functional global that I need for different user interfaces. So I converted that vi to a vit and use the reference to it when needed .

I noticed that whenever I make a new instance of the vit with  "Open VI-reference" a new name is generated by appending a number.

The user interface is open only for a while, will be closed  and maybe opened anew later.

 

Closing the reference of the vit does although not release the number and the next time I need an instance a new higher number is appended.

 

This may be save. Can anybody tell me if the VIT-Clone still idles somewhere around and uses memory or what happens when after hopefully many, many weeks of uninterrupted operation i reach vit 2000000 ?

 

Thanks

7.1 -- 2013
CLA
0 Kudos
Message 1 of 5
(3,283 Views)

There is a property called 'All VIs in Memory'. Use this to check how many instances of the template are still open.

 

Felix

0 Kudos
Message 2 of 5
(3,273 Views)
Solution
Accepted by topic author GabbyG

A better approach would be to use reentrant VIs. I think you will need the 'don't share clones' option.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 3 of 5
(3,270 Views)

Ton,

 

The OP said the VI is a functional global. I think that functional globals cannot be reentrant.

 

Gabi,

 

Can you tell us a bit more about your application?  Post examples if possible.  Someone can probably suggest a way to do what you want.

 

Lynn

0 Kudos
Message 4 of 5
(3,260 Views)

Thank you guys for your inputs.

Since I use the functional global only by reference a reentrant VI with no code share is  perfect.

I don't really need an extra version of the source in this case.

I have another case where I spawn daemons from a reentrant vi and it is bad that I cannot find them with the "All Vis in memory".

Maybe I'll redo that case as well, but then with VIT.

 

Thanks again

 

Gabi

7.1 -- 2013
CLA
0 Kudos
Message 5 of 5
(3,227 Views)