Save for previous 2009 -- 8.5 with value signaling

I have the following VI, that is an example for a friend of mine. I am not sure if the property "Value signaling" is in 8.5, but if it is not, I would not expect a crash, rather a warning or something to that extent.
Error:
Attached is the simple example VI in both 2009 and 8.6 (which saved fine) If someone could take it down to 8.5 (if possible), I would appreciate it.
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?
Solved!
Go to Solution.
Attachments:
valueSignalingExample2009.vi ‏16 KB
valueSignalingExample8.6.vi ‏11 KB

Hi Paul,
LV2009 has the (known) problem of saving VIs with an event structure back to previous versions prior to LV8.6...
Message Edited by GerdW on 11-24-2009 09:38 PM
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
valueSignalingExample_85.vi ‏19 KB

Similar Messages

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!

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.

Save for previous error on FPGA vi (LV2009 - LV8.6)

Hi all,
I have an RT project i want to back save from LV2009 to LV8.6. When trying to save for previous, all FPGA subVI's are saved correctly but the top level FPGA vi returns error 1536:
LabVIEW: To save a password-protected VI for a previous LabVIEW version, you must enter the password.
However, no VI is password protected :-s
All other top level VI's in the project referencing the FPGA VI also return this error.
I searched this forum but found no similar topic, so maybe i'm missing something
Can someone please help?

I am getting the same error. LV 2009 on Windows Vista. There are only 4 VIs (FPGA Main, FPGA subVI, Host Main, Host SubVI) and a Shared Variable Library file. The SV library file and on the FPGA subVI get copied into the new directory along with the LVbit file but nothing else. I am not even sure what VI is having trouble on.
Joji

FPGA save for previous

I recently needed to save a LabVIEW FPGA 8.6 project to LabVIEW FPGA 8.5 and encountered a mess!
I crashed LabVIEW many times before I found the culprits.
To convert from FPGA 8.6 to 8.5
1.) Remove all express VIs - the timing and interrupt VIs are express VIs.
2.) Remove all FPGA references from the Host VIs - as the references are different between these versions.
3.) Save for previous.
4.) Replace deleted express VIs
5.) Replace FPGA references in the Host VIs
6.) Recompile
Visualize the Solution
CLA
LabVIEW, LabVIEW FPGA

I am getting the same error. LV 2009 on Windows Vista. There are only 4 VIs (FPGA Main, FPGA subVI, Host Main, Host SubVI) and a Shared Variable Library file. The SV library file and on the FPGA subVI get copied into the new directory along with the LVbit file but nothing else. I am not even sure what VI is having trouble on.
Joji

Save for previous changes original source

