LabVIEW 2012 LLB for VBAI 2011

Hi
I'm trying to build some labview vi's in LabVIEW 2012, to be compatible with Vision Builder AI 2011. I want to include some shared variables. I have the library file containing a string shared variable and a labview VI with just a string control into the shared variable. This is to read text from the vision build inspection. Both the library and the vi is saved under version 2010 but when I try to make a LLB file, the versions change to 2012 again. Do you have any inpute into why this could be?
Cheers.

You need to use the LV project to create a source distribution that includes all the dependencies (including vi.lib). Then close out LV 2012 to make sure you don't accidentally get any cross linking. Open the main VI of your built LLB with LV 2012 and then go to File>>Save for Previous. If there are any licensed VIs from vi.lib included, those may not save for previous, but I think this is what you should try to do.
I'm not sure exactly what you are trying to do, but if you want to use shared variables, VBAI (2010 or later) can update a shared variable with it's results (or read the variable if you want to pass data to VBAI), and then any version of LV can read/write that shared variable because shared variables are not LV version specific so you don't have to have the same version of LV to read/write shared variables. If this is all you want to do, you could just keep your LV code in LV 2012 and read/write the variable that is used by VBAI 2011. You can also use the VBAI API to control the inspection from any version of LV 2010 or higher regardless of the version of VBAI. You can see an example here:
C:\Program Files (x86)\National Instruments\Vision Builder AI XXXX\API Examples\LabVIEW Examples
Let us know if this still does not address your question and provide more details if this doesn't help.
Thanks,
Brad

