NI Vision Builder vs. LabVIEW RT + NI Vision Assistant

Hello
I’m designing a vision application which should be able to run stand-alone (EVS-1463RT). The app will have up to 30 inspection states (read gauge value, checking for the presence specific objects, etc.) approximately. The second requirements are the communication ability with other devices not NI via TCP/IP and logging pictures in FTP.
Now I’m thinking about the two possible solutions.
Create an AI with NI Vision Builder
Create LabVIEW RT app and with using NI Vision Assistant build inspection states
A have to say that the first solution is not my favorite because I tried to implement the TCP/IP communication in NI Vision Builder and it was function but the using of the server is limited. In the other hand the building the inspection is “easy”.
The second solution has following advantages for me: better control of the app, maybe better possibility to optimize the code, implementation my own TCP/IP server. My biggest concern is the using NI Vision Assistant to generate the inspection states.
In conclusion I have to say that I’m not experience in the vision app but the LV RT is no problem for me.
Thanks for any opinions
Jan

Hi Jan,
> A have to say that the first solution is not my favorite because I tried to implement the TCP/IP communication in NI Vision Builder and it was function but the using of the server is limited.
Could you give more feedback on this point? What do you mean by "using of the server is limited". More precise feedback and suggestions would help us improve the functionality.
What I would recommend you look into is the use of the VBAI API. You can find examples in <Program Files>\National Instruments\<Vision Builder AI>\API Examples\LabVIEW Examples
This features allows you to run VBAI inspection within your LabVIEW application, an retrieve results that you can send using a TCP implementation of your own in LabVIEW, without having to use the VBAI TCP functionality.
You retain the configuration feature of the Vision part of the application, and can add extra code in LabVIEW.
The API functions allow to basically open an VBAI inspection file, run it synchronously or asynchonously, and retrieve images and results.
As you mentioned, the other solution is to implement your state diagram in LabVIEW and use the Vision Assistant Express VI in different states. What VBAI give you that Vision Assistant doesn't is the pass/fail limits for each step (and the state diagram).
Best regards,
Christophe

Similar Messages

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

Vision Builder Crashes Labview

I have an application where I need to acquire and inspect many high resolution images 3Mp at high throughput.
I'm using:
LabVIEW 8.5.1
NI-Imaq 4.1
Imaqdx 3.2
Vision Builder AI 3.6
ISG 3Mp Camera through Startech 1394a PCI card
In order to meet the cycle rate, I'm trying to multi-thread the application by having one thread that acquires images and enqueues them into another thread that saves them to the hard drive then runs the VBAI inspection. The VBAI inspection then uses the "simulate acquisition" step inorder to load the image from the hard drive and make the appropriate measurements. I've run the application and monitored the processor usage, and the processor seems to stay within 0-80%. However, my application will crash intermittantly.
I've been able to repeat the behavior pretty reliably if I activate/toggle a ring control on my front panel while the cycle is running, and I can't do so if the VBAI thread is not running.
I understand that this is could be a difficult problem to help debug remotely. I'm wondering if there is anyone with similar experience, or some better way for me to creat a high throughput machine vision app with VBAI.
Thanks,
Ryan

Dear Ryan,
You are right, this is difficult to debug remotely, but I can make a suggestion or two. Perhaps you've taken care of these, perhaps not...
One potential downfall with this setup is running into a race condition. If you don't establish data dependency, and make sure that you save and close a particular image before trying to open back up again with VBAI, you could cause the behavior described. Race conditions would be even more of a concern if you were using a certain number of files as an image buffer, and then recycling through them.
What in this ring control? What does the ring control do?
Have you tried generating LabVIEW code from your VBAI inspection, and then encapsulating the VBAI code in a subVI, and just passing your images into that instead of saving them to disk? I would suggest doing this to see if you still experienced the crashes when you are only working in LabVIEW, and without saving and opening images from disk.
Let me know how things go; I hope the above suggestions provide some help.
Best Regards,
~Nate

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

Interfacing Vision Builder with Labview version 7.1

i can't export my design in Vision Builder version 7.0 to Labview version 7.1 using the Create Labview VI under the Tools tab as taught in the demo on this website. please advise. thanks.

Hello,
Most likely, this is due to having a version of Labview that is newer than your Vision Builder / Vision Assistant software. There are updates available for both Vision Builder and Vision Assistant. These updates can be found at:
Vision Assistant 7.0.1 if you previously had Vision Assistant 7.0
Vision Builder for AI 2.0.2 if you previously had Vision Builder AI 2.0
After installing one of the above, everything should work as you saw in the online demonstration.
Hope this helps,
Robert

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

Migracion de Vision Builder a Labview

Buen dia
stoy realizando una inspeccion de una pieza en Vision Builder donde genero steps de Calipter para verificar dimensiones horizontales y verticales.., estos arrojan el resultado en pixeles..
Al migrarlo a LabView, se genera todo normal... pero en ningun lado aparece el dato de los pixeles...
Quisiera saber si estoy omitiendo algun paso..?' o hay que programar algo en labview??..
Muchas gracias,...
Envio un rar con la migracion a LabView 2010 sp1
Attachments:
Inspect Main.vi ‏98 KB

