How can I run Teststand sequences in Real Time Labview Engine7.0?

[LV2010]

Hello all,
Before I was using Teststand2.0. Now I shifted to TestStand3.0.I wanted to run all my sequences with Labview RealTime Engine7.0.
If I change Adapter in teststand3.0 to Labview RealTime Engine7.0, then i am not able to run sequences.

If somebody know, how to make it, Could you please drop me a message..

Thanks
Sashi

[Kyle_Gupton]

Hi Sashi -

Though you can't run TestStand sequences with LabVIEW Real-Time, TestStand can call test VIs on a LabVIEW Real-Time system.

You make this configuration on a per-step basis on the LabVIEW Specify Module Advanced Settings dialog. You select the "Run VI on Remote Computer" option and enter in the name or IP address of your real-time system. If you don't specify a path to your VI and the VI is not currently loaded in memory on the real-time system, TestStand will download the VI and its hierarchy. You can find more information about this topic in Appendix A, Calling LabVIEW VIs on Remote Systems, in the Using LabVIEW with TestStand manual.

Sincerely,

Kyle Gupton
National Instruments

[LV2010]

Dear Kyle,

Thank you for your message. Actually What I wanted is, with out Labview and TestStand (In a plan Machine), I wanted to run Teststand Sequences. We already developed one Operator Interface as a executable, which will execute sequences.

Could you please tell me, Is it possible to do like that?

Thanks,
Sashi

[LV2010]

Dear Kyle,

Sorry it was not a real time engine, It was Labview Runtime engine..

[Kyle_Gupton]

Hi Sashi -

Ah, got it. Yes, you can run your test VIs using only the LabVIEW Run-Time Engine (7.0 or later). To do this, you will need to make sure that:

1. You configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine to execute VIs.

2. You make sure that all of your VIs are compiled correctly with the same version of LabVIEW as the Run-Time Engine you are using. You will also need to make sure that the entire hierarchies of your VIs are available on the test machine. The easiest way to do both of these things is to use the TestStand Deployment Utility to build an image and/or installer for your test system. It will ensure that all of your VIs are "packaged" correctly for distribution.

You will also need a valid TestStand insta
llation on your test computer. If you are planning on running only from an operator interface, the Base Deployment Engine license will suffice. If you build an installer using the Deployment Utility, you can choose to bundle the TestStand Engine with the installation. Or, you can build a separate installer that includes only the TestStand Engine. These different scenarios are described in Chapter 14, Deploying TestStand Systems, in the TestStand Reference Manual.

I hope this helps....

Kyle Gupton
National Instruments

[LV2010]

Hi Kyle,

Thank you for your response. I am trying to create image with Deployment. But if I am trying to add a folder, I am getting Error ( Operation failed 17500), after getting that Error it is adding that floder.

Could you please tell me why I am getting that Error.

Thanks,

Sashi

[Kyle_Gupton]

Can you tell me exactly what you are doing when you get the error?

Kyle

[Anil Naidu]

Hi Hyle,

Can TestStand call any functions present in any Real-Time System apart from LabVIEW Real-time system like VxWorks..etc

-Anil