Previous version LABview

Hi there,
I was just wondering if there is any way I could obtain LABview 8.6?
I am currently using the 2013 student version for college, but my proffessor stresses that the 8.6 is required for use.
Thanks very much.

I managed to find the download here: LabVIEW Development System 8.6.1
What drivers and add ons will you need. The drivers that work with 2013 will not work with 8.6.1. So there is that potential issue.
The problem with Save For Previous is when you use a "new" feature, like conditional autoindexing tunnels. It might result in something you might now like.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Labview 2011 save for previous version crashes

Hello,
I am trying to save an existing Labview 2011 project to any previous version. I have tried 2010 all the way down to 8.0. I have a clean project, all files are LV 2011, it builds and runs correctly. I have mass compiled. It did call 2 dynamic vi's but I have removed those. The project did contain conditional compilation, but that is removed. It did contain disabled diagrams, but they are removed. I did a save hierarchy to a seperate folder, just to make sure the standard save works. It does. There are 1196 vi's and controls in the project.
If I save to LV 2010, quite a number of sub vi's are saved (909 including controls), but none of the top level ones. The crash is manifested by Labview leaving memory (task manager doesn't see it any more) and the Labview window dissapearing.
Attached is the save dialog at the instance before crashing.
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
Has anyone experienced similar problems? If so, any clues on how to fix this?
Thanks,
Bart Schroder
Attachments:
LV2011 save crash.jpg ‏17 KB

BartSchroder wrote:
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
In the advanced build configuration, check "generate build log file". See if you get more information. Good luck.
Quote from the help:
Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
LabVIEW Champion . Do more with less code and in less time .

Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1. The code was saved with the 'Save for Previous Version' option available in Labview 8. When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes). Are there any ideas what's going on and how to fix this?
Thanks for your help!
Mike

I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
Try to take over the world!

Save for previous version 8.5 to 8.2 generates code that crashes Labview (uses classes)

Hello,
I'm working on some java style interfaces for labview for hot swapping of instrumentation for design patterns. When I try to port this code, developed on Labview 8.5 back to labview 8.2, the code it generates crashes labview (both 8.5 and 8.2).
Included is a small snipet of the work that demonstrates this behavior.
It includes to classes:
untitledProject1 - the containing project (version 8.5)
FunctionGeneratorI - Similar to a Java style interface (A class with all Dynamic VI's with no useful functionality)
FunctionGenerator33220a - An intended implementation of Function generator (only a few functions implemented)
and a folder "labview8_2Distribution"
Which contains the port of the 8.5 code to 8.2.
To recreate the error:
A.
1. Open "labview8_2Distribution\Users\Laptop\Desktop\object\Untitled Project 1" (8.2 save)
2. Verify it crashes labview 8.5 and labview 8.2.
3. Watch labview crash?
B.
1. Open the "Untitled project 1" in the root directory. (Using labview 8.5)
2. Save the project as a labview 8.2 type.
3. Try to open the saved version with 8.5 and 8.2.
4. Watch labview crash?
Greg Sonnenfeld
Attachments:
error.zip ‏885 KB

Hello Karunya,
In regards to your questions:
>Can you post your code? Have you tested this by creating another project?
Do you have an xcontrols in your projects? Do you have typedefs? Do you
have a LVOOP constant on your block diagram? Are you also using Classes?
I cannot post the cost as it is way too big. Not really my code but a spaghetti code from a previous programmer. I think problems saving it to a previous version have to do with a few things:
1) Memory - I have 1 GB of RAM and I am running XP. I notice the available RAM dropping quickly as it is saving and then it blow up.
2) Long Filenames - The directory path of the original file is incorporated into the saved "previous version" of the code. While a good design, it does make the file/path a bit longer when saving
3) One of teh things it saves is the drivers and their menus. This is due to the drivers being in a subdirectory of the original code and not in the c:\program files\national instruments\labview 8.5\instr.lib directory. I saw this when I tried to save the file as an LLB.
4) If I work with smaller parts of the code without long paths, it saves fine.
There probably are xcontrols, definitely typedefs, no LVOOP's or Classes. Hope you can do something with all this. It just seems that converting to a later version of the code should be reversable. Thanks.
Michael

How to run the VI developed in labVIEW 2011 in its previous versions