Hola Morenita, gracias por contactarnos,
El problema podría estar en que al momento de generar el código para LabVIEW, Vision Builder pide varios parámetros, como indicadores que va incluir el código. Probablemente te esté faltando activar algún indicador que muestre la información de píxeles que deseas. Si gustas enviarme tu aplicación de Vision Builder y lo revisamos. Te anexo también un tutorial en 3 partes para que tengas documentación a la mano.
Customizing the Inspection Interface in NI Vision Builder for Automated Inspection:
http://www.ni.com/white-paper/6714/en
Saludos!
NavasMonk
National Instruments, México
ELP Support Engineer
www.ni.com/soporte

Vision builder migrating to labview... Many VI

Hi,
I am using the latest version of labview and NI vision builder. By using the Vision builder am getting the X and Y coordinates of the object in that area. I need to export this to labview. I tried by going to "migrate to labview" . Then I created a new folder, then I gave the name. When I click OK. It creates many VI's. I need this in single VI. When I open the "main.VI" i could only see "pass, start" ; when i check the block diagram.I couldn't find the programe that i needed for it.
Hope you have understood my question.
Can you please help me.
Thanks in Advance
Solved!
Go to Solution.

Another option, which could be used in conjunction with the API solution Christophe mentioned is to make your X/Y values shared variables that you update in your VBAI inspection and then read in your LV code. Here's a tutorial on using shared variables to communicate results to LV from VBAI:
http://digital.ni.com/public.nsf/allkb/D492139A746F91A8862576E80051BBCE
Here's a video of how to use the API that Christophe was mentioning:
http://zone.ni.com/wv/app/doc/p/id/wv-2424
Here's a video of using shared variables (demo shows using RT targets, but the same idea would work locally):
http://zone.ni.com/wv/app/doc/p/id/wv-2423

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

NI vision builder AI 关于彩色cable的检测

各位高手你好，首先我是一个彻底新手，请不吝指教！
现在我们要对一个连接器连接的线缆进行颜色是否插错、有无漏插等的检测，请问使用NI Vision Builder AI 这个程序怎么编程？
连接器如附件所示：
附件:
P40911-112654.jpg ‏2388 KB

使用NI Vision Builder AI 需要您有一些Labview编程经验，然后通过范例和帮助文档来使用NI Vision Builder。一种是您找一些书籍自学，还有就是参加NI关于labview和Vison的培训，当然是需要收费的。

Vision builder AI 可以用USB相机并使用外部触发吗

刚刚接触NI的产品，下载了VBAI的评估版，觉得使用非常方便。但碰到一个问题，使用USB相机如何使用外部触发呢？请别笑话，我是用笔记本自带的摄像头测试的。我觉得外部触发通过serial I/O给电脑一个信号，然后电脑采集相机的图象，再作分析检测，应该可以实现。可是找来找去找不到这方面的资料，太困惑了。

Most advanced functions of USB cameras are not supported in Vision Builder or LabVIEW.
Triggering is one of those advanced functions.
Your only option might be to run the camera at maximum speed, and grab the image closest to your trigger point.
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

How to use the examples in IMAQ Vision Builder?

I tried many times to use the examples brought in IMAQ Vision Builder(or LabView 6i ?) or download the similar examples from website of NI in order to learn some skills(I am really new with it!). But Whenever I click the example I want to run and a new dialog window always opened and ask me to find a VI named ???(??? is like for emample: IMAQ Windraw) and I always failed to find this VI!!! Where are this VI or How to use those emamples??? Thank you advanced!!!
Swedlin
[email protected]

Hello Swedlin,
IMAQ WindDraw is a VI that is included in the IMAQ Vision toolkit (see http://sine.ni.com/apps/we/nioc.vp?lang=US&pc=mn&cid=1305 for ordering information).
If you are tring to run examples that include IMAQ WindDraw (or any other functions that are in IMAQ Vision), a dialog message will prompt you locate the VI manually (because the initial search failed).
- Installing IMAQ Vision for LabVIEW will remove the message, and the examples will run.

How to integrate NI Vision Builder and Lab view 8.0

Hi to all.,
I want to integrate NI vision builder and Labview.... Please give me the idea and procedures to be followed........

Hello Tec-sol,
Are you using the Vision Builder for Automated Inspection? If you are, then you can create LabVIEW code. In the configuration interface go to Tools>>Migrate Inspection to LabVIEW. To do this you will need to have the Vision Development module installed.
Or are you using the Vision Builder? Depending on the version of the vision builder you are using you can also generate LabVIEW code.
If you want your code to run in LabVIEW I would suggest that you create your code with the Vision Assistant (this has replaced the Vision Builder, and ships with the Vision Development Module). The Vision Builder for Automated Inspection is intended to be a standalone application.
Regards,
Jasper S

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

NI Vision Builder vs. LabVIEW RT + NI Vision Assistant

Similar Messages

Maybe you are looking for