Compilation sous LabVIEW 2009 et windows XP

Bonjour,
J'ai besoin d'une info :
Est-il possible de compiler un exe sous LabVIEW 2009 et windows XP et le faire tourner sous windows 7 ?
Merci d'avance.
Philippe B.
Certified Associate Developer / Dépt Moyens d'essais
www.ingenia-system.com

Bonjour,
Oui c'est possible
Le run-time de LabVIEW 2009 est compatible avec Windows 7.
Tant que vous ne souhaitez pas creer un executable 64 bits cela reste possible.
Que vous compiliez un executable sous Windows XP ou Windows 7 sa structure reste la meme.
Cordialement,
Da Helmut

Similar Messages

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

Equivelent Solver Excel sous LabView 2009

Bonjour,
Je souhaite reproduire le comportement du Solver Excel sous LabView 2009 ?
Mon objectif est de tracer un Fit Super Gaussien d'odre N avec 4 paramétres à optimiser et un à minimiser.
Merci d'avance pour vos retour.
Cordialement
Jean,

Bonojur,
J'ai fait plusieurs recherches sur les différents outils disponible dans la palette mathematics=>fitting mais cependant je ne trouve pas de fonction permettant de gérer 4 paramètres à contraindre avec un fit d'ordre >2..
La fonction qui me semble s'appocher le plus de mon besoin est:"Nonlinear_Curve_Fit.vi" cependant j'ai plusieurs erreur liée au paramètre d'entrée.
Ci-joint un exemple de ma test.
Cordialement
Pièces jointes :
TU_Piste_3_Nonlinear_Curve_Fit.zip ‏107 KB

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.

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

Newport Conex-CC drivers for LabVIEW 2009

Dear all;
I am using LabVIEW 2009 on Windows 7. I need the drivers for the Newport Conex-CC controller. They are available in the web site http://www.newport.com/CONEX-CC-DC-Servo-Controller-Actuators/934114/1033/info.aspx#tab_Literature , but the version is LabVIEW 2010, so I can`t open them.
Please, could anybody open the .vi's, save them as LabVIEW 2009 or older, and attach them to a reply message?
Thank you.
Javier

Please post the VIs to the Version Conversion board. The link is at the top of the LabVIEW board.

Compatibilité Labview 2009 Windows / Labview 8.5 Linux

Bonjour à tous
J'ai une petite question à laquelle je suis certain bon nombre d'entre vous avez une réponse
J'utilise deux PC avec Labview 2009 WIndows sur chacun qui communique avec la fonction UDP.
Seulement voilà, la trame qui va d'un PC à un autres, je souhaiterais la faire passer par une passerelle, un troisième PC, toujours en UDP mais lui équipé de Labview 8.5 sous Linux.
Le truc c'est que cela fonctionne pendant une minute ou deux et après la communication s'arrête au niveau du PC Linux Labview 8.5
J'aimerais donc savoir si la communication UDP entre Labview 8.5 Linux et Labview 2009 Windows est bien possible
Je vous remercie énormément pour vos réponses....
A très bientôt.
Vincent

Bonjour,
Si vous voulez vérifier la compatibilité entre Linux et Windows, le mieux serait d'utiliser les exemples LabVIEW. Ces exemples se trouvent dans Aide>Recherche d'exemples...>Réseau>TCP & UDP. Vous pourrez ouvrir "Client de données simple" (ou "Simple Data Client") sur votre LabVIEW Linux et "Serveur de données simple" (ou "Simple Data Server") sur votre LabVIEW Windows.
Après l'avoir configuré selon votre configuration, exécutez en premier le Serveur de données simple sur Windows puis le Client de données simple sur Linux.
D'après l'aide de la fonction UDP Open de LabVIEW 2011 une mention a été ajoutée par rapport à l'aide des version 8.5 et 2009. Il semblerait qu'il y ait un comportement particulier aux version non Windows de LabVIEW lorsque vous cablez l'entrée "net address". Dans le cas où les exemples ne fonctionneraient pas, je vous conseil d'essayer en supprimant cette entrée et de ne vous baser que sur le port de communication.
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

