Save a LV8.5 application to LV6.1?

Hello,
I'm currently using LabVIEW 8.5 to develope my SW.
A customer is still using LV6.1.
Is it possible to save it to LV6.1 in a way??
Thanks
Solved!
Go to Solution.

I have converted the file down to LV8.0 from 8.6. It seems to be the lowest version I can convert to. Hopefully this will help so the next person can downgrade it a little further.
Attachments:
Screenshot.LV8.zip ‏266 KB

Similar Messages

Trouble running LV8 application w/RTE

I am new to LV8. I am trying to build an exe file from a VI that was created I believe with LV 6, and downloaded from the example code library. When I build the application, it creates a folder with the exe file, an ini file and a .aliases file. Also a subfolder named data, which contains lvdaq.dll. When I try to run the application with the developement PC, I get an error message indicating that it cannot communicate with the DAQ board. I believe that this indicates that the application has loaded properly, but since the PC does not actually have the DAQ board installed, it cannot run properly. The second PC has the LV8 RTE installed as well as NI VISA 4.3. It also does have the DAQ board installed. When I try to run the application with this PC, I get an "endless" string of eror messages. The first message is:
"The ordinal 2011 could not be located in the dynamic link library nidaq32.dll"
This seems odd, because I cannot see where this dll is referenced anywhere in the VI or sub VIs. The second error is:
"lvdaq.dll is not a valid labview file."
The lvdaq.dll file located in the data folder is the same size and date as the file in the LV8 daq folder. The second PC does have LV6.02 installed. Is it possible that for some odd reason the LV8 RTE is trying to use the version of lvdaq in the LV6 directory?
Jim
LV 2013
Attachments:
Function Generator.zip ‏62 KB

The new PC has NI-DAQ 6.8 installed. I am trying to solve the problem that I posted in this thread: http://forums.ni.com/ni/board/message?board.id=170&thread.id=286721
The VI runs under LV6 on this PC until I get the error message, which can take 20 minutes or so. I am grasping at straws in the hope that there is something in LV8 that will prevent the underrun/overrun problem that I am experiencing with LV6.02.
Jim
LV 2013

ActiveX broken during upgrade ?

Hi there,
Labview's ActiveX server seems to have broken in some way after upgrading from v.1 to 8.0.1
I had LV6.1 installed and the activeX server seemed to work ok, allowing me to browse LV from Origin.
I installed LV8.0 and upgraded to 8.0.1, whilst still leaving LV6.1 installed and the functionality to browse LV from origin disappeared when I was using LV8, if I opened LV6.1 then the activeX server functions seemed to work.
I uninstalled LV6.1, LV8.0 and the re-installed LV8.0.1 but the activeX functionality has not been fixed. Origin won't browse labview VIs.
I tried running the example "labview/examples/comm/freqresp.xls" and this fails when I try to run the VI from the excel macro - I get an "Compile error: Can't find project or library" with the line in the code "Dim lvapp as Labview.Application" highlighted as the source of the error.
Under tools|Options|Vi Server: Configuration, I have the ActiveX protocol checked and all the accessible server resources checked.
Any ideas on how I can debug this one and get windows to recognise LV8.0.1 as my activeX server ? Has the LV6.1 installation left something behind which is preventing LV8 taking over ?
regards
dave Langstaff

Hi Dave,
Sorry to hear you are having trouble with LV 8.0.1, the first suggestion I would give you is have you Mass Compiled your LabVIEW directory.
Tools >> Advanced >> Mass Compile
Once you have done that I would then look at your other VI Server settings.
Tools >> Options >> VI Server: Machine Access
Make sure you are allowing access to your local machine or all machines, so put in either your IP address or a * to allow all access.
Then please check VI Server: Exported VIs
and make sure you have a * to allow all access.
Please note that if you allow a IP or a VI in these lists (so they have a Green Tick) and then further down the list you deny all IPs or VIs (Red cross) then the deny will take precedence as it the last setting enabled.
Regards
JamesC
NIUK and Ireland

Error 0 occured at printing invoke node blb bla bla..., if I try to change the Postscript printing to bitmap printing using Options-printing menu.

Who might comment why I can not change the printing type without Error message in LV8.0.1. LV6.0 worked OK. Info: It is Russian locale system.
BR Vladi

Anyone?

XY Graph Zoom Mouse Wheel

I'm developping a very lightweight world map on XY graph. The attached VIs are LV8.0.
It almost works but I dont understand why it's not stable as you can notice by running worldmap.vi with zoom.vi as subvi. Your mouse wheel should zoom in, zoom out the graph's limits... I dont understand why it doesnt change X and Y ranges simultaneously... And the position of the mouse should stay on the same position of the world map, after zooming.
I realize that my comment is not really clear, you can try it and suggest what I should change, I'm using LV8.6, you dont have to spend time to save for LV8.0
Post question I should reply quickly.
Regards,
Jimmy
Attachments:
worldmap.zip ‏364 KB

The problem isn't with the notifier mechanism (although that code can be simplified). The problem is with the way you're calculating the new ranges and increments. When the calculations are done the proportions of the graph are not kept consistent, thereby causing a stretching of the "figure". Also, you are not putting a limit on the XScale.Increment and YScale.Increment such as when you hit the max/min scale ranges. This means that you can continue to "zoom out", with no chance in the scale, but the increment values keep increasing. This throws off the calculations when you try to "zoom back in".
My suggestion for using the picture indicator was not to try to draw 70,000 points. This would be way too slow. Rather, read in an image of the world to get drawn onto a picture indicator and then draw the axes over it. I don't know what your eventual goal is, so I don't know if this is a more suitable method.

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

LV6.1 to LV8 Upgrade Problems