Hi all,
I am currently using LabVIEW 2011 in my home PC.
But, all my school computers are installed with LabVIEW 2010 and 2010 SP1.
How to run the VI developed in LabVIEW 2011 in its previous versions?
Is there any conveter for that?
Regards
Prasanth T
Solved!
Go to Solution.

Open the VI in LabVIEW 2011 and use the File menu option, Save for Previous Version.

Reading data saved on previous version of Labview

I've recently bit the bullet and upgraded to Labview 8.0 after using Labview 7.0 for a good few years now. I'm currently experiencing problems accessing data saved on the previous version of Labview which I've been working on until the upgrade.
An example is the waveform files saved on Labview 7.0 which I'm trying to read using Labview 8.0. A dialog box appears when I try to use Labview 8.0 to read the waveforms advising me to convert the files to the new version of Labview which I've duly agreed to. However, it appears that the conversion process has managed to corrupt the waveform files as I am unable to access it on either Labview 8.0 or 7.0.
I'm including a couple of files to highlight my point, one saved on Labview 7.0 and the other converted to Labview 8.0 by the programme.
Cheers.
Attachments:
Labview 7.0 Waveform1.txt ‏395 KB
Converted Labview 8.0 Waveform File1.txt ‏1 KB

Hi
Have a look at this thread: http://forums.ni.com/ni/board/message?board.id=170&message.id=163651
There you'll find a workaround regarding the message.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...

Does the downloadable LabView 8.0 demo require uninstall of previous versions?

I want to try the downloadable LabView 8.0 demo from ftp://ftp.ni.com, however I need to know if I need to uninstall previous versions of LabView prior to installing this demo?
Best regards,
Kevin Coggins

Dennis wrote;
"If, you also choose to download any new hardware drivers like DAQmx, VISA, NI-GPIB, etc, those new drivers will overwrite your existing drivers though. "
Add to this note that if you are using DAQ of Fieldpoint functions that are older than LV 7.0, support for those functions will be REMOVED from the eariler versions.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

LV 8.2 Error in opening vi saved with LV 8.5 in previous version

Hey,
I'm currently using LabVIEW 8.5 at my laptop to program, but at my lab we have LV 8.2. I'm having the following problem:
I save a vi with LV 8.5 in a previous version (8.2), and it sends me a warning wich says:
"Fixed-point numbers are not supported in the previous version of LabVIEW. They have been converted to double precision numbers."
When I try to open it with LV 8.2, it gives me the following messages of error:
Load Error: "Improper Format".
Load Error: "Unknown Error".
LabView Generic Error: An error occurred loading "file.vi" . LabView load error code 24: This VI cannot be loaded because it is broken and it has no block diagram.
Thanks in advance,
Moritz

Hello.
Could you send us your VI (v8.5) please? Thanks.
Regards.
Romain D.
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;}
NIDays 2010 : Conférence mondiale de l'instrumentation virtuelle
>>Détails et Inscription<<

How do I continue to save for previous version?

Hello. I am currently using LabView 9.0 32-bit, Windows 7. Unfortunately, my university uses Labview 8.6.1 32-bit, Windows Vista Business. First, I tried to open my VI's which I started at the University and modified on my machine back on a university machine. I received an error stating that the files were saved with a newer version of LabView and could not be opened. I went home, and opened the VI's again and used File > Save for Previous Version. This is okay, except it forces me to create a new destination folder. When I close LabView and open the VI's from this destination folder, they open up automatically with an asterisk to indicate the files have changed and require saving. Obviously this is automatically converting my 8.6 files to 9.0. This is very frustrating.
How can I force LabView to stick with the version that the files were created or saved as? If I attempt to save the "asterisked" files for previous version, it refuses to let me. Thank you for your time and consideration.

