LabVIEW 2014 to LabVIEW 2012

Hello there, 
Would you convert my LabVIEW 2014 vi's as available for LabVIEW 2012 ? 
Thanks for your all support 

Here you go.

Similar Messages

  • Conversion from LabVIEW 2014 to LabVIEW 2012

    Couls someone convert me this file from LB 2014 to the 2012 version, please?
    Solved!
    Go to Solution.
    Attachments:
    Ejercicio Optativo.vi ‏38 KB

    Saved for 2012.
    Adam
    CLD & CTD
    Attachments:
    Ejercicio Optativo.vi ‏27 KB

  • LabVIEW 2014 to LabVIEW 8.2

    I would be most appreciative if someone would convert these LabVIEW 2014 files to LabVIEW 8.2.
    Many thanks,
                          Rufus

    At the end of the day, the project file is not necessary.  So I no longer need a converted copy of the project file.  I see now that my interest lies chiefly in the other two files that I posted, DGE Control User Version 090514 and Read 9219 User Version 080114.  Were you able to convert both of these to LabVIEW 8.2?
     

  • Labview 2014 to Labview 2013

    HI,
    Please help down revert the attached vi.
    THanks.
    Attachments:
    usbsimplecommand (4).vi ‏24 KB

    LV13
    Attachments:
    usbsimplecommandLV13.vi ‏22 KB

  • Conversion LabVIEW 2014 to LV 2013

    Hello. please help me by converting this program from LabVIEW 2014 to LabVIEW 2013 version. This file is very important for me and you will help me a lot. Thx.
    Solved!
    Go to Solution.
    Attachments:
    alarm_2.vi ‏17 KB

    Here you go.  There is a missing subVI though.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    alarm_2.zip ‏10 KB

  • LabVIEW 2014 array constant change

    Why did the "graying out" of array constants change between LabVIEW 2014 and LabVIEW 2013? In 2014 the effect is much more subtle and it's far harder to tell the # of elements in an array constant. Please change this back ASAP!

    My only thought was that they tried to make the disabled elements more readable.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Disabled Elements.PNG ‏24 KB

  • Compile 9076 with LabVIEW 2014 Worked good with 2012 SP1

    An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
    Error 7 occurred at Open VI Reference in nirviOpenVIRefByNameOrPath.vi->niFpgaRemapObjsAndListIfUnderXNode.vi->niFpgaRemapObjsHandleXNodeSubErrors.vi->nirviMassageErrorList.vi->niFpgaErrorDialog_ParseErrors.vi->niFpgaErrorDialog_ReadErrorData.vi->niFpgaGenerateCode_ErrorDialog.vi
    Possible reason(s):
    LabVIEW:  File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
    VI Path: C:\Program Files\National Instruments\LabVIEW 2014\rvi\CodeGenErrorUtilities\Diagram Constant
    All text parsed:
    <CodegenErrorList>
              <CodeGenErr>
                <ErrorCode>-64001</ErrorCode>
                <DynamicText>
                  <TreeLineInfo>
                    <TreeInfo>
                      <TreeID>1</TreeID>
                    </TreeInfo>
                  </TreeLineInfo>
                </DynamicText>
              </CodeGenErr>
              <CodeGenErr>
                <ErrorCode>-64001</ErrorCode>
                <DynamicText>
                  <TreeLineInfo>
                    <TreeInfo>
                      <TreeID>1</TreeID>
                    </TreeInfo>
                  </TreeLineInfo>
                </DynamicText>
              </CodeGenErr>
              <CodeGenErr>

    Hi Nieman,
    You have the right compilers for your FPGA targets, based on KB 609GUVBT.
    Error -64001 indicates that there is an issue with one of the nodes in your VI. Since you are able to compile a blank FPGA VI, then you should try to identify the node that is causing this problem. When trying to pinpoint this node, I’d recommend executing your FPGA VI with simulated I/O on the development machine, as described in KB 3W6EFRLX,
    Also, are you able to reproduce this issue when running one of the LabVIEW Example Finder FPGA VIs that targets your NI 9076? You can find these examples in the Example Finder's  Hardware Input and Output>>CompactRIO section.
    Regards,
    Tunde S.
    Applications Engineer
    National Instruments

  • Labview 2014 Excel Active X Property Nodes disabled - Why?

    Hello,
    I am using Labview 2014 and want to open, write to and close Excel by the use of Active X.
    I am confronted with the problem, that, if connecting (Active X-) property nodes to the references (e.g. "Excel_Application"), right-clicking on the context menue doesn´t let me choose any properties, the item is disabled (one can read in German "Keine Eigenschaften" (no properties)).
    How can I resolve this? What am I doing wrong?
    Thank you!

    I am having the same problem.  When I left click to choose/change the property I do not get a list - instead I get the greyed No Properties popup - see screenshot.
    If I drag and drop an existing property node from within an example subVI it connects to the reference and keeps showing the current property but I cannot change to a different one.
    I am using LV 2012, Win7, Office 2013.
    When I try with LV 2012, Win7, Office 2010, it works properly.  So my guess is that is has to do with the version of office.  But I would like to know the reason why as well.
    Attachments:
    NoProperties.png ‏67 KB

  • When replacing Labview 2013 with Labview 2014, do I firstly need to uninstall Labview 2013?

    I have just recieved my latest version Labview 2014 CD.
    When installing this new version, do I firstly need to uninstall previous Labview versions?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    The reverse, however, is not true.  Once you install one version of LabVIEW, you cannot install an older version without uninstalling everything and "starting over".  Be warned ...
    Not exactly true.  You can install just an older version of LabVIEW.  I have had LabVIEW 2012, 2013, and 2014 installed on a computer and then installed 8.2.1.  It is all of the support drivers and what not that do not install side-by-side.  So the real lesson here is that if you install an older version of LabVIEW, pray that your current drivers support that version of LabVIEW.  You will need to reinstall the drivers to install the support for the older version of LabVIEW though.  Installing just the support takes hardly any time.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Como puedo instalar ISDB-T/Tb Digital Video Signal Generation Toolkit - MaxEye Technologies en labview 2014

    Hola me gustaria que me ayuden con un problema que tengo, descargue  ISDB-T/Tb Digital Video Signal Generation Toolkit - MaxEye Technologies evaluation pero cuando lo quiero instalar me aparece un mensaje diciendo que primero debo instalar labview 2012 pero yo tengo labview 2014, como puedo instalar esta herramienta sin tener que cambiar la version de mi labview?

    Saludos Mafilu,
    Gracias por utilizar los Foros de Discusión de National Instruments, con respecto a tu consulta creo que lo mejor será que contactes directamente al equipo de soporte de MaxEye Technologies para corroborar si existe alguna necesidad especial, o bien, si tienen alguna alternativa.
    Support Information
    For technical support, contact MaxEye Technologies at:
    Phone: +91-80-2527-0024, +91-94-4806-7717
    Email: [email protected], [email protected]
    Web: maxeyetech.com
    Quedo al pendiente, saludos.
    David P.
    National Instruments
    Applications Engineer
    www.ni.com/soporte

  • New LabVIEW 2014 Tray Icon

    I now have LabVIEW 2104 on my Windows PC and love the new Tray Icon.  Can somebody produce an Icon file for the other labview versions? I don't have the tools or the skill.
    I have LabVIEW 2009, 2010, 2011, 2012, 2013 as well as the new 2014 (see Below).
    Ken

    http://forums.ni.com/t5/LabVIEW/How-To-Setup-your-LV-Icons-so-you-can-tell-versions-apart/m-p/125285...
    Try to take over the world!

  • Open vi reference conversion from Labview 6 to Labview 2014

    Is there a way that someone can help me convert this VI written in Labview 6.1  so that I can work en EXE in Labview 2014.
    I succed to open this vi from 6.1 to 2014 but it does not run. The open vi reference those not work in exe program. Someone know how I can  replace that function...
    Thanks!
    Solved!
    Go to Solution.
    Attachments:
    to convert 2104.zip ‏17 KB

    Error 7 is File Not Found.  So your dynamically called VI is not in your executable.
    In the build spec for the executable in your project, there is a section for "Source Files".  On of the options for the VIs is "Always Include".
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Making labview 2014 and Access 2013 db working correctly

    Hi all,
    i'm trying to gain access to a database created by Access 2013 from Labview 2014. Since we dont want to buy the NI toolkit i thought to use the old LabSQL library. Has anyone tried to do the same thing or give me some hints about it?
    Actually i have tryed to run the example shipped with LabSQL but i received an error:
    Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][Driver Manager ODBC] Nome origine dati non trovato e driver predefinito non specificato. in ADO Connection Open.vi->Example - Fetch a Table.vi
    Reading the README file of the LabSQL i found this:
    2. As with any database application on Windows, you'll need to create a DSN (Data Source Name) in the ODBC control panel. This DSN is used in your LabVIEW application to connect to the appropriate database. If you want to set up the example database, do the following:
        a.Go to your Windows Control Panels, and open "ODBC Data Sources"
        b.Click on the "System DSN" tab
        c.Click on the "Add..." button.
        d. From the list of drivers, choose "Microsoft Access Driver"
        e.At the dialog box, type in "myDB" for the Data Source Name. Then click on "Select..." button, and find the file "Sample Database.mdb" included with the LabSQL examples. Leave everything else as it is, and hit OK.
        f. Close the ODBC control panel
        g. Test the connection by running one of the examples provided.
    My problem is that i can't find the driver named "Microsoft Access Driver" so i can't continue through the points of the instructions. I only found "SQL Server" and "SQL Server Native Client 11.0" but if i select one of this the dialog box that appear later is different from the one described in the README instructions...

    You can certainly access the database without the toolkit. There are drivers that I posted on the forum and I have a small complete application on my blog -- you can even download the code from my SVN repository.
    In terms of you specific problem, you don't need a DSN. What you need is something called a "connection string". Also, don't waste your time with ODBC. The built-in ADO drivers are easier to use. Again, check my posts for details -- I did a 3-part series on database connectivity.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Unknown error when adding a DAQ assistant to a blank VI in LabView 2014

    Hello,
    I currently have an issue when I try to add a DAQ assistant to a blank VI  in LabView 2014 Service Pack 1, version 14.0.1.
    It was working previously and has now stopped working.  I have reinstalled LabView 2014 but the problem still exists.
    I have also reinstalled NI-DAQmx 14.5 but this did not cure the problem either.  
    I have made sure that the C:\Program files\National Instruments\MAX folder has Read & execute, List folder contents, Read function allowed for the user account in use on Windows 8.1
    Thanks in advance for the help.
    Scott.

    As soon an the DAQ assistant is dropped onto the VI block diagram an error window pops up stating that "An unknow error has occurred" with an ok button.   This does not force LV to close, the DAQ assistant icon stays on the block diagram, the block is non functional i/o signals available to wire to, I can not access any properties for the DAQ assistant.  Other than that LV appears to be functioning.

  • Bug LABVIEW 2014 - Calcul Quotient et Reste

    Bonjour à tous,
    Avez-vous remarqué ce bug dans labview 2014 sur la fonction quotient et reste?
    J'ai lu sur le forum anglais que le bug a déjà été vu en 2009. Il est à nouveau présent!
    C'est la seconde fois que je tombe dessus et qui m'oblige à utiliser un "patch maison", mais cette fois j'en informe la communauté:
    Par exemple dans mon cas 8.6 / 0.1 = 85 et reste 0.1... (voir PJ).
    Merci aux personnes concernées de prendre en compte ce bug dans vos prochaines mises à jour car c'est une fonction assez basique...
    Bonne journée.
    Julien P.
    Certified LabVIEW Developer
    Résolu !
    Accéder à la solution.
    Pièces jointes :
    quotient.vi ‏7 KB

    Bonjour à tous les deux,
    En effet, comportement particulier mais qui n'est pas un bug.
    Le "souci" vient des règles qui régissent la façon dont sont arrondis les nombres à virgule:
    IEEE Rounding rules
    C'est pour celà que dans l'aide détaillée de la fonction une remarque est présente (cf Quotient et reste (fonction)):
    "Remarque  Certains nombres réels ne peuvent pas être représentés par les nombres à virgule flottante de la norme ANSI/IEEE. Il est donc possible que des erreurs d'arrondi surviennent et que LabVIEW produise des résultats inattendus si vous utilisez les nombres à virgule flottante avec cette fonction. Pour obtenir des comparaisons et des calculs exacts, convertissez les nombres à virgule flottante en entiers."
    Bonne journée,
    Valentin
    Certified TestStand Architect
    Certified LabVIEW Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Travaux Pratiques d'initiation à LabVIEW et à la mesure
    Du 2 au 23 octobre, partout en France

Maybe you are looking for