Hallo, we control a testsetup in a temperature chamber with teststand 3.0 (batch model). The testsequence runs about 14 hours. So the the operator starts the sequence in in the afternoon and gets the results next morning. Now it happens from time to time ( about once every two months) that the operator starts the sequence in the afternoon and the next morning the operator interface (standard labwindows CVI operator interface), which is the only application running on that Windoes XP computer, has just vanished. No error message, no crashlog, nothing. The only thing which exist, are the report files with zero bytes lenght. We've allrady added some logging code to our teststeps (written in Labwindows/CVI) and we know now that our last teststep does it measurement.
Any ideas what might cause this or how I can debug that ?
Are there logging options in teststand, which log the teststeps also in the model sequence to get an idea in which teststep the sequence fails ?