Hello,
I am trying to load a LV6.1 vi in LV8. I can load it in LV6.1 with no problems, but when I try to load it in LV8 (on the same PC), it can't find these vi's:
Convert RTD Reading.vi
Convert RTD Reading (scalar).vi
AI Acquire Waveforms.vi
AI Acquire Waveforms (waveform).vi
I could probably open them directly from the LV6.1 program files folder, but this just seems like a bad idea. I would like to take advantage of LV8's new features - mainly the LV Project view, but I'm not sure what the best way around these missing VI's is. Does anyone have any suggestions?
Thanks in advance!
Derek

DerekSRD wrote:
My last interaction with LabVIEW and hardware was using "Traditional" NI-DAQ. Hopefully that will give you some background on my ignorance!
Here's the situation, one of our test fixtures that has not been used in a very long time, decided to have issues when we tried to run it. It contains some legacy cards:
AT-AO-10
GPIB0
PCI-6031E
PCI-6503
No this does not mean that you cannot use LV8 this just means that you cannot use Daqmx with the AT card you will have to use the traditional daq. Do not worry because you are already using traditional and just don't know it yet. ie AI Read, AI write and so on. Heres what I would do since all versions of LV can coexist together. I would make a copy of the vi and give it a unique name that way when you open it in LV 8 and in case it does not work you will have a back up copy that has only been opened in LV 6.1. Install LV 8 and daqmx 8. You will like daqmx it is much easier to use than traditional.
Joe.
"NOTHING IS EVER EASY"

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 KB

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

Binary file save - bug in lv8 for MAC ?

Hi,
Using LV8 on Mac OSX, I found a bug concerning binary file saving (attached file).
Write an array of double in a binary file. Read it back.
If you used little endian,ok. If you used Big-endian, result is wrong (but no error).
Could a mac user replicate ?
Boris Matrot
Attachments:
bin_file_save_lv8_mac.vi ‏14 KB

Just as an additional data point, everything works fine under Windows.
(As a workaround, have you tried flattening the data for writing? I don't have a MAC, so I cannot test.)
Message Edited by altenbach on 01-19-2006 12:41 PM
LabVIEW Champion . Do more with less code and in less time .

How to save graph to jpg file ?could you give me a demo vi of lv6.1 ?thanks

thanks

You could use an "invoke node" for the graph with method "get image". See attached LV6.1 code.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
SaveJPG61vi.vi ‏29 KB

Can't save the illustration. The file may be read only, or the file is in use by another applicatio

Getting error "Can't save the illustration. The file may be read only, or the file is in use by another application." The file is not read only and is not in use by another application.

The same thing may happen in Windows Explorer, specifically if it is a very big file (physical size), so preparing the preview may take a lot of time.
In that case it is used by "another application", that is: Explorer.
By the way, which version of Illustrator are you using, Tetons?

Best way to save entire program seperately in LV8?

Greetings.
What is the best way to save the entire application that I am writing so that I can go back a version if I make too many mistakes in Labview 8? Note that I use FPGA vi's which complicate matters.
To clarify, I am writing quite a large program, it has 900+ vi's and also many type definitions, even an FPGA program and vi's for some other hardware... various libraries, ect. I would like to be able to save the entire program including everything to... let's say version 1, and then make changes, save to version 2, then I would like to be able to go back to this working version 1. The problem I am currently having is that if I edit a type definition or anything other than the main vi in Version 2, then the version 1 of my program ceases to work as tt tries to use this same type def I just altered. If instead i do a build to a new directory for each version, the program tries to make me re-compile my FPGA program. What is the best way to handle saving different versions in Labview 8 so that they are complete and seperate but so that I can still edit them and so that they still access my FPGA vi without having to re-compile it? Note that my FPGA vi is already working so I'm not changing it with different versions of the program.
Thanks very much.
Richard Cisek
[email protected]

Create a "source distribution" of your project. (under "Build Specification" in the project explorer)
LabVIEW Champion . Do more with less code and in less time .

Globals in VIs converted from LV6.1 to LV8.0

All,
I

Thanks
Hopefully this will work.
All,
I am having a problem with Globals variables.
I have converted our code from LV 6.1 to LV 8.0. In one instance a VI writes some globals which are available for use in other independent VIs. After converting these global values are not reliably available when running the separate VIs. I see LV8.0 uses shared variables and have found info talking about usage and differences but nothing stating traditional globals must be converted to shared variables in LV 8.0.
Is conversion to shared variables the answer or am I missing something else?
Thanks

How to migrate LV 5 vi to LV8.5 - do I need to install V6, V7...

Hi
Have several large app's last worked on in LV5.1.1; these apps need updating to LV8+ now. Will I have to install LV6 in a machine, migrate the applications, install LV8, migrate the applications, install 8.0, migrate the applications, and then install 8.5 to finish the process. My bet is, there will be a large amount of effort involved.
Thanks
Blair Smith

Hi Blair,
Here is a link with a table that explains what versions of labview you can convert your VIs to:
http://digital.ni.com/public.nsf/allkb/7B7AC79F7742D492862570E7007E2387?OpenDocument
All you have to do is install any version newer than 5.1 and earlier than 8.5, followed by your 8.5 installation.
Let me know if you have any issues.
How many VIs are you converting? If it is only a few I can convert them for you and then you can save yourself the installation of an intermediate version.
Sappster

Need to use LV5 llb in LV8.6

I came across the attached llb of windows API VI's and would like to use them, but they are saved in LV5.0 Curious if anyone out there has the appropriate the LV versions to save this llb as LV6 or greater so I can open it with LV8.6? Thanks!
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
Solved!
Go to Solution.
Attachments:
windows_api_1.0.zip ‏186 KB

moved to here

Save a LV8.5 applicatio​n to LV6.1?

Similar Messages

Maybe you are looking for

Save a LV8.5 application to LV6.1?