My compiled program crashes after first run (LabVIEW 2009)

I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly.
The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM). On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's. Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running. The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down. The program is then gone from memory as far as I can tell. There are no processes in memory or anything.
Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once.
In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see. Also, when I run my program in the development environment the program does not behave this way. It has no problems at all.
I have used this style of architecture before in LV8.6 with out any problems. Can anyone suggest some possible solutions or even some debugging tips? I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue.
Thanks for any help.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!
Solved!
Go to Solution.

I have solved the problem I think (at least as far as testing to this point has revealed). After I added in the ability to log the states passed to the QDSM's, I was able to determine that the program was "crashing" after I dynamically closed the front panel of the launcher. My program was designed to close the front panel of the launcher then pop-up the front panel of the main UI. My EXE is built on to contain the launcher with my other QDSM files being maintained externally in specific directories. What appeared to be happening is that when the launcher closed its front panel and before the UI opened up the run-time engine would decide since there were no windows open it would close itself down. This is my supposition about what may be happening any way. I modified my code to changed the launcher window to hidden and delay for 1/2 a second to give the main UI a chance to start fully running. This fixed the problem, or at least worked around it. If someone out there can explain to me exactly what is happening I sure would appreciate it.
Thanks for all the help those of you who responded. Your advice was very beneficial and certainly led me to a resolution faster.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

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

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

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

Font size on Windows 7 with LabVIEW 2009

Hello,
after installing labview 2009 on windows7, I have a problem with the font size of my old application written in 8.6.
the Application Font has seemed to default to another style under windows7 so I searched the forum for the default font under XP when I used lv 8.6. Tahoma 13pt seemed to the correct choice, however when i changed all default fonts to Tahoma 13pt it helped and they look very similar, but the Tahoma under windows7 is slightly longer that the original and it looks like there is some sort of font smoothing going on... perhaps windows is doing its "cleartype" thing by default and influencing its length (thou i thought this shouldnt be the case).
This small difference is causing havoc in my GUI as objects are being resized in a bad way.
Please see the screenshot for an example of my concerns
Another question on the side... is there a Font I can use that will keep the appearance and size over all OSs?
Any help would be appreciated...
Best Regards
Alex.
:. LV2010 SP1 ... W7 .:
Attachments:
Font Difference.png ‏3 KB

Actually this problem affect LabVIEW itself even while editing!
Many of NI's screens suffer from the same problem. Configuring events is one of the most obvious cases. Since teh edit events screen does not allow for resizing, there are some events that you can only guess what they are.
I tried reporting this but the AE wanted me to spoon feed screen shots and ....
I think what really irks me over this problem is that I purchased a laptop with the biggest screen available just to let me do LV and in the end LV can't handle the laptop.
Double -
Ben
Message Edited by Ben on 05-06-2010 10:13 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_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_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
Any suggestions?
Thanks

For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine. On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
This may not be a complete fix to the problem but at least in this one case it worked.

Support in LabVIEW 2009 for IMAQ legacy drivers on 64-bit windows

Hi,
I have been trying to use a VI that was created in LabVIEW 7.0 that makes use of IMAQ 1394 VI's in LabVIEW 2009. When I first tried to run the VI an error told me that the VI's in question were missing, to overcome this problem I thought I should attempt to replace them with legacy VI'. After downloading the legacy installer, I then realised that these VI's would not function on a 64-bit version of windows even though I have a 32-bit version of LabVIEW.
I was wondering if there is an alternative way of replacing these VI's or a way of implementing the lagacy VI's? Would it be suitable to replace the IMAQ 1394 VI's with IMAQdx VI's?
Thanks for your time,
Alistair Martin

Hi Alistair,
The following KB states that it should be possible to do what you require: http://digital.ni.com/public.nsf/allkb/3358528DF8648DC2862571F500586140?OpenDocument
The KB also links to some development articles for upgrading and using IMAQdx to acquire from 1394 cameras.
I hope this helps,
Kind Regards,
Applications Engineer

