We are using TestStand 2013 and LabWindows 2013. Using TestStand, we test multiple products, within an environmental chamber, which take hours to run. We have an issue, where occassionally a unit will fail and we lose communication to it. The timeout delays, waiting for a communication response which will never happen, are causing major issues. My soution is to add a StationGlobal, array of integers- one for each unit being tested, in which I set one of the array elements to indicate that the unit being tested should be aborted. Within TestStand, I check the array element, for the unit under test, to determine if it has aborted or to continue with the testing. TestStand calls a LabWindows module which performs the communication write and read. Within Labwindows, I want to set the FileGlobal to abort when there is a communication failure. The inherited code is far worst than this but that was the simplistic explaination and easiest approach to fix the problem. I do not seek help on how to do the testing as I do not have the luxury of rewritting it.
What I need help on is the exact sequence of calls (module names in order) to connect to the TestStand runtime engine, that is calling the LabWindows module, whatever other modules that I need to execute, the call to the function to set the StationGlobal (I think it is shown below), and then release all of the handles that I used. Without stopping the other threads that are running the other units under test.
TS_PropertySetValNumber (TSSeqContext, NULL, "StationGlobals.ManualSlotAbort[0]", 0, 1);
Or better yet or in addition to, is there a link to a manual that explains what the calls are and what they do, in detail?
Thank you for your help.