Conversion of Labview 5 to 2012

Similar Questions

• get the message "setup.exe has stopped working" when trying to install labview 2011 or 2012 on a windows machine 7

  When you try to install labview 2011 or 2012 on a windows machine 7, I get a message "setup.exe has stopped working". I tried to run setup.exe as an administrator with the same results. I have Microsoft .NET Framework installed on the affected machine 4.5.1. Could be the cause of this problem? Or does anyone know the root cause of this error?

  Hi - are you getting it at the beginning of installation, during or after 100% progression ended?

  Is it fair to LabVIEW you install, or is it drivers too, in this case, what was the last big package that has been installed at the time?

  This can be caused by the NVIDIA chipset driver:

  https://decibel.NI.com/content/message/46299?TSTART=-130

  Thank you
  Sacha

• conversion of LabVIEW 8.5 in 2012

  Hello

  I'm trying to convert my application written in LabVIEW 8.5 with NOR-traditional Daq OR DAQmx LabVIEW 2012.

  You can find the code as an attachment

  Thank you

  Are you aware of that very specific baord is available for applications for upgrading / downgrading.

  http://forums.NI.com/T5/version-conversion/BD-p/VersionConversion

  In addition, a VI that is created in LabVIEW 8.5 version can be opened in the 2012 version & later recompile (upgrade) it.

  Edition: Find VI improved with DAQmx functions in the attachment.

• LabVIEW Signal Express 2012

  We have Labview 2012 Signal Express (version 6.0.0) installed on an XP computer and we want to upgrade to a Windows 7 machine.  Will be the last version of Labview 2012 to work on the Windows 7 machine?  The 2012 Labview Signal Express is used to control a cDAQ-9172 with module 4 channels thermocouple.

  It's the Commission of LabVIEW. Please, click on Options and ask that the moderator moving your question to the Board of Directors SignalExpress. LabVIEW itself runs on Windows 7, but they are two different products and not many people here use SE.

• Keithley 6221 pilot - upgrade to labview 2009 to 2012

  Hello

  I use the Labview drivers provided by Keithley, to control a power supply Keithley 6221. They provide for LV 8 and 2009 versions, and I currently use 2009. However, I have to spend to LV 2012. Compatible drivers 2009 will be ok with LV 2012? This who should I look for?

  As you have to connect to the Web of Keithley site to download the drivers, I have attached to them.

  The drivers are provided with VISAS, so I don't expect upgrade problems around 2012.  The thing I noticed is that the files are set to read-only.  Disable via Windows Explorer so that you can compile mass screw before use.

• Conversion of LabVIEW 5.1 VI LabVIEW 8.0 or newer

  Hello

  Anyone have the opportunity to open a Labview 5.1 VI and could convert to a newer version for me?  I currently use 2010 and have access to 8.6 as well.  Thanks in advance!

  -Adam

  Here's a conversion to 8.2.

  Be aware that, for example, the temporal delay code is not healthy and probably belongs in the threads of Rube Goldberg .

  See if you can simplify it...

