LABVIEW 4.0 to LABVIEW 2010

Please your help with this Labview Conversion :
Source LabView version : 4.0.1
Target LabView version : 2010
Thanks,
Solved!
Go to Solution.
Attachments:
Weather.vi ‏168 KB

mass compiled with LabVIEW 7.1.1. This allows to open the VI in LabVIEW 2010. I do not have FTRUNLV.LLB in LabVIEW 7.1.1 = When I open the VI, it is broken. If you have this LLB, the VI should not be broken.
Attachments:
Weather.vi ‏123 KB
MassCompileResultLV71.txt ‏1 KB

Similar Messages

NI-LabVIEW run-time engine interop 2010 failed to install

Hi,
While installing Labview 2010 (32 bit) I got an error message:
NI-LabVIEW run-time engine interop 2010 installation has failed with the following error:
Error 1935. .... (see the .ppt for screenshot if interested)... HRESULT 0x8002802F
I googled HRESULT 0x8002802F and found a page that said that this error is usually b/c of a missing/corrupt entry in the registry: file %windir%\system32\mscoree.dll, and that "repairing the highest version of the .NET Framework on the system will correct any problems resulting from this error."
I have verified that mscoree.dll is not present, and I don't have the .NET Framework installed on my system. SO, I have the following questions:
1) do you concur with the advice given on the page referenced re: the reason for the error;
2) If so, should I install .NET Framework, and what do I then need to do in LabVIEW to tell it that the .dll is now present?
3) If your opinion is other, what do you advise?
Cheers
Attachments:
Labview Installation error.ppt ‏227 KB

Hi Luke,
After doing some research, there are two possible solutions.
1) According to a KB, it could be your antivirus. You may want to try to turn off any spyware blocking software such as Ad-Aware, Norton, etc and try the installation again.
2) Another customer had the same error, and they got it working by installing .NET 3.5 from Microsoft's website and then installing LabVIEW again.
Hope one of those options work for you!

Using LabVIEW 7.1 and LabVIEW 2010 on the same PC (Windows XP)

I have LabVIEW 7.1 on a Windows XP 32-bit PC and we plan to upgrade to LabVIEW 2010 soon. A lot of our software is using Traditional DAQ, DAQmx and DeviceNet. We need to use both versions of LabVIEW for some time on the same PC. Is this possible at all?
I installed an evaluation 2010 version and now I don't have DAQ and DeviceNet in LabVIEW 7.1. Any suggestions will be very helpful.
Thanks, Nick
Solved!
Go to Solution.

For what it is worth, I tried having multiple versions of LabVIEW on the same PC. If you are (very) careful, it is possible to do so, as long as you are only doing development work, i.e. you don't try and install LabVIEW drivers. However, as I've discovered to my great sorrow (which involved installing and removing various versions of LabVIEW on the same machine probably 5-8 times, eventually leading to wiping the machine and installing WinXP all over again, then only one version of LabVIEW), if you want to actually run your code, particularly if it does anything with hardware, you need to stick to one version!
There's another "gotcha" for those of us working with "older" versions (namely before 2009, though one can "trick" 8.6 if you're careful) -- Windows 7 doesn't "play well" with the older software!
So my development machine runs Windows 7. I have a VM of Windows XP in which I installed LabVIEW 7, which I use for my "legacy" work -- I use the Win 7 machine for LabVIEW 8.6, 2009, and 2010 development (and only development, see above).
The machine that got "rebuilt", where I wanted to run LabVIEW code for various hardware and potentially various LabVIEW versions, I did a really nutty thing -- I created a quadruple-boot PC! (It really is a triple-booter, as the Windows 7 system, which is the key step, is "hidden"). To make this work properly, I needed three hard drives in the machine (one for each OS -- I might have figured out how to put two XPs on a single drive, but since I already had the disks, one-OS-per-disk seemed easier). I'm using Windows 7's Boot Loader to give me the startup choice of which system to use (the message says something like "System for Hardware A", "System for Hardware B", "Test System"). True, you need to do a Restart, but since you're going to be collecting data, it's not such a bad idea to start with a "fresh machine".
[I did think about doing this with Virtual Machines, which would have been much simpler, but I didn't have "virtual drivers" for the hardware! One piece was actually a USB device, but the other was a proprietary device that plugged into my PC ...]

Upconvert from Labview 5.1 to Labview 2010

Please convert these VIs (in zip) from labview 5.1 to Labview 2010
Solved!
Go to Solution.
Attachments:
c3d_reader_labview_b.zip ‏864 KB

Attached as 8.2, which you can open.
Note: The VIs in the "Files IO" folder have been deprecated. You should replace them with the single Read from Binary File function.
Attachments:
C3D Reader.zip ‏706 KB

Seamlessly migrating Labview 6.1 to Labview 10

Hi,
My company have several legacy projects that were written in Labview 6.1.
We recently bought Labview 2010 and tried to convert the projects over and found several issues:
1) Report Toolkit changes
    Write PNG (word). vi
    Write JPEG (word) . vi
    were missing
