Conversion of VIs from LabView 2013 to 2011

Hi,
I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
Thank You,
Michal
Solved!
Go to Solution.
Attachments:
main VIs.zip ‏38 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
main VIs 2011.zip ‏27 KB

Similar Messages

  • Please Convert Vis from Labview 2013 to Labview 2011

    Please convert the attached Vis from Labview 2013 to Labview 2011
    Solved!
    Go to Solution.
    Attachments:
    Convert from2013 to 2011.zip ‏255 KB

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

  • Please Convert from LabView 2013 to 2011

    Hello, Could someone please convert these VIs from LV13 to 11 please?
    Thanks, 
    Laura
    Solved!
    Go to Solution.
    Attachments:
    Syringe Pumps New.zip ‏953 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Syringe Pumps New.zip ‏364 KB

  • Labview 2013 missing smtp VIs from Labview 2011

    We are upgrading to LabView 2013 and any VI that we open that uses SMTP is broken. It seems that NI updated the SMTP functionality but do we have to rewrite every VI that was using SMTP to mail emails from our applications? Are the old 2011 VIs avalable in 2013? Two that we use a lot are "SMTP Send Message.vi" and "SMTP Send File.vi". Where can we find these and any others for LabView 2013?

    0utlaw wrote:
    It appears that they've been replaced with the SMTP Email VIs available in Data Communication>>Protocols>>SMTP Email - there's .......  The old functions are still present at <root>\National Instruments\LabVIEW 2013\vi.lib\Utility\SMTP, but don't appear in the palettes.   
    That's actually where I went to look for my SMTP e-mails in LV 2012.  The VI hierarchy path for these VI's is LabVIEW 2012\vi.lib\Utility\SMTP\smtpeml.llb  I thought those were the VI's the original poster was looking for and not finding.
    0utlaw wrote:
    - there's even a nifty-looking Send Email express VI I wasn't aware of.   
    I haven't seen that in 2012.  Maybe that is a new addition to LV2013.

  • From LabVIEW 2013 to 2012

    Convert from LV 2013 to LV2012
    Solved!
    Go to Solution.
    Attachments:
    Generate_Voice_Event.vi ‏35 KB
    Main Voice.vi ‏35 KB
    Text Callback.vi ‏43 KB

    Hi,
    Here it is in LV 2012
    Kees
    Attachments:
    Voice Init Folder.zip ‏131 KB

  • Where to download the exercise VIs from "LabView Basics II"?

    Hello everybody,
    Where can I download the files with sample Vis for "LabVIEW Basics II" course?
    In the company I currently work, they couldn't find these files. I have got only books.
    TIA,
    Yazilim.

    I think you have to purchase it. Contact NI for more information.
    Nam.
    Yazilim wrote in message
    news:[email protected]..
    > Hello everybody,
    > Where can I download the files with sample Vis for "LabVIEW Basics II"
    > course?
    > In the company I currently work, they couldn't find these files. I
    > have got only books.
    > TIA,
    > Yazilim.

  • VIs from LabView libraries not found in .exe built with Application Builder

    I have added VIs that are called by reference to the dynamic vi list in the App Builder, but some of them fail to run because of sub VIs that aren't found at runtime.
    These sub VIs are from the standard LabView libraries. For example: "Open/Create/Replace file.vi", "Write Key (I32).vi", "Open File+.vi" and "Read File+ (string).vi". Also, a typedef "ADC.flx.ctl" can't be found(from the Motion CustomControls library).
    Even if I have those VIs open when I compile all of my VIs (using Ctrl-Shift-Run), they can't be found when I run the executable.
    Brian Smith
    Advanced Light Source
    Lawrence Berkeley National Laboratory

    Are you running the executable on the development machine? If not, make sure that all the required drivers are installed on the target machine (i.e. NI-MOTION etc.).
    The version of the LabVIEW Runtime Engine also has to be the same as the LabVIEW development version.
    Under �Application Builder >> Target >> Build Options� make sure to choose �Single target file...�. This way all sub VIs will be compiled into the executable.
    In LabVIEW 7.1 you can choose to �Disconnect type definitions�� under the �Application Settings� in Application Builder. Does it help to remove the checkmark?
    Best regards,
    Philip C.
    Applications Engineer
    National Instruments
    www.ni.com/ask
    - Philip Courtois, Thinkbot Solutions

  • 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

  • From Labview 9.0 to Labview 8.2.

    I need a conversion, if possible, from Labview 9.0 to Labview 8.2.
    Thank you for the support
    Attachments:
    Write Std Out with Redirection.vi ‏24 KB

    attached
    WARNING: There is a bug in LabVIEW 8.2 where you cannot use the error cluster to chain together the Call Library Function Nodes. You will need to either create wrapper VIs for each CLFN or you will need to use case structures around each call.
    Attachments:
    Write Std Out with Redirection.vi ‏28 KB

  • ODBC from LabVIEW 4.1

    Hi.
    I need to access to odbc database from LabVIEW 4.1. I looked through
    the online reference and found that it looks like that the only way to
    do it is to buy additional pack for accessing the DBases. For me it is
    not the best case, though.
    Is there any other way to work with odbc databases than that?
    Thank you.
    ---Dmitry Rozmanov.

    This was already taken care of here: http://forums.ni.com/t5/Version-Conversion/convert-vi-from-LabVIEW-4-1-to-LabVIEW-2013/td-p/2735335
    For future reference place all of these type of requests in the Version Conversion subforum.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    If someone helped you out, please select their post as the solution and/or give them Kudos!

  • Conversion from LabVIEW 2011 to 8.2

    Dear All
    Can any body help me to convert the attached file from LabVIEW 2011 to LabVIEW 8.2.
    Kind Regards
    Muhammad Irfan
    Solved!
    Go to Solution.
    Attachments:
    LabVIEW 6281-40 Replace.vi ‏76 KB

    This is what the Version Conversion board is for.  But here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    LabVIEW 6281-40 Replace.vi ‏99 KB

  • Conversion from 2013 to 2011

    Hi,
        can you the attached file from 2013 to 2011 version.
    Thank you

    Hello,
    this is a snapshot and it cannot be converted. But the vi's used are present in Labview 2011 also, so you can apply them yourself.
    Best regards,
    K
    https://decibel.ni.com/content/blogs/kl3m3n
    "Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

  • Request for Conversion from labview 4 to labview 2013

    Dear Support,
    Could you please update these vi to be readable by Labview 2013?
    Thank you in advance, Mary

    Mass compiled in 8.2.1, which you can open with 2013.
    One of the VIs kept crashing my LabVIEW, so it is not included in this zip file.

  • Convert from LabVIEW 2011 to LabVIEW 9.0

    Please convert from LabVIEW 2011 to LabVIEW 9.0
    Attachments:
    Watlow Vis.zip ‏76 KB

    Looks like somebody forgot to attach the zip file.  Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Watflow.zip ‏57 KB

  • Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installati​on package for Run-Time Engine 7.0

    I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit).  The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading.  I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013.  Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0.  If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
    I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected).  How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0?  Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    Are you running your VI from a Project?  If so, you can look at Dependencies and get an idea what "dependent" VIs you might have.  There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
    If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it.  If all of your relevant VIs are in a single folder, add the entire folder.  Now look in Dependencies.
    BS
    Yes I am running the VI from within a LV Project.  After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
    1.  Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
    2.  Restart the PC
    3.  Open the project, close the project choosing to "save all"
    4.  Restart the PC
    5.  Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
    6.  Restart the PC
    7.  Open the project, close the project choosing to "save all"
    8.  Open the project and run the VI.  No more messages about LabVIEW trying to find Run-Time Engine 7.0.

Maybe you are looking for