When test cycles run and fail for some reason, sometimes LabVIEW will either crash or get hung and wont close.
Even when exiting or restarting Teststand, LabVIEW does not close properly...or re-open properly, locking any HW resources. Non-technical savvy operators are unsure / do not know what to do.
If the operators were notified with a pop-up informing them of a windows restart is needed to clear LabVIEW PRIOR to even the login prompt, that saves a lot of false start/false fails and headaches.
We have implemented this in the "FrontEndCallbacks.seq" and works great for false-fail runs.
Teststand should have this implemented built-in.
