LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why the search for VI's at Labview start ?

Solved!
Go to solution

Hi,

 

Since I deleted a "..\Support VI" directory, originally created during a Teststand deployment, whenever I start

Labview 8.6 a search for several VI's is performed.

These VI's are NI provided and were originally located in the above Support directory.

 

My questions are:

 

1. Why is Labview looking for these VI's at startup, even though no VI is loaded into the editor ?

2. Why doesn't the search path update after the original source directory has been deleted ?

    (why not use the new location for subsequent Labview start ups ?)

 

 

thanks,

 

 

Gary.

 

 

0 Kudos
Message 1 of 5
(2,948 Views)

Gary,

 

what VIs are searched for?  Is there any error displayed because "VIs are not found"?

I asume that your support directory is included in the search paths of LV. You should remove it (find the search paths in the LV options).

 

hope this helps,

Norbert 

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 5
(2,944 Views)

Norbert,

 

The search is loading whitespace.ctl and Trim Whitespace.vi , the search dialogue boxes show titles such as

gws_init.vi and gws_main.init.

 

There is no error displayed after the search dialogue box has disappeared, Labview home page displays

as normal.

 

The ..\Support directory is not included in the search paths of LV.

In the Paths setup (LV Home page\Tools\...Options - Paths - VI Search paths), there is a list of locations enclosed

in "< >" characters, e.g. <foundvi>.

At the end of the path list there is 1 absolute path, C:\Program Files\National Instruments\LabVIEW 8.6\resource.

 

I tried moving <foundvi> to the end of list, restarted LV, but the searches continue to occur.

 

Is it possible to view the defintion of <foundvi>, i.e. what paths are represented by <foundvi> ? 

 

Gary.

0 Kudos
Message 3 of 5
(2,935 Views)
Solution
Accepted by topic author Gary_H

Propably this is one of the cases, where a mass compile could help.

I guess that some vi's are loaded at LV startup that are still linked to that directory. Also you fix them, they are not saved, so you get to fix them every time. If you know which vi's that might be, you can also look them up in the LV directory and open them manually and save them with the changes. 

 

Felix 

Message 4 of 5
(2,923 Views)

Felix,

 

I did a mass compile on my C:\Program Files\....\LabVIEW 8.6, it solved the problem, no more search dialogue

boxes as I start and whilst using Labview.

 

thanks,

 

 

Gary. 

0 Kudos
Message 5 of 5
(2,886 Views)