TestStand exceution stops but resumes on mouse click

[Josh_W]

Jaggs1,

I'm not exactly sure what could be causing this trouble, but I worked up a quick example that will at least help us start debugging the issue.

Attached find a sequence file that I wrote that will output a string to a text file at a set interval (right now it's set to output every 10 seconds).  I think if you use this architecture, we might get some information about when bad behavior starts happening.  Is it after a certain amount of time, does it follow a pattern, etc.

Also,  a few other questions (I know you've probably already checked these things, but I want to verify):

1. Do your power settings shut down your harddrive or computer after a certain amount of time?
2. What version of TestStand are you using?
3. What version of Windows are you using?
4. Does this behavior happen with the sequence editor or only with a User Interface?  If UI, which UI are you using?
5. Are you posting UIMessages to your UI?  If so, are they synchronous or asynchronous? What data are you passing?
   

[Jaggs]

Thanks Josh.  I will try  implementing your suggestion. I have a quick question. 

We just upgraded the application from LabView 6.01 to Labview 8.5 and we have not recompiled all the VIs in 8.5.  So when we create a EXE in 8.5, will all the VIs automatically recompiled in EXE or will the version some Vis remain same as 6.01.

I am asking this because in one panel the functionality was not working as intended.  The panel was using some sub VIs which were not saved in 8.5, they were just compiled in 8.5 in run time.  So we saved them in 8.5 and the panel started working fine.  So We were starting to think that if we are creating a EXE with a combination of VIs (some 6.01 and some 8.5), as they are not recompiled in source code, they may still be of same orginal (some 6.01 and some 8.5) version in exe and may be causing some problems.

[Josh_W]

Jaggs,

Did you get any useful results from the test?

When you compile an .exe from LabVIEW, that file will then run with the LabVIEW Runtime Engine (RTE).  Because each version of LabVIEW has its own RTE, to build an executable all dependent VIs must be saved to the same version.  So any VIs that were saved in 6.1 would be automatically updated to 8.5 (and you should see a screen asking you if this is OK).

It is interesting that mass compiling fixed some of your troubles, but it is likely that by doing that you refreshed dependencies to vi.lib and other libraries and that is what alieviated the problem.

Please let me know what the current status is and what else we can help you with.