Running Vision Builder AI Inspection from TestStand

Hello, I have installed the

Hello,
I've found some more information that may help. Since these TestStand steps are simply call a DLL with an exported ActiveX API, path issues may exist. In fact, the overwhelming number of times this error appears, paths seems to be the case. I am not sure why the error is an indication of a path issue, but that seems to be the case. I would recommend that you would reregister the DLL, this time in the same directory as the example sequence. To do this:
- Unregister the current DLL by going to Start Menu>>Run, and typing: regsvr32 /u NIVBAITestStandAPI.dll
- Move the DLL from the system32 folder to the folder in which the example sequence is saved.
- Reregister the DLL from the run command (regsvr32 <folder path>\NIVBAITestStandAPI.dll)
- Restart TestStand if it is open
I apologize for not having any concrete answers, but this one is proving tough without me being able to replicate the issue.
crisR

Similar Messages

Run time error running Vision Builder AI inspection from TestStand

Hello,
I have TestStand 3.1 and Vision Builder for AI v2.6.1.
I would like to run from TestStand a Vision Builder Program or steps. For to achieve that, I have followed the instructions on Application Note 215, Running a Vision Builder AI Inspection from TestStand.
After installation, the option in TestStand InsertStep>NI Vision Builder AI>Inspection works properly.
But when try to execute a step with that inspection, and whatever operation of that one, the result is the following error:
Run-Time Error
Details: Error executing substep 'Post'.
An error occurred calling 'ExecuteStep' in '_NIVBAITestStandSteps' of 'NIVBAITestStandAPI'.
Error Code: -2147417851; User defined code. Possible System Error: The server sent an exception.
At this point really I don´t know what to do, and I don't find any extra help apart of application note.
I will appreciate some suggestion.
Gonzalo.

Hello,
I've found some more information that may help. Since these TestStand steps are simply call a DLL with an exported ActiveX API, path issues may exist. In fact, the overwhelming number of times this error appears, paths seems to be the case. I am not sure why the error is an indication of a path issue, but that seems to be the case. I would recommend that you would reregister the DLL, this time in the same directory as the example sequence. To do this:
- Unregister the current DLL by going to Start Menu>>Run, and typing: regsvr32 /u NIVBAITestStandAPI.dll
- Move the DLL from the system32 folder to the folder in which the example sequence is saved.
- Reregister the DLL from the run command (regsvr32 <folder path>\NIVBAITestStandAPI.dll)
- Restart TestStand if it is open
I apologize for not having any concrete answers, but this one is proving tough without me being able to replicate the issue.
crisR

Call Vision Builder 2014 AI from TestStand 2014.

I need info on how to run Vision Builder 2014 AI from TestStand 2014

Hello jspeedz,
I did have a look at that doc it didn't address in enough details to my needs. I figured out the process thanks.

Extract red image with Vision Builder Automated Inspection

Hello
I have 2 camera connected to a CVS and I want to process the images to have only the red part of the images.
for that I tried to use VBAI but I din't sucess, I think nit should be in the vision assistant step, but I already tryed with "extract a color plane" and "treshold color", and when I test with an image it don't work.
Does anybody know how to that?
Thank you for your help

Hello
I may be find a way to delete everythimg that is not red by substract green and blue with vision assisatant, it seems to work.
Now I try to extract only little part of the picture, only the part of the picture who are red, for that I created ROIs for some red parts of the images, and I want to record only this ROIs, to reduce the size of the file and kipping the same resolution.
Does anybody know how to do that?
I attach my Vision builder code to the message
Thanks for your help
Attachments:
Color Example red-21-7-12h30.vbai ‏108 KB

Vision Builder for Automated Inspection and communication to external programs

I want to use Vision Builder for Automated Inspection in my application to do the vision tasks. However, the vision task
is only a part of the total application. Like for example, the application starts by reading the input of a barcode scanner.
Based on the value of the barcode, the proper program should be loaded in Vision Builder for AI. I was thinking about
using the .NET environment to build the application and call Vision Builder for AI from out of there. Is this possible? If
not, are there other solutions?
Thanks!
Bert Christiaens