My compiled help files was working and now is broken in LabVIEW 2009

I've created a .chm file for distributing an add-on VI Library. In order to get my product certified as "LabVIEW compatible", a help file with pretty good documentation is required. Using the Microsoft Help Workshop, I have created a .chm file that works in LabVIEW 8.5 and 8.6. Once I distribute to LabVIEW 2009, the javascript portions of the help file fail. These functions are:
1) Place on Block diagram
2) Find on Functions Palette
3) Open Example
I have determined that this is due to a variable written in NI glang.chm file. The file internal to the chm file is called "lvversion.js" and contains a variable named "lvversion". The marketing decision to name the product "LabVIEW 2009" has contributed to this problem since this variable is equal to "9.0.0", yet the path is (typically) C:\Program Files\National Instruments\LabVIEW 2009\help
I originally decompiled NIs glang.chm file to analyze the javascript functions that are required for the above 3 buttons to work.I found that NI hardcodes the URL of the help services in a file called "helpserver.js" to be something like "http://127.0.0.1:3580/National%20Instruments/LabVIEW/LabVIEW {major-version}" where major version is "8.5" rather than "8.5.1"
A call to the function "openProj" would then look something like:
http://127.0.0.1:3580/National%20Instruments/LabVIEW/LabVIEW 8.5/OpenVIFromHelp?PROJ=myProject.lvproj
NI hardcodes these URL in glang.chm::/helpserver.js, and I would gladly read them directly if Javascript were less crippled. Since that hasn't worked yet, I did a regular expression in javascript to determine the version based on the path of the document. This worked until LabVIEW 2009 where the path is (typically):
C:\Program Files\National Instruments\LabVIEW 2009
but the version in glang.chm::/lvversion is "9.0.0"
Yes, I can workaround that by doing some javascript that says:
if(version == 2009)
            version = "9.0"
        else
            version = version
However, when 9.0.1 comes out, will it be LabVIEW 2009 still, or LabVIEW 2010? I'd like my javascript code to decoupled from any particular version so I don't have to relase a new version of my toolkit for each LabVIEW major or minor release.

OK I finally worked around this. Here is some javascript code that will look for a file called "lvversion.js" inside the <LabVIEW Directory>\help\glang.chm file. save this as a javascript file named "myjavascript.js"
var path=getPath();
function getPath() {
path = unescape(location.pathname); //replace %20 with " ", etc.
path = path.replace("@MSITStore:","");
path = path.replace(/\w+.html/,""); //strip off .html file
path = path.replace(/\w+.chm::./,""); //strip off .chm file
//Write javascript paths to page. Helpserver URL is hardcoded in each LabVIEW version
document.writeln("<script src=\"ms-its:" + path + "glang.chm::/lvversion.js\"></"+"script>");
document.writeln("<script src=\"ms-its:" + path + "glang.chm::/helpserver.js\"></"+"script>");
return path;
Then refer to it in an html document that will be compiled into a .chm file along with the javascript.
<script src="myjavascript.js" type="text/javascript"></script>
Now when you call functions from NI's glang.chm::/helpserver.js file, you won't need to prepend and URL or path information to the function to determine which version of LabVIEW you are in. I tested this on 8.5, 8.6, and 2009 and it now pulls up all my examples properly in all of those versions. The following demnostrates a call to "openProj" which opens a project containing all of my examples from a javascript button in the detailed help .html file that gets compiled into the .chm file:
<p class="Body">Refer to the Read From Mobile Registry VI in the <span class="Monospace">labview\user.lib\mobile_registry\examples\Mobile Registry Examples.lvproj</span> for an example of using the Close Registry Key VI.</p><p class="Body"><a href="javascript&colon;openProj('user.lib%5C%5Cmobile_registry%5C%5Cexamples%5C%5CMobile%20Registry%20Examples.lvproj');"><img src="minibutton.gif" border="0"></a> Open example&nbsp</p>

Compilation sous LabVIEW 2009 et windows XP

Similar Messages

Maybe you are looking for