2) Received the following warnings:
   Labview changed a constant that was wired to a Case Structure to a hidden control to maintain compatability with Labview 7.1 and earlier
Is there an easy way to port from Labview 6.1 to Labview 2010?
I am not a Labview developer myself so pardon me for any silly questions.
Thanks & Best Regards

Generally upgrading over 4 versions will result in some warnings and some things broken, as you have observed. First thing is to save the warnings to a file so you can go back through it as often as necessary.
Use the dialog which comes up when you try to run the broken (upgraded) VI. That will take you with one click to places where something is broken. Systematically work through those. Often replacing an obsolete subVI with one from the current palette takes care of most of the problem. You may need to reconnect wires if the connector pane is different. For some replacements you may need to change datatypes on inputs. Examples include arrays to waveform or numerics to enums. As you do this check the functionality of the replacements to see if anything has changed which will affect the performance of your program.
Then work through the warnings list. Verify that the warning does not cause undesired behavior in your program. If it does, then you need to change something. If it does not, make a note to consider modifications to get rid of whatever the warning was about after everything is fully functional.
Although it does not sound like this has occurred in your case, consider whether it would be better to use the old program as a guide to establish a test or performance specification. Use that to write a new program, probably with a better architecture and taking advantage of new features. For example the old program might use lost of sequence structures and local variables, making it difficult to modify or even to understand. The new one might be written using a Producer/Consumer architecture and LVOOP techniques. Rewriting may not take much longer than trying to "fix" the old program and results in a program which takes full advantage of new features and techniques.
I am planning a rewrite this summer or fall in LV 2010 or LV 2011, depending on timing, of a program whose ancestor was written in LV 1.2 in 1988-89. The kind of rewrite I described above has already been done twice on this program.
Lynn

How to open labview program with Quit Labview function inside?

Hi Any idea how to open labview program with Quit Labview function inside?
I forgot to add and set the condition of the type for this program.
If the program is an application, it would close straight away.
If it is still labview work, it will go straight to editing program without closing.
So I need to recover, open it and make some changes.
Clement
Solved!
Go to Solution.

Put the VI in a project and open it from there, then it shouldn't autorun. You can use App.kind property of application to decide whether to close or not.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

From Labview 9.0 to Labview 8.2.

I need a conversion, if possible, from Labview 9.0 to Labview 8.2.
Thank you for the support
Attachments:
Write Std Out with Redirection.vi ‏24 KB

attached
WARNING: There is a bug in LabVIEW 8.2 where you cannot use the error cluster to chain together the Call Library Function Nodes. You will need to either create wrapper VIs for each CLFN or you will need to use case structures around each call.
Attachments:
Write Std Out with Redirection.vi ‏28 KB

UDP Error when upgrading from Labview 8.6 to Labview 2009

I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

Can I run 64 bit LabVIEW and 32 bit LabVIEW on the same machine?

If I have a 64 bit OS (Windows 7 64 bit or Server 2008 64 bit) can I install and run 32 and 64 bit LabVIEW on the same machine?
John

