03-31-2009 04:41 PM
04-01-2009 10:15 AM
04-01-2009 10:57 AM
Let me explain in more detail. I have a mostly working sequence, and added a "Run VI Asynchronously" step. This launches the VI in a new thread, while the rest of the sequence continues running as before. But now if I pause to look at an error (I'm still debugging the test sequence), the restart button will not light up and I can't continue. This should not be the case, since the thread I've stopped is the one I want to continue, not the new thread. This also doesn't happen on my co-workers test set when he does the same thing, i.e. run a new thread.
More background info, in case this helps, the Asynchronous VI is running on the same PC, but calls a vi on a remote PC. Would it matter if I changed it to an Step that called the VI remotely in a new thread? Logically this is the same thing, but maybe it executes a little differently? Thanks for your help.
04-03-2009 03:14 PM