Le changement de version de labview de 6.1 à 7

I go on a project engineer. This engineer worked on labview 6.1 and I work on version 7.
When i launch the programm, VIs aren't known by version 7.
I want to know news VIs for this old VIs:
- dio port config
- dio port write
- dio port read
- calculate finite pulse specs
- counter group config
- conuter control
- counter set attribute
- counter get attribute
- set pulse specs
- normalize pulse specs
- finite pulse train.ctl
- generate delayed pulse
thanks

jumarion wrote:
> Les VIs que vous cherchez sont probablement dans les librairies
> LabVIEW \vi.lib\daq\digital.llb pour les E/S numériques et ctr.llb
> pour les compteurs.
Those VIs sit in vi.lib so they should be found automatically. If not
they are probably not installed. Install the correct NI-DAQ software
drivers and make sure it installs the NI-DAQ support VIs for your
installed LabVIEW version.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

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.

Identifying and Converting from an older version of LabVIEW

I have an old .vi program that I am trying to access and run now. I don't know what version of LabView it was written in but I do know it came off of a Windows 95 computer.
Any Suggestions?
Will Huntley
Solved!
Go to Solution.

You said "trying to". Does that mean you've been unsuccessful? On what OS are you trying to run it?
When you open an old VI in a newer version of LabVIEW, if the VI isn't too old, then it will open. If you close the VI you'll get a dialog asking you to save it. The "explain changes" will tell you the version of LabVIEW used to write the VI.
If you cannot open the VI because it's too old, and your LabVIEW is too new (e.g., opening a LabVIEW 5.x VI with LV2011), then you can post a request in the Version Conversion board. If the code is really old (e.g., LabVIEW 3.x or earlier), chances are you will not be able to get it upconverted since versions that old require a special toolkit from NI that is not publicly available.
EDIT: Duplicate answer. Was creating my response while Dennis posted his.

Is there a way to programmatically tell what version of LabVIEW a VI is compiled in?

Is there a way to tell programmatically what version of LabVIEW a VI is compiled in?
LabVIEW seems to know. If you click on "List Unsaved Changes", it (sometimes?) tells you the version of LabVIEW that the VI is already saved under (i.e., 8.0 instead of 8.0.1). So if LabVIEW knows, maybe they've provided a way for us lower-echelon folks (i.e., customers) to know too, eh?
Is there a way to get this from, say, VI Properties (i.e., Property Node gets passed a ref to a VI & I select the right property name)? I couldn't find any property name that has "version" or anything like that, but maybe what I'm looking for is using terms that are so different than what I'm expecting that I just can't tell.
Or by some other method? (I gvimmed a few .vi files, and see some stuff that looks like I *could* get the version by parsing/searching the file itself, but parsing the binary might give pretty unreliable results.)

Just dro a proerty node on the diagram and select property: "Application...Version number" and display the resulting string output.
Message Edited by altenbach on 07-02-2006 11:33 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
version.png ‏9 KB

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

"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

Event structures in older versions of labview?

Can anyone tell me how to create a workaround for a 'value change' event structure in an older version of labview? I have a student version of LabVIEW 6i and need to create a queued buffer from each value change. Thank you.

James.Morris wrote:
Ah, you're only one release away from the event structure. That's too bad.
You're going to have to implement a Polling loop that continuously checks the user inputs. Make sure you add a Wait function to the loop (~100ms) because that will act as your chance for the user to make changes. You can use shift register(s) to keep the previous loop's values and compare to get a bunch of Value Change booleans. If you want a specific case for the specific events, then you can group all of your Value Changes in to an array and act upon the ones that are True via a Case Structure.
The Event Structure only pulls a single event per loop and has a queue of events to handle for following loops. You might encounter multiple value changes in a single loop if the user clicks fast enough, or you trigger value changes. To avoid losing the trailing events, you should probably have a For loop within the Polling loop that handles all True values. Either that, or have a consumer loop that handles all of your events.
James, I swear I'm not picking on you today
You can set the maximum number of events alowed in the event queue per event in the edit event dialog box. Check box and int fields in the lower right side.
6.i didn't have a "Value (Signaling)" property- (a subject of some CLAD exam questions not that you suggested it)
Student editions could not use 6.i events. From 7.0 or 7.1 through 2011 Student Edition could use but not edit event structures. 2012 and on Event Structures are available in "All Versions" of LabVIEW- at the time. I haven't looked into the newer license options.
On to licensing options. (Not a lawyer! consult your Legal Dept!)
If you are not doing work towards earning a educational certificate you should not be using Student Edition. And, in some cases (Like working on a student project with commercial investment) not even then!
The Home Edition is also a new option. It is intended to enable fast "Proof of Concept" development or development for your sole non-comercial use.
LabVIEW Full and Professional are for comercial use and have a "Home Use License Agreement" clause attached. If your company owns a LabVIEW License you CAN install a copy on a "Home PC" for the limited use of aiding your employer (who paid for the license) such things would arguably enclude "Training"
NI is not totally opposed to negotiating "Exceptional" agreements for mutually beneficial reasons. Youl'd better bring a justification better than "I can't afford it" Go find some investors and buy a license in that case. And Yes, until the moderators take this down, I did at one time have a LabVIEW license for exclusively engaging the LabVIEW Community (Forums and NI Sponsored events use only- LAVA was not encluded) I'm not sure if such a deal could be negotiated in the future. In Fact, The Home Edition would have been less costly.

