Loading VI in Vision Builder AI 3.0 takes a loooooong time

[crelf]

I'm using LabVIEW 8.0 with Vision Builder AI 3.0, and I've got a handful of cusomt LabVIEW steps - when I load the vbai file (irrespective of whether I'm doing inspection or configuration), the progress indicator zips along to about 80% and then stays there for a long time (around 20 - 30 seconds or so).  Is there any way I can speed this process up?

[VuD]

Hi crelf,

I am not sure that there is anything we can do to directly reduce the speed of loading your VBAI file.  Does it take this long every time or just the first time you load the file?  Does it take this long if you load only one LabVIEW step (i.e. does the time reduce with fewer LabVIEW steps)?  Assuming that you are loading the Run LabVIEW VI step, I would suggest trying to combine some of the steps or calling fewer libraries.  Please let us know if you would like further clarification or assistance. 
Best regards,

Vu D

[crelf]

It doesn't matter how many Run VI steps I have in the inspection - if there's more than one then it performs as listed above.  If there are no Run VI steps then is loads quickly.  Are you sure there's nothing I can do to speed up the loading of the VI?

[crelf]

I'd like to show you a creen shot of where it stalls out, but I can't upload an image to this discussion forum.  Here's one hosted (for a short while only) on LAVA:

[VuD]

Hi crelf,

To help clarify, are you referring to the initializing progress?  I have attached a screenshot below to make sure we are talking about the same thing.  Also, after you load up your inspection, does it take as long every time you load it again?  When you are actually running an inspection is there a delay or lag due to the LabVIEW VIs?  If you are referring to the initializing progress, then I do not think there is a way for us to increase this process as it is related to the time required to upload the appropriate functions, library calls, etc. that are contained in the VI.  Please let us know if you are referring to something else.  Also, a screenshot will help clarify the issue.

Best regards,

Vu D

[crelf]

As my screenshot above suggests, it does indeed happen during initialization.  My release will go to the client with about 12 different scripts (one representing each product they inspect), so whenever they change products they'll need wait for a long time.  It's also a huge inconvenience when I'm debugging, as I need to switch between scripts often.

[brad.buchanan@ni.com]

The reason the Run LabVIEW step could be taking a long time to load is because it may not be finding all the dependencies of the VI and so it searches your entire Hard drive.  If all the dependencies are in LabVIEW's vi.lib, make sure you have the following line in your VBAI .ini file under the [Vision Builder] section:
viSearchPath=C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\vision\*;C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\*

(If your LabVIEW is in a different location, put the correct path)

If this doesn't fix the problem, then put your VI in an LLB with all the dependencies and this will fix the problem.  The Run LabVIEW VI Context help explains how to make an LLB with all the dependencies.

Hope this helps,

Brad

[crelf]

Neither adjusting the searchpath (those items were already in there, and I added the location of my VIs as well) nor the building into a llb worked - any other other ideas?

[Brad]

Did you include vi.lib VIs in your LLB?  Is your code something that you could send to me with your VBAI Inspection so I can see if we can reprodcue it here?  Is there any hardware, or special DLLs/drivers required by your Run LabVIEW step?

Thanks,

Brad

[crelf]

I sure do, but I can't post them to the public domain - is there a secure place I can post it to?