NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Reentrant VI in a Sequence

HI,

 

I have inserted a vi in my sequence with this option:

 

Zuc_Lab_0-1719482491342.png

 

since that VI will be used more then one time simultaneusly. My question was on how TestStend manages those reentrant vi with the TestUUT entry point. If i run the main sequence 3 times, will TestStand continuosly adding a copy of the vi in the memory or it will flush them at the end of each loop of the main sequence (so every time that a new UUT will go under test)?

 

Thank you for the help and feel free to share any advice on the best practice to use the reentrant options.

 

Best Regards,

Zuc

0 Kudos
Message 1 of 7
(807 Views)

Handling of clones is performed by LabVIEW. TestStand doesn't do anything special here.

So the LabVIEW settings are used

 

0 Kudos
Message 2 of 7
(794 Views)

Thank you for the correction. So if a run a test sequence for ten UUT how will LabView behave? will it load 10 copies of the same VI?

 

 

0 Kudos
Message 3 of 7
(790 Views)
0 Kudos
Message 4 of 7
(785 Views)

Teststand is a massive useless layer

 

Labview calls TS API ActiveX server, that calls Labview that calls TS API. Infinite nested layer and massive headache.

 

Useless nesting process with 90s technology stack.

 

Luckily we have just dismanted every NI product in my multi billion company 

0 Kudos
Message 5 of 7
(769 Views)

Thanks for sharing your opinion...

How does this help Zuc?

0 Kudos
Message 6 of 7
(759 Views)

I don't know! I'm just trying to avoid memory problems if i run my sequence for a long time with reentrant VI... I'm just searching for that answer.

 

Best Regards,

Zuc

0 Kudos
Message 7 of 7
(741 Views)