Programmatically Changing Build Version

We are wanting to automate our build process and we have a particular problem. We have been looking into the Jenkins tool and quite possibly, LabVIEW 2011 may help us out when we upgrade, not sure though. But before we look outside of LabVIEW for a solution, we want to run this dilemna by some of the LabVIEW users. We are using the Unit Test Framework and let's say we have some unit tests in our project. We wrote a wrapper VI that will do the following:
1) progammatically execute the unit tests using the Run Tests from File.vi.
2) unbundle the test status from the output cluster array and look for a "Passed" result
3) if the result is indeed "Passed" then this means that the overall results for the unit tests are OK and go ahead and call the Build Targets Programmatically.vi with the appropriate path, name of build and target. The name of the build is set in the properties of the build specification in the project.
This works fine. What we want is the ability to either auto-increment the version number (which the checkbox is selected in the build properties) or set a version for the build. Only when you press the Build button in the build specification properties does the version get incremented automatically, not via programmatically.

In versions before LabVIEW 2014, this was truly difficult, as the Version Number for a particular Build Spec is stored deep within the XML that is part of a Project (modify at your own risk). There are also some inconsistencies in the XML Tags, in particular whether the third dotted number of the Build Spec is called "Fix" or "Patch".
LabVIEW 2014 introduced a Set Build Specification Version that allows you to set the Build Spec within the Project by supplying the name of the Target (usually "My Computer"), the name of the Build Spec, and the path to the Project file. There is also in LabVIEW 2012 and higher (I don't know if this is present in LabVIEW 2011) a Build option called a Pre-Build Action, whereby you can specify a VI to run before the Build takes place.
In my LabVIEW implementation, my LabVIEW Projects live inside folders that are part of a SubVersion repository. I wrote a utility that, given the path to the Project File, can return the SubVersion Build number. Using the Pre-Build Action, I can call this Utility, get the SVN Build Number, and use Set Build Specification Version (or other LabVIEW code to diddle the Project XML file directly).
This, in fact, works, but there's a bug -- the file that results from this Build does not have the Build number specified by the Pre-Build Action. It turns out that as part of the Build process, the Version is cached first, then the Pre-Build Action is applied (updating the Version, perhaps), then the Build takes place using the cached Version. The "simple fix" is to Build twice -- the first time to save the SVN Version into the Build Version number, the second time to use this saved Version number in accomplishing the Build.
I've alerted NI to this conundrum. I didn't get the sense that they are willing or eager to change this behavior.
Bob Schor

Upgrading to latest versions of labview development software, drivers, engines

What is the best way to upgrade to a newer version of labview and drivers, but still maintain support for projects created and deployed with older software, drivers and deployment engines? If I have to make changes to an existing project and then deploy them to a controller or create an exe application, I seem to always have some issues when I have to update drives and deployment engines. Problem is I would really like to ulilize the newest software and drivers but the conversion of projects created in older version seems to be such a hassle. Any suggestions on the best way to do this would be helpful. I can offer more details if needed.

The most sure way I have found is to dedicate a PC to the LV version. I have a PC for 6.1, and one for 7.0/7.1. I do
develop with 7.1 and 8.2.1 on my laptop, but the 7.1 is only straight LV, no drivers to speak of.
Some pertinent threads:
http://forums.ni.com/ni/board/message?board.id=170&message.id=288055#M288055
http://forums.ni.com/ni/board/message?board.id=170&message.id=248018#M248018
Matt

HT4623 changement de version sur iphone 3

Comment changer la version actuelle 4.2.1 a plus actuel?

Most of the warnings probably have to do with coersion, since LabVIEW made a major change on how it deals with conversions in later versions. Usually, this is not a problem, and the program will run fine. Because you are getting warnings and not errors, the program will run. I would open the program in LabVIEW 7, save it under a different filename and then run it. Watch it carefully to make sure you are getting the expected results. If there are any changes needed, they should be minor.
Dave.
==============================================
David Kaufman
LabVIEW Certified Developer
==============================================

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
I have the professional development system
I can run the main VI
all the required DLL's are in the dependencies section of the project window.
I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
Thanks in advance to all labview users for your help
Attachments:
project window.PNG ‏36 KB

other PNG
Attachments:
Broken Arrow on EXE.PNG ‏179 KB

Multiple versions of labview on 1 computer

Hello,
I have just purchased LV 8.2 and am about to install it on my computer. The old version of LV I currently have on my computer is 7.1. Can I run both versions on the same computer or is it beneficial to take off LV 7.1 first before installing the new 8.2. Any opinions?
Azazal
Azazel
Pentium 4, 3.6GHz, 2 GB Ram, Labview 8.5, Windows XP, PXI-5122, PCI-6259, PCI-6115

Azazal,
You can certainly run both versions on the same computer. I have 6.1, 7.1, 8.0, and 8.20 installed on this machine and I regularly have more than one version open at the same time.
However, Paulo is very correct by saying that toolkits typically only install for one version of LabVIEW and that you need to be careful not to open your VIs in the wrong version of LabVIEW. If you were to open and save a LabVIEW 7.1 VI in 8.20 you would be unable to open it again in 7.1.
Matt, great links - I'm going to repeat that first one here in clickable form:
Installing Toolkits for Use with Multiple Versions of LabVIEW
Regards,
Simon H
Applications Engineer
National Instruments
http://www.ni.com/support

Problem with an old version of LabVIEW 4.0.1

Hi,
I'm rather new to this, so I appreiciate any help that you can give me. Our lab has an old computer running Windows 95 and LabVIEW v. 4.0.1. I would like to take one of the progams on this computer and run it on a newer computer in a different lab. This newer computer is running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000 machine, and then copied the needed file onto this machine. However, when I try to run the program, I get the following error messages:
Error 7 occurred at Open File+.vi: Open File
Possible reasons:
LabVIEW: File not found.
OR
NI-488: Non-existant Board.
after that error I get this one:
Error - 10401 occured at AO Group Config.
Possible reasons:
NI-DAQ:LV The specif
ied device is not a National Instruments product, or the driver does not support the device (e.g., the driver was released before the device was supported).
Now, there are a couple reasons that I can think of that would cause these problems. First, LabVIEW 4.0.1 is not compatable with Windows 2000. Second, I had to install the Windows 2000 driver for my PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW 4.0.1. Third, that there is something else that I need to copy over from the old computer. Once again, thank you to anyone that can help me out.

Raven3182 wrote:
> Hi,
>
> I'm rather new to this, so I appreiciate any help that you can give
> me. Our lab has an old computer running Windows 95 and LabVIEW v.
> 4.0.1. I would like to take one of the progams on this computer and
> run it on a newer computer in a different lab. This newer computer is
> running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000
> machine, and then copied the needed file onto this machine. However,
> when I try to run the program, I get the following error messages:
>
> Error 7 occurred at Open File+.vi: Open File
> Possible reasons:
> LabVIEW: File not found.
> OR
> NI-488: Non-existant Board.
>
> after that error I get this one:
>
> Error - 10401 occured at AO Group Config.
> Possible reasons:
> NI-DAQ:LV The
specified device is not a National Instruments
> product, or the driver does not support the device (e.g., the driver
> was released before the device was supported).
>
> Now, there are a couple reasons that I can think of that would cause
> these problems. First, LabVIEW 4.0.1 is not compatable with Windows
> 2000. Second, I had to install the Windows 2000 driver for my
> PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW
> 4.0.1. Third, that there is something else that I need to copy over
> from the old computer. Once again, thank you to anyone that can help
> me out.
You pretty much summed it up. NI-DAQ which is compatible with LabVIEW
4.0 won't support Windows 2000 almost certainly. And NI-DAQ supporting
Windows 2000 won't have VI support for LabVIEW 4.0. There was a
significant change in the way LabVIEW interfaced to NI-DAQ between
NI-DAQ 5.x and 6.x which happens to be around LabVIEW 4.x as well. So
you are most probably stuck with either a LabVIEW
upgrade or downgrading
to a Windows 9x computer.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How do I change the Version Code in the Flash Android settings Android app market?

I recently tried to update my app in the Android app market and when I uploaded it I got the following message:
"The new apk's versionCode (1000000) already exists."
In the Flash Adnroid settings I changed the version label but that did not help.
So I have two questions:
How do I change the Version code in the Flash Android settings? I changed the version number and version label but that did not work.
What is the difference between the version number and version label?

I tried that but it did not work. Apparently there is a difference between the version code and version number (which is set in the Android settings). From my research the version label is optional, so there are no problems there.
This is the what the XML file says:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<application xmlns="http://ns.adobe.com/air/application/2.6">
<id>com.company.nameofapp</id>
//Below is the correct version number, but has no relation to the version code.
<versionNumber>1.1.0</versionNumber>
<versionLabel>NewLayout</versionLabel>
<filename>Name of app</filename>
<description/>
I did find this piece of information for Androin version codes. (http://developer.android.com/guide/publishing/versioning.html) But I don't know how to place it into the xml file without conflicting with other code.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      package="com.example.package.name"
      android:versionCode="2"
      android:versionName="1.1">
    <application android:icon="@drawable/icon" android:label="@string/app_name">
    </application>
</manifest>
Any other thoughts are much appreciated.

Le changement de version de labview de 6.1 à 7

Similar Messages

Maybe you are looking for