Deploying TestStand app on TestStand-less target

[mrbean]

I want to deploy a TestStand app on a target that doesn't have TestStand installed on it.  I ran into this before on a different target, and the only way I could get around the ActiveX error messages I saw was to install TestStand on the target.  Now we're going to send this deployment out, and I remembered my previous troubles.  Will I again have to install TestStand at the target.  If not, what specific files should I look for in my LabWindows/CVI and TestStand projects that will tell me that I have what I need.

[daijoubu]

As I understand it, TestStand "apps" require the TestStand engine at a minimum.  You can create a distribution kit from within TestStand that just distributes the engine.  The sequence files have a separate installer.  This is how I've done my test systems in the past.  You will need to provide a serial number and activate the engine when you deploy it.  Otherwise it will run in demo mode only.

If you want to make it easy for the people installing your app, you could build a distribution kit in TestStand that distributes the engine along with your application.  I don't think it's easy to do this in CVI.

[Tyler T.]

Yes, you will definitely need to distribute the TestStand engine in order to run TestStand sequences.  You will also probably need the CVI Run Time engine if you are deploying CVI components.  The Deployment Utility provides the option of including the TestStand engine in a distribution.  If you are using TestStand 3.5, you can easily include the CVI Run Time engine in your deployment installer as well.

Note that once the TestStand engine is installed, the engine must be activated either with a base license, debug license, or development license.  The base license only allows for the execution of sequences, and is usually used for TestStand application deployments.

Let me know if you have any questions.

Regards,

Tyler Tigue
NI

[mrbean]

By "Note that once the TestStand engine is installed, the engine must be activated either with a base license, debug license, or development license", do you mean I'd have to buy one of these licenses and when it asks for the activation code, I enter the serial number, etc.  I've noticed that activation popup comes up for just TestStand.  My TestStand app is using CVI, shouldn't I see a CVI activation popup also?

[daijoubu]

The CVI run-time engine can be freely distributed.

[mrbean]

Can the LabVIEW runtime engine (it's called that) also be freely distributed?  The app I have will be expanded soon to call not only CVI modules, but LabVIEW also.

[daijoubu]

I think it's best that you look at section 12 of the NI Software License Agreement.  If you're planning to sell you're software, you may want to get your lawyer to spend a few minutes reading it as well. 

IANAL, but it looks like the LabVIEW run-time engine can be freely distributed.  I also noticed that you are required to have a copyright notice in the about box and the written documentation.