Teststand as an Executable

[Clint Eastwood]

Where is the best place to look when creating an executable from Teststand 4.1.  I'm using Labview Coded Modules, NI PXI 4071 and switch executive to name a few.  I want to make sure I get ALL the supporting/driver files that I need to put this executable, created from the Develope SW onto the Target Machine.

Checked NI Site and searched on "Creating a executable with Teststand" and most of the returns were" know issues with ..."

 Nothing that told "How".

Thanks,

Clint

[Dennis_Knutson]

I'm not sure what you are asking for. Typically, the only exe is the Operator Interface. You can't make an exe from a .seq file. To get everything on the target pc, you would use the Deployment Utility.

[herosphro]

Clint,

This KnowledgeBase article explains more about the concept behind TestStand deployments and has links to some other great resources on the subject.

[RayFarmer]

Hi,

use the links Josh has highighted to write an application using the TestStand API

http://forums.ni.com/ni/board/message?board.id=330&thread.id=24429

As Dennis points out the only executable is Operator Interface.

You dont turn the sequence files into executable you leave them as either a text file or if you are using TestStand 4.x, then they are in a binary format, but they are just saved in that format.

Regards

Ray Farmer

[Clint Eastwood]

I guess what I'm getting at is creating something such that the Manf Floor can't chg the code.  I remember doing something a long time ago where I created an "exe" file to port to the target machine.  Can't remember if it was LV or TS.  Does the OI "package" everything to put on a Target Machine?

Thanks,

Clint

[RayFarmer]

Hi,

What you can do is create a deployment build using the Deployment Tool.

This will deploy the TestStand engine and OI and therefore you will not have the development tools on the target system and therefore you will not beable to edit your test sequences.

You can also include the tests but its probably better to deploy the test sequences and code modules seperataly. Also set the LabVIEW adaptor to use the LV RTE on the target system rather than the LabVIEW developement system. 

Hope this helps.

Regards

Ray Farmer

[Dennis_Knutson]

The sequence can only be changed by someone with the correct login. If you've been using TestStand, you've had to log in as at least developer to create your sequence.

You must have used LabVIEW and even the exe created in LabVIEW does not include everything. For example, it does not include hardware drivers.

The OI packages the OI. As said already, you have to use the TestStand deployment utility. You have options to install the TestStand runtime license, the OI, the sequences you've created, the support files, etc.

[Clint Eastwood]

Thanks everyone!