LabVIEW 64-Bit vs. 32-Bit Applications FAQ
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
The FAQ will likely answer other questions you have regarding the restrictions and issues you will have with having both versions and compiling in one vs the other.

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I can think of two possible stumbling blocks:
What are your 8.6 options for "byte order" and "prepend array or string size"?
Overall, many file IO functions have changed with LabVIEW 8.0, so there might not be an exact 1:1 code conversion. You might need to make some modifications. For example, in 7.1, you should use "write file", the "binary file VIs" are special purpose (I16 or SGL). What is your data type?
LabVIEW Champion . Do more with less code and in less time .

How to open labVIEW 8 file in LabVIEW 7.1

Hi
I want to open a LabVIEW 8 file into LabVIEW 7.1 version? when i tried to open there is an error appiers and I couldnt open it so please give suggestion how to open it..
Thank you

If you open the vi with a higher version of LV and save it, you can't open it with the earlier version, as I said before, because the vi is no backward compatible.
What you could do is open the vi with LV8.0 and browse the menu to File >> Save for Previous Version. Then just follow the instructions given on the dialogs.
Using LV8.0
Don't be afraid to rate a good answer...

I want to convert my source code in Labview 5.1 to labview 2011

HI
I want to convert a labview program which is in labview 5.1 to labview 2011 version
i am not able to open the program in the 5.1 version.
if there is no way to convert it ,then can you tell me if 5.1 version is avialable online that is compatible with the windows7 .?
thanks
Attachments:
plant.vi ‏31 KB
PID.vi ‏104 KB
integration3.vi ‏18 KB

Post your request in this Version conversion Board
The best solution is the one you find it by yourself

How to open program developed using labview 8.2 in labview 7.1?

Dear friends,
I need to open program developed by using labview 8.2 in labview 7.1.help me in this regard?

In order to open it up, you have to backsave it to 7.1. You would need to first save it to 8.0 and 8.0 can save it as a 7.1 file. Attach your VI and ask if someone can do it for you if you don't have the intermediate version.

Error Code "1097.....this might corrupted LABVIEW's memory.........." appears after exit the labview and re-start labview

        I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
        The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
        The only solution now is to re-generate or update the wizard to generate the API.
        I try to find the answer in
        http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
        The paragraph in above article shows
         "LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Attachments:
test_api.h ‏1 KB
link_test_api.h ‏1 KB

wewe1215 wrote:
        I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
        The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
        The only solution now is to re-generate or update the wizard to generate the API.
        I try to find the answer in
        http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
        The paragraph in above article shows
         "LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Which of the 2 functions do you call? How?
The documentation of InitSocketEx() seems to indicate reversed parameter order than what the function prototype looks like!
I indeed do not see much possibilities to pass in to small a buffer that the DLL function might be overwriting past the end. This really only leaves one more possibility:
Your DLL is doing something largely illegal somehow. Maybe something as silly as storing the reference to the ipAdress instead of the address itself. The memory passed as parameters into a C function is generally only valid for the duration of the call. This is especially true if you use LabVIEW since LabVIEW will re- and deallocate memory buffers frequently as soon as they are not used anymore and the parameter to a Call Library node is considered to not be required anymore after the function returns.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Request to downconvert from LabVIEW 8.0 to LabVIEW 7.1

Hello,
I'd really appreciate it if someone could downconvert this instrument driver library from LabVIEW 8.0 to LabVIEW 7.1.
Thank you!
Brooks
Attachments:
hp34970a.llb ‏2094 KB

Try the Version Conversion Board. That is what it is there for.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Load VI from labVIEW 8.6 in labVIEW 7.1, run VI from later version

I'm trying to use VI server to load and run application wrote in labView 8.6 using labView 7.1, becouse I don't have this library for 7.1, but when I'm trying to attach reference of 8.6 vi I can't do that, "The selected file is not valid". How should I do that ?
Thank you for replying
Karol

You migth be able to do this the hard way:
First you need some 8.6 applicatoin that has the VI-server .Net interface enabled.
In LabVIEW 7 you can open a .Net reference to this application and perform the normal VI-server routines.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

LABVIEW 4.0 to LABVIEW 2010

Similar Messages

Maybe you are looking for