Similar Messages

  • Convert TCPIP_Nagle_algorithm.zip from LabVIEW 2012 to LabVIEW 2011

    Hello,
    can somebody convert the VIs in the zip file from LabVIEW 2012 to LabVIEW 2011 please. I need them to study.
    Thank you very much for your support.
    Solved!
    Go to Solution.
    Attachments:
    TCPIP_Nagle_algorithm.zip ‏63 KB

    Additionally I am sorry that I have put my post in LabVIEW and not under Version Conversion

  • Labview 2012 to 2011

    Hi,
    Could anyone convert this labview 2012 driver to labview 2011?
    Thank you in advance.
    Attachments:
    hp4195.zip ‏263 KB

    Saved for 2011.
    Adam
    CLD & CTD
    Attachments:
    hp4195_2011.zip ‏177 KB

  • VBAI 2011, possible to migrate directly to LabVIEW 8.6 code?

    Hi,
    Just wondering if VBAI 2011 can migrate inspections directly to LabVIEW 8.6 code.  I have installed on my computer:
    VBAI 2011
    LabVIEW 8.6
    LabVIEW 2010
    LabVIEW 2011
    NI Vision Development Module 2011
    I don't see the option for LabVIEW 8.6 on my menu.  Any suggestions?
    John Wu
    Riobotics Consulting
    Solved!
    Go to Solution.
    Attachments:
    problem.png ‏34 KB

    I encourage you to look at the Vision Builder AI LabVIEW API, which is supported in LabVIEW 8.6.
    This feature allow you to control Vision Builder AI from LabVIEW (open inspection, run once, get results etc.)
    Unless your application requires really tight hardware integration, with hardware that you can only do in LabVIEW code, the code you're going to write with the API will be much cleaner than working with the code generated, which is somehow complex.
    Look at the examples located here:
    C:\Program Files (x86)\National Instruments\Vision Builder AI 2011\API Examples\LabVIEW Examples
    Best regards,
    Christophe

  • Installing NI-USRP for LabVIEW 2012

    It's been a few months since LabVIEW 2012 was released. Is there a supported way to install NI-USRP support for LabVIEW 2012 or does a new installer of NI-USRP need to be released? As of right now, NI-USRP 1.1 is available and installs support up to LabVIEW 2011 but not LabVIEW 2012.
    Thank you!
    Dr. Spaceman
    "Really? I think you mean radio."

    Dr Spaceman,
    Generally we recommend that most people use the 32 bit version of LabVIEW unless they are planning on using our vision software. Many of our toolkits and modules only work with LabVIEW 32 bit. This article talks more about the difference between 32 bit and 64 bit. http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
    Regards,
    Leah
    "All right, now that the popsicle's melted we've got ourselves a tongue depressor."
    Regards,
    Leah
    National Instruments
    Applications Engineer

  • Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

    Hello,
    I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
    I'm confused; did I accidentally install LV 2011 too?
    Thanks
    Solved!
    Go to Solution.

    Also, some addons use older RunTime Engines.  It is not suprising that you need the 2011 RTE patch.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • After Replace queue.llb and notifier.llb for LabVIEW 6.1, I can't use find examples.vi any more.

    After Replace queue.llb and notifier.llb for LabVIEW 6.1, I can't use find examples.vi any more.Error list shows that SubVI 'EF-remove queue element with exit or error stop vi': subVI is not executable.
    Attachments:
    snap158.gif ‏13 KB

    I believe that by your action, you removed the compatability VIs and it would appear that the Find Examples used the older queue functions that require the compatability VIs. I would suggest you revert back to the LLBs that were distributed with 6.1. The new queue functions are there for you to use in new development and older VIs won't be broken. You could also make a request to NI support to see about an updated Find Example that uses just the new VIs.

  • File conversion of LabView 2012 to 2011

    Hello ,
     I am new to Lab View. I am stuck with conversion of this file from LabView 2012 to 2011 .Help is very much appreciated
    Thank you ,
    With Regards,
    Jagadish
    Solved!
    Go to Solution.
    Attachments:
    kiran_prob2.vi ‏7 KB

    duplicate post

  • Please Convert tktds5xx from LabView 2012 to LabView 2011.

    I was directed here to have an instrument driver converted from LabView 2012 to LabView 2011.
    Thanks in advance!
    Solved!
    Go to Solution.
    Attachments:
    tktds5xx.zip ‏777 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Attachments:
    tktds5xx.zip ‏529 KB

  • OpenG Toolkit for LabVIEW 2012?

    I'm trying to install OpenG Tooklit using VI Package Manager. The LabVIEW 2012 is registered in VIPM and VIPM successfully connects to LabVIEW. But when I'm trying to install the package, VIPM says that "This package is not compatible with your operating system or any LabVIEW version installed on your computer".
    The package is displayed in LabVIEW tool network VIPM window where I get from the LabVIEW's welcome screen. I don't understand what I'm doing wrong. Any idea?

    I do not know if VIPM can install packages without Admin rights.  It places files in the Program Files folder and this may not be allowed if you aren't an administrator.
    This is not a VIPM or JKI forum.  You are welcome to ask questions regarding VIPM here but you may get more support over at the VIPM Forum.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Driver NI PXIe 5641r for Labview 2012

    hi. i have module NI PXIe 5641r and labview 2012, i installed driver NI PXIe 5641r; however this driver did not support labview 2012 softwave. help me please!

    Hello!
    You should be able to download the PXIe-5640R 1.7 to work with your PXIe-5641R. Here is a link to that driver:
    http://www.ni.com/download/ni-5640r-1.7/4371/en/
    According to the readme, this will work with a PXIe-5641R as well as 32-bit LabVIEW 2012. Hopefully this helps!
    Thanks,
    Stephanie S.
    Application Engineer
    National Instruments

  • Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

    Hi,
    I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
    On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated. 
    Please see the attached images for more details.
    Thanks
    Attachments:
    1.png ‏33 KB
    2.png ‏71 KB
    3.png ‏40 KB

    Check out this thread.  It looks like someone else ran into a similar issue and made changes that fixed their application.
    http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
    Jeff B.
    Applications Engineer
    National Instruments

  • Compatibility of LabView 2012 installed on XP with Vision and Trad DAQ

    Is LabView 2012 runnung under Windows XP compatible with
    A: NI Vision 2011 ? 
    B: Traditional DAQ 7.4.4 ?

    This should answer your question:
    Windows Version Compatibility with LabVIEW
    Compatible Versions of Vision Development Module with LabVIEW and LabWindows/CVI
    NI-IMAQ, NI-IMAQdx, NI-IMAQ I/O, and VAS Compatibility with Different LabVIEW Versions
    NI-DAQ and LabVIEW Version Compatibility (for Windows)
    I would still suggest to have a look at the readme files as well.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • LabView 2012 Security System Main vi's have error 200559

    The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step 
    is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
    Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current 
    version of LabVIEW.  http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
     I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
    I  appreciate help from any one.
    Ali Tariq Bhatti
    Ali Tariq Bhatti
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    NI ELVIS II Security System VIs (2).zip ‏313 KB
    Error 200559.docx ‏500 KB

    RavensFan,
    I) Yes, I open up the front panel of the Express VI's and probe into them.
    2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
    3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
    4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    did probes for Export Press and Key vi's file.docx ‏340 KB

  • What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

    OK.  Just to be clear.  I am a complete newb to ANYTHING LabVIEW or LabWindows related.  I am a programmer, but I have never used any version ever.  That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date.  The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1.  You can just imagine how ancient this is by today's standard.
    Have I set the stage properly?  I hope so.  Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
    Now here is what I "think" I know about what is required.  Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle.  I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
    Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.  
    What exactly do I need to zip up and what can I leave out? 
    Are there LabVIEW vi and llb files in a "project" that are not needed? 
    Are there any setup/configuration/project specific files I need to include? 
    Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
    Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date.  Is there any way I can send my files to a specific NI guru via email instead of just posting them?
    Solved!
    Go to Solution.

    So if I understand you correctly,  all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
    Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this?  Once done, LabVIEW 2012 will then allow me to open them and do what I need to do?  Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
    When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files?  Based on what is installed on that NT v4.0 system, we have the following items installed:
    NI VISA
    NI ComponentWorks 3D Graph
    NI DataSocket
    NI LabVIEW 5.1.1 Advanced Analysis Library
    NI LabVIEW RTE 5.1.1
    NI LabVIEW v5.1.1
    NI Measurement and Auto Explorer 1.1
    NI-488 2.1.60
    NI-DAQ 6.6
    NI-PAL 1.3.110
    NI-Reports
    NI-VXI/VISA
    You mention DAQ.  Our program uses NI DAQ v6.6 now.  I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now? 
    Thanks for your help so far.  If we had a support contract in place, this wouldn't be an issue.  However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest.  However, I am specifically not allowed to just place the files on a public forum for all to see.  It just isn't done.  We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.   
    I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself.    Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

Maybe you are looking for