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

Similar Messages

  • 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

  • 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

  • LabVIEW 2014 toLabVIEW 2013

    Hi,
    Can someone please help me and convert these files from LabVIEW 2014 to LabVIEW2013 ?
    Thank you very much !
    Solved!
    Go to Solution.
    Attachments:
    Aufgabe3.vi ‏8 KB
    MatheSubVI.vi ‏11 KB

    Here are all of your VI saved in 2013.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    2013.zip ‏17 KB

  • LabVIEW 5.0.1 to LabVIEW 2014 SP1 conversion

    Could anyone help me with conversion of attached vi from LabVIEW 5.0.1 to LabVIEW 2014 SP1, please?
    Thank you.
     

    Request is now posted in the Versioin Conversion board here.
    http://forums.ni.com/t5/Version-Conversion/LabVIEW-5-0-1-to-LabVIEW-2014-SP1/m-p/3175879

  • 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

  • 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

  • LabVIEW 2014 Install failed

    They did it again...
    Tried downloading the new LV 2014 version via the NI Update tool (which first popped-up for update of itself).
    Everything went smoothly during the download (except that there was some conflict with NI Vision - but I was not offered to update NI Vision?) but ignoring this, eventually I was told that the install failed because of some permission issue with a datasocket forlder and that I should login as an Administrator.
    I AM AN ADMINISTRATOR on my machine!
    I tried to find the downloaded installer to at least try to run it as Administrator (Windows 7 64 bits), but the download was nowhere to be found (thanks NI Update...not).
    No comments.

    Let me comment:
    - NI Updater prompted me that an update of itself was available. A 110 MB update no less (this is an updater!).
    - Once this was over, I was prompted to take a look at the cool updates available: LabVIEW 2014 64bit and 32bit, some MathScript RT and FPGA stuff, as I recall.
    It was a bit late and I was dreading the GB+ download so I only checked the LV2014 64bit version. It took some time but eventually it fired up (no download option or anything), albeit with a cryptic message about the lack of a NI Vision Toolkit for 2014 (I don't recall the details, but I remain under the impression that NI Vision 2013 was not compatible with LV 2014?). Anyhow, as I was just curious to check which bugs had been fixed (I watched the useless promotional video for LV 2014, which is a model of corporate marketing with zero informational value and had a look at the "what's new" page, with a feeling of deja vu all over again).
    As I said, the install failed because of permissions rights for a specific folder. Since I could either retry or cancel, I did both (in that order), with the retry option running in a loop and the cancel one leaving me flat face in the mud with no way of finding the installer to try and run with Administrator privileges. I tried the usual NI Downloads folder, and I have no idea where this putative NI Updater Install folder may be, so for me that was "let's call it a week and wait for SP1".
    I had install problems pretty much every year since I recall using LV, but up to now I was DOWNLOADING the installer from NI's website and I had a handful of versions, toolkits, etc. My installation is currently pretty clean, with only LV 2014 64 and 32 bits, so not really that challenging, I would say. At the very least, I would expect a 110 MB NI Updater to do the job properly.
    But, hey, silly me, I probably just need to get me a LabVIEW Installer Certification... Where can I sign up?

  • No aparecen los iconos de vision al instalarlo en labview 2014

    Hola, instale la  version de prueba de labview 2014 y de vision. Resulta que me aparece el nombre en el menu de funciones (vision and motion) pero no los iconos, por lo que no puedo usar este modulo. Por otro lado si realizo la instalacion de labview 2013, si que puedo utilizar vision. Parace como si hubiera algun problema con labview 2014 y vision. ¿Alguna idea? 
    He descargado la ultima actualizacion de vision que he encontrado que corresponde a febrero de 2014.
    gracias

    Do you have the Zoom feature activated? To zoom out, do this:
    ¿Tiene la función de zoom activado? Para alejar la imagen, haga lo siguiente
    Zoom in or out: Double-tap the screen with three fingers. By default, the screen is magnified 200 percent. If you manually change the magnification (by using the tap-and-drag gesture, described below), iPod touch automatically returns to that magnification when you zoom in by double-tapping with three fingers.
    copied from iPod_touch_iOS4_User_Guide , page 160ff

  • NI LabVIEW 2014 Digital Electronics FPGA Board Driver

    Hello all,
    When NI LabVIEW 2014 Digital Electronics FPGA Board Driver Release date?
    Thanks.

    Hi mlewis1973
    We have no information regarding the next release of this driver yet. As you mention, the 2013 version is available, so, for now, the solution would be to use LabVIEW 2013 until R&D gives us an update regarding this topic.
    Thanks!
    WenR

  • 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

  • LabVIEW 5.0.1 to LabVIEW 2014 SP1

    Could anyone help me with conversion of attached vi from LabVIEW 5.0.1 to LabVIEW 2014 SP1, please?
    Thank you.

    crossrulz wrote:
    Saved in 8.2.1, which you can open with 2014.  But be warned that you really need to replace the Traditional DAQ calls and use DAQmx.  This can be a not so simple thing to do.
     Actually, That DAQ to DAQmx would be a simple conversion.  What surprises me is the SCXI 1104/C is still supported (Its at least 15 years old an a few years ahead of DAQmx itself)  
    However, The VI makes no sense! Default is 200 scans per second and 100 samples to average  isn't that EXACTLY the 2Hz filter that the signal conditioning module does in hardware?

  • LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

    I'm having a problem building an installer in LabVIEW 2011SP1.
    It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
    Now when I try to build the installer I get "The build was unsuccessful."
    Possible reasons: Error generating preview for My Application 3.1.7.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    *** Error: An internal error occurred for which the cause is unknown. (Error code -41)
    *** Error Details:
    Error in MDF API function: _MDFCommon_GetNextLogMessage
    Error in MDF::GetInstance - MDF static instance is not initialized!
    *** End Error Report
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
    Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.

    I do have the LabVIEW 2013 discs but didn't install it.
    I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
    I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
    Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
    So now I need to distribute 2 runtimes with my application?!?!
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle

  • 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

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

Maybe you are looking for