LabVIEW
Build breaks because vi is broken ... but it's not :/
Hello,
I got an odd problem. the application builder crashes, because it thinks my vi is broken ... but that's not the case
For the SearchBot
Cannot complete build because following VI loaded broken:
C:\Users\User1\Desktop\Insanu\InSanu_Controller\InSanuCore.vi
Open the VI in LabVIEW and fix the listed errors. If the VI loads as expected but errors are still detected during the build, contact National Instruments technical support for assistance.
Broken VIs:
<Call Chain>Error 1003 occurred at AB_Get_Detailed_BrokenVI_Message.vi -> AB_Targetfile.lvclass:Open_Top_Level_VIs.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Page_Preview.vi
Possible reason(s):
LabVIEW: (Hex 0x3EB) The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.
Any Ideas?
Martin
Are you calling any VI's dynamically? It sounds like something needs to be placed in Always Include, but that's a guess.
Yes I do run a few dynamically as threads.
They are called via something like this:
and trade data via queue, notifier and shared vars.
But on build I notice that:
what are the 3 arrows? The broken run button and the green arrows show only up on the build attempt.
PS: I did always include the threaded/dynamic vi's
@kutt wrote:
But on build I notice that:
what are the 3 arrows? The broken run button and the green arrows show only up on the build attempt.
The 3 green arrows are explained in the LabVIEW help:
Synchronize with Other Application Instances applies changes to the VI in all application instances. You cannot undo changes made to the VI after you click this button. This button is available only if you edit a VI that is open in multiple application instances.
Edit:
https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/environment/vi-toolbar-buttons.html
I did find the thread, where someone had this issue. But sadly - I don't use any Conditional Disable Structures
The only one I found are from NI an can be found in vi.lib (so I can't edit them)
Is there some log, what the compiler exactly complains about?
@kutt wrote:
Is there some log, what the compiler exactly complains about?
In the Advanced Categorie of the Application Builder you can check 'Generate build log file'. I don't know how many details are in the log.
@kutt wrote:
But on build I notice that:
What application instance does the VI show (lower left corner of the VI)?
What error do you see when you click on the broken run arrow?
When I see problems like this, my first thing to try is to clear the compile object cache (Tools->Advanced->Clear Compile Object Cache). This is where the object code from files using the Separate From Compiled VIs go. It does tend to get corrupted or confused, so many of us regularly clear this out. I know some who clear it out before any attempt to build an executable as part of their CI scripts.
If that doesn't fix things, sometimes a mass compile on the project helps.