Hi Bert,
Vision Builder includes a Product Selection functionality that allows to automatically change an inspection based on the result of a step. For example, if the interface to the barcode scanner is Serial or TCP, you can use the corresponding step in Vision Builder to read the barcode, and based on the result select the appropriate inspection.
That is if you want to stay within the Vision Builder environment.
If your application is already written in .NET and you need to add Vision to it, then as mentioned in the post above, Vision Builder has a programmatic API that you can call from .NET (example located here:
C:\Program Files (x86)\National Instruments\Vision Builder AI 2011\API Examples\dotNET Examples
The API allows to programmatically load an inspection, run it and get results, close it, etc. From the information you're providing, it seems like it might be the option that is the most appropriate to your application.
Best regards,
Christophe

Vision builder AI running Ethernet IP server on my computer

Hi,
I am running Vision bulider AI on my computer and I need to exchange data thru the Ethernet/IP protocol.
In vision bulider I have startet the Ethernet/IP server.
I am using a Devicenet to Ethernet IP gateway from Hilscher, When I go online on this device I see that it can not see any slaves.
Using wireshark I can also see that the gateway is actually trying to establish communication.
How can I see which NIC VBAI is trying to establish communication thru?
Is this type of communication only possible on a smart camera?
Johan
Attachments:
hilscher.jpg ‏18 KB
VBAI.jpg ‏51 KB

Hi Johan,
Could you please provide some more information on your setup, model number on the Hilscher device etc. Are you for instance running Vision Builder AI on a computer with multiple network cards?
Have you tried connecting to your device using MAX?
Have you gone through a setup process similar to this one?
Setting up Implicit Ethernet/IP messaging between an Omron PLC and Vision Builder AI
http://www.ni.com/white-paper/13579/en/
Best regards,
Robert P-F
Applications Engineer
National Instruments Sweden

Compatibility of developed Vision library with NI Vision Builder AI

We developed a specific Vision library using NI LabVIEW and Vision Toolkit.
My requirement is to identify the compatiblity of this library with NI Vision Builder AI.Can we use the existing VI's with Vision builder?
Please provide me your comments asap.
Regards:
Vaibhav Kanchan
Sr. Engineer
NI Certified LabVIEW Developer(CLD)
NI Certified TestStand Developer(CTD}

There are multiple ways to add functionality to Vision Builder AI using a set of VIs you wrote:
1) Vision Builder AI can run a VI you write that use your VIs using the Run LabVIEW VI step.
2) You can also develop a custom step (that include the configuration page) for a better user experience, using the VBAI SDK, and use your VIs inside.
With these 2 solutions, you will need to use a specific version of LabVIEW to integrate your library, as Vision Builder AI is a LabVIEW application, and VBAI will execute the code from the Run LabVIEW step, or custom step using the LabVIEW runtine engine that it was built with. The version of LabVIEW depends on the version of VBAI. For example, for VBAI 2011SP1, you need to use LabVIEW 2010.
3) You can automate/drive Vision Builder AI from LabVIEW on Windows. (Open an inspection, run once, run continuously, etc, and get the resulting results and image that you can further process using your library. You can use the API on Windows with any version of LabVIEW.
For example, the VBAI 2011 API supports LabVIEW 8.5 through 2011.
You will run your developped application on Windows only, but it will be able to control Vision Builder AI running on remote targets.
If you're running Vision Builder AI on Windows, I see no compatibility issues with any of the above solution, except for using the correct version of LabVIEW in the first 2 solutions I mentioned. Using 1) and 2), you will also be able to develop code that can run on targets that Vision Builder AI supports, like smart cameras, and embedded vision systems.
If you plan to support remote targets, like smart cameras or Embedded Vision Systems, there are things to consider for your library to be compatible:
These targets run different operating systems: some run Pharlap, some run VxWorks, all run LabVIEW real-time on these OSes. If you used LabVIEW and Vision Development module to build you library based on VDM, the only thing to consider is to make sure to use the same version of LabVIEW and Vision Development Module installed on the target. Let me explain:
When you configure one of these remote targets from Vision Builder AI running on the Windows host machine, we install an image that contains a specific version of LabVIEW Real-time and Vision Development Module (For example, in the case of VBAI 2011 SP1, the remote target image has LabVIEW Real-Time 2010 and Vision Development Module 2011). Those should be the versions you need to use to create your VI to run with the Run LabVIEW step or custom step). We ran into some compatibility issues when customers update their Windows machine with a newer version of Vision Development Module, and write a VI or custom step they want to run in VBAI, that uses a new function that is not supported with the DLLs installed on the target.
If your Vision Library uses some other DLLs (code you may have written in text based language or third party DLL), you will have to recompile the DLL for the operating system of the target (Pharlap or VXWorks, depending on the target) for the code to work on the remote target.
Hope this helps and is not too confusing.
Best regards,
-Christophe

