LabVIEW version vs. OS compatibility

I know this page provides the 'official line' on which versions work on which OS, but I also know that v5.1f1 will work just fine on WXP, but it isn't marked for that.
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
I have a new laptop with W7P64 and still need to support projects as far back as LabVIEW v5.1f1. When I try to install, the initial screen comes up, but when I click 'Install LabVIEW 5.1', it complains that it can't find the installer.
If I go directly to 'setup.exe' in the LabVIEW\install directory, it complains about version compatibility. I have set both of these to run with WXP SP3 compatibility and tried to 'Troubleshoot compatibility '.
Has anyone had success with this? What steps did you take to accomplish it?

As Titou said, Good Luck.
Windows 95 is at least 17 years old. You've been lucky you've been able to keep it running this long.
This is probably the point in time where you need to take the time and effort to upgrade. It will be even more cost prohibitive when you get to the point that your existing equipment is no longer able to run. Unfortunately you are already past the point of obsolescence, and you are going to just keep spending more time and money trying to prevent the inevitable day that whatever you do doesn't work, assuming you haven't already reached that day.
If you feel that you are able to get LV 5.1 to work with WinXP, then you should just reformat your new laptop and install WinXP on it. The changes from WinXP to the Vista/Win7 environment are pretty significant.

Similar Messages

What are developers' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

I have a large set of code that I've painstakingly migrated from one labview version to another over the years. I have lots of deployed applications that I need to continue to support. From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward. Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again. That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example. Compatibility is often being sacrificed so NI can develop labview in the direction they choose. So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
In light of this, how are other developers managing older applicatiosn written in older versions of labview. Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate. I strongly recommend this approach. But keeping my large libraries of code separate is tough. They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi. Are other people also trying to maintain separate copies of all their code in different labview versions? How are other people managing this problem?
-Devin
I got 99 problems but 8.6 ain't one.
Solved!
Go to Solution.

Hi,
The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables. All distributables required to reproduce a test-station should be located under <Production>.
<Software_Root>
<Development>
| <Common>
| | <LabVIEW_61>
| | | <Drivers>
| | | | <DMM>
| | | | <OS>
| | | | <PS>
| | | <Utilities>
| | | <File>
| | | <Error>
| | | <String>
| | <LabVIEW_711>
| | <LabVIEW_82>
| | <LabVIEW_851>
<Programs>
* Program-specific applications that (probably) have distributables
| <Program_#1>
| | <Application_#1>
| | <Docs>
| | <Source>
*       Individual, application-specific, VIs go here
| | <Application_#2>
| | <Application_#3>
| <Program_2>
| | <Program_3>
| <Tools>
* Tools are NOT "program"-specific, and, may have distributables
| <SomeTool>
| <SomeOtherTool>
<Production>
| <COTS&Freeware>
| <Programs>
| | <Program_1>
| | | <Application_#1>
| | | | <Application_#1_Rev#1>
| | | | Application_#1.bld>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#1.llb>
*           Distributable is created from LLB "snapshot", not directly from development tree
| | | <Application_#2>
| | | | <Application_#2_Rev#1>
| | | | Application_#2.lvproj>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#2.llb>
| <Tools>
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
StyleGuide.doc ‏941 KB

Labview version 6.1 failure:"linker.cpp", line 2302

I have the labview version 6.1 failure:"linker.cpp", line 2302 fault.
Does any one can help me please ?
Solved!
Go to Solution.

Actually HeapPeak existed as far back as LabVIEW 4 or maybe even 3. However it is not usually helpful for linker errors as that is something in the LabVIEW compiler itself. HeapPeak can be sort of useful for Insane errors to locate the element that the compiler considers insane (and consequently delete and/or rewire it).
If this is a recent error on a VI that used to work before, it is most likely related to a corruption to the VI and the best course of action is to replace the VI from a backup (source code revision control would be a great advantage here). If it is something where no previous (working) state is known about, then it is going to be a tough cookie. This version is 14 years old and eventhough I still have some installation of that version somewhere it is several years ago that I started that up for more than some accidential reasons. I'm pretty sure NI would need to do some archeological work nowadays to come up with a system they could use to replicate such an error and the OP would need to be a pretty high profile customer that they would go through that sort of effort.
Maybe it is related to this error. It is the closest available in the publically accessible list of errors. A complete recompile of the entire source code tree is definitely one of the first actions to try. It may fix the problem or run into even more errors that could maybe point into a more specific location. Upgrading to a more recent LabVIEW version is another possibility although hampererd by the fact that the currently shipping version isn't officially supporting XP anymore and that the Vision software is one piece of software that underwent serious changes in the course of time and an update from 6.1 to the most recent version is most likely not a seamless operation.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to upgrade labview version 7 to version 8

