Which version of labview?

How can I tell which version of labview was used to create a vi and application?
Is there a VI viewer.

Hi Sally,
No VI viewer as far as I know... To know the version of LV used... hummm... ... Do you have any idea if it's close to LV2 or LV8 ?
There might be some tricks but I would try open with LV5, then LV6 and so on starting from the oldest version you have.
When you know the first digit (e.g. LV7) I have no idea of how to find out if ti was LV7.0 or 7.1 or 7.1.1....
I often have to switch form a version to another when I maintain old apps so I always put that kind of info in the "documentation" of my VI...
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Similar Messages

Which version of LabVIEW needed?

I developed an application with the students version of LabVIEW 6.1 (prof.). I think I don't need all the features of the prof-version. Now I want to use the version 7. How can I find out which editon (Base-, Professional- or Full-System) I need? Is there a testversion of the base-edition?

The base version is just as the name implies. You would be better off if you chose the full developemet edition of labview 7.1(current version) This will give you all the functionality of the base version plus a lot more features. Some you may not need NOW but will become valuable in the future as you use labview more. I think the full version will satify your needs. Here is a link you can use to make a better choice.
http://sine.ni.com/apps/we/nioc.vp?cid=1382〈=US
Hope this helps
Joe
Joe.
"NOTHING IS EVER EASY"

Could there be independent VI paths for different versions of LabVIEW?

Hello,
When jumping between different versions of LabVIEW (6.1, 7.1, 8.5) it is annoying that the current path for one becomes the current path for the other.
If I am working with LV 7.1 in a folder dedicated to 7.1 VI's, and then open LV 8.5, I don't want 8.5 to go to that 7.1 folder by default. Alternately. if I was working in LV 8.5, closed it out, and then I click on a 7.1 VI, I don't want it to open in LV 8.5.
I've tried changing the path options in each version of LabVIEW, but that doesn't seem to help. Is there any way of isolating these folder paths from one another? One of our newer LV guys accidently opened some 7.1 code in 8.5.1 and then saved it. Luckily, I had archived code to return to, but it could have been a disaster.
Thanks for any ideas,
McSynth

You're actually asking two different questions.
The first question has to do with which version of LabVIEW gets launched when you double-click a file. This is an operating system thing. The one that gets launched is the last one that got used. (Your first question will be: can this be changed? Answer: Change the operating system. Or, play around with the registry each time you quit out LabVIEW.)
The second question has to do with search paths. These are independent. However, a VI will contain information about its subVIs in terms of where to find them. This is not a function of LabVIEW, as it is a function of the VI. Thus, it will make no difference which version of LabVIEW you use to open the VI. You can, if you wish, modify the search paths that LabVIEW uses to find VIs for each version of LabVIEW from the Tools->Options menu. However, this will not eliminate the problem, and your best bet is to keep those backups frequent.

"VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

Hi,
I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
Solved!
Go to Solution.

Hi Rajshekar.
> Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
- The version of Labview on the win7 64bit PC is also lv8.6 full development system.
> Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
- the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
I have listed the environments in which application ran and how the application was put in to the PC.
I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
1. Use the installer to install the application.
2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
3. The PCs might either be a blank one with no history of LV installed in them
4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.
Thanks

Controlling different versions of LabVIEW

In "NI eSupport News Vol. 6, No. 11 - November 2002" you brought following, but the link does not work (wrong subject). And can't find the subject on your web. Got another link??
<==Controlling which Version of LabVIEW Opens When You Double-Click a VI in
Windows==>
If you have two or more copies of LabVIEW on one computer, you might notice
that when you double-click a VI in Windows, the last version of LabVIEW you
closed will open. The following KnowledgeBase document describes how you
can double-click a VI and have a specific version of LabVIEW open:
http://digital.ni.com/express.nsf/express?openagent&code=esup110211

Sorry about that. We'll fix the link to point to the right place, but meanwhile, here's the KnowledgeBase entry that was being referenced:
http://digital.ni.com/public.nsf/websearch/63EB67ED9D45797E86256C35006C257E?OpenDocument
Or, you can search the KB for document ID 2PEDLK2Q.
Regards,
John Lum
National Instruments

Using mutliple versions of LabView

I am using 3 different versions of LabView right now (7.1, 8.0, 8.2). Mainly because I haven't had time to upgrade all our software to 8.2. Some of the programs I don't want to upgrade yet because I don't have time to fix the bugs that come with updating them to newer versions of LabView. My question is weather LAbView knows which version of LabView to use to use to open VIs when I open them through windows explorer or if it just defaults to the last one used.
Regards

Basically, LV opens VIs in the last version you started (although 8.2 has an apparent bug in that area).
If you force explorer to open VIs in a different version (right click the VI and select Open With...), then it should start trying to open them in that version.
Dataact makes the LabVIEW version chooser, which I believe should make it easier to select, but I haven't tried it.
Try to take over the world!

Is Windows XP supported, and by which versions of NI-DAQ and LabVIEW?

Which versions of NI-DAQ, LabVIEW, and LabVIEW Run-Time run under Windows XP?