Installing both Vision Builder 2012 and LabView 2012 on same Computer

am new to NI Vision Builder Automation Inspection 2012 (Which I am supposed to learn and use for part inspection) as well as LabView (Which I need not know at this time)
When I was presented (to work with) a 1722 Camera and the computer, Labview 2012 was already installed but not Vision Builder.
The IT folks installed the Vision builder without uninstalling LabView.
I have my problems getting upto speed with my inspection work, but is any of it attributed to both systems being on the computer?
Can I (Must I) uninstall LaView??
Thanks

LabVIEW and Vision Builder run fine on the same computer. I have several versions of each on mine with no problems.
Bruce
Bruce Ammons
Ammons Engineering

Migrating inspection from Vision Builder to Labview

When I migrate my inspection, which includes an Acquire Image function, from Vision Builder for AI 2.0 to Labview 7.0, it asks me to find a bunch of *.vi and *.ctl files such as "IMAQ Resource Manager.vi", "IMAQ Configure Buffer.vi", "IVB Image Providers Manager Function.ctl" etc. I cannot locate these files so I just hit "Cancel" when these messages pop up, and the migration is said to be successful but the resulting vi can not be run in Labview. What's wrong? I do have IMAQ Vision 7.0.1.

All of the Vision Builder AI generated VIs are typically installed in the following directory: C:\Program Files\National Instruments\Vision Builder AI 2.0\LV\SubVIs. Within that folder you should have approximately 25 VI libraries (such as Common.llb, IVB Match Pattern.llb, etc.) and several other VIs (i.e. Inspect Result.vi and Inspect Setup.vi, etc.).
Did you install Vision Builder AI to a different directory than the default location? Have you tried repairing/reinstalling Vision Builder AI?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Vision Builder 2010 Active time not working when calling Vision inspection from testand 2010

I have an issue where I am timing a flashing light using the active time variable, when I run the inspection from the inspection view everything works, however when I run it from the configuration view or by calling it through teststand 2010 with the Vision Vi's the Active Time never changes from 0.00000.
I do not need precides timings so I am NOT worried about the +/- 20ms from the windows system clock.

Hi Ryan,
Can you read any of the other variables using the Get Inspection statistics VI? Is it only the Active Timer that doesn't change?
Cole R.
National Instruments
Applications Engineer

Run-time License for Vision builder

HI
I have created a VBAI file for my inspection in, but now I want to transfer the inspection LabVIEW and build an exe to run the application.
Now for running that application do I require a NI Vision Builder for Automated Inspection Run-Time License or a NI Vision Development Module Run-Time License.
Thanks,
Ninad Regundwar
Junior Engineer | ARAV Technologies | www.aravtech.com

Instead of migrating to LabVIEW, you might want to consider automating Vision Builder from LabVIEW and running your inspection by using the VBAI API.
Check out the examples located here: C:\Program Files (x86)\National Instruments\Vision Builder AI 2013\API Examples\LabVIEW Examples.
The VBAI API allows to start a VBAI engine, open and run an inspection and retrieve images and results for each step.
When using this method, if you're running the LabVIEW program on the same machine VBAI is installed, you do not need to purchase the VBAI runtime, neither the Vision Development Module Runtime (unless you wish to process further the image returned by VBAI.
If you need to deploy that LabVIEW application on a different machine, then you'll need to purchase a VBAI Runtime license.
If you choose instead to migrate the inspection to LabVIEW, then you will need to purchase a full license of Vision Development module for your development machine (the code generated uses Vision Development Module VIs).
If you choose to build the resulting code into a LabVIEW application and deploy it on a different machine, you will need a Vision Development Module Runtime License for the deployment machine (but not a VBAI license).
Migrating the code to LabVIEW is recommended only in cases where you need to modify the code generated by VBAI. The code generated is indeed a lot more complex than using the VBAI API that I described in the first option.
Hope this helps.
Best regards,
Christophe

