When testing a DUT based on a PC you may have to reboot the DUT PC a number of timers during the test.
Teststand remote sequence execution seems not to handle this in a proper way. Teststand spends a long time to synchronize the two PC’s after reboot of the DUT. I have not been able to find a good method for this. Any ideas?
It would be nice to have better access to the remote sequence execution system running like: Is REngine runnning on DUT PC? Is remote PC available? SetRemoteEngineConnectionTimeout(x sec) e.t.c.
These functions could then be used in the sequence running on the Host PC to eighter report DUT communication errors or wait for DUT to be ready (after reboot or startup).