"VI Is Not Executable" Error when Running My Sequence in the LabVIEW Operator Interface Primary Software: TestStandPrimary Software Version: 3.0 Primary Software Fixed Version: 3.0 Secondary Software: LabVIEW Run-Time Engine
Problem: I have a sequence that calls some VIs created in LabVIEW 7.1. When I configure the LabVIEW adapter to use the LabVIEW Run-Time Engine 7.1 and run my sequence using the LabVIEW Operator Interface, I get the following error: Error loading step 'Action' of sequence 'MainSequence' in file 'Test Sequence.seq'.My sequence runs correctly in the Sequence Editor and any other operator interface. Why is this happening and how can I fix it? Solution: The problem is caused by conflicting versions of some LabVIEW VIs. The issue arises only if your sequence calls a test VI created in LabVIEW 7.1 and this VI happens to use one or more of the subVIs used by the operator interface. This is because the shipping LabVIEW operator interface was built with LabVIEW 7.0 and, when you run the operator interface, the LabVIEW 7.0 subVIs used by it are loaded in memory. Since the TestStand LabVIEW adapter is configured to use the LabVIEW run-time engine 7.1 to load and run test VIs, this run-time engine returns an error when trying to execute VIs saved in any LabVIEW version other than 7.1. For example, the LabVIEW operator interface uses the "Merge Errors.vi". Upon launching the operator interface, the "Merge Errors.vi" version 7.0 is loaded. When a test VI compiled with 7.1 is loaded by TestStand and the VI also uses the "Merge Errors.vi", the LabVIEW run-time engine finds the 7.0 version of the VI used by the operator interface since it is already in memory, thus, causing the problem. In order to solve this problem, you have two options:
Related Links: Attachments:
Report Date: 06/16/2004 Last Updated: 03/19/2007 Document ID: 372L0FMF |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