I've been having a couple of issues in LabVIEW 2009 when I try to save for previous to v8.6. One problem is a message, after it starts cranking, that it could complete, there was a file area, either disk full (40GB left) or permissions. Then when I try and close the original project it asks if I want to save 124 vi's, as they were loaded from a previous version (8.6). When I did the save this morning in my hotel (I'm on the road, as usual) to my "thumb drive" it worked ok. The reason for all of this saving back and forth is that I have 8.6.1 at the customer's, only 8.5 and 2009 on my laptop.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Weird! Well I'll get around it by dragging around yet another laptop! Between that and the roughly 300 m from my desk to the lab, I'll work off some of the seasonal food results! Have made the round trip 8 times today, once when I hadn't copied a file to a shared drive accessible at the other end.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Save for previous does not work

In LabVIEW 7, there is no possibility to save for a previous version. The reference to "Save with options" in file menu, given in Help, leads nowhere. I have also tried to save programmically, using method "Save for previous", but it did nothing (and did not say anything in the Warnings or Error).
What to do?

> In LabVIEW 7, there is no possibility to save for a previous version.
> The reference to "Save with options" in file menu, given in Help,
> leads nowhere. I have also tried to save programmically, using method
> "Save for previous", but it did nothing (and did not say anything in
> the Warnings or Error).
> What to do?
Can you be more specific? Save with options has six options listed on
the left side. The next to last in LV7 should allow for saving the
LV6.1. Really, you should just have to click that radio button and if
you aren't using any toolkits, you click save and choose a folder for LV
to place the VIs into -- it does this trying to avoid saving over the
originals. If you need the VIs for versions before 6.1, load into 6.1
and go furthe
r back into time. In general, each LV release will save
back to the previous major release.
Where in this sequence do you run into a problem?
Greg McKaskle

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 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

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 Minnesota

Not 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

Report for Storage location wise Stock with value..?

Hi guru's
Can anybody explain me what is T.code i want to use to get a report for STORAGE LOCATION STOCK with VALUE..?
Urgent reply me ..
Thanks
sap-mm

Sorry Mr chetan,
I want to see only the stock available in my company with Value and storage location wise..
Please try to get report for this
Thanks
sap-mm

QT v10.0 "save for web" creates file names with spaces?

I find it strange that the additional exported files from "save for web" (iPhone, etc) auto exports files with spaces in the file names. Not only that, but changing the file names breaks the javascript.
I work on a server that denies permission to files with spaces in the file names. I know it's a bit archaic - but it's also a long standing tennent of "good HTML" to creates files with a hyphen or underscore instead of a space.
Is this something that can be addressed in the next update?

If your using cs5 or cs6 you might try Image Processor Pro which seems to use underscores
and has a save for web option.
Dr Browns Services 2.31
http://www.russellbrown.com/scripts.html

"Save for Web" does not work with mac OS 10.6

Everything else runs fine with PSE 6 and OS 10.6, but nothing (!) happens when choosing "Save for Web" (German Version).

Here are the directions for PSE 6 in general:
http://forums.adobe.com/thread/422596?tstart=30
and for save for web:
Finally, to make the Save For Web work, you must do the same thing as above (which is make a folder owner be a non-admin account, and fix the read/write so that in 10.4 the You can says Read & Write). The folder to change with the "command i" get info is :
/Library/Applications Support/Adobe/Photoshop Elements/File Agent/6.0/en_US.
Once this en_US file is owned by a non-admin account and the Read & Write is set, and the padlock is unlocked, the Save For Web works.

How to make TRIM in 10.6.8 work for Aug 2009 macbook pro with 120 GB SSD?

Just installed 10.6.8 on a August 2009 Macbook Pro with 120 GB SSD (which is Apple installed memory), and TRIM is not enabled. When I installed 10.6.8 on an August 2010 Macbook Pro with 500 GB SSD (Apple installed), the TRIM became enabled without me doing anything else. Is there some procedure I should use to enable TRIM on the August 2009 unit? Thank you for your advice. Carl

but there's no proof that such hacking is either safe or beneficial to performance
Not my take on this at all. My Air for example struggled with write fatigue something chronic - after filling it up the drive performance was down to about 40% on benchmarking, and in the real world felt a lot slower than it was. Enabling TRIM and then erasing free-space resulted in it benchmarking back to where it was at new, and the real performance being back to how I remembered it.
The Sandforce controller enabled Vertex 2E - I don't know if it's made a world of difference to that as I don't remember that unit suffering with write fatigue particularly.
The Crucial M225 struggled with write fatigue, and again TRIM sorted it out - and still has.
All the above perf tests/comparisons etc. are all on my blog if you want to have a look see.

Save for web as PNG-24 with slices is saving in JPEG format!

Hello all.
I'm using Photoshop Extended CS6 13.0.1 x64 and when I save for web as PNG-24, all the slices from the project, the final result are JPEG format pictures. I tried the same but exporting as GIF and it keeps saving as JPEG. I tried Save As instead of Save for Web and it works, but this way I'm not saving by slice and not for web.
Any idea why this happens?

Found the solution. I had to select all the slices.

Save for previous 2009 -- 8.5 with value signaling

Similar Messages

Maybe you are looking for