For all Windows/LabVIEW/Toolkits compatibility questions, check out this KnowledgeBase.
(I know this is a pretty old post, but I'm replying anyway for posterity.)
Happy developing!
Sarah K.
Search PME
National Instruments

Poll - Which Version Control Software Do You Use With LabVIEW?

I wish the forums had a poll feature. I created a poll in the developer community - Which Version Control Software Do You Use With LabVIEW?
http://decibel.ni.com/content/polls/1818
Edit: I just saw that there already is a poll for that
http://decibel.ni.com/content/polls/1050
=====================
LabVIEW 2012

julieann wrote:
You can use a source control provider to share files among multiple users, improve security and quality, and track changes to shared projects. Use LabVIEW with third-party source control providers so you can check out files and track changes from within LabVIEW. See info. here.
Looks suspiciously like someone trying to increase hits on their blog. A coincidence that it was posted the same day as the blog post?
Message has been reported to the moderator. Laura can decide whether or not it's appropriate.

Can NI-PSP be used to communicate between machines developed with different versions of LabVIEW?

Hi all,
A customer has a large PC application developed with LabVIEW 2010 SP1.
They would like to add extend their system with a cRIO-9075. According to this document (ftp://ftp.ni.com/pub/devzone/tut/crio_software_versions.htm ), the minimum supported version of LabVIEW (with Scan Engine support) is LV 2011.
To minimize risks, it is preferred that we don't upgrade LabVIEW for the main application, which is atively being used in production.
I was thinking of developing the cRIO software in a newer version of LabVIEW (say, LV 2013 SP1), and using shared variables only to communicate between the PC and the cRIO.
Is this a viable option? Does it matter if the PC and the cRIO have different versions of the LV runtime?

It shouldn't matter, but then with shared variables you can never know for sure -- there are so many things that can make them break.
You might be money ahead to write the comm using TCP/IP. You know that will work.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How do I determine which version of windows os is installed on the computer that my application is running on.

I need to determine which version of windows os in on the computer running my application to make some minor adjustments to a subvi. Is there a programmatic way to determine this using Labview.

Or, use the Application property node Application>OS>Detailed Name. Although I can't say anything about its output on other-than-Windows OSes.
By the way, I think you win the "reviving old thread" award today
Dave
David Boyd
Sr. Test Engineer
Philips Respironics
Certified LabVIEW Developer

Is it possible to open a VI using an older version of LabVIEW, and if so how?

As stated in the title. I have installed all the run-times from lv6 to lv8.6, but cannot open any VIs that have been compiled in a more recent version of LabVIEW. We run (on different computers) lv5, lv6.1, and lv8.5. Upgrading some of the older machines is not possible since they cannot handle the required OS.
Is there any way to open a VI created/compiled in a higher version of LabVIEW? This is proving to be a major sticking point with us and our ability to transfer VIs between computers.
James
Never say "Oops." Always say "Ah, interesting!"

Hi James,
I was able to use VI server to invoke LV 6.1 VI's using LV 7.0 without issue.
After discovering this and mentioning it in a post somewhere, Rolf Kalbermatter indicated that was expected. and I should not be suprised.
So....
Vi Server may help you.
James Mamakos wrote:
Is there a separate place for me to post VIs to be converted? What's a ballpark figure for the maximum file size i could put on to be converted?
Do you know if the LabVIEW developers can/will create a way to overcome this problem rather than having to convert a VI through all the intermediate versions?
To the best of knowledge NO.
For each versino of LV there isw code included that runs behind the scenes when you open a VI from an earleir version which replaces old functions with the new versions. This is called Mutation code. To accomplish its task it has to know everything that changed between version X and Y. Since it is possible to baby step the versions up and the number of user that jump multiple major versions is small, I don't think any effort will go into that work.
THe largest attachment I have managed to upload was 3 or 4 Meg.
Just trying to help,
Ben
Message Edited by Ben on 04-28-2009 08:58 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

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

I have upgraded to newer version of labview, and the older versions of LavVIEW are now piling up. Can I uninstall the older versions? if yes how?

Do I have to keep all the old versions of LabVIEW as I did not uninstall the older versions, but only downloaded the latest version of labview from the website and installed it. A new version and icon is installed on my PC now. What can I do?

You asked "Do I have to keep all the old versions...". Of course not. You can do whatever you want. Each version of LabVIEW installs in its own directory, which is what allows you to keep multiple versions installed in case you need to support programs written in earlier version that cannot be upgraded yet for whatever reason. Conflicts may arise if you install older versions later than new ones and you install the libraries for the hardware interfaces like VISA and such. Older versions of these libraries sometimes cause problems with newer versions of LabVIEW.
If you do not want multiple versions, common practice is to completely uninstall the current version before installing the new one. If you have more than two versions but only want the latest, simply uninstall the older ones from the main NI installer. Depending on how old the versions are that you are uninstalling something with the new one may break so you may need to repair that installation. You may just want to simply uninstall all NI software and then just do a clean install of the latest version. That will likely be your best course of action.

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

Can we use latest version of Add-Ons and Toolkits with older version of LabVIEW core?

Hi every body
I'm new to LabVIEW
I have a question .
Can we use (indeed install) latest version of Add-Ons and Toolkits(for example 2009 or 8.6.1 version) with older version of LabVIEW core(for example LabVIEW 8.6)?
No problem ?!
I have LabVIEW 8.6(Evalution) and I want istall Real Time Module 2009.
Message Edited by mostafi on 10-31-2009 02:49 AM
Solved!
Go to Solution.

I think perhaps 8.6 and 8.6.1 is compatible. But I am 100% sure that 2009 and 8.6.(1) is not downwards compatible
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Which version of labview?

Similar Messages

Maybe you are looking for