Error saving for previous version 2009 to 8.5
I have a project with a VI containing DAQmx Data Acquisition VIs, timed loops and other standard conrols and indicators. When trying to save for previous version (from LV2009 to LV8.5) an error occurs. All of the dependencies can be saved to previous versions but the main VI cannot. Can anyone help with this problem?
The error message can be seen in the image attached.
Attachments:
error.JPG 18 KB
Backsaving creates a folder structure with the backsaved VI and all support files in their relative locations. This might be useful in most cases.
Very often I just need a single VI (without SubVIs) backsaved. I do this programmatically using VI server (open VI reference, then call the "Save For Previous" method, then close the reference). See image below.
To do this for a project you could of course use a recursive file list and go through the whole list (programmatically), saving the VIs in a parallel folder structure (create destination folder before saving the VI).
Similar Messages
-
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. -
Improper Format error while saving for previous version
Hi all,
I have been developing some Daq code with LabView 8.5. Recently I needed to open the vi on a computer which has Labview 8. I used the save for previous version option. I used low-level vi's in my code which are both available to 8.5 and 8 instead of using new express vi's. LV warned me about converting fixed point numbers to double precision while saving, which in my opinion should not cause a problem.
I have also enabled "Show front panel when called" and "Show front panel when loaded" options from VI Properties dialog (as adviced by previous threads http://forums.ni.com/ni/board/message?board.id=170&thread.id=369331).
However I was not able to solve the problem. Are there any suggestions to solve my problems?
Thanks.
GokcenI dont understand exactly what the problem is.
Have you used fixed point numbers in your code? and if so does it matter if LabVIEW converts them to DBL? If not then dont worry about it.
What problem do you have with the 'show front panel when called' as it isnt clear from your message.
Also, if you can post your problem code as it makes it easier for people to see the problem
David
www.controlsoftwaresolutions.com -
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. -
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!
MikeI 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! -
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. -
Vi written in 8.0.1 saved as previous version can't open with 7.1
This vi is a modified version of the example Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample shipped with LV 8.0.1. I saved it for previous version, but it will not open in LV 7.1. I get error code 24, This vi cannot be loaded because it is broken and has no block diagram. Any ideas?
Attachments:
Collect Data.vi 143 KBI was actually asking where the "Collect Data" VI came from. I know where the "Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample" comes from. As I indicated, I cannot seem to find "Collect Data" in the hierarchy for "Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample". As a test I opened LV 8.01., opened the "Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample", saved it for 7.1 and then opened it in 7.1 with no issues. So, I go back to my questions as to where "Collect Data" came from.
I guess I don't understand what you mean by where the "Collect Data" VI came from.
This is what I did:
I opened the example Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample in LV 8.0.1. I modified it to do what I needed, and I saved it as "Collect Data.vi". Then I copied it to the machine with LV 7.1 and attempted to build an exe. That is when I got the error.
Thanks for the tip about the app builder on OpenG. I will give it a try. -
Illustrator CC 2014 files saved as previous versions corrupt
On occasion we need to save Illustrator files as version 8.0 ai files and version 3.0 eps for customers with older software and to import into industry specific software for further work (CAD).
Illustrator CS6 works fine for these tasks. Using CC 2014 the save files are corrupt:
The file saves normally, no errors indicated. Trying to reopen the saved files results in the dialog above. The CC 2014 files reopen fine, the corruption happens to the files saved in previous versions. The files are fairly simple structural designs for the box industry, all basically straight lines, no placed graphics, minimal text for labels.
Mac OS Yosemite, CC 2014Hi,
It is not possible to open the files in a previous version of Muse. It is not backward compatible.
Regards,
Aish -
How To Build exe for Previous Versions
I'm new to LabView and still struggilng a little with all the files associated with a project, so I'm sure this is a simple question.
I'm running LabView v10 for development, but wish to create an exe that can run on a v8.5 runtime version. I've seen the threads that suggest that this is as simple as 'Save For Previous Version'... but for some reason I cannot seem to make this work. I have tried saving the vi for 8.5, then choosing to build the exe, but upon being prompted to create an associated project, I'm told there are unsaved changes - that the subvi's have been converted to version 10. I've tried declining the changes and opting to use those in memory, but this also doesn't work; the built exe then gives me a runtime error, complaining it does not have LV Runtime 10.
I've tried saving the project with 'Save for Previous Version', then building. Again, this doesn't work - even though when i open, then immediately close either the project or it's contained vi's, I'm told there are unsaved changes where it has been converted to LV10 - implying the saved files were indeed saved in LV8.5 format.
I seem to be going round in circles here. Would someone mind laying out the necessary steps to build an exe that can run on a previous runtime environment?
Thanks in advance
Solved!
Go to Solution.To my knowledge, none of NI's device drivers can have multiple versions co-existing. Now, that doesn't necessarily mean if you use any hardware that you will run into problems. If the hardware is NI hardware, then they will also have specific drivers which can be in conflict, but if they are another manufacturer, it'll come down to NI-VISA probably. If you are using any NI data acquisiton cards, then you have DAQmx installed.
As long as your program doesn't access these devices, you are OK. You are not required to update the drivers if you don't use the hardware. You need to look in the relase notes for each of the drivers you need to update and see if you can find a version that supports both 8.5 and LV2010.
Even if you do this, it is not a 100% guarantee that you won't have problems. I had written an application for a customer once that used NI-RFSA. I had a control on the front panel based on a typedef in the driver. I updated my laptop for a new project, but later had to come back and make an update for the original project. The typedef had changed and caused a recompile. Nothing broke on my end. When I sent the update, it crashed on the customer PC because of the typedef change. I ended up getting them to upgrade the driver on their machine. -
Bug in LV8 : 'Save for previous version' and 'Write to Binary File' VI
Hello
I am using LabVIEW 8's revamped 'Write to Binary File' VI with a 'TRUE' boolean constant wired to the optional 'prepend array or string size?' to write non-trivial structures to a binary file. I then read the file with the 'Read from Binary File' VI and everything is fine. I don't wire anything to the 'file (use dialog)' input (don't know if this can help).
However, after saving my VI for LabVIEW 7.1, I cannot read the binary files created with the LV7 version of the VI anymore. After examining the LV7 converted version of the VI, there is a 'FALSE' boolean constant that is wired to the equivalent of the 'prepend array or string size' input, which breaks the binary format that is expected.
The attached files are LV8 and 'saved for LV7' versions of a dummy VI that writes an array of 5 integers into a binary file. To test the bug, start LV8, open the LV8 version, run it and create a 'test-lv8.bin' file, then open the LV7 version, run it and create a 'test-lv7.bin' file. Check the content of the two files : the size of the array is indeed missing from the 'test-lv7.bin' file, which can be assimilated as a bug in my opinion.
I think I found another one too : if in LV8 I wire the 'cancelled' boolean output of the 'Open/Create/Replace file' to the selector of a case structure, the 'converted to LV7' version VI will have an error, saying the Case Structure selector is not wired.
Could someone please confirm these are indeed bugs ?
Thanks in advance and have a nice day.
Eric Batut
Attachments:
Test Binary File v7-v8 LV7.vi 15 KB
Test Binary File v7-v8 LV8.vi 7 KBI'm using LV8.6 and need to read a .bin file created in MATLAB. This file obviously does not contain the 4 byte header that LabVIEW prepends .bin files with. So when I use Read from Binary File, I get no data (I'm trying to read an array of doubles). I've tried making my .bin file both in native and big-endian format and changing the representation (double, int64, float64) but none of this works. I noted that if I create the same array in a .bin file in LabVIEW and wire a FALSE to the "prepend array or string size?", my VI for reading .bin files can't read this file either.
Any work-arounds here?
(I'll try attaching my write & read VI's)
Attachments:
ReadWriteBinFile.zip 19 KB -
VBAI2011 Save for Previous Version option
Hello,
Since VBAI 2011 is one of NI products, I am curious that it has an option of Save As For Previous version like Labview, or is there any way around it?.
I currenlty have running Labview 8.6 in my systems which doesn't work well with VBAI 2011. What I have done is using Labview 2012 evaluation version to re-save my VI 8.6 till to 2010 version. I am thinking an option of down-grade my VBAI if possible.
Thanks.
Hoa Huynh
University of MinnesotaNot sure if you're aware, but you can use the Vision Builder API in LabVIEW to control an any version of VBAI 2010 or greater with any version of LV 8.5 or higher. There is a shipping example located in your Vision Builder AI\API Examples folder. The API has several advantages over migrating your inspection to LabVIEW, so you might want to check it out. Here is a web video of how to use the API to control VBAI, run inspections, and get the results and images:
http://zone.ni.com/wv/app/doc/p/id/wv-2424
Hopefully Vision Builder will eventually support saving for previous, but until then, using the API allows you to use a variety of LabVIEW versions with a variety of VBAI versions.
Hope this helps,
Brad -
Create snippet for previous version
Hello!
Is there a way to create and save a snippet from the block diagram for a previous version? I have realized that even if I save my VI for previous version, and open it, the created png snippet from this eariler version is still LV version 2014.
Is this possible somehow?
thanks for info!
Solved!
Go to Solution.hello,
Thanks for the info!
Unfortunately I cannot install it via the VI Package Manager, i get the following error msg: "one or more packages you have selected cannot be installed together. this could be due to a conflict between them, blablabla..."
I only try to install this package, and the following ones I have already. Maybe one or more of them are incompatible with the Code Capture Tool?
MGI 1D Array-1.0.0.28
MGI Application Control-1.0.2.45
MGI Cluster-1.0.0.16
MGI Error Handling-1.0.0.23
MGI File-1.0.0.33
MGI Graph-1.0.0.15
MGI Numeric-1.0.0.22
MGI Picture & Image-1.0.0.16
MGI Read/Write Anything-2.1.2.37
MGI String-1.0.2.25
MGI Timing-1.0.0.13
NI Icon Library Update Tool-1.0.0.13
OpenG Application Control Library-4.1.0.7
OpenG Error Library-4.2.0.23
OpenG LabVIEW Data Library-4.2.0.21 -
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 | CLADYes 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 -
I cannot install the QuickTime component for MPEG-2 to read and covert video files created by Sony video cameras. My iMac tells me that the software is designed for previous versions of OS X.
Any ideas?Ok, so after like 4 days of going through all these different issues, I figured out that several programs weren't downloading, and it was an issue with my wireless connectivity messing up the digital signatures, so if you plug in your comp to the modem and delete your temp files, it should start to work!
-
VZAccess Manager install hangs looking for previous versions of software
UGH! Trying to install the VZAccess Manager for the UM175 USB modem. Driver installs but it gets to the point of the installation where the message box says "Checking for previous versions of VZAccess Manager..."
It just sits there and never goes away. FRUSTRATING!!!! The driver actually installs but the manager software never does. What gives?
Oh ya...Windows 7 is the OSVZAccess Manager software must be installed before inserting the PC Card / USB Modem into the computer for the first time. Only after the software has been installed can Windows successfully install and configure the PC Card / USB Modem.
Start Device Manager.
Windows 7 Click Start > Control Panel > System and Security > Device Manager.
Click on the link below on using device manager.
http://support.vzw.com/clc/devices/knowledge_base.html?id=20416
Maybe you are looking for
-
Forward all X2 info to Motorola in THIS POST
First to Verizon: Make a separate forum for posts for the DROID X2 by Motorola please. A lot of people will probably like that. Ok, now to the Motorola forwarding information: 1: Battery Status Bug There is a bug on most of the DROID X2's now that if
-
Right click clip in sequence to remove attributes does not work?
Trying to get my old head around the three way color corrector. In the process when I try to right click a clip in the sequence to remove the attributes it does not work. When I do it again the filter square is still ticked. What am I doing wrong? Th
-
HI getting Below Error Item WBS Element XXXXXX Budget exceeded Message BP604 When User wants to release the Budget in CJ32 he get the above error they do Bottom up budget, Period Wise they have assigned the Budget At first level after total up budge
-
Can't gotoAndStop ...what's wrong with this button code?
Hi, I'm totally stumped as to why I can't navigate to another frame. I have put 2 days into this simple problem now and I'm ready to give up and go back to AS2. Please help! I'm using CS4; publish settings AS3, 10.0 I have a button on frame 2 that sh
-
My brother and I are trying to open our NAT so that we can play multiplayer without having to wait forever to get added to a game, or get kicked out of the system multiple times. I really don't want to lag in the new AC3 multiplayer. Can anyone help?