How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

[hp7550]

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

[Matt Pickard]

hp7550,

I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.

To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.

Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.


To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.

For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).

To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.

I hope that helps.

Best Regards,

Matt P.
Applications Engineer
National Instruments

[hp7550]

The link has problem to download the file. Would you check it out?

Is that right to install the CVI runtime engine on each test system that I deploy the TestStand engine?

When I create distribution kit, do I include the operator interface and testexec.exe in the build?

[Matt Pickard]

hp7550,

You are right. It doesn't work. I reported it. You can also grab it from our FTP site at:

ftp://ftp.ni.com/support/labwindows/cvi/runtime/7.0/win32/

If for some reason that doesn't work, like you hinted in your third question, you can create a distribution kit for your operator interface (assuming it was written in CVI), which will get the CVI run-time engine on your target machine. By the way, the operator interface should be called testexec.exe; so the operator interface and testexec.exe are the same thing.

Yes, if your TestStand sequence calls CVI code (DLLs, EXE), you will need to install the CVI run-time engine on every machine that your TestStand sequence runs on.

To answer your third question, as I already mentioned,
you can distribute your operator interface using a CVI distribution kit. You can also deploy it with the TestStand deployment utility. Just include the testexe.exe file in your TestStand workspace.

Best Regards,

Matt P.
Applications Engineer
National Instruments

[hp7550]

How do I distribute the custom data type and station global var defined in ".ini" files at TestStand3.0>cfg folder?

[Matt Pickard]

hp7550,

You can copy the ini files over manually, or you can add them to the workspace and let the deployment utility deploy them for you.

Matt P.
Applications Engineer
National Instruments