@codypro wrote:
I am running several different test stands on my manufacturing floor and have run into a very similar issue on some of them. Labview will get hung up on some sort of VI while running a test sequence and the operator ends up force closing the application because they think it froze. When they go to launch the VI that runs our sequence again it won't launch the sequence because it says it is missing the station globals file.
Any idea why this happens?
Luckily, I keep a backup of all my station globals on a network drive but sometimes it won't be the latest one so I'll have to go back and re-add the most recent changes I have done.
Just curious if anyone else has this issue?
If you have long running VIs, the VIs should implement TestStand Termination Monitor. That way if the operator chooses to Terminate the test, then the VI can respond to the signal. Properly terminating will allow the TSEngine to do the needed cleanup and the StationGlobal file will not get corrupted. Also, the VI can also send UIMessages back to User Interface to give feedback to the user. For example you can send a progress bar update or a progress text update. To do these things just make sure you pass the SequenceContext to the VI.
