Executables stop running

[dan_lectrosonics]

I am using 7.1 on Windows XP controlling a GPIB system. The

problem is that some of the Exe Files using the Run Time Engine run

strangely. I can run a number of units(4-7) and then the test stops

running and will not run any more that day. I can reboot the computer and

the test still will not run. Not only that, but I can not even run the

Source Code from Labveiw. I tried to reinstall Labveiw with no change.

But I can turn the computer off and come back the next day which is 16hrs

later and I can run the test again until it stops running. I am at a loss

and need help. What can you suggest?

Dan Boardman

[ni_n_hp_fan]

Have you tried taking a SPY capture to see where the application is failing in the software? It might not explain why reseting the system and reinstalling LabVIEW don't fix your problem, but simply waiting does, but it might give us some ideas. Do the instruments that you are communicating with get reset at any point in this process, perhaps in the 16hrs between partially successful runs of the software?

If you've never used NI-SPY, check out the following tutorial:
NI-SPY Tutorial

[TongY]

Hi Dan, your descriptions of the problem is not very clear to us.

By saying "will not run anymore", do you mean the code is trapped somewhere inside or the vi just starts and shuts down itself without any code being executed? If the code is trapped somewhere and hanging, you can use highlight execution to find out which function did the code trap in.

I hardly see any difference between reboot and shut down and start of your computer in this case, apparently how many hours it takes to "repair" the code didn't make sense.

When your code stops running, what happens? Do you see any error or warnings? Do you see the data that's being collected very strange? SPY capture is good for us to see what have happened, it would also help if you can give us a step by step description on the issue.