03-06-2008 01:43 PM
03-07-2008 11:08 AM - edited 03-07-2008 11:09 AM
03-31-2008 02:50 PM - edited 03-31-2008 02:50 PM
03-31-2008 02:50 PM - edited 03-31-2008 02:51 PM
03-31-2008 02:50 PM - edited 03-31-2008 02:55 PM
<< - N - >>,
I ran a few short tests on my machine, and I was able to reproduce the exact behavior that you were experiencing. After speaking with a few of the TestStand developers, we believe that this problem has something to do with the way that LabVIEW launches its executables. Specifically, we believe that the behavior when launching multiple instances of the same executable changed between different versions of the LabVIEW Runtime Engine.
The LabVIEW full-featured operator interfaces with TestStand 4.0 or 4.0.1 are built with LabVIEW 8.2.1 but the LabVIEW full-featured operator interfaces with TestStand 3.5 are built with LabVIEW 7.1.1.
Which version of LabVIEW are you using to build your OIs? It is possible if you just rebuild them in a newer version that it will solve the problem.
While searching, I found this post which describes an ini key that might be useful as well.
04-04-2008 03:36 PM - edited 04-04-2008 03:37 PM
04-07-2008 10:23 AM