Calling LabVIEW VI in a sequence

[Tyler T.]

Troy,

There are a couple of different options to distribute a Search Directory for a computer that does not have the Sequence Editor.

(1)  Distribute your TestExec.ini file.  The TestExec.ini file is in the <TestStand>\Cfg directory.  It contains the StationOptions and SearchDirectories for a computer.  You can add the TestExec.ini as a relative path and it should get distributed correctly to your other computer.

(2)  Distribute one of the Full Featured Operator Interfaces found in the <TestStand>\OperatorInterfaces directory.  Each of these OI executables contains a Menu similar to the one you would find in the Sequence Editor.  You can adjust Search Directories from within the OI.  It isn't a bad idea to have one of these OI's on your distributed machine so you can make other adjustments.

(3)  Programmatically set a Search Directory.  You can get the SearchDirectories from within a Sequence by using the RunState.Engine object.

(a)  Insert an ActiveX step to your Sequence with the following settings.

Object:  RunState.Engine

Server:  TestStand API

Class:  Engine (IEngine)

Get Property:  Search Directories

Parameters:  Locals.mySearchDirectories (must be created as an Object Reference in the Locals).

(b)  Insert an ActiveX step after the previous one:

Object:  Locals.mySearchDirectories

Server:  TestStand API

Class:  SearchDirectories

Call Method:  Insert

Parameters:  You can assign all the parameters that are also available in the Search Directories dialog from here.  Check the help on this function for specific details on all the different parameters.

Let me know if you have further questions.

Thanks,

Tyler Tigue

[Troy12]

Thank you Tyler.

I added the search path using the full featured TestExec OI on the target computer. However, it did not help. When I remove the SupportVIs folder from the application VIs folder, the application does not work at all and when I add the folder back in, it works without any problems.

SupportVIs folder was obtained using the TestStand Deployment Utillity. However, it is not installed on the target computer using the installer. The folder was just copied over.

Application (or custom) VIs and llb files call low level VIs which are generally present in 'vi.lib' folder in National Instruments\LabVIEW 8.0.

Since the target computer only has LV run time engine, it does not have any such 'vi.lib' folder. In LabVIEW development system, there is an option for adding search path, but I don't know how to do it on a computer that only has run time engine installed.

Thanks.