LabVIEW version for Vision Builder AI 2012 plugins

Hi all,
Ii was a bit of a challenge to find out which version of LabVIEW was necessary to develop custom plugins for Vision Builder AI 2012, I found it by starting the installler, it is LabVIEW 2011 (but I wish I could find this information in Vision Builder AI 2012 readme file).
Now my question is : is it possible to use LabVIEW 2011 SP1 to develop custom plugins for Vision Builder AI 2012?
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
Go to Solution.

Right... I tried, I installed all the VBAI and LabVIEW versions I could.
I turns out LV 2011 sp1 is just an upgrade of 2011 and as such LV2011 SP1 can be used to develop custom plugins for Vision Builder AI 2012.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Similar Messages

  • Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1.  I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported.  Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later.  The Vision RTE version should correspond to the version of Vision you are using.  For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed.  With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
    Ryan M.
    Applications Engineer

  • Run-time License for Vision builder

    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.
    Ninad Regundwar
    Junior Engineer | ARAV Technologies |

    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,

  • Vision builder migrating to labview... Many VI

     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
    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:​F91A8862576E80051BBCE
    Here's a video of how to use the API that Christophe was mentioning:
    Here's a video of using shared variables (demo shows using RT targets, but the same idea would work locally):

  • Speeding up LabVIEW scripts generated by IMAQ Vision Builder

    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 Ammons
    Ammons Engineering

  • Which LabVIEW version is used for CLA exam?

    The CLA Exam Preparation Guide (link) states that LabVIEW 2009 will be installed on the test computer.  Is this still true?  If not, is there an official "Current LabVIEW Version for Certification Exams" link/document that is updated when it changes?  If not, there should be - this seems to come up a lot.
    I'm writing the exam at NI week, if that matters.

    I used 2010. But it shouldn't really matter that much. I can not think of anything in 2010 that would have made the test any different.
    LabVIEW 2012

  • Vision builder 2.6 general/tutorial

    I'm slowly trying to learn the functions of image acquisition and processing with LabVIEW.  So far, I've stepped through some basic tutorials of LabVIEW (check).  Next I installed some NI-IMAQ components and attempted to look at some examples (half check).  Finally, I have found Vision Builder; unfortunately, I do not have a copy of the latest version and I'm forced to use a trial version of Vision Builder 2.6.
    At this point, I'm kinda stuck because I can't seem to find any good Vision Builder tutorials.  I understand that the program itself comes with a few example programs, but it doesn't help to much if it doesn't go through each building step.  National Instruments has some video tutorials online, but it looks like the tutorials are with respect to new versions of Vision Builder with differing interfaces.
    Finally, my reason for resorting to Vision Builder is because I downloaded some LabVIEW image processing tutorials, but some of the's were missing (IMAQ mult, IMAQ sub).  So as a result, I was unable to step through the projects, or observe how they functioned.  I downloaded Vision Builder because someone mentioned that it might update my .vi library so I could run these image processing programs.  But now I'm still unable to run these programs, and I have another program that I need to learn.
    Does anyone have any recommendations of tutorial sites, or pages that might help get me started with Vision Builder?  Or possibly any general suggestions about how to go about programming a vision processing program (maybe I'm not understanding the process correctly)?

    Well it looks like no one replied to this post.
    Just for a future reference (if anyone else has a question like this)
    I called National Instruments and talked with one of their applications engineers.  This description of the products helped me get a better understanding of how each one works, etc.
    LabVIEW is Lower level programming that involves customization of user interfaces, peripheral device control, and data manipulation.  LabVIEW is the center piece of the National Instruments software that will integrate code from other NI products.
    IMAQ is a supplemental package that can be added on to LabVIEW for additional functionality.  IMAQ provides LabVIEW with a library of image acquisition functions.
    Vision Assistant functions much like LabVIEW itself.  The Vision Assistant provides the user with image processing functions which clean/restore/manipulate an image so that it can be handled in LabVIEW or the Vision Builder.  Vision Assistant code can be exported so that it can be handled by LabVIEW.
    Vision Builder is a complete control/programming module in and of itself.  The program interface provides a high level programming design which controls the image acquisition, all the way through the image processing.  Vision Builder also contains the Vision Assistant.
    Vision Development Module is a combination of the Vision Assistant and the Vision Builder.  First off, the module provides LabVIEW with an extensive library that contains many of the image processing functions that is included with Vision Assistant.  Secondly, the program also has an embedded Vision Builder program, that gives the user the option of a provided UI, or self developed UI through LabVIEW.  The Vision Development Module is a complete package of vision acquisition and processing software.

  • Vision Builder key navigation​(toggle)

    I'm wondering if you can assign a key (ex: enter, F1, F2) to a button in the user interface for vision builder.
    I know LabView allows users to assign a key toggle to the buttons; can you do that in Vision Builder?
    If not, is there any way that i can use keyboard to control the user interface buttons?
    Thank you

    Hi Jon,
    Unfortunately to my knowledge we can not assign keys to toggle booleans in VBAI.  If this is something you are highly interested in, you may want to create a feature request at the LabVIEW idea exchange so it can be considered for future versions.​s
    Cole R.
    National Instruments
    Applications Engineer

  • Integrate Vision Builder 2009 (VBAI), into Test Stand 4.2.1?

    Does anyone know of an easy way to integrate Vision Builder 2009 (VBAI), into Test Stand 4.2.1?
    earlier versions of Vision Builder seem to accomidate this very easily.  But i have not found the same ease to make this work in the newest version.  any ideas?

    Thanks a lot for your support.
    Well...yes I followed the instructions in the ReadMe.html file.
    I have loaded the sequence "Vision Builder AI TestStand Examples.seq" into TestStand.
    TestStand crashes after some delay  when trying to select the first test step "Run Inspection once".
    TestStand obviously has problems loading the Vision Builder API functions and the engine (whatever is necessary).
    As I could not succeed testing VBAI 2010 from TestStand, I then tried the LabVIEW example which is also located
    in the \examples folder.
    I had no problems loading the "LabVIEW API Examples (Local).vi" into LabVIEW 2010 and execute it.
    This example works without any problems with a simple USB Webcam.
    I can test different "Inspections" and studied the API functions in this VI.
    So the problem is only related to TestStand.
    I am wondering whether TestStand has problems with the evaluation version of VBAI 2010.
    When executing the LabVIEW example the VBAI engine asks me first if I want to evaluate the software (as it is not activated yet).
    I never reach this point from TestStand. It crashes before.
    Another point is that I am asking myself why the test step "Run Inspection Once" is the first test step the TestStand sequence.
    Comparing the sequence of steps with the LabVIEW VI, you can see that there is a differnce in the initialisation sequence.
    The LabVIEW VI launches "VBAI Interface - Launch VBAI" first before all other API VIs.
    I could try to change the TestStand sequence and introduce additional initialisation steps before "Run Inspection Once".
    I simply fear that TestStand crahses again before I have been able to change the sequence.
    Ok...another thought...on your system it is working fine using the example TestStand sequence?
    This means that the initialisation of the VBAI engine is automatically executed.
    Which process is responsible to initialise the VBAI engine in TestStand?
    Perhaps I have to configure something ...somewhere in TestStand.
    Ok... that's it for now... i will try out a couple of things....
    Thanks again for your support
    Best regards,

  • What are developers​' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

    I have a large set of code that I've painstakingly migrated from one labview version to another over the years.  I have lots of deployed applications that I need to continue to support.  From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward.  Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again.  That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example.  Compatibility is often being sacrificed so NI can develop labview in the direction they choose.  So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
    In light of this, how are other developers managing older applicatiosn written in older versions of labview.  Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate.  I strongly recommend this approach.  But keeping my large libraries of code separate is tough.  They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi.  Are other people also trying to maintain separate copies of all their code in different labview versions?  How are other people managing this problem?
    I got 99 problems but 8.6 ain't one.
    Go to Solution.

    The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
    Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables.  All distributables required to reproduce a test-station should be located under <Production>.
    | <Common>
    | | <LabVIEW_61>
    | | | <Drivers>
    | | | | <DMM>
    | | | | <OS>
    | | | | <PS>
    | | | <Utilities>
    | | |   <File>
    | | |   <Error>
    | | |   <String>
    | | <LabVIEW_711>
    | | <LabVIEW_82>
    | | <LabVIEW_851>
    * Program-specific applications that (probably) have distributables
    | <Program_#1>
    | | <Application_#1>
    | |   <Docs>
    | |   <Source>
    *       Individual, application-specific, VIs go here
    | | <Application_#2>
    | | <Application_#3>
    | <Program_2>
    | | <Program_3>
    | <Tools>
    *   Tools are NOT "program"-specific, and, may have distributables
    |   <SomeTool>
    |   <SomeOtherTool>
    | <COTS&Freeware>
    | <Programs>
    | | <Program_1>
    | | | <Application_#1>
    | | | | <Application_#1_Rev#1>
    | | | |   Application_#1.bld>
    | | | |   <EXE>
    | | | |   <Installer>
    | | | |   <Source>
    | | | |     Application_#1.llb>
    *           Distributable is created from LLB "snapshot", not directly from development tree
    | | | <Application_#2>
    | | | | <Application_#2_Rev#1>
    | | | |    Application_#2.lvproj>
    | | | |   <EXE>
    | | | |   <Installer>
    | | | |   <Source>
    | | | |     Application_#2.llb>
    | <Tools>
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    StyleGuide.doc ‏941 KB

  • Registration of several reference images in a test image using vision builder

    I have downloaded the trial version of vision builder, and I am attempting a test to determine if it's worth buying:
    I would like to determine the position and orientation of two reference parts within a set of test images.  I am able to load the reference images, obtain the grayscale, perform appropriate filters, determine their global orientation based on some straight lines, and select the desired ROI's that I would like to match up.  I am also able to load in a test image, take the grayscale, and filter it.  My state diagram has three heads with the three loading steps that converge. This all seems to be great, but how do I find the position and orientation of the reference ROI's within the test image? 
    I would like to use something like the geometric matching tool, but it only seems to work on using a part of a first image on subsequent images in the same folder.  I suppose I could use my reference as the first image in the folder, then loop through the remaining ones, but...
    Once I find the position and orientation of the first reference in the test image, I would then like to find the position and orientation of the second reference in the same test image, then report values like relative distances and angles between these found references.
    Does this mean I need two folders, with their own reference image and the same set of test images?  Would I combine the geometric matching results using some variables or math functions?
    What is the best way to perform this image registration in vision builder?

    Thank you for your interest in Vision Builder AI.  If I understand what you are trying to do, you are looking to compare the position locations of two separate parts in an image.  We have a tool that does this very well.  If you use the pattern matching to find both instances of the part, you should be able to determine the distance and angle between them relatively easily.  To do this, you will need to find an edge in between the two so that you can justify the angle between them, and then simply use a few Geometry functions to actually find the angle.  To record this information, you can simply use a Data Logging step to write your findings to file.  
    If you are looking for a more complete analysis on how you might be able to do this, you will need the Vision Assistant on your computer (if you do not have it already, you can get it by downloading a free trial of our Vision Development Module).  In the Vision Assistant splash screen, click on the Solution Wizard.  This pulls up a menu.  From there, go to Tutorial » Bracket Inspection.  Click Load Solution.  If you step through that example, this displays how to do what you are looking to do with the Vision Assistant, but it should be no different at all in Vision Builder AI.  Hopefully this helps.
    Keith M.
    Applications Engineer


    I try to do 9 point calibration by using run labview method in Vision builder .
    here i tried teo labview files here Reference working (it gives in mm) (here i am not assigning 9 points )
    Reference file i did invidual points to so that i can enter directly 9 point and real world ..
    but its not working .
    Is there anyway to 9 point calibraiton in vision builder .
    if i have to use run labview step means .. please give me vi file to to enter 9 points (from set variable )
    Attachments: ‏12 KB ‏23 KB

    I'm using Flash Builder 4.7 for a pure flash project (ie, no mxml) & all my graphics objects are in a swc that was exported from an FLA. 
    I've made some progress with that issue. If I explicitly assign the scale9Grid dimensions in the code, it seems to work:
      obj.scale9Grid = new Rectangle(x,y,w,h)
    ...but having to do that is a real productivity killer.  Would be nice to use the 9-slice guide setting in the FLA

  • Open labview versions till 7.x with 8.5

    I've update my labview version for 8.5. Uninstalling the previous version in other to avoid some complications in the future that can be caused by the mix of versions (that's what I think).
    But the first problem that I've found it's that I can open vi's made on versions till 7.x.
    In this specific case. i can't open the
    How can I turn around this problem without installing old versions of labview?
    Software developer
    PS: Don't forget to rate a good anwser ; )
    Currently using Labview 2011

    Jorge Amaral wrote:
    Uninstalling the previous version in other to avoid some complications in the future that can be caused by the mix of versions (that's what I think).
    Hi Jorge,
    That's an interesting problem that you posted... Glad you found a solution.
    As for multiple LV installations, I have on one PC LV7.0, LV7.1, LV8.2 and LV8.5.  Furthermore, you can open different releases at the same time (ie: work on both LV7.1 & 8.2 at the same time).  They do not seem to interfere with one another and I think that it's rather common to have multiple installs. So theres really no need to remove a past installation when upgrading to a new (major) release.. 

  • 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??

    LabVIEW and Vision Builder run fine on the same computer.  I have several versions of each on mine with no problems.
    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...
    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

Maybe you are looking for