cvi runtime engine

[mrbean]

Using TestStand deployment, if I (in the workspace file) point to a sequence file whose module calls are developed in LabWindows/CVI 7.1, does TestStand package the TestStand and CVI engines in the deployment, and place them on the target. OR, do I have to explicitly install the CVI runtime engine on the target.

[RajivG]

Hello MrBean,

TestStand will not install the CVI 7.1 RTE by itself. But the best way to do this would be including the RTE inside the TestStand workspace and then use a custom command (Deployment Utility -> Installer Options -> Custome Commands) to start the CVI RTE installation. So when you install your package on the test system, your RTE will be automatically included.

I hope this helps,
Rajiv Garg

[mrbean]

Could you possibly provide an example of how this is done, or provide more information. Thanks.

[Caroline Bright]

Hello MrBean,

Actually when you create a deployment in TestStand, you can automatically include the runtime engine for both TestStand and CVI. Just make sure that under Installer Options (within the deployment utility) you have the box checked for "Install TestStand Engine". When you run the Installation Wizard for TestStand, it gathers up the contents of the folder /setup and its sub-folders. The runtime installers for LabVIEW and CVI are stored in /Setup/Engine/LVRTE and /Setup/Engine/CVIRTE respectively. So you can just create a normal deployment with an installation of the TestStand engine and it will automatically include the CVI RTE as well.

Thanks,
Caroline
National Instruments

[mrbean]

How do I include the CVI 7.1 RTE inside the TestStand workspace. What file(s) specifically are we talking about.
When I deploy using TestStand, should I see a .exe that I can double click, because I currently am not.

[mrbean]

You said 'you can just create a normal deployment with an installation of the TestStand engine and it will automatically include the CVI RTE as well.'

By 'installation of the TestStand engine' - does this mean that I need to check the 'Engine' box under Engine Options.

What should I see after I deploy. Should I see a TestExec.exe in the deployment directory, or do I go to Start::Programs::NationalInstruments::TestStand::OperatorInterface::LabWindowsCVI

Is this (the latter) the normal way to kick things off, or can an icon be created that the user can click to run the app.

[Caroline Bright]

Hi MrBean,

You do not need to include any files for the runtime engine in the workspace. The deployment will automatically include the runtime engine when under installer options you select to create an installer and to install the TestStand engine. Nothing else needs to be done to include the CVI RTE. As to where the exe files are saved, you can select this by specifying the path in the Installation Destination under the Distributed files tab. Finally, you can create a program in the Start Menu to run your application by selecting to Create a Program Item also under the Distributed Files tab. This will place a start item (by the name you specify) under Start -> Program -> National Instruments -> TestStand -> name of file. Also, I would like to point you to Chapter 14 of the TestStand Reference Manual. This chapter covers how you make a deployment set by step.

Thanks,
Caroline
National Instruments