1 reply to this topic

[Mark Yedinak]

We are in the process of deploying a custom user interface for TestStand and are running into some issues with the build process. First, our UI and the TestStand sequences will need to share some data and we are using shared variables for some of the data. Secondly, we are using LabVIEW 8.5.1 and TestStand 4.0. We have been testing in the development environment and everything appears to be working fine. When we did get a system to build we noticed our shared variables did not appear to be getting updated correctly. Data was not getting added or updated. Everything worked as expected in the development environment. In an effort to isolate some of the issues we are seeing we decided to use a very basic system to test things out. We built the example Shared Variable Client-Server.lvproj from the NI examples. When we try to build the system we get the following error message:
[size=2][quote] [size=2]The VI is broken. Open the VI in LabVIEW and fix the errors.[/size][size=2][/size] [size=2]C:\Program Files\National Instruments\LabVIEW 8.5\examples\Shared Variable\Variable Server.vi
<Call Chain>Error 1003 occurred at AB_Application.lvclass:Open_Top_Level_VIs.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Page_Preview.vi[/size][size=2][/size] [size=2]Possible reason(s):[/size][size=2][/size] [size=2]LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable.[[/size][/size][size=2]/quote]

Some research seemed to indicate that the variables had to be configured as absolute rather than target relative. Changing the shared variables to absolute does appear to eliminate this error but I believe we will need to use the target relative for our implementation. Does anyone know why this would happen? Besides upgrading to 8.6 (there was something in the release notes regarding a fix for this type of issue) is there some work around which we can try.[/size]

[Michael Aivaliotis]

The error message is implying that the application builder itself is broken. The AB prefix on the VIs stands for Application Builder.