Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Run VBAI in LV. (Error -354703 occurred at VBAI Interface - Open Connection.vi)

Solved!
Go to solution

 

Hi everyone,

Im trying to run VBAI2015 in LV2015 (Evaluation). I load example <NI>VBAI 2011/API examples/LabVIEW. Error 354703 appears when I "Launch Vision Builder AI Engine". I try to create simple prog similar to the example, same error. I attached files for review.

*Im new to LabView & I have ambition to build an Inspection Machine by Vision using LabVIEW.

Thanks,
dane

 

unknown.jpg

 

 

 

 

0 Kudos
Message 1 of 8
(4,839 Views)

Hi Again !


Its been a month. I tried to uninstall all National Instruments products from my PC and re-installing LabView 2015 32-bit, VBAI 2015, yet the error still there. Either using example <NI>VBAI 2015/API examples/LabVIEW or  Simple API test.vi both return Error 354703. 
Can someone please comes up with solution for this problem.

Capture.PNGCapturea.PNG

Much Thanks !

0 Kudos
Message 2 of 8
(4,759 Views)
Solution
Accepted by topic author tr_dane

It looks like in the latest screen shot you're getting a different error that is about the inspection not being valid. For the inspection to open without errors, make sure any resources it uses are available (i.e. if using a camera, make sure no other application is using the camera, and any VI used by Run LV step is available at the expected location, etc.). Try closing VBAI and MAX and anything else that may be using resources. If the problem still persists, try rebooting and opening the VBAI inspection from VBAI and see if there are any issues opening the inspection in the VBAI environment. If so, fix them and save the inspection. If not, and you still get errors after closing VBAI and running your code, please attach your inspection so we can see what it is doing that might cause it to be broken when opened from LV.

 

Thanks,

Brad

Message 3 of 8
(4,740 Views)

Thank you Brad! After re-installing everything... again, example in <NI>VBAI 2015/API examples/LabVIEW can run without a hitch. I found out there was a Fail step in the vbai inspection. 

wrote:

It looks like in the latest screen shot you're getting a different error that is about the inspection not being valid.


That is why vbai file could not open from LabVIEW API Example (Local).
Next, I will try to open 3 vbai inspections by sequence.

Any advice would be greatly appreciated...

Thanks,
dane

0 Kudos
Message 4 of 8
(4,728 Views)

Hello,

 

 

I've got the same issue, but before to open an inspection.

I've only try to open VBAI with the API (not opening an inspection). The API UI is openning, but before it finnished is "Open Connection", It occurs an error:

 

"Error -354703 occurred at an unidentified location
Possible reason(s):
Vision Builder AI:  (Hex 0xFFFA9671) Critical components of Vision Builder AI are missing or not installed."

 

I've try to reinstall and repare vbai (2014SP1) but it doesn't resolve it...

 

What is the next step?

 

Regards

 

 

 

 

 

0 Kudos
Message 5 of 8
(4,183 Views)

This usually means the registry that contains the path to Vision Builder is messed up (not sure how it gets in this state). I attached a picture of my registry entry for the 32-bit VBAI API Path. To access this, from your start button, type "regedit" to launch the Registry Editor. Then navigate to the location shown in the toolbar of the picture and make sure the APIPath is specified correctly. For 64-bit VBAI, just remove the WOW6432Node from the path you go to and make sure the path you specify for the APIPath is for your 64-bit VBAI. If you need to add a new entry for this APIPath, just right click on the right area and select New>>String Value.

 

Hope this helps,

Brad 

0 Kudos
Message 6 of 8
(4,178 Views)

(Since this is being run via .NET, I can make this its own thread if needed. However, this is the same error at the same entry point best I can tell)

We're attempting to run VBAI 2015 f3 x64 inside a Windows 10 VM. We've added the APIPath to the appropriate registry location (i.e. without the WOW6432Node) but we're still continuing to get error -354703 after calling vbaiOpenConnection() via a .NET SDK provided by NI (since there seems to only be a 32-bit version available via the install).

Any ideas for next steps? I haven't seen a x64 .NET SDK for VBAI 2018 otherwise I'd try that next. I could go into LabVIEW and compile my own DLL around the VBAI API palette?

Galen

Message 7 of 8
(3,775 Views)

Try specifying the VBAI engine version in the command to ensure it's opening the 64-bit VBAI engine:

engine = new VBAIEngine("APITest", "2015_64", true);

 

If it's trying to open the 32-bit version and your registry doesn't have the APIPath, this could explain it. We aren't sure why the APIPath is sometimes missing, but I would go ahead and make sure it's present in both places:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\Vision Builder AI\15.0.0\APIPath

HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Vision Builder AI\15.0.0\APIPath

and make sure it's set to to the same value as the "Path" setting in that location.

 

Hope this helps,

Brad

0 Kudos
Message 8 of 8
(3,761 Views)