From LV 10 to labview 2009

How you guys doing ?
can you please do the conversion for me to version 2009 ?
Thank you guys
Bill David
Solved!
Go to Solution.
Attachments:
Read raw data mod_HR_detrend_denoise(5).vi ‏98 KB

Hi,
Converted to LV 9
Kees
Attachments:
Read raw data mod_HR_detrend_denoise(5).vi ‏86 KB

Similar Messages

Excecutable VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly

Dear all,
I have a VI which runs perfectly and I can control, a Keithley 2612A for transistor measurements.
The VI run well when I excecute it from the computer which has the platform Labview 2009 (XP OS)
The equipment (ie Keithley 2612A) is linked to another computer which don't have labview 2009.
I installed Run-time-engine 2009 (OS XP 32 bits) on this computer.
Then I create an excecutable of my VI with the "build application" option.
The excecutable VI starts normally on the computer but when I want to run it, I am getting an error message from the Keithley 2612A (which was not the case when I ran the VI directly from the computer haing Labview 2009 installed on it). The error message is 222 (ie parameter too long)
I thought that I did something wrong and I create an excecutable from an original VI from Keithley (ie without any change). I am getting the same error message.
When I create an excecutable with run time engine 2009 included (as it is possible to do it wiht LB 2009) , I am geeting the same error message.
So I need no to check step after step when the message happens but
Does anyone knows anything about such an issue ?
Thank you
Solved!
Go to Solution.

Dear all,
Just for those who might encounter a similar issue.
I found the solution after tackling all possibilities.
The source of the problem was (for unknown reason) that the country setting of the computer was wrong
and decimal numbers were written with a , instead of a point.
Since I reset correctly the country setting, the stand alone files are running normally.
Best regards
Youki

Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing. Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO. I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
So far, so good. After much fighting with Windows 7 network location settings, I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
Any advice will be greatly appreciated.
Kevin
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
Export the variables from the master library as a csv file and copy that to the remote machine.
Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
Find the network path column (it was "U" in my file).
replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
NOTE the single quotes around the process name; they are required.
The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
Once the formula worked on line 2, I could copy it into all the other lines.
Save the CSV file.
Import the CSV into the remote library to create the variables.
Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
Open the properties for the first imported variable.
There is probably an error message at the bottom saying the alias is invalid.
In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
Change the setting to "PSP URL" with the same path and the error message should disappear.
Close the properties box, save the library, and then export the variables to a new CSV file.
Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
The first one is NetworkingleWriter; it should already be FALSE for all lines.
The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
Save the edited CSV file.
Go back to the remote library, and import variables from the just-edited remote library CSV file.
Once you have imported them and the Multiple Variable Editor opens, click on done.
You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
It actually took longer to write out the process here than to perform these steps once I figured it out.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

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.

Convert code from LabVIEW 2009 to LabVIEW 8.6

Hi Everyone,
Could a kind person with LabVIEW 2009 please save the attached code in LabVIEW 8.6.
The code is of the Creating an Office 2007-like Ribbon in LabVIEW community page.
It would be very helpful!
PS. Will reward kudos.
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Solved!
Go to Solution.
Attachments:
LabVIEW Ribbon.zip ‏306 KB

Any problems let me know and I will look at again
David
www.controlsoftwaresolutions.com
Attachments:
New Folder (2).zip ‏108 KB

LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

When installing our LabVIEW integration package on a system running
LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
walker' reveals, that 'nicont.dll' causes this crash because of a
side-by-side configuration problem. After some debugging I found out
that on this particular system installing a certain version of the
Microsoft CRT will stop LabVIEW from functioning. My fix now is to
recompile our code with a newer version of VS. I now ship a VS9 version
of the runtime and everything is working as expected.
However
I guess the real problem lies within the LabVIEW installer. I guess a
needed version of the CRT is not installed by LabVIEW. It still works
because due to some policy files on the machine it gots defaulted to a
compatible version at startup. However when I install the following 2
merge modules on the target system LabVIEW does no longer work:
Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
Renaming
the *.policy file in the SxS dir on the target system gets LabVIEW back
to run, but of course other SW needing this file does not run then
I was using XP, 32 bit SP 3
I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
Message Edited by anotherStefan on 02-05-2010 05:44 AM

