06-27-2024 05:06 AM
HI,
I have inserted a vi in my sequence with this option:
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
06-27-2024 06:42 AM
Handling of clones is performed by LabVIEW. TestStand doesn't do anything special here.
So the LabVIEW settings are used
06-27-2024 06:53 AM - edited 06-27-2024 06:54 AM
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?
06-27-2024 07:05 AM
06-27-2024 09:31 AM - edited 06-27-2024 09:32 AM
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
06-27-2024 09:50 AM
Thanks for sharing your opinion...
How does this help Zuc?
06-28-2024 03:30 AM
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