Using mutliple versions of LabView

I am using 3 different versions of LabView right now (7.1, 8.0, 8.2). Mainly because I haven't had time to upgrade all our software to 8.2. Some of the programs I don't want to upgrade yet because I don't have time to fix the bugs that come with updating them to newer versions of LabView. My question is weather LAbView knows which version of LabView to use to use to open VIs when I open them through windows explorer or if it just defaults to the last one used.
Regards

Basically, LV opens VIs in the last version you started (although 8.2 has an apparent bug in that area).
If you force explorer to open VIs in a different version (right click the VI and select Open With...), then it should start trying to open them in that version.
Dataact makes the LabVIEW version chooser, which I believe should make it easier to select, but I haven't tried it.
Try to take over the world!

Similar Messages

  • How can I handle deploying multiple test systems on the same PC that have been developed using different versions of LabVIEW, TestStand, and/or Switch Executive?

    The major issue here is that the test systems must be documented and validated before being released to the production floor. Given this if a test station has multiple test systems deployed on it that have been developed on various versions of LV, TS, and Switch exec how can I force the test system selected to use the correct versions of TS, LV, and Switch exec.? I understand that the solution would be to recomplie everything and bring them up to the latest version but that would then require re-validation according to the QA department. Any advice would be greatly appreciated.
    It would be nice if theTS deployment was more like an LV executable... meaning when a LV executable is launched it always knows what LV runtime engine to use when there are multiple engines installed on a PC.

    Hi,
    Multiply versions of teststand can reside on the same system, but only one version can run at a time. They is a utility that has to be run to set the active version.
    The SequenceFiles have a version number, and you will find an error will be generate if you try to Load the sequencefile in the wrong version of TestStand.
    The labview VIs will only work providing the correct version of the RTE is also installed on your system, even a labview executabe requires the correct RTE to be installed, either as part of the executable installation or as a seperate installation, before the labview exe will work correctly.
    I'm not fimilar with the Switch exec but I would expect that it will also require the correct lower level device drivers to be available for the version you are using.
    Therefore, as you are indicating that some of your system are at  a older version, its difficult to image how you could achive this, considering if you say you have different versions of the software(s). For a start, you may have the problem that newer code/ sequencefiles using additional functionatily not available in the older versions.
    I would think your only solution would  be to have different deployments covering the different versions you have, or at least bring all your test systems up to the same version of teststand.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Using call library function on a dll file created in an old version of labview

    So I'm trying to update an old labview program to work in labview 2012. Everything converted over just fine but labview will always crashoverwrote some while using a  library function in a DLL that was compiled using labview 8.5. Labview exits, stating that it vital memory area. It passes an array of data to the library call and an empty array for output. I thought I could get around this problem by changing my code to initialize the array being passed in so that it would be large enough to hold all the expected output. Now instead of overwritting areas of memory it shouldn't, I get a pop up message that says:
    fatal internal error
    memorymanager.cpp line 406
    8.5.1.f5 
    So it appears because I don't have the ability to recompile the DLL file it runs off of the 8.5 runtime instead of the more recent one. Is there any thing I can do about this?

    rjpierce wrote:
    So I've been trying to figure out a way around this on my own while waiting on a response. From what I'm reading, a dll created in one version of the labview runtime can't be used by a different labview runtime. Am I correct in this? I feel like I must be mistaken since that's basically the opposite of how a dll should work. If nothing else works I have access to the original code for the DLL but it requires the control and simulation toolkit. I would like to avoid having to recompile the DLL since it was put in to a DLL to avoid the need for the toolkit to begin with. 
    Your problem most likely is that you try to pass native datatypes to the DLL function? That only can work if the caller and callee use the same LabVIEW runtime engine. Otherwise the memory block created in the memory manager of the caller will be accessed by the memory manager in the callee and bad things happen. Instead you should define the DLL function to use standard C datatypes (Pointer to C array) and also make sure to allocate the according buffer in the caller for all output array parameters.
    An even more elegant way would be to completely abandon the DLL approach and call the according functions directly in LabVIEW. Then you won't have the problems about mismatched runtime engines. Passing C array pointers to a DLL is less performant than passing native datatypes, but if you use native datatypes you have to make sure the DLL is compiled in the same LabVIEW version as the one you call it from.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Can NI-PSP be used to communicate between machines developed with different versions of LabVIEW?

    Hi all,
    A customer has a large PC application developed with LabVIEW 2010 SP1.
    They would like to add extend their system with a cRIO-9075. According to this document (ftp://ftp.ni.com/pub/devzone/tut/crio_software_versions.htm ), the minimum supported version of LabVIEW (with Scan Engine support) is LV 2011.
    To minimize risks, it is preferred that we don't upgrade LabVIEW for the main application, which is atively being used in production.
    I was thinking of developing the cRIO software in a newer version of LabVIEW (say, LV 2013 SP1), and using shared variables only to communicate between the PC and the cRIO.
    Is this a viable option? Does it matter if the PC and the cRIO have different versions of the LV runtime?

    It shouldn't matter, but then with shared variables you can never know for sure -- there are so many things that can make them break.
    You might be money ahead to write the comm using TCP/IP. You know that will work.
    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

  • Is it possible to open a VI using an older version of LabVIEW, and if so how?

    As stated in the title.  I have installed all the run-times from lv6 to lv8.6, but cannot open any VIs that have been compiled in a more recent version of LabVIEW.  We run (on different computers) lv5, lv6.1, and lv8.5.  Upgrading some of the older machines is not possible since they cannot handle the required OS.
    Is there any way to open a VI created/compiled in a higher version of LabVIEW?  This is proving to be a major sticking point with us and our ability to transfer VIs between computers.
    James
    Never say "Oops." Always say "Ah, interesting!"

    Hi James,
    I was able to use VI server to invoke LV 6.1 VI's using LV 7.0 without issue.
    After discovering this and mentioning it in a post somewhere, Rolf Kalbermatter indicated that was expected. and I should not be suprised.
    So....
    Vi Server may help you.
    James Mamakos wrote:
    Is there a separate place for me to post VIs to be converted?  What's a ballpark figure for the maximum file size i could put on to be converted?
    Do you know if the LabVIEW developers can/will create a way to overcome this problem rather than having to convert a VI through all the intermediate versions?
    To the best of knowledge NO.
    For each versino of LV there isw code included that runs behind the scenes when you open a VI from an earleir version which replaces old functions with the new versions. This is called Mutation code. To accomplish its task it has to know everything that changed between version X and Y. Since it is possible to baby step the versions up and the number of user that jump multiple major versions is small, I don't think any effort will go into that work.
    THe largest attachment I have managed to upload was 3 or 4 Meg.
    Just trying to help,
    Ben
    Message Edited by Ben on 04-28-2009 08:58 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Can you run a window version of LabVIEW on an Apple MacBook Pro using boot camp?

    Can you run a window version of LabVIEW 8 on an Apple MacBook Pro using boot camp?

    I don't have a mac, but you may want to read this:
    http://themacview.blogspot.com/
    Should give you more info about what NI is saying.
    Matt Holt
    Certified LabVIEW Architect

  • Can we use latest version of Add-Ons and Toolkits with older version of LabVIEW core?

    Hi every body
    I'm new to LabVIEW
    I have a question .
    Can we use (indeed install) latest version of Add-Ons and Toolkits(for example 2009 or 8.6.1 version) with older version of LabVIEW core(for example LabVIEW 8.6)?
    No problem ?!
    I have LabVIEW 8.6(Evalution) and I want istall Real Time Module 2009.
    Message Edited by mostafi on 10-31-2009 02:49 AM
    Solved!
    Go to Solution.

    I think perhaps 8.6 and 8.6.1 is compatible. But I am 100% sure that 2009 and 8.6.(1) is not downwards compatible
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Could there be independent VI paths for different versions of LabVIEW?

    Hello,
    When jumping between different versions of LabVIEW (6.1, 7.1, 8.5) it is annoying that the current path for one becomes the current path for the other. 
    If I am working with LV 7.1 in a folder dedicated to 7.1 VI's, and then open LV 8.5, I don't want 8.5 to go to that 7.1 folder by default.  Alternately. if I was working in LV 8.5, closed it out, and then I click on a 7.1 VI, I don't want it to open in LV 8.5. 
    I've tried changing the path options in each version of LabVIEW, but that doesn't seem to help.  Is there any way of isolating these folder paths from one another?  One of our newer LV guys accidently opened some 7.1 code in 8.5.1 and then saved it.  Luckily, I had archived code to return to, but it could have been a disaster.
    Thanks for any ideas,
    McSynth

    You're actually asking two different questions.
    The first question has to do with which version of LabVIEW gets launched when you double-click a file. This is an operating system thing. The one that gets launched is the last one that got used. (Your first question will be: can this be changed? Answer: Change the operating system. Or, play around with the registry each time you quit out LabVIEW.)
    The second question has to do with search paths. These are independent. However, a VI will contain information about its subVIs in terms of where to find them. This is not a function of LabVIEW, as it is a function of the VI. Thus, it will make no difference which version of LabVIEW you use to open the VI. You can, if you wish, modify the search paths that LabVIEW uses to find VIs for each version of LabVIEW from the Tools->Options menu. However, this will not eliminate the problem, and your best bet is to keep those backups frequent.

  • Identifying and Converting from an older version of LabVIEW

    I have an old .vi program that I am trying to access and run now. I don't know what version of LabView it was written in but I do know it came off of a Windows 95 computer.
    Any Suggestions?
    Will Huntley
    Solved!
    Go to Solution.

    You said "trying to". Does that mean you've been unsuccessful? On what OS are you trying to run it?
    When you open an old VI in a newer version of LabVIEW, if the VI isn't too old, then it will open. If you close the VI you'll get a dialog asking you to save it. The "explain changes" will tell you the version of LabVIEW used to write the VI.
    If you cannot open the VI because it's too old, and your LabVIEW is too new (e.g., opening a LabVIEW 5.x VI with LV2011), then you can post a request in the Version Conversion board. If the code is really old (e.g., LabVIEW 3.x or earlier), chances are you will not be able to get it upconverted since versions that old require a special toolkit from NI that is not publicly available.
    EDIT: Duplicate answer. Was creating my response while Dennis posted his.

  • Multiple versions of labview on 1 computer

    Hello,
    I have just purchased LV 8.2 and am about to install it on my computer.  The old version of LV I currently have on my computer is 7.1.  Can I run both versions on the same computer or is it beneficial to take off LV 7.1 first before installing the new 8.2.  Any opinions?
    Azazal
    Azazel
    Pentium 4, 3.6GHz, 2 GB Ram, Labview 8.5, Windows XP, PXI-5122, PCI-6259, PCI-6115

    Azazal,
    You can certainly run both versions on the same computer.  I have 6.1, 7.1, 8.0, and 8.20 installed on this machine and I regularly have more than one version open at the same time.
    However, Paulo is very correct by saying that toolkits typically only install for one version of LabVIEW and that you need to be careful not to open your VIs in the wrong version of LabVIEW.  If you were to open and save a LabVIEW 7.1 VI in 8.20 you would be unable to open it again in 7.1.
    Matt, great links - I'm going to repeat that first one here in clickable form:
    Installing Toolkits for Use with Multiple Versions of LabVIEW
    Regards,
    Simon H
    Applications Engineer
    National Instruments
    http://www.ni.com/support

  • Is there a way to programmatically tell what version of LabVIEW a VI is compiled in?

    Is there a way to tell programmatically what version of LabVIEW a VI is compiled in?
    LabVIEW seems to know.  If you click on "List Unsaved Changes", it (sometimes?) tells you the version of LabVIEW that the VI is already saved under (i.e., 8.0 instead of 8.0.1).  So if LabVIEW knows, maybe they've provided a way for us lower-echelon folks (i.e., customers) to know too, eh?
    Is there a way to get this from, say, VI Properties (i.e., Property Node gets passed a ref to a VI & I select the right property name)?  I couldn't find any property name that has "version" or anything like that, but maybe what I'm looking for is using terms that are so different than what I'm expecting that I just can't tell.
    Or by some other method?  (I gvimmed a few .vi files, and see some stuff that looks like I *could* get the version by parsing/searching the file itself, but parsing the binary might give pretty unreliable results.)

    Just dro a proerty node on the diagram and select property: "Application...Version number" and display the resulting string output.
    Message Edited by altenbach on 07-02-2006 11:33 AM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    version.png ‏9 KB

  • Using IVI drivers in LabView 5.1.1

    Hi,
    We have a set of IVI drivers ( class specific and custom specific ) developed in LabWindows/CVI 7 and IVI Compliance package 2.2 version. We want to use these drivers in a new application in LabView 5.1.1 version. I want to use the class specific drivers through the IVI class drivers in LabView 5.1.1 so as to cater for the interchangeability aspect configuring the logical names in MAX. Finally I would be creating an Installer with executable and distributing it.
    I want to clarify few issues.
    1. Please let me know whether I need to install any other software's apart from NI DAQ, IVI compliance package 2.2 and the Installer in the User PC. Does the IVI engine, Tool set, Class drivers for LabView 5.1.1 come with the compliance package?
    2. Does MAX 2.1 support IVI drivers, interchangeability through class drivers and compliance package 2.2 or should I use MAX 3.0 for best results?
    3. When I import a IVI driver (developed using IVI compliance package 2.2) to LabView 5.1.1 and try to use the functions there are some problems in the functions. As per the IVI specifications 3.2, functions GetErrorInfo and ClearErroInfo are changed to GetError and ClearError. But it shows error in the functions at those points and we have to go to IVI Error Converter.vi and change the configuration of the library node and direct it to the GetError function. Do we have an alternative to avoid this process?
    It would be of great help if somebody can clear these issues.
    Thanks & Regards,
    Siddu

    1.  The IVI Compliance Package (ICP) 2.2 installs the IVI Engine and Class Driver support for LabVIEW 7.0 and 7.1.  It does not install Class Drivers for LabVIEW 5.1.
    2.  ICP 2.2 requires MAX 3.0 to get the IVI interchangeability provider in MAX.
    3.  LabVIEW 5.1 was released before the official IVI specifications 3.2 were approved.  Prior to 3.2, the function names were GetErrorInfo and ClearErrorInfo.  Those changed to GetError and ClearError.  The LabVIEW wrapper generation tool that shipped with LabVIEW 5.1 is not aware of these changes.  Therefore, my suggestion is to upgrade to a later version of LabVIEW so that you will have support for the current IVI specifications and class drivers.

  • Does Instrument I/O Assistant only work in the activated version of LabView 8.0 and not in evaluation version?

    I'm using the LabVIEW 8.0 evaluation CD and every time I try using the Instrument I/O Assistant I get this error message "Measurement and Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from the LabVIEW Driver CD." So I tried installing both from the Device Driver CD and still it didn't work. I also tried uninstalling all NI softwares and components and reinstalled everything from the LabVIEW evaluation CD and Device Driver CD and still the same result.
    I was wondering maybe the Instrument I/O Assistant will only work after I activate LabVIEW. Is this the reason why I can't use it or does Instrument I/O Assistant also work even if I'm only using the evaluation version? Please help!

    Glynster -
    Yes, Instrument I/O Assistant does work with the evaluation version of LabVIEW 8.0.  However, you need to install Instrument I/O Assistant from a version of the National Instruments Device Driver CD that shipped with LabVIEW 8.0 (or later). 
    NOTE: The link provided for Instrument I/O Assistant 1.0.1 DOES NOT work with LabVIEW 8.0. It is only for LabVIEW 7.x.
    You will need to obtain a Driver CD to get Instrument I/O Assistant to work with LabVIEW 8.0
    -Tommy

  • How to measure voltage changes using a NI-9219 with strain gauges and use the data in labview

    I am updating an old LabView/Data Acquisition system that uses strain gauges to measure two forces (normal and axial) as well as two moments (Pitch and Roll). I am having trouble reading the voltage changes over my strain gauges using my NI-9219 as well as filtering the data with both a lowpass and smoothing filter. The program attached has the project and should have all the sub-vi's used in the program. This program was written on LabView version 8.5 and is being updated to a 2013 version of LabView. Also, the hardware previously used was a combination of a NI SCB-68 and NI USB-6251. If anyone could help me it would be greatly appreciated! 
    Attachments:
    New SSWT.zip ‏751 KB

    Hi Coffeyfj, 
    Did you ever had this set up working? The first thing that I would do as I mentioned in the previous comment would be to use one of the LabVIEW examples. I recommended to you using the (strain - Continuous Input.vi). If you can read any voltage changes with the example vi, then we will know the problem we are having is in your code. If you cannot read any voltage changes using the example I mentioned, we can start trouble shooting the hardware connections. Are you connecting the excitation voltage? If yes, Are you making the right connections. Please refer to page 19 of the following document (half and full bridge modes)
    NI 9219 Operating Instructions and Specifications - February 2009
    http://digital.ni.com/manuals.nsf/websearch/4197ED4BD126E0B486257546005851CA
    Regards,
    William Fernandez
    Applications Engineer 
    National Instruments 

  • Does the academic version of Labview 8.5 allow running AT MIO 16e-1 DAQ board?

    I just bought the academic version of Labview 8.5.  I have an AT MIO 16E-1 DAQ board.  I have installed the Labview software.  Then I installed the Legacy NiDAQ 7.4.  I put in the board and MAX recognizes it.  Windows detects the board twice.  The first time is installs automatically.  The second time there is an error.
    I can't find the instrument driver/VIs in the Labview functions pallette for the AT MIO board. 
    Thanks.

    Hello Test11111,
    In order to use Traditional NI-DAQ devices in LabVIEW you need to know the device number as given in the Measurement and Automation Explorer.  Unlike the IMAQ or NI-DAQmx devices, Traditional NI-DAQ devices do not auto-populate in the channel controls or constants.  The good news is that if the device shows up in MAX and the test panel works there then your device is working properly.
    There are some Traditional NI-DAQ example VIs available through the NI Example Finder.  To access these examples open LabVIEW and go to Help» Find Examples...  Then in the top left select Directory Structure; the "daq" folder contains all of the Traditional NI-DAQ examples organized by device and function (analog, digital or counter I/O).
    I hope this helps, and please post back if you're still having trouble.
    Cheers,
    Brooks

Maybe you are looking for