LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview 2009 ini prevents app builder from getting VIs

The attached INI file is doing something ODD, When I try to build an application (LV2009F3), any VIs that reside in LLBs are missing.  The App builder reports ONLY that the VI is broken. (Read here for error).  I deleted the LabVIEW INI file, then restarted labview.  App build fine.  See attached VI for reproducing this issue.

So my question is, what setting(s) are causing this and why?


Paul
Download All
0 Kudos
Message 1 of 6
(3,801 Views)

Search path?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 6
(3,792 Views)

Search Path is in the INI file. 

Deleting the INI file enabled me to build the Test VI, the project that I am trying to build still has issues.  Maybe related to daqMX?


Paul
0 Kudos
Message 3 of 6
(3,784 Views)

After building a VI that dynamic loads the entire Hierarchy of a VI and checks its status.  All the VIs that are broken, are related to missing files from vilib.

here is the entire list:

<vilib>:\Utility\libraryn.llb\Check if File or Folder Exists.vi
C:\projects\Sandbox\CA-Hans\utilities\computeScanRate.vi
<vilib>:\DAQmx\configure\task.llb\DAQmx Configure Logging (TDMS).vi
<vilib>:\DAQmx\read.llb\DAQmx Read (Analog 1D Wfm NChan NSamp).vi
<vilib>:\DAQmx\configure\system.llb\DAQmx Self-Test Device.vi
<vilib>:\DAQmx\configure\task.llb\DAQmx Start Task.vi
<vilib>:\DAQmx\configure\task.llb\DAQmx Stop Task.vi
<vilib>:\DAQmx\configure\timing.llb\DAQmx Timing (Sample Clock).vi
C:\projects\Sandbox\CA-Hans\drivers\daqMxReadAvailableSamples.vi
<vilib>:\Utility\error.llb\Error Cluster From Error Code.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmArr(clu)ToGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmArrToGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmBooToGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmCluToGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\fmCtrlObjToIni.vi
C:\projects\lv2009\reuse\utilities\file\ini\fmIniToCtrlObj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmNumtoGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmPathToGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\fmStringtoGobj.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToArr(clu).vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToArr.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToBoo.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToClu.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToNum.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToPath.vi
C:\projects\lv2009\reuse\utilities\file\ini\utility\poly\GobjToString.vi
<vilib>:\Utility\error.llb\Merge Errors.vi
<vilib>:\Utility\config.llb\Close Config Data.vi
<vilib>:\Utility\config.llb\Config Data RefNum.ctl
<vilib>:\Utility\config.llb\Get Section Names.vi
<vilib>:\Utility\config.llb\Open Config Data.vi
<vilib>:\Utility\config.llb\Read Key (Boolean).vi
<vilib>:\Utility\config.llb\Read Key (Double).vi
<vilib>:\Utility\config.llb\Read Key (I32).vi
<vilib>:\Utility\config.llb\Read Key (Path).vi
<vilib>:\Utility\config.llb\Read Key (String).vi
<vilib>:\Utility\config.llb\Read Key (U32).vi
<vilib>:\Utility\config.llb\Write Key (Boolean).vi
<vilib>:\Utility\config.llb\Write Key (Double).vi
<vilib>:\Utility\config.llb\Write Key (I32).vi
<vilib>:\Utility\config.llb\Write Key (Path).vi
<vilib>:\Utility\config.llb\Write Key (String).vi
<vilib>:\Utility\config.llb\Write Key (U32).vi
<vilib>:\_oldvers\_oldvers.llb\Open_Create_Replace File.vi
C:\projects\lv2009\reuse\utilities\projectTools\configFiles\findConfigFile.vi
C:\projects\lv2009\reuse\utilities\projectTools\configFiles\findConfigFile.vi\2
C:\projects\Sandbox\CA-Hans\utilities\retrieveLast30secData.vi
C:\projects\lv2009\reuse\utilities\templates\_smHelpers\smDequeue.vi
C:\projects\lv2009\reuse\utilities\templates\_smHelpers\smEnqueue.vi
C:\projects\lv2009\reuse\utilities\templates\_smHelpers\smQueueManager.vi
<vilib>:\express\express input\FileDialogBlock.llb\subFile Dialog.vi
<vilib>:\Platform\system.llb\System Exec.vi
<vilib>:\Waveform\WDTOps.llb\WDT Get Final Time Value DBL.vi
<vilib>:\Waveform\WDTOps.llb\WDT Index Channel DBL.vi

 

In tracking down my VIs that are broken, they are ALL broken because they can not fine VIs in vilib. I can not help but wonder if this is why the app builder is choking.

I have mass compiled the VIs, no help there.

 

 

 


Paul
0 Kudos
Message 4 of 6
(3,772 Views)

Sorry I can't give this a serious look but what heppens if you toss the line

 

viSearchPath="<topvi>:\*;C:\projects\lv2009\reuse\*;<foundvi>:\;<vilib>:\*;<userlib>:\*;<instrlib>:\*;C:\Program Files\National Instruments\LabVIEW 2009\resource"

 

?

 

I ask since toosing the whole ini makes it work (if I understand correctly) and you are leaning toward a path issue with this last post.

 

Please forgive if this is a distraction,

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 6
(3,764 Views)

No tossing the VI search path does nothing. Nor does using the defaults.  It is almost like LabVIEW does not know the path reference <vilib> for the app buildler or run time environments


Paul
0 Kudos
Message 6 of 6
(3,759 Views)