How can I keep teststand 3.0 from running more than one instance?

[jsharlan]

I would like to be able to detect a running instance of teststand 3.0 and keep another from starting.

[RayFarmer]

Hi,

Is it for the Operator Interface?

There are examples of this on the NI website depending on which language you are using.

I dont think you can stop this if it the SeqEditor.

Regards

Ray Farmer

[Yuri_IL]

What do you mean in ' running instance of teststand 3.0'  and 'to detect'?

If you meant regars windows processes so you can check it from -> Ctrl+Alt+Del ->Task manager

[Tyler T.]

You can restrict the number of instances of the same process by using the command line parameter "/useExisting".  Therefore, if the user attempted to execute the Operator Interface twice, then only one instance of that application would be running.  I have been unable to find information that pertains to limiting the number of processes that use the same ActiveX server (in this case, the TestStand Engine).  You should note, that the TestStand server is a singleton class for every process that is a client.  That means that for an application that instantiates the TestStand engine, if it attempts to instantiate the engine again, it will only be returned a reference to the original instance of the engine.

Is there a particular behavior you are trying to restrict?  Perhaps you could provide a bit more detail on what you are trying to accomplish.

Regards,

Tyler Tigue
Applications Engineer
National Instruments