Lv 2009 sp1

Bonjour, je suis actuellement sous lv 2009 f2. avec des ajout openg je vais devoir aller faire des test sur un pc ou la version 2009 sp1 est installée :
1) si je fait des modif sous le pc en sp1 , devrais je installer la sp1 sur mon 1er pc pour relire les nouveaux fichiers
2) le correctif sp1 est il un simple ajout ou bien est ce une reinstall , cad aurais je besoin d'installer a nouveau les bibli open G ?
Cordialement
Tinnitus
ps: désolé je peux pas me relire j'écris dans un champ de 1*4 cm (filtrage interne temporaire j'espère)
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte
Résolu !
Accéder à la solution.

bon , la reponse c'est non :
c'est une mise a jour et pas besoin de reinstaller les lib openg
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte

Similar Messages

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 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

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 Run-time 2009 SP1

When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required"
The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

Do you have administrator privileges? Also, do you have any security programs installed on your computer that could hinder the installation?
Applications Engineer
National Instruments

Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
Thank You
Attachments:
Broken VI.gif ‏8 KB

Scott,
Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
I would recommend starting with these steps. Let me know if any of these solutions work for you.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

LV 2009 SP1 Build Error NI

While trying to make a build on LV 2009 SP1, I get this error:
The build was unsuccessful.
An error occured while saving the following file: Sample.VI
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 1 occurred at 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_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Note I do not use any GPIB. Also when I build the project on VL 2009 (no SP1) on a different machine, I get no errors. Any ideas?
Solved!
Go to Solution.

Ugh. I've seen this in 2009 as well as quite a few others here. There seems to be no real explanation or consistent solution to this error. 1st thing to try is to remove all boolean constant-driven case selectors. For some reason the compiler gets confused with those - sometimes. See how that goes. Eventually this problem seems to resolve itself after a few days of development. That's been my experience. Sorry I can't be of more help.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

2009 SP1 Debug Deployment Only

I've install LabVIEW 2009 SP1 and it works fine but it indicates "Licensed for Debug Deployment only" on the opening screen. We use the Volume License Manager and it correctly checks out a Development License which is correct for me.
Is this something I should be concerned about? It doesn't seem to be constrained in any way, i.e. I can build executables.

Here they are. I'm "DC10020"
Attachments:
VLM_Screenshot.jpg ‏511 KB
NILM_Screenshot.jpg ‏227 KB

2009 sp1 slow build

Trying to build my application after I just upgraded to sp1 on LabVIEw 2009.
It seems to take a long time, while using a lot of cpu power.
Progress is very slow. Hard drive is not being used intensly.
Running the same on the 2009 f2 version. Building from the same sources.
Very slow as well.
I'm new to the performance of the build feature in 2009. Coming from version 7.1.1
And I'm very surprised on the difference. Why does the build take sooooo looooonnnnggg on the 2009 version(s)??
We build smaller apps before on 2009, and did not seem a big deal. But this bigger application.
And then after about 15 minutes, I get an error message:
Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
So this is running with the 2009 f2 version on XP pro with 1Gb of ram. And for the 2009 sp1 version on windows 7, with 8Gb of ram....
So do not expect any memory issues with the SP1. Could this be a windows 7 x64 issue?
Anyone any experience with building larger applications?

Hello Everyone,
We have observed that building executables in LabVIEW 2009 is slower than in 8.6. In most cases it was about 10 to 20%. However, in some larger builds we have seen almost a 3x or 4x slow down. This large slow down has been reported to R&D for further investigation (CAR 205343). In the case that was reported to us the build was about 8000 VIs and took 2GB of memory to complete.
There wasn't a difference between LabVIEW 2009 and 2009 SP1. The slow down occurred between 8.6.1 and 2009. Does your slow down occur between 2009 and 2009 SP1?
Message Edited by Jon S. on 03-09-2010 08:42 AM
Regards,
Jon S.
National Instruments
LabVIEW R&D

LV 2009 SP1 EXE Builder issue

Hi Guys:
I found that the exe file built from LV 2009 SP1 can be easily extracted by WinRAR , i can see all the main or sub vi , is this a bug? or a settings risk? I haven't found the same problem in LV 8.6 ,
thanks
Solved!
Go to Solution.