Is there a way to bypass the first two inspection block after first cycle in Vision builder AI?

I want to inspect the C-C of a matrix of holes (holes side by side). But when I do re-cycle the routine, the hole #'s change location (not in same place twice) and the my C-C are all not side by side and all over the place. For example, diaganal 4 holes away, etc...

laj,
I'm not sure that I completely understand the question that you are asking in your post. You may want to repost your question with some additional information and explanation to allow this forum to help you more effectively.
As for the question that you posed in the title of your email, can you bypass the first two steps of your Vision Builder for Automated Inspection (VBAI) script? The answer is unfortunately no. VBAI is designed to repeatedly run through the same script and does not allow only a portion of the script to run.
If you need more control over your application than VBAI can provide, you may need to move a programming language like LabVIEW, which will allow for lower level decision making.
Please post a follow up if you have any additio
nal information you would like to add, or have additional questions.
Regards,
Jed R.
Applications Engineer
National Instruments

Send variable from vision builder to NXT Brick

Hello,
I have a color sorting machine controlled by an NXT Mindstorms brick. I believe that Labview has a module to communicate with the Lego brick, but I was wondering if the Vision Builder (which we are currently using for another application) could also communicate with the brick (we don't have Labview). Ultimately, after insecting the object with Vision Builder, I would like to send a variable (based on the inspection) to the NXT mailbox, preferably via usb, otherwise BT, that would serve as a motor command for the servo. If there is no such communication module, is there a code that I could insert into the Vision Builder program that would allow for such a communication?
Solved!
Go to Solution.

Hi there,
As far as I know, Vision Builder will not be able to "target" the Lego Mindstorms brick.
The LabVIEW add-on for Lego Mindstorms can be found here: http://zone.ni.com/devzone/cda/tut/p/id/4435
I'm assuming you're planning on connecting your camera to a PC?
Although I just found a camera that can connect directly to the Lego brick here: http://www.mindsensors.com/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=78
If your LabVIEW code is running on your PC, you should be able to use either vision builder or vision assistant and then have your brick "do something" based on the results. You'll have to choose your PC as the "target" for your code and you will need LabVIEW and the Mindstorms add-on to make this work.
Patrick Allen

From vision builder to labview

Would anyone possibly know how to convert a tool developed in vision builder for automated inspection into labview so that when we connect a thermal camera and have a live image, the tool from vision builder analyses the image on labview?
Thanks for the help

It is very weird, this is what I get as a reply when I try to convert from VB AI to LabView
And here is also a picture of my NI License Manager, from where I have activated "successfully" VAS and VDM...
I don't understand why it won't work...
Attachments:
conversion impossible.png ‏259 KB
NI license manager.png ‏107 KB

Vision Builder AI: (Hex 0xFFFA960C) Cannot open the inspection file.

I hav built an inspection in vision builder for automated inspection (the code , image and inspection is provided in the attachment)
but my program is unable to open the inspection it is throwing an error : Error -354804 occurred at VBAI Interface - Open Inspection.vi .
I am using the NI 1742 smart camera and running the program on this remote target
I am not getting the reason for this error.
If smbdy can solve.. please...
Solved!
Go to Solution.
Attachments:
barcode_test1.vbai ‏144 KB
TEST2.vi ‏63 KB
img.png ‏320 KB

I am having this same issue. I do not have Labview Real-Time. The Open Inspection.vi returns the error of
Error -354809 occurred at VBAI Interface - Open Inspection.vi
Possible reason(s):
Vision Builder AI: (Hex 0xFFFA9607) The validation of the inspection returns errors.
This error has to be the path chosen no?? Any help would be greatly appreciated.
Steve Loescher
Test Engineer
Attachments:
NICameraTest.vi ‏20 KB

Running Vision Builder AI Inspection from TestStand

Similar Messages

Maybe you are looking for