• LabVIEW FPGA SP1 2012 & EVS1464RT FPGA IO

  Hello

  There seems to be problems with the new Labview FPGA 2012 SP1 in combination with an EVS1464RT embedded Vision system, which took place only after upgrading to SP1 2012 Labview:

  • While trying to compile our code for the EVS1464RT FPGA or (Vision system embedded with e/s based on a FPGA Virtex-II FPGA) Xilinx tools (V10.1, since it's a Virtex-II FPGA) has reported an error saying that the compilation work has tried to set the property 'Data (output events)', which does not exist, so the Xilinx tools just quit with an error.

    A complete uninstall and reinstall 'clean' do not solve the problem.

    Research has shown that there is a property correct for Xilinx tools, called "done (output events)." An extended search in the Labview upwards 'incorrect data (output events)' some text files in 2 files "resource.xml" in the directories '...\National Instruments\LabVIEW 2012\Targets\NI\FPGA\IMAQIO\IMAQIO-1 "and '...\National Instruments\LabVIEW 2012\Targets\NI\FPGA\IMAQIO\IMAQIO-5' (and nowhere else).". " Change these 2 texts to 'Done (output events)' corrected the error and allowed to compile the code again.

  • Another problem is that you can not start the VI FPGA-interactive (for example by clicking the Run button). This product just another error message saying that the VI '...\National Instruments\LabVIEW 2012\vi.lib\FPGAPlugInAG\IMAQIO-5\niFpgaOpenAndRun_IMAQIO-5.vi' could not be found (and there really is not anywhere on the hard drive).

    The FPGA VI can be started from an another VI on the target host by using the function "Reference open FPGA". Then it works without any problems, so the bitfile has been obviously compiled correctly.

  All of this worked out of the box without any problems on my old installation of Labview (before 2012 SP1 update).

  The first problems now seems to be a simple typo, and using the function "Open FPGA reference" is a workaround for the second problem. But I'm very angry that National Instruments does not seem to test their software before releasing. A service pack should never break things that worked before.

  Find these alternatives cost me 3 days, which, in my opinion, could be acceptable for open-source software, but not if you pay hundreds of euros per year for a "Standard Service program. For that kind of money, I expected NOT to test all the changes that they do well.

  Best regards

  Dr. Merlin Welker

  Hello Mr. Welker.

  First of all, thank you for your comments. I'm really sorry that you stumbled on this issue. Please let me give you some background information on it.

  You are right that the update for the versions of service pack is to address reported problems and he should never break things that worked before. Unforunately, a change in LabVIEW FPGA exposed an underlying issue with e/s NOR-IMAQ driver FPGA compilation. We have identified this issue and addressed it in the Acquisition of Vision Software communicated in February 2013, including e/s NOR-IMAQ 2.6.1.

  It is now available in the Update Service of NOR. We also found and addressed the issue with the FPGA Open running and run interactively in the thatsame release.

  We recommend the upgrade to use the latest version of driver, whenever you upgrade from versions of LabVIEW, to ensure better compatibility between them. Please note that whenever you upgrade LabVIEW FPGA or Vision Acquisition Software, you should also recompile your LabVIEW FPGA projects.

  While these issues were found and corrected in the latest version, we are now reminded our development and testing processes for future versions. Please accept our apologies for the inconvenience. National Instruments is committed to your satisfaction and to maintain your confidence in our products.

  Thank you

  Elmar

• float to bytes conversion using labview

  in the project of the University to number of float serialy using labview. I don't know how to convert his individual bytes actualy I want to encode float in its float bytes. kindly help me in this regard

  Send "bytes" is usually done in the form of strings. Just use catalogued with the disconnected type entry (or use "flatten chain").

  To get started, simple would be to use the finder example in LabVIEW and search for serial communications.

• Conversion of LabVIEW download

  Hello

  Can someone help me in converting some files labview 5.1 in labview 8.6-readable files?   I'm ready to do it myself if someone can tell me were to download a converter, but if I need several versions of labview, I am probably out of luck.

  Thank you

  I converted to LabVIEW 7.1 - I think that 8.6 might be able to open and convert 7.1

• conversion of LabVIEW 2011 to 8.2

  
  

  Click on file and select Save to the previous version , select the version you want and save it (if you have the support 8.2 I guess), otherwise check the jury of the conversion of the version to convert the version of vi

• C code conversion for labview

  Hello

  As I'm not familiar with C code, can anyone please help me convert this function in Labview (8,6)? See attached txt file.

  Thank you

  LabVIEW 8.6

  This is a very direct translation.  If you know that the length parameter will be equal to the length of the array, then you don't need the length parameter and you can use an automatic indexing for loop, cut just the last element if the parameter 'create' is true.  (Code snippet is LV 2009 but attached VI is saved to 8.6)

  

• conversion of labview 7.0 to 6.1

  I have a set of FTDI labview vi 7 I need converted to 6.1.  They are designed to use a usb dll.

  Thanks, Jeff

  Downconvert requests Thread

  

• conversion of labview in c ++

  Hello

  I'm not an expert in computer programming. So, I choose LabView rather than an other other languages. But I just came across another problem here. The instrument I use takes only c ++ codes, not of LabView.

  Is it possible that I can convert the screw that I wrote in c ++ codes, so that my instrument include LabView programs?

  Thanks in advance,

  Pui

  
  

• MATRIX Toolkit for LabVIEW 2012 for LEGO Mindstorms Installer?

  Hello

  

  Help, please

  Hi 40123157,

  MATRIX support is included in the competition MINDSTORMS Kit. Here you can find the box tool from last year: http://www.ni.com/download/labview-ftc-toolkit-2012-2013/4331/en/.

  An updated version of this tool for 2014-2015 aims to be released at the end of August.

• 2013 LabVIEW allows the user to return to the LabVIEW 2012 or 2011?

  Hi all

  I have LabVIEW 2013. I noticed that in LabVIEW measurement and Automation Explorer (MAX) under the LabVIEW Run-Time 2012 SP1 f2 software is listed. This somehow means I can return or switch between LabVIEW 2013 and 2012 without having to install/reinstall?

  The reason why I ask, is that I have several instrument drivers written for LabVIEW 2012 sp1 I want to use.

  This is probably a silly question, I know.

  On a related note, is it possible to tell if a driver written for an older version of LabVIEW will work in a new version of LabVIEW? Or you just have to play with the software?

  Thank you

  Oh, John

  Hi John,.

  More explicitly answer your main question - you can install multiple versions of LabVIEW in parallel (at the same time, on the same PC), however that one version of patch of each major version (for example, 2011, 2012, 2013) can be installed - you can not install 2012 and 2012 SP1 at the same time.

  The runtime that you noticed has probably been installed with another component that was built in this environment.

  As Dennis said, the big thing to keep in mind is that your screws will have to be upconvertis/resized when moving between versions.

  If your instrument driver is written in 2012 LabVIEW using the serial at low altitude of LabVIEW drivers, it will certainly work in 2013.  If you open the screw driver in 2013 and that you do not see workload issues, you should be good to go.  If pilots request DLL or another have external dependencies can be involved more work.

  Kind regards