12-05-2022 07:32 AM
Our test engineers often debug by opening a VI's front panel from a sequence during edit time, then running that sequence and inspecting the VI's input and output parameters afterwards.
At least that's what they often did in TestStand 2016.
In TestStand 2020, after the sequence completes, the VI front panel automatically closes.
(Running in LabVIEW Development System with a non-reentrant VI)
After reopening the front panel, the values are still there (so the VIs do not get completely unloaded), but reopening gets rather annoying when you have a setup of multiple VIs you want to compare.
In TestStand 2016 the VI front panels stayed open during and after execution.
Did this behavior change or did we accidentally change a configuration for TestStand 2020?
Is there a way to change this behavior?
Thanks.
Stefan
09-14-2023 12:57 PM
I am experiencing the same issue and would like to know how to prevent an asynchronously called .vi from closing when stopping it from running.
09-14-2023 06:06 PM
Hi,
If you are referring to this issue 1498966 from TestStand 2020 Bug Fixes - NI, it has been fixed in TestStand 2020 f1 patch.
Regards,
Anand Jain
NI
10-06-2023 03:49 AM
Now I have installed "TestStand 2020 f1".
The problem still exists:
After the TestStand execution stops (=background is getting grey) all the LabVIEW Frontpanel window were closed by TestStand.
10-06-2023 04:05 AM
Detail: TestStand 2020 f1 closes only that Vis which were called during the execution.
Not called Vis will stay open.
10-06-2023 06:49 AM - edited 10-06-2023 06:49 AM
Here is a Workaround 🙂
Part 1: Put this into 'Cleanup' of all your sequences and add a precondition:
RunState.CallStackDepth == 0
Part 2: SubVI will do the "re-open".
The small delay is needed to wait until TestStand has finished closing windows.
Thank You for Kudos.