Sure! I tried to attach the installer causing the problem to this message.
However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
It will install some other stuff as well (A bunch of VIs, a DLL and an
OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
The only difference between the two packages is, that the OCX in the
attached file has been build using VS2005SP1 and in the package the link
points to I did use VS2008. Apart from that I changed the 2 merge
modules from Microsoft (CRT and MFC)

Labview 2009 32 bit not running on xp 64 bit

Hi all,
I tried to upgrade to LabVIEW 2009 from LabVIEW 8.6 on 64-bit windows XP machine. Following about a 2 hour removal of 8.6 and subsequent installation of LV 2009 it turns out that the device drivers are not compatible with a 64-bit machine. On launching LabVIEW 2009 (32-bit) an error box appears stating that it is corrupt or missing files and to correct this using control panel etc. I have tried this and still the same error occurs and LV refuses to start.
All the license files are correct and the compnents are activated.
Anyone know how to fix this? Or should I go back to 8.6 and cancel my upgrade subscription?
Secondly, I am using a firewire camera and was informed that Ni-IMAQ legacy are no longer supported and to go to ni.com/ifo and enter legacy1394 to see how to download drivers etc for this. I end up on a page that says "not authorized".
Any help gratefully appreciated.
Solved!
Go to Solution.

Leeser wrote:
I agree that XP64 and LV 2009 are not compatible as I installed LV 2009 on another 32-bit machine with no problems. I was just surprised as there were no problems or issues that I came across for 8. on XP64. Ah well, a uninstallation and reinstallation lies in wait for me on Monday morning!!
As an aside why call it LV 2009 instead of LV 8.7 or even LV9.0...sounds reminiscent of an operating system!!
Regards,
Leeser
LabVIEW 2009 is according to the internal version scheme actually equivalent to LabVIEW 9.0. Why they changed the naming? I guess marketing told them to do so. Why then? Well marketing has some funny ideas sometimes. I guess since THE software provider in this world has started to do this since about Windows 2000 someone must have thought it to be the best idea since sliced bread and decided to do it for LabVIEW too.
Another guess is that in about 2010 there would have been something like 9.1, and 10.0 would then come out in 2011 and that sounded somehow to someone like a bad scheme so they decided to change it now. But maybe it will be forgotten and everybody returns to the old versioning at the begin of next year when 9.0.1 will come out, which would then otherwise be LV 2009.1??? Or maybe LV2009 SP1?
It has already happened with LabVIEW 6i (iMacs, iPhones, iAnything), LabVIEW 7 Express and LabVIEW 8.20 (following 8.0.1 and marking the 20th anniversary of LabVIEW, and being internally LabVIEW 8.2). All some marketing fun or hysteria.
Rolf Kalbermatter
Message Edited by rolfk on 08-17-2009 11:08 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Enum in a Typedef Reverts to Default (LabVIEW 2009)

When I add additional items to a typedef'd enum, constants of that enum on some BD's revert back to the default zero index enum value. In the past (8.6.1 and previous), adding items to an enum in no way would ever change constants that were already dropped on a BD. Now, in LabVIEW 2009, when I add items, about 60-70% of the constants dropped on different block diagrams will be changed to default value.
This happens in a "large" enum (~400 elements) that spans about 3 dozen VI's between RT and HMI block diagrams (a total of about 300 instances). This is a mature project that has never had this problem with 8.2, 8.5, 8.6, or 8.6.1...
I cannot post an example, because in the process of stripping down the VI, the problem goes away. It is extremely repeatable in the context of the project, but I cannot repeat it on an individual VI basis.
The current workaround is to edit the typedef'd enum while all referencing VI's are in memory. If the VI's that use the typedef are in memory, they will always properly recompile and maintain the correct constant value. However, if the VI is not in memory, and the typedef is changed, the next time the VI is opened, when it recompiles it will change the constants back to the zero index default value of the enum in only about 60-70% of VI's. Unfortunately, we cannot yet find a common thread in the VI's that recompile wrong, and the ones that recompile correctly.
Has anyone ever seen this problem? Suggestions?
Best regards,
Jack
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

We just realized a flaw in our "workaround", as partially pointed out by Ben (he was probably typing his response as we were confirming it here). If the constant is inside of a cluster on the BD, even if it is in memory, it will null out the enum inside of the constant. Therefore, the "workaround" is to rewrite the clustered enum constants from scratch (in other words, there's no workaround). Two of us spent a decent portion of the morning finally nailing this as the source of what we thought was an unrelated bug... and that's after spending a long day yesterday trying to find a fix. Yes, we feel Ben's angst of reverting back to previous SCC editions and manually editing dozens of VIs.
The severity of this bug is a showstopper for us. We cannot risk adding elements to an enum and consequently have referencing VIs changing their constants.
Force compiling a VI one at a time is not an option for us. I know this bug manifests itself even after a mass compile. So, is there a way to "mass force re-compile" that we could test?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Labview 2009 I/O assistant issue

Hi,
I'm using labview 2009, and I can't get the I/O assistant to work-everytime I try to run it, it gives me the error message "Measurement & Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from LabVIEW Driver CD". I've tried uninstalling and re-installing the I/O assistant, but it's not helping-is there anything else that can cause this error I should be looking for?
Thanks

Hi ciwong,
This problem usually originates from installation order. You want to install the drivers after you install after you install LabVIEW.
Another things that jumps out is that you are listing NI VISA 488.2 as version 2.1. The current version of NI VISA is version 5 and the current version of NI 488.2 is version 2.73.
Please let us know if you have any questions
Joe Daily
National Instruments
Applications Engineer
may the G be with you ....

Can i build an application with Labview 2009 for Windows 7?

Hello
i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
Solved!
Go to Solution.

Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application. After installation I had to move the files from 1 location to the other to make it work.

Build Specifications gone with LabVIEW 2009

I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
Is this a known issue and is there a fix for it?

Hello,
this might be a corrupt project file. Does this only happen with this project?
If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
Regards,
Joseph Tagg

Issues about labview 2009 application builder

first of all, sorry for my poor English ~~~i am not quite sure about whether i could make myself clear for you guys.here it is:
SFX-ZIP archive is choosed as the file format for built-exe in labview 2009.when building any project into exe in labview 2009, you can always turn the suffix of the application file into zip. then use any compress-decompress software to open that file.shocked? right? yes, all the vis that used in your project are there. of course, you can decompress all the vis from the archive.although the block digram is removed during the building process, they still can be dragged into any vi and work perfectly.
this is so insecure both for the application and the source code.how about you?
Message Edited by hunt978 on 05-10-2010 04:16 AM

Double post

LabVIEW 2009 x64 and application builder

Hi
My organisation has just got a site licence for LabVIEW so I have just installed 2009 x64.
My question is this:
If I build applications written using LabVIEW 2009 x64, will they only run on 64 bit computers? I would test this but both my computers are 64 bit machines. I have had a brief look through the build specs but there doesn't seem to be anything about 32/64 bit compatibility.
thanks.
J
Solved!
Go to Solution.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

LabVIEW 2009 build memory usage exceeds Windows limit

We have a large application that builds without problems using 8.6.1, but failed to build using LabVIEW 2009 with the error "Not enough memory to build this application".
We solved the problem by adding the parameter /3GB to the Windows XP boot.ini file. This increases the available memory for a Windows XP application from 2Gb to 3Gb.
It appears that LabVIEW 2009 uses more memory during the build process and, in our case, this took it over the 2Gb limit.

We are also facing the same problem...
can National Instruments help us ??????
Following error is occuring while creating exe.
"Build was unsuccessful
An error occurred while saving the following file:
D:\BIS_Main_2009_V3.XY\branches\BIS_Main_2009_V3.61_Trans\User Interface Panels\Inspection.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>"
Please suggest!!!

From LV 10 to labview 2009

Similar Messages

Maybe you are looking for