You must be doing something wrong, or perhaps Windows 7 is interfering. Here's the step-by-step process:
Launch LabVIEW 2009.
Open an 8.6 VI. It should show up with an asterisk in the title bar.
Make some changes.
Select File -> Save for Previous Version.
Verify that "8.6" is selected in the dropdown.
Click "Save...".
In the dialog click the "Save" button to accept the default of saving the VI into a new folder called "<VI Name> Folder".
Close the VI. When asked if you want to save changes click "Don't Save".
Check the timestamp on the newly created file in that folder.
Open the same 8.6 VI again.
Make some changes.
Select File -> Save for Previous Version.
Verify that "8.6" is selected in the dropdown.
Click "Save...".
The "File name" textbox should have the same default name as previously. If you click "Save" Windows should move you into that folder, and the save dialog should remain open. The file listing should contain the VI.
Click on the "Current Folder" button. You should get a dialog warning you that the operation will save over existing files. Click "OK" to continue. The VI will be saved as the previous version over the previous save that was done. To verify this, check the timestamp on the file.
I just did the above on LV2009 running under XP just so I could get the button names correct.
You can repeat steps 10-16 as many times as you want without needing to create a new folder.

LV2011 bug - Error wired to boolen function breaks when saving for previous version

I just downloaded LabVIEW 2011 this morning. I created this VI and saved it for LV2010 to see how it would deal with it. I opened the VI in LabVIEW 2010SP1 and the error wire is broken. There were no warnings about problems saving this VI as an earlier version.
=====================
LabVIEW 2012
Solved!
Go to Solution.

I would not consider this to be a "bug".
I would call it rather an "incomplete feature" were the extra-mile (backwards compatibility) is not fully implemented. So filing a suggestion is really the best thing to do (i will not file one since it is your idea, but i will kudo it!).
Saving VIs to previous versions does not change the BD itself. The requested functionality would require BD analysis and inserting (per scripting) an unbundle into the error wire. This is a complete new functionality, at least i am not aware that this is happening anywhere else....
As a "part time solution" i would like to see a BD analyzer which warns you about possible issues during downconvert. So in your case an "errorlist entry" like:
Warning: Connecting the error cluster to boolean functions is a new feature to LV 2011. Saving for previous version will lead to a broken VI.
just my 5 cents,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

8.2.1 save for previous version

I have a few problems with Labview 8.2.1 "Save for Previous Version" for use with a computer with Labview 8.0.
1-Labview 8.0 does not see the VI (created by 8.2.1 that was saved for previous version 8.0) as an 8.0 VI.
it complains:
"The VI, last saved with LabVIEW 8.0, has been converted to version 8.0. After a VI has been saved with LabVIEW 8.0 it can only be loaded by LabVIEW 8.0 or later. Use Save for Previous Version... to save VIs for older versions of LabVIEW."
2-I can't Reset the History to zero. The history resets only down to 1.
3-Save for Previous Version will not save only the one VI specified, it saves a bunch of VIs. I have to pick out only the changed VIs and place them with the unchanged 8.0 VIs. Is there a way to just save a single changed file as 8.0?
Are these problems that were fixed in later versions of Labview, such as 8.5.1, 8.6 etc?

Gaslight wrote:
So keeping a copy of Labview 8.0 for an unspecified length of time means keeping one or more computers running Windows XP for an unspecified length of time. Labview 8.0 will NOT run under Vista or Windows 7. This also means the computers runing Labview 8.0 will no longer remain on out company LAN. They are eliminating all computers running XP.
I will be forced to order fewer copies Labview 2010 upgrade. Less money for National Instruments.
You could use the included VM version of xp in windows 7 if you needed to, but it runs really horribly.
You could also keep a VMware image of XP on a computer.

Save as previous version causes events to disappear in event structure

I am using 2009 and I am trying to save a VI as previous version...saved it in 8.6, 8.5,8.2 and 8.0.
I mass compiled the Main VI in 8.6 and tried to open it. I get about 30 errors one for each event case and the event structure has no events added.
"Event Data Node:Contains unwired or bad terminal"
I am attaching a zip file containing my 8.6 source code which I down converted from LabVIEW 2009. I am trying to open it in 8.6
Is this a bug or am I doing something wrong?
Brian
Attachments:
8.6.zip ‏556 KB

