Programmatic Selection of " Run on Remote Computer "

[Prithivi]

Thanks Jervin

It works well. I think your valubale information will be very helpful to most of Teststand developers.

With Regards,

Gopal

[Prithivi]

Hello Friends,

In the sequence editor , i am able to get the TestStand API  RunState.Step.Module.AsLabVIEWModule.RemoteHost = ""

But i am not able to get the same Teststand API properties in Labview with sequence Context. Herewith in attached the image for your ref.

Anyone knows how i can get the above teststand API in LABVIEW.

Thanks

Prithivi

[Jervin Justin]

Hi Prithvi,

Basically what you would have to do is convert the Module ActiveX object reference to the adapter (LabVIEW) specific module class, LabVIEWModule (from the NI TestStand API). You can do this by using the Variant To Data VI in LabVIEW, and wiring in a LabVIEWModule for the type input.

This is described in:
KnowledgeBase 39D9AHO6: How Can I Programmatically Access Information about a Code Module that a Ste...

Also, if you look at the auto-generated code for a LabVIEW module, you will notice the following comment under the Sequence Context input:
Refer to the "Using the TestStand ActiveX API in
Different Programming Languages" topic in the
TestStand ActiveX API Reference online help for
information on how to use this reference to access
TestStand properties and variables from your test VI.

This document will be really useful to you and will help you better understand you to interface between LabVIEW and TestStand and I recommend that you take a look at it. You can find it here:
Product Manuals: Using LabVIEW with TestStand
Specifically look at Appendix C: Using the TestStand ActiveX APIs in LabVIEW

I've also attached a sample VI that shows you how to do this.

[Prithivi]

Thanks a lot Jervin.

But one small change requred in the sample code that you have send. We should not open the LABVIEW Moudle with the automation open. It is giving error. Instead of that we can directly connect the Labview Module ref which works without error.

Herewith i attached the img for your ref.

[Jervin Justin]

Ouch.

Yeah, I use the automation open to quickly get to the ActiveX server selection dialog and then remove it when I'm done, and totally forgot to do that.

Thanks for the catch!

[Jervin Justin]

One last point...

The Using the TestStand ActiveX APIs in LabVIEW reference mentions:

When a method or property returns an ActiveX reference, you must release it using the Automation Close function in LabVIEW.

So you'd want to close the reference to Step.Module after your Variant To Data vi since the vi actually outputs a separate reference.

(See attached screenshot)

Message Edited by Jervin_J on 06-06-2008 12:07 PM

[Prithivi]

Thanks Jervin

Really it is a useful information for all the teststand developers