Bjarne Joergensen Posted February 27, 2009 Report Share Posted February 27, 2009 Hi All Is there a way to find VIs where a specific VI is used, whithout loading all the VIs I might assume that call the specific VI? best regards Bjarne Quote Link to comment
crelf Posted February 27, 2009 Report Share Posted February 27, 2009 QUOTE (Bjarne Joergensen @ Feb 26 2009, 04:34 AM) Is there a way to find VIs where a specific VI is used, whithout loading all the VIs I might assume that call the specific VI? You mean a reverse dependancy (what VIs depend on me?) - Vis don't store that information, so I think you're out of luck. Quote Link to comment
LAVA 1.0 Content Posted February 27, 2009 Report Share Posted February 27, 2009 The Linker.Read_info_from_file might not-load the VIs into memory. Ton Quote Link to comment
Anke Schenk Posted February 27, 2009 Report Share Posted February 27, 2009 Bjarne, I don't know about LV Versions above 7.1, but until then a simple text search for the Vi name whithin the xxx.vi files does help. Anke Quote Link to comment
Grampa_of_Oliva_n_Eden Posted February 27, 2009 Report Share Posted February 27, 2009 QUOTE (Bjarne Joergensen @ Feb 26 2009, 04:34 AM) Hi AllIs there a way to find VIs where a specific VI is used, whithout loading all the VIs I might assume that call the specific VI? best regards Bjarne If the VI is in a project you can right-click and select find callers. I use this method to fix-up projects where someone turned on "auto-populate" with broken VI in the folders. THe missing links in the Depndencies can then be used to chase up the tree to the caller. Ben Quote Link to comment
Bjarne Joergensen Posted February 27, 2009 Author Report Share Posted February 27, 2009 QUOTE (Anke Schenk @ Feb 26 2009, 05:15 PM) Bjarne,I don't know about LV Versions above 7.1, but until then a simple text search for the Vi name whithin the xxx.vi files does help. Anke Hi Anke Did you do this from LV or a file bowser? Bjarne Quote Link to comment
Anke Schenk Posted February 28, 2009 Report Share Posted February 28, 2009 QUOTE (Bjarne Joergensen @ Feb 26 2009, 06:12 PM) Did you do this from LV or a file bowser? Bjarne, My best used tool is the "Total Commander" by Christian Ghisler ( a must have for anyone who once used the Norton Commander). The built in search command works just fine. I don't know about other browsers. hope this helps regards Anke Quote Link to comment
Bjarne Joergensen Posted February 28, 2009 Author Report Share Posted February 28, 2009 QUOTE (Anke Schenk @ Feb 27 2009, 03:39 PM) Bjarne,My best used tool is the "Total Commander" by Christian Ghisler ( a must have for anyone who once used the Norton Commander). The built in search command works just fine. I don't know about other browsers. hope this helps regards Anke Hi Anke I works just great :worship: Now I can find those VIs I have used a buggy lowlevel VI. Tanks Again /Bjarne Quote Link to comment
Rolf Kalbermatter Posted March 2, 2009 Report Share Posted March 2, 2009 QUOTE (Bjarne Joergensen @ Feb 27 2009, 10:00 AM) Hi AnkeI works just great :worship: Now I can find those VIs I have used a buggy lowlevel VI. Tanks Again /Bjarne It won't work in LabVIEW 8.6 AFAIK. They compress most of the information in a VI file. Freee text labels on the front panel for instance can not be found anymore in this way. Rolf Kalbermatter Quote Link to comment
Bjarne Joergensen Posted March 4, 2009 Author Report Share Posted March 4, 2009 QUOTE (rolfk @ Mar 1 2009, 10:19 PM) It won't work in LabVIEW 8.6 AFAIK. They compress most of the information in a VI file. Freee text labels on the front panel for instance can not be found anymore in this way.Rolf Kalbermatter Hej Rolf It works for me, execpt when the files that use the file I'm looking for is in a llb! /Bjarne Quote Link to comment
Rolf Kalbermatter Posted March 4, 2009 Report Share Posted March 4, 2009 QUOTE (Bjarne Joergensen @ Mar 3 2009, 03:25 AM) Hej RolfIt works for me, execpt when the files that use the file I'm looking for is in a llb! /Bjarne Yes that can't work. The VI's inside an LLB are each compressed with an NI specific (by far not as good as zlib but at least something) algorithme into a resource and added to the LLB file. So the resource stream and therefore the LLB file does not contain intelligible ASCII characters due to that compression. This is so since the beginning of LLBs although NI added also an uncompressed LLB resource stream variant to the LLB format at around LabVIEW 8 but that seems only getting used when creating in the Application Builder the LLB that gets later turned into an executable. Rolf Kalbermatter Quote Link to comment
Aristos Queue Posted March 4, 2009 Report Share Posted March 4, 2009 There is a VI Analyzer test you can use to analyze VIs on disk to see if they call a given subVI: http://forums.ni.com/ni/board/message?boar...ssage.id=365628 This can search inside .llb files. I don't know what version of LV the earliest VI Analyzer was available. Quote Link to comment
Bjarne Joergensen Posted March 4, 2009 Author Report Share Posted March 4, 2009 QUOTE (Aristos Queue @ Mar 3 2009, 03:33 PM) There is a VI Analyzer test you can use to analyze VIs on disk to see if they call a given subVI:http://forums.ni.com/ni/board/message?boar...ssage.id=365628 This can search inside .llb files. I don't know what version of LV the earliest VI Analyzer was available. Hi Aristos It works just fine and then I can do the search from the LV environment, instead of using other programs. best regards Bjarne Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.