Hey Brian,
This was reported to R&D (# 194525) for further investigation. A possible workaround for this issue is to save the VI to LabVIEW 8.6 and then save it to the various versions you wish to save the VI to. Also, another workaround is to manually re-enter the event specifiers to your cases.
When I saved the VI from LabVIEW 2009 to 8.2, the only thing that seemed to be out of place was the event specifiers. You can re-configure these by right-clicking on the event structure and selecting "Edit Events Handled by This Case...". Also, when I first saved the VI to LabVIEW 8.6 and then to LabVIEW 8.2, everything seemed to be in order.
Thanks for your feedback. Let me know if I can clarify any of my proposed workarounds.
Hope this helps.
-Ben
WaterlooLabs

Save for previous version (8.6 to 8.5) including dependencies

Hello everyone,
Once again please forgive me if I use the wrong terminology as I am very new to Labview.
Here is what I am trying to do. I have a project written in Labview 8.6. It has a number of files and some dependencies (which include .lvlib's .lvlclass's and some .vi's). I need to save this project as a previous version (8.5) and send it downstairs to the lab. I've tried to save it as a previous version using the the project explorer: file->save for previous version. When I zip up the project folder and send it to the lab and try and run it on 8.5 it says there are missing files. Specifically:
NI_report.lvclass
NI_reportGenerationCore.lvlib
NI_HTML.lvclass
NI_StandardReport.lvclass
I am not creating an executable as they need to be able to make some minor changes to the code. Both computers have the full Labview development suite. Also there is no chance that the lab can simply upgrade to 8.6 from 8.5 as these upgrades are scheduled by another department.
Is there any way to save this project so that it includes the dependencies that are missing in the project folder? I'm sure there must be a simple solution but I can't seem to get it to work.
As always any suggestions or advice is greatly appreciated. Please let me know if there is any more information I can provide. Also please feel free to tell me what I'm doing wrong as I'm keen to understand why what I'm trying to do isn't working.
Cheers,
Alex
Alexander H. | Software Developer | CLAD

Yes the toolkit is installed on the computer in the lab. I was able previously able to work on this project on either computer and only had problems once the upstairs computer was upgraded to Labview 8.6.
Alexander H. | Software Developer | CLAD

Save for Previous version and post!

Hi,
This is a request for all the users posting in the NI Discussion forum. Please save your VI for the previous version (atleast to 8.6) before posting because the people who knows your best solution might not have the latest version that becomes tough for them to solve.
So make it easier and get the solution faster....
The best solution is the one you find it by yourself
Solved!
Go to Solution.

smercurio_fc wrote:
Not sure what you mean by this. Are you saying you can't create snippets in LV2010?
No. Am asking about the VI's posted not as snippet as attachements (eg: Read from RS232). Is it that much tough to add a feature to make LabVIEW Compatible for the latest version (Atleast from LV2009 compatible for LV2010). Then the need for Upconvert VI Requests ( Its really usefull thread. Kudos to smercurio_fc) will gradually decrease .
The best solution is the one you find it by yourself

How do I save a type for a previous version of TestStand (4.0 -- 3.5)?

I have a number of step-types saved in a type file, in TestStand 4. I would like to use this file in TestStand 3.5. Is there any way of saving this file for TestStand 3.5. I have gone into each step-type and custom-type defined in the type file, and under the Version tab, selected the "Set earliest TestStand Version that can use this type", to 3.5.0.725. However, still this file is not openable in TestStand 3.5.
Thanks
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au

Hi Manooch_H and Chris,
The 2nd suggestion would seems to be the route to take but doesn't seem to do what Manooch suggests. If you try to save a palette out as a previous version eg TS4.1 to TS3.5 then the WriteFile wants the compatibility version in the Compatibilty TS3.5 folder otherwise it generates an error.
"An error occurred calling 'Writefile' in PropertyObjectFile' of NI TestStand API 4.1. The compatibility type palette files for selected version could not be found"
Also you need to change the Path as it will overwrite the Current version. Again not what you want. Therefore, you can not seem to do what Chris wants to do because you need the compatibility version file to create the previous version type palette file. (Manooch, Maybe I doing something wrong...)
So the first option seems to be the only workable solution.
Point to bear in mind.
Adding Types to a SequenceFile Types then saving out to a previous version doesnt modify the Type fully if you dont have a compatibility file. ie Take the "Default Step Name Expression" of a Custom Step Type contains ResStr("CUSTOM_STEPTYPES", "DEFAULT_STEP_NAME").
This resource strings don't exist in Version 3.5 or lower and therefore when you load the SequenceFile into the previous version of TestStand eg TS3.5 it will generate an error.
Regards
Ray Farmer
Message Edited by Ray Farmer on 08-08-2008 09:24 PM
Regards
Ray Farmer

Previous version LABview

Similar Messages

Maybe you are looking for