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

Similar Messages

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

Vision builder AI ve labview IMAQ görüntü alma hız farkı ?

merhabalar
firewire 1394b kameradan vision builder ile görüntü alıp labview'e migrate ediyorum. bundan ayrı olarak labview içerisinde imaq kütüpanesini kullanarak görüntü alıyorum. migrate ettiğim vision builder kodu daha yoğun olmasına rağmen daha hızlı görüntü alıyor. Bunun temel kaynağı nedir acaba.
Eğer Vision builder dan migrate ettiğim kodları kullanırsam kamera shutter değerini değiştirmeme izin verilmiyor.
Teşekkür ederim.
Solved!
Go to Solution.

merhaba sitede mevcut örnekleri denerken buldum. ben snap komutunu kullanıyordum. grab komutu ile desteklenen hızdagörüntü alabildim. Örnekler ektedir.
teşekkür ederim.
Attachments:
IMAQ grab 2010.vi ‏36 KB
IMAQ grab 2011.vi ‏41 KB
IMAQ snap 2010.vi ‏36 KB

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

Speeding up LabVIEW scripts generated by IMAQ Vision Builder

Hi,
I am an experienced c++ software developer, I have mainly used Microsoft's Visual Studio for development. Now, I am developing a real time application using LabView and IMAQ Vision Builder. The LabView application I developed calls a script that was generated by IMAQ vision builder...the application works, but it is too slow for the processing I need to do. In C++ I wouldn't have any trouble speeding the application up, but I am still learning how labview handles threads etc. Does anyone have any ideas?

Your question is very difficult to answer. Without knowing anything about the processing you are doing, I can't suggest anything to increase the speed.
Vision Builder does not produce the most efficient code possible. It is likely that the algorithm could be improved, but this really depends on what you are doing. It is also possible that your acquisition could be what is slowing you down, especially if you are using Snap.
Perhaps if you post the code generated by Vision Builder it will be possible to help you more.
Bruce
Bruce Ammons
Ammons Engineering

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

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

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

Functions in IMAQ Vision for Labview same as those in Vision Builder?

Hi all...
i just have a simple question..Does IMAQ Vision for Labview has the same functions of Vision Builder?
I know that with Vision Builder you can develop an application interactively...but does it has more functions than IMAQ Vision?
So if i buy IMAQ Vision can i develop the same kind of applications that i would make with Vision Builder?
I´m specially interested in color matching and color analisys functions.
Thanks

IMAQ Vision has much more than Vision Builder. Basically, VB was created using Vision and they implemented a good number of the functions in a menu driven format. However, there are many more functions available that were not integrated into VB.
Vision does have some good color matching and analysis tools.
Bruce
Bruce Ammons
Ammons Engineering

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

Vision builder AI 2011 incompatible with Vis created by Labview 2011 ?

Hi,
I have some issues to drive some motor by a Vi created under Labview 2011 using an inspection built under vision builder AI 2011
The step for running a Labview Vi said me that it only support 2010 VIs or earlier ? How two NI softwares 2011 can be incompatible ?
So I try to save under a old version but this vi is part of a huge LLB...Is it possible to save this LLB as a 2010 version without saving all subvis .ctl etc.. ? I am a little confused...
Thank you for your help

You should be able to save the top level VI for previous to LV 2010, and all VIs from that LLB will also be saved to a LV 2010 version LLB that can be used by VBAI. There is a restriction that any VIs from a toolkit that you have to pay for (i.e. Vision), even if they are in your LLB will not be saved for previous, but driver VIs (i.e. Motion, DAQ, NI-IMAQ) if they are in your LLB will be saved in the resulting LV 2010 LLB.
I realize this isn't ideal and VBAI will be supporting LV 2011 or a future version later. Another option will be to use the VBAI API in LV 2011 to have VBAI do just the image processing portion of your control system and do Motion, or other functionality in LV environment and control VBAI from LV using the VBAI API (this allows you to load inspections, run them, get images, and results, etc.), which does support LV 2011.
Hope this helps,
Brad

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

Vision builder migrating to labview... Many VI

Similar Messages

Maybe you are looking for