Profibus labview 2009 install

I currently have a problem installing the visa drivers for labview that come with the DF profi 2, it tells me I need a Labview version greater than 7.1 -even though I have labview 2009 install. I could install the DF profi 2 in windows using the supplied ini... and labview MAX is picking it up. I can even run some of my older profibus slave programs by including the .bin file with my VI. The thing is I want to now try out the 'master' examples but so far have had no luck.

Dear WireJunky2,
the problem could be that, the necessary registry of LabVIEW "CurrentVersion" has been deleted by unisntallation of an old LabVIEW version.
Please check if the following necessary entries exist:
[HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW\CurrentVersion]
"VersionString"="9.0"
"Version"="9.0"
"Path"="C:\\Programme\\National Instruments\\LabVIEW 2009\\"
Regards,
Sven

Similar Messages

Labview 2009 install on windows 7 fails with error code 1935

Hello all,
I have problems installing LV9 on my windows7 machine.
It always ends with:
Any ideas would be welcome.
Thanks
Albert

Since it is not simple to reinstall only .net framework on W7 (it is part of the operating system),
I checked the .net framework with the .NET FRAMEWORK VERIFICATION TOOL
( http://blogs.msdn.com/astebner/pages/8999004.aspx.)
Verification succeeded for .net 2.0,3.0 and 3.5.
Since there are more problems on this pc. (1:windows update problems with strange errorcodes, 2:unable to turn windows features on/of)
i decided to rerun the W7 setup.
i selected the upgrade option , assuming this would update corrupted files, and it did.
After that LV9 installed without problems.
Albert

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

How to install Labview 2009 on Windows 7

This might be a Windows 7 configuration. I tried "Run as administrator" or Run in Compatibility mode" the setup.exe file. Windows 7 does not allows to copy files in the System32 folder, so I can't install Labview.
Is somone can help to install Labview 2009 on Windows 7?
Thank you

Seems as though you're seeing something different than what I first thought.
LabVIEW should install to a drive other than "C" without trouble.
I had a look around to see if anyone else had seen this problem, and I found something interesting here: http://windowstipsandfixes.blogspot.com/2008/10/error-1310-cant-write-to-configmsi.html
Specifically with regards to resetting the Windows installer with the following:
msiexec /unreg
msiexec /regserver
Other than that, I'm not sure what might be causing the problem you're seeing.
Patrick Allen

Installing 64 bit version of toolkit and modules for Labview 2009 64 bit?

Hello I recently contacted NIabout installing Mathscript and Signal processing toolkits for my Labview 200964 bit that I am running on Windows 7. I was sent the following link as aresponse: http://zone.ni.com/devzone/cda/tut/p/id/10383. From this link it is my understanding that I cannot run any programs thatcontain an astrestik, since they only work for 32 bit version of Labview? In particular I really need to use Mathscript. Is there any workarounds? Do I have to also install the Labview 2009 32 bit version? Doesanyone know when Labview will allow me to run everything in the 64 bit versionof Labview? Thanks.
Kevin

Hello Kevin,
There is no workaround available, and there are no released dates as to if/when Windows 7 x64 support for the toolkits in question will be introduced.
The LabVIEW Mathscript RT Module is not supported in LabVIEW 64-bit as mentioned at the bottom of the following page: http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/labview_mathscript/ .
Vivek Nath
National Instruments
Applications Engineer
Machine Vision

Unable to install LabVIEW 2009, "Unknown Error"

I'm installing LabView 2009 on Windows 7 on my Hp and when I run the setup after I unzip it, it come up with an error and says "Unknown Error". How do I get around it to install the program as soon as possible.

This is a screenshot of the error...
Attachments:
Capture.PNG ‏1152 KB

Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

We have discovered an issue with the above listed software. Specifically this pertains to Print Report.vi in the Report Gen palette. Basically, we have discovered that with Office 2003 installed the VI will error out. We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft). With Office 2007 we don't have a problem. We've tried building the examples into executables, and those work because they are printing HTML reports.
Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly. Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

yeah, we had seen that, and been told about it by another user. we tried, to no avail. we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

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)

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.

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 .exe not working with windows 2000

I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
Thanks
Solved!
Go to Solution.
Attachments:
Serial Number Reset Cell 2.vi ‏15 KB

There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
George M
National Instruments

Error in ni visa control out for usb in labview 2009

Hi,
I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface.
the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL OUT.vi gives error "0xBFFF003E : Could not perform operation because of i o error.". while the control in.vi works fine in both the labview versions and any other PC that i tried.
I have run the application in total of 4 PCs with same set of cards/interfaces. two of them having labview 8.6 are running fine and giving no error but other two with labview 2009 are giving error.
and it doesn't stop here.... i searched in the vi and did some experiment and found that when i give Request value input to control out.vi as "0x36 "(as required by my PIC program) then it is giving error but when i give other value such as " 0x35 or 34 or 55"(used for other purpose) then it is not giving error.
Can it be a PIC programming problem? (i dont think so as everything is fine in other PC with LV 8.6)
I have already explored the ni forum for this error solution but could not find helpful.
Can anyone solve my problem?

I installed labview 8.6 in that machine and made a small program with only 3 vis (visa open session, visa close session and visa usb control out.vi) which is working in LV 8.6 platform.
Sorry the above statement is not correct actually.
When i run the program in LV 8.6 it giving that same error but this time it is not displayed as pop up window. so i could not judge that error was still there.

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

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.

Profibus labview 2009 install

Similar Messages

Maybe you are looking for