Hello,
I have an issue with running my software from the TestStand Operator Interface. I have a TestStand sequence file that is attached to an executable running in CVI. I have a batch file that I run which opens my code in the TestStand Operator Interface, from where I run "Test UUTs" which launches the CVI executable and then continues with the sequence file. The issue I seem to be having is that when I first open the Operator Interface one sequence call in my sequence file fails in both TestStand and the corresponding step in the CVI executable fails as well. The TestStand sequence fails because there is a value that should get updated from CVI from a 0 to a 1, but for some reason it fails to do this. If I terminate out this execution, but don't close the Operator Interface window and start another execution with absolutely no changes, the sequence doesn't fail and neither does the CVI executable. After the first time, every subsequent time the sequence file is run in the same window, it works perfectly fine. Is there some sort of a setting issue that is causing this type of issue to occur or is it something on CVI side?
Thanks,
Shreya
