|
Solution As suggested in the document聽TestStand System Deployment Best Practices聽we recommend to deploy the LabVIEW code modules using a source distribution or a project packet library.
To handle much of this process automatically, you can use the TestStand Deployment Utility to deploy your sequence files that call LabVIEW code modules. The TestStand Deployment Utility saves all VIs in a single LabVIEW version and includes any required dependencies that are part of the LabVIEW ADE. The deployment utility can also optionally generate a Packed Project Library (PPL). For more information, refer to聽Deploying VIs in LabVIEW Packed Project Libraries.
The LabVIEW Run-Time Engine does not have all of the capabilities of the LabVIEW Development environment. Here are a few reasons why this error can come up:
The VI called by the step contains a subVI that is saved in a different version of LabVIEW than the top-level VI. Mass compiling your VI's directory or the VI itself may take care of this problem. Mass compiling聽the top-level VI can save all of the subVIs in the same version of LabVIEW. For more information, see How to聽Mass Compile in LabVIEW.聽There is a dependency that the LabVIEW Run-Time聽engine cannot find. Ensure that all dependencies for any VIs can be found by the engine by trying these different steps:
Put all of your VIs and subVIs within one directory, if possible.聽If the directory for the VI or its subVIs is not in the聽TestStand search directories, first add the directory to the TestStand search directories. This can be done at聽Configure禄Search Directories...聽and clicking聽Add聽to browse for your directory.If your VIs or their dependencies have the compiled code separated option enabled, it is not possible to execute the VI in the LabVIEW Run-Time Engine. The LabVIEW Run-Time does not have access to the compiled object cache of the LabVIEW Development Environment.
If the bitness of the LabVIEW Run-Time engine does not match the bitness of TestStand, then this error will occur. If this is a requirement, refer to Using 64-bit TestStand to Execute 32-bit LabVIEW VIs.There could be a naming conflict due to LabVIEW Application instances. For more information on this error, please see the section labeled "Errors Related to Naming Conflicts" in the article,聽How TestStand Interacts with LabVIEW Application Instances. The method for fixing this error will differ based on the use case, for instance:
If you do not intend to share VI instances between the sequence and the user interface, follow these steps:
In the Build Specifications of your Operator Interface, with the聽Dependencies聽item selected, check the聽Apply prefix to all selected items聽option in the聽Source File settings聽tab of the Build Specifications Window.Specify a prefix to use.聽This will ensure that the user interface and the sequence do not conflict.聽
If you do intend to share memory, you can prevent this error by deselecting the聽Modify project library file after removing the unused members聽option in the聽Additional Exclusions聽tab of the Build Specifications Window.聽 Note that this change can lead to larger executables due to the inclusion of unnecessary VIs.
Make sure the version of the Run-Time Engine matches the version of LabVIEW you are using. You can check what software is installed by using NI MAX.If you are accessing the VI from a Packed Project Library (PPL) try rebuilding the PPL again and call聽the TestStand sequence after reloading it. Note: After you create a project library in a LabVIEW project, create a separate LabVIEW project for the project library before you build the packed library. If you build the packed library in the same LabVIEW project where you create the project library and you replace the project library with the packed library, you cannot rebuild the packed library.
|