I do not think you should think to much about it. One of the first discussions about it is here http://forums.ni.com/t5/LabVIEW/decompiling-2009-executable/td-p/991662. It is correct that they will be able to extract the VIs But they will not be able to see any more than you show in your program.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Image ROI ID number in LabVIEW 2009 SP1?

In LV 8.5 (Vision), multiple ROIs had ID numbers displayed next to them:
Apparently not so anymore in 2009 SP1:
The only difference between the two VIs is that I was using a classic image object and I am now using the modern version;and the image tools window is replaced by the image tools palette associated with the image. There is no image property that I can find to turn the ROI "legends" on or off.
How is the user supposed to know which ROI is which?
Solved!
Go to Solution.

Ooops...: Indeed. I checked my LV 8.5 code (in fact written in LV 6 or whenever the first Image control was released) and I did overlay the ROI numbers myself at that time!
Since I had meanwhile used overlay to get ROI numbers, I just reinvented the wheel...twice.
I still think that would make sense to have this feature by default in the Vision toolkit.
X.

Timer( ) resolution in CVI 2009 SP1

In the CVI 2009 SP1 Contents Help for Timer() function I find
The resolution is normally 1 microsecond. However, if you set the useDefaultTimer configuration option to True, the resolution is 55 milliseconds.
But if you click on the useDefaultTimer hyperlink, a new page is opened, where you can read that the resolution is 1 millisecond if you set useDefaultTimer to False.
Which is the right resolution?
I wrote my application considering 1 microsecond, but I found strange problems, and I think it is 1 ms.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Hi vix,
Thanks for bringing those documentation problems to our attention.
1. There does seem to be a problem with a lot of the function prototypes in the .chm help in the CVI 2009 SP1 and 2010 versions, where an extra asterisk seems to have been added to a number of output parameters. We'll fix this and post a corrected version of the affected .chm files as soon as possible. In all these cases, the parameter data type as it appears in the Parameters section of the help topic is correct, as is the prototype in the corresponding function panel.
2. Concerning the timer resolution issues, the async timer resolution is in fact 1 millisecond, as confirmed by the GetAsyncTimerResolution function. But note that asynchronous timers are a library in and of themselves, and are not covered by what is discussed in the documentation of the Timer() function or the useDefaultTimer option.
The resolution of the Timer() function should be 1 microsecond, as of CVI 9.0 and later. The function documentation is correct. When that change was made, however, the documentation of the useDefaultTimer option was incorrectly not updated. It should say that "the performance counter timer provides a resolution of 1 microsecond".
You mentioned that you didn't think that the resolution of the Timer() function was 1 microsecond. If you run the following code, what do you see?
int     i;
double time[10];
for (i = 0; i < 10; i++)
    time[i] = Timer();
for (i = 0; i < 10; i++)
    DebugPrintf ("timer = %f\n", time[i]);

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...
When I use it with my temperature logger most of the time I get an Error 66...but some times it does work and actually retrieves the document.
I can use the same address "http://172.22.21.68/XMLfeed.rb" (Internet Explorer or Google Chrome) in my browser and get a response every time. When accessing from my browser the server in the temperature logger does take around 6 seconds to respond, but it does respond every time.
Is the URL Get Document Vi exceeding a timeout? If so, where can I set it to wait longer?
Attachments:
Error 66.jpg ‏183 KB

It looks like the TCP Buffered Read has a 2.5 sec timeout, I believe that is where I had trouble as well. Try creating your own URL Get HTTP Doc vi in which you call URL Get Document in normal mode, with an appropriate number of characters to fetch (enough characters so that you capture all the important data in the XML file).
Attachments:
ex1.PNG ‏33 KB

LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.
Attachments:
Connector pane.PNG ‏4 KB

Troy K wrote:
I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
So you must be using crazy non-standard connector panes, or you would not have discovered this bug. Right? Actuall this is a good catch for it to go unnoticed for this long.
- tbob
Inventor of the WORM Global

Lv 2009 sp1

Similar Messages

Maybe you are looking for