Unable to include Operator Interface in TestStand deployment

[TheSleeve]

Hello.  I have created a test system using TestStand 3.5.  There is only one sequence file, and this sequence calls several VIs that I have created in LabVIEW 8.0.  I would like to distribute this test system to a target computer, which will then run the default Operator Interface.  No bells and whistles, just plain and simple.  However, I'm running into problems.

First, I created a Workspace file in TestStand.  I then added a Project to it.  In the Project, I added all necessary files for my project (the sequence file as well as all of the custom VIs).  Then I proceeded to follow the TestStand reference manual in order to deploy my system.

For reference, text in italics is the reference guide and text in bold is my comments.
-----------------------------------------------------------------------------------------------

Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.

I did this, and set up my build how I wanted it.

2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.

I did this, and copied my Operator Interfaces\NI folder to Operator Interfaces\User.  This would assure (I hope) that I would have the default operator interfaces included in my project.

3. On the Installer Options tab, enable the Install TestStand Engine
option.

Done.

4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.

Done.  Everything is checked.

In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.

This is where things go wrong.  There is NO Operator Interfaces box in my tree view.  It simply doesn't exist.

-----------------------------------------------------------------------------------------------

I've tried several different builds using different strategies.  I've done builds with the CVI operator interface in the User directory, and I've also tried copying over the files manually.  On the target computer, I've always gotten either an error message (Could not open the TestStand Engine), or else TestStand opens in evaluation mode.  In both cases, my custom VIs and sequence files are nowhere to be seen.  Can anyone shed some light on this?  It's driving me a bit crazy!

Thanks very much,

Brett Gildersleeve

[Antonio Lie]

Brett,

You deploy your operator interface by including it as part of your workspace.
Just add the operator interface executable(TestExec for CVI) as part of your workspace and it would be included in your installer.
You will have the TestStand Engine too.
It seems that the reference manual is out date. I will report this issue to the documentation team.
Hope it helps.

Antonio Lie.

Message Edited by Antonio Lie (NI) on 07-28-2006 02:42 PM

[TheSleeve]

Thank you, Antonio.  I had tried this earlier, but I added the LabVIEW operator interface instead of the CVI interface.

Now, I have added the whole folder "C:\Program Files\National Instruments\TestStand 3.5\OperatorInterfaces\NI\Full-Featured\CVI" to my Workspace.  Is this correct?

I will build and do a test install, and then post a message when I am able to confirm success or failure.

Thanks very much for your help.

Brett Gildersleeve

[Antonio Lie]

Brett,

I think the only two files you would need are TestExec.exe and TestExec.uir.

Check page 14-10 of the Reference manual. Distributing an Operator Interface Scenario.

Regards.

Antonio Lie.

[JonathanN]

Hi Brett,

As a reference guide to deployment, refer to the KnowledgeBase Deploying TestStand Systems.

Hope this helps!

[JonathanN]

Hi Brett,

I forgot to mention that including your operator interface in TestStand 3.5 is a little different. You must always add the operator interface executables to your workspace. Earlier versions of TestStand had the option of adding operator intefaces under the Engine Options section just like you described.  The text inside the manuals you referenced was a bug that was found as the text wasn't updated for TestStand 3.5. Sorry for the confusion.

Best Regards,

[TheSleeve]

Thank you for your help.  With every build I am coming closer and closer to what I want.  I have finally been able to include the sequence files, custom VIs, and Operator Interfaces how I want to.  There is only one problem remaining:

When installing the deployed build on the target system, the user is asked to register their copy of TestStand, or to continue using the evaluation version.

I don't want to install the full-featured development version of TestStand on the target system... just the operator interface and the run-time engine so that my technicians can test equipment.  Therefore, I need them to have the free-of-charge deployable license.  Hmmm, I hope this is making sense...?  Unfortunately, I'm not sure about any of the legal terminology involved.  Can anyone shed some light on the licensing protocol when deploying a simple test system?

[JonathanN]

Hi Brett,

Whenever you deploy your TestStand application to target machines, you will always needs a license.  The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.

LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.

In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.

Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.

TestStand Development System License

The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.

TestStand Debug Deployment Environment License

The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.

The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.

(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)

TestStand Base Deployment Engine License

The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.

The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.

I hope this clears things up.

Best Regards,