Hi,
1. I wish to know how to upgrade labview version 7 to version 8?
2. If I save my VI under labview 7, how can I run in labview 8 and back to labview 7. What are the steps needed?
Ridwan

Yes, the option that Mike is speaking of is called File » Save for Previous Version ....
LabVIEW 7 files will automatically open with LabVIEW 8, you don't need to do anything special.
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/

Sypris Teslameter Driver_too early to convert to 8.5 labview version

I am new to labview (8.5) programme and trying to use it to run my setup. I connected the Gaussmeter/Teslameter (FW Bell Sypris 6010) to the computer using serial port and RS-232 cable and used the driver (from the company) for this type of devices in order to allow labview to communicate with this device but there is always an error when I try to access the device through labview. This error says:
"VI version is too early to convert the current LabView version"
I would really appreciate any help in getting this solved.
Many thanks
Hadiq
Islam means peace
Solved!
Go to Solution.
Attachments:
FWB6010.zip ‏412 KB

Thanks for your suggestion. I did it and hope to get it sorted.
Many thanks,
hadiq
Islam means peace

Get Project LabVIEW Version

Lets say I have a random LabVIEW file. I can use the Get File Type.vi found in the VI.lib to figure out what the file type is. It could be an Instrument, Control, Project, Library, XControl or a bunch of others. If it is a VI I can use the Get VI Version invoke node to find what version of LabVIEW it was made with. If it is a Library I can use the Library.Get File LabVIEW Version to get the version, or if it is a project I can use the Project.Get File LabVIEW Version.
What I find strange, is if I have a VI saved in 2013, and I run the invoke node for reading the LabVIEW version but my development environment is 2011, it will say the VI was made with 2013. But if I have a project saved in 2013, and use the invoke node to read the version, and my development machine is 2011, I get an error saying File version is later than the current LabVIEW version error 1125.
Is this a bug? I mean I can read the project file as text and parse it with a XML parser to find the version. So why does this function choke and die when trying to read newer file versions, but a VI and Library can be read no problem?
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Solved!
Go to Solution.

This was a bug in the "Project.Get File LabVIEW Version" method. It was fixed in LabVIEW 2012.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Eye Diagram using Labview version 8.6 and Digitizer 5922

I am trying to implement an eye diagram for some analysis. I have Labview version 8.6 and NI PXI Digitizer 5922. Is it possible to do some eye diagram analysis using this hardware/software. Do I need a specific toolkit for this?

To answer your questions in order:
Yes, you can and No you don't.
Remember that an eye diagram is basically just an XY plot of one input channel against another. For example, amplitude vs phase.
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

Interfacing Vision Builder with Labview version 7.1

i can't export my design in Vision Builder version 7.0 to Labview version 7.1 using the Create Labview VI under the Tools tab as taught in the demo on this website. please advise. thanks.

Hello,
Most likely, this is due to having a version of Labview that is newer than your Vision Builder / Vision Assistant software. There are updates available for both Vision Builder and Vision Assistant. These updates can be found at:
Vision Assistant 7.0.1 if you previously had Vision Assistant 7.0
Vision Builder for AI 2.0.2 if you previously had Vision Builder AI 2.0
After installing one of the above, everything should work as you saw in the online demonstration.
Hope this helps,
Robert

LabVIEW version for Vision Builder AI 2012 plugins

Hi all,
Ii was a bit of a challenge to find out which version of LabVIEW was necessary to develop custom plugins for Vision Builder AI 2012, I found it by starting the installler, it is LabVIEW 2011 (but I wish I could find this information in Vision Builder AI 2012 readme file).
Now my question is : is it possible to use LabVIEW 2011 SP1 to develop custom plugins for Vision Builder AI 2012?
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
Solved!
Go to Solution.

Right... I tried, I installed all the VBAI and LabVIEW versions I could.
I turns out LV 2011 sp1 is just an upgrade of 2011 and as such LV2011 SP1 can be used to develop custom plugins for Vision Builder AI 2012.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Convert these VIs ZLibInflate,ZLibDeflate of LabVIEW version 5.0 into LabVIEW 2009

Convert these VIs ZLibInflate.vi,ZLibDeflate.vi of LabVIEW version 5.0 into LabVIEW 2009

Hi priyash,
you should be able to download them with the VIPM.
Mike

How to convert llb from LabVIEW version 8 to 7.1

Can someone tell how to convert the llb from LabVIEW version 8 to version 7.1?
I hope to sent the program to the others, but the other side are using LabVIEW version 7.1 but not version 8.0.
I know I can save to VI file as previous version, but it contains severals of VI in the library, it is quite time consuming.
Can everyone sugguest any method or solution to solve my problem.
Thanks.

Hi anson,
it will run also in LV7.1 - but you should check those warnings (probably things not/differently supported by LV7.1...) anyway!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Labview 7 crashes when opening an earlier Labview version VI

Hello guys. I am using Labview 7 professional edition. The labview crashes when opening an earlier labview version VI. The error message I'm getting is just "Labview has encounted a problem and eneds to close. We are sorry for the inconvenience." The VI contains a few Tag SubVIs, and It is written with an earlier version of Labview(BridgeView is what it was called).
Do anyone have any ideas that how I can fix this bug? It's going to be a great help. Thank you very much.

Hello,
LabVIEW should not be crashing in this situation. Now, does this happen for other similar VIs too? It could be possible that a particular VI is corrupt. Also could you post your VI here so that I can try and reproduce the problem at my end.
Regards,
Chetan K
Application Engineering
National Instruments

Labview VERSION need HELP

Hi
I just bought the LabView 5.0 student version. I have been using labview at my
university and i tried to load a vi that i was working on at university but got
the message "labview code error 9:version of vi is newer than labview version".
Is there any way around this. Any would be great.
Thanks
Shafiq

Schau100 wrote:
> Hi
>
> I just bought the LabView 5.0 student version. I have been using labview at my
> university and i tried to load a vi that i was working on at university but got
> the message "labview code error 9:version of vi is newer than labview version".
>
Apparently the vi was saved with version 5.1, the only way around this is to
go to the university run Labview and use the "Save with options" menu.
This brings up a dialog where you can select "Save for 5.0.x". This will
save the VI in the 5.0 format so you can load it with your student version.
Hope this helps
Kevin Kent

Lvwutil32 version too early to covert to current LabVIEW version?

Hi all,
I am looking to control the windows panel with some of the useful vis stored inside the lvwutil32 lib. However when I tried to open the vis inside the library, an error message saying that the vi version (4.0) is too early to be converted to my current LabVIEW version (8.5.1).
Is there anyway to reconvert the vi that my current LabVIEW can use? It is a great shame as from the readme that comes with the lvwutil32, it seems that there are a lot of useful vis that I would find very useful for my projects.
Hope someone could provide some help on this. Thanks!
Solved!
Go to Solution.

                       Hello,
                       I am having the same problem as YuanGe(the topic owner). I wanna open a file from the 5.1.1 LABview version on my LABview 8.6 and occurs the same error message.
                      I would be very grateful, if anybody could help me.
                      Thanks.
                      ps: The file is just down here.
Attachments:
ag8614x.zip ‏2795 KB

Opening LabView version 5.1 VIs in LabView Version 8.5

We are trying to open VIs saved in LabView version 5.1 with LabView version 8.5 and we are getting error code 10. The error message states that version 5.1 is too old to be opened in version 8.5, yet on the knowledge base files seem to indicate that it should be okay. Can you tell us how we can open these older files in LabView 8.5?
Thank you,
Keir Neuman

You can't. The earliest that 8.5 can open is version 6 VIs. See http://forums.ni.com/ni/board/message?board.id=170&message.id=271171. If you have any version of LabVIEW between 6.0 and 8.2, you can open them with that, save them and then open them with 8.5.

Hello, sombody knows how to start MS Excel from LabView (version 8.2)? Thanks

Hello, sombody knows how to start MS Excel from LabView (version 8.2)? Thank you in advance.
Regards Robert

In the example finder ">Help>Find Examples >>search for Excel", you'll find a sample program called "ActiveX Event Callback for Excel".
It opens the Excel Application.. You can build on this to open/create new worksheet(s), etc.
RayR
Message Edited by JoeLabView on 06-20-2007 08:21 AM
Attachments:
OpenExcel.PNG ‏34 KB

LabVIEW version vs. OS compatibility

Similar Messages

Maybe you are looking for