Close windows application by Labview 2009

hi,
i would like to close a windows application (ie : scientific calculator) automatically by LabView 2009
i've read on differents posts that we must use API Win32 with the user32.dll, i have followed recommandations and procedures.
i have written the vi in attached file and tested it but unfortunatly it doesn't work, the windows "calculator" remains open without error message in the error cluster
Could you help me?
thaks a lot
Attachments:
FermetureApp.vi ‏10 KB

Hi Pimpon,
As you already got an answer on the French forum, I just place a link to it here for english talking people.
There were two suggestions :
Use Windows API Function Utilities (32-bit) for LabVIEW
Use .NET (see VI Snippet in the other forum post)
Regards,
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...

Similar Messages

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.

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

Close HyperTerminal Application using LabVIEW

I have a client who wants LabVIEW to close the HyperTerminal Application automatically is it has the serial port open.
Detecting that the serial port is already in use is simple. I already have a popup that tells the operator to close any communication application because the port is already in use; however, they want it done automatically.
HyperTerminal does not have ActiveX support and they will not go to the more professional version which does.
A long time ago, I had read a thread where it was possible to close (or open?) and application that did not have ActiveX support. I was hoping to use this similar approach.. Opening the app is simpler, but closing it is a different story. You need some sort of reference to that application to tell Windows which one to close. The OS in Win-XP.
Suggestions are welcomed.
R
Solved!
Go to Solution.

http://www.howtogeek.com/howto/windows/kill-processes-from-the-windows-command-line/
OR
Taskkill (command line as well) http://technet.microsoft.com/en-us/library/bb491009.aspx
taskkill /IM hyperterm.exe
will kill all hyperterm windows open, BUT it will ask you if you want to close any open sessions, which I think you don't want.
taskkill /F /IM hyperterm.exe
does the trick (without chewing up the com port, I just tried)

How to get drop shadow text in windows version of LabVIEW 2009

In the lower left corner of the attached JPG you can see that "Instrument Cluster" has a drop shadow. I created it by accident and would like to use drop-shadow for control names, but I cannot figure out how I did it. The only "Style" options in my Text Properties drop-down menu are Plain, Bold, Italic, Underline, Outline and Strikeout.
The Help file implies that it can be done in MAC OS. I just did it in Windows.
Does anyone know how?
Solved!
Go to Solution.
Attachments:
Instrument cluster.JPG ‏21 KB

Drats! An artifact.
I guess it is floating because I typed it on a boundary?
Thanks for the tip. As Nick Danger would say, "You saved me a lot of investigative work, flatfoot."

Control windows application and enter field

Hi ,
I am trying to run a windows application (with labview 2009) and input required values .Attached is the example front panel of the application.The requirement is to input the values,as well as simulate some button presses.
Hope some one can help.
Regards,
Alban Aruja

Use Microsoft Spy++ to find the handle of the objects on the Window.
George Zou
http://webspace.webring.com/people/og/gtoolbox

NI-Fieldpoint support in Windows 7 and LabView 8.6

We have a "classic" FieldPoint system with an ethernet controller. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Window 7. Is NI-FieldPoint supported in LabView 8.6 and Windows 7?
Regards,
nate
Solved!
Go to Solution.

Hi natewkidd,
I feel like there is some confusion between the operating systems running on a development machine (like Windows 7) and the real-time operating systems that run on our real-time controllers (like the FP-2000). I will do my best to clear up this confusion by first answering your questions.
1) What is the difference between LabView Real-Time 2009 and LabView 2009?
LabVIEW Real-Time 2009 is actually a software package officially known as the LabVIEW 2009 Real-Time Module that is installed after the LabVIEW 2009 development software to allow the user to develop and deploy real-time applications to real-time targets such as your FP-2000. You can think of the LabVIEW 2009 Real-Time Module almost as a plug-in for LabVIEW 2009 to allow for real-time application development and deployment.
2) If I have a FP-2000 on the ethernet network and want to use a computer running Windows 7 and LabView 2009 to record and display data, will I still be able to communicate with the FieldPoint network using the FieldPoint Read/Write VIs from my Windows 7 machine?
If you were just going to use the FP-2000 as a network module (NOT deploying a real-time application to run on the FP-2000 itself), you should be able to communicate with it using just the FieldPoint Read/Write VIs from your Windows 7 machine with LabVIEW 2009 and the NI-FieldPoint 6.0.5 driver. In this situation, you actually do not need the Real-Time Module since you are not deploying the application to the real-time target.
Regarding the FP-2000 not being supported beyond LabVIEW 8.5.1, this is because the memory on the controller is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Real-Time Module and the LabVIEW 2009 Real-Time Module. For more information on this please check out this KnowledgeBase article.
I hope this is helpful! Let me know if you have any further questions.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

LABVIEW 2009 and lvanlys.dll

Hi,
I'm relatively new to LABVIEW and I'm building an application with LABVIEW 2009. The application works well on my PC. However, the application is
intended to be ran on another machine. I then tried two approaches. First, I copied the executable file onto the second machine and second, I created
an installer file. Both methods resulted in an error when the executable was ran on the second machine. Here is the error:
"Missing external function lvanlys.dll Mean_Head.C in VI NI_AALBase.lvlib:Mean.vi". I'm hoping anyone out there knows the solution to this.
Thanks!
Bobby C

I'm not sure that link is appropriate since it talks about LabVIEW 7.1 installer and windows NT.
For LabVIEW 8 or higher, make sure that the data folder is part of the install. Done correctly, there will be your application, the data folder, and in the data folder, lvanlys.dll.

Help needed in adding custom About box in built application in LabVIEW 2009

Hello,
Can anyone please help me add custom About box in built application in LabVIEW 2009? I had successfully built my application in labview 8.6, 8.5 and 8.2 before to include custom About box. However, when I tried the same method in LabVIEW 2009, it only showed LabVIEW 2009 About box rather than my custom About box.
Here is what I did:
1) Wrote an "About Application.vi" in the built VI folder;
2) Included this "About Application.vi" in the "Always Included" section of Source Files in Application Build;
3) Built the application;
4) Ran the built application, the About box showed only LabVIEW 2009 about (attached a picture).
You can see that on the upper left corner of the picture, there is my custom icon.
Your help is greatly appreciated,
Cathy
Solved!
Go to Solution.
Attachments:
About Box.JPG ‏34 KB

Here is the link to download LabVIEW 2009 f2 patch:
http://digital.ni.com/public.nsf/websearch/C3F88F3596A164AD86257647006FB022?OpenDocument
Thanks for the help,

Remote Panels and LabVIEW 2009

Hello,
I have updated my real-time PXI application to LabVIEW 2009 (Pro) and I'm now trying to connect to it with remote planels. I can only have one remote panel opened. The second one gives me the "Remote Panels connection exceeds maximum numbers of licences" The problem wasn't occuring in LabVIEW 8.5 and I have the remote panel license (unlimited) is actived in the license manager.
How this can be resolved?
Regards,
Patrick
Solved!
Go to Solution.

Have you transfered the license files to the controller since the switch to 2009? There should be a .lic file under ni-rt>>system>>shared>>licenses on the controller. Is that present on your system?
Justin Parker
National Instruments
Product Support Engineer

LabVIEW 2009 Build Path Problem

[Cross Posted to LAVA]
I had some code that worked fine on my home PC, when I moved it to work, the exe would not build due to errors.
The errors coming back weren't that good at explaining the problem
Until I got this one:
Look at the path in the error:
C:\Users\Developer2\Desktop\User Group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build executable file paths\dist\application 9.0\my application.exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb
That path is referring to a VI inside my executable!
This may be a bigger issue that I first thought
So my question is:
If a have a path inside my build that would be relative to the executable and LabVIEW needs to resolve it, could that process fail depending on where the exe sits in a folder hierarchy?
I guess this could have happened before? but it would be more likely now due longer paths!
Message Edited by jg-code on 08-26-2009 05:20 AM
Certified LabVIEW Architect * LabVIEW Champion
Solved!
Go to Solution.

Solution in cross post
Certified LabVIEW Architect * LabVIEW Champion

Why does labview 2009 32-bit closes up with no error message?

Hello.
I am developing an application using a PCI-6534 board, Windows XP SP3, and LabVIEW 2009 32-bits. In this application I am generating a 300 Hz signal using the P2.0 digital line. I am trying to make digital acquisition using the P0 port (8 bits), using N-sampling. The program that generates the 300 Hz clock, works with no problem. However, when I start running the program that performs the data acquisition, LabVIEW suddenly closes up with no error message. The LabVIEW windows just disappear from the screen.
As for me it looks like a LabVIEW bug.
In case anyone decided to help me, I could attach the programs so that you could check them.
What can I do to solve this problem?
Thank you.

I had the same problem with one of our applications. I supplied gigabytes of process monitor and desktop execution toolkit logs, but nothing was resolved. I upgraded from WS2003 and LV2009sp1 to W7 64b and LV2010, per NI's recommendation but the problem persists. I had the corresponding service ticket open for 3 months where NI said the application ran fine for them on W7 with 2010. (long story)
I understand your frustration, and I recommend getting your local application engineer involved as an advocate with application support.. If you pay for service, pound on them to provide it. My $0.02.

Find names of all open windows including other applications besides LabView VIs

Hi All, I have researched this subject, i.e., to find names of all open windows including other applications besides LabView VIs, but found no solution. Could someone suggest a solution to this? Thanks.

Hi,
Certainly! The Windows API Function Utilities (32-bit) for LabVIEW includes set of LabVIEW libraries (llb) with VIs that make calls to the Windows Application Programming Interface (API) for managing and controlling windows (minimize, maximize, move, resize, rename, close, and so on) including task list with names of windows application running. The Readme.doc contains information on running these VIs.
Attached below is a zipped file with a VI that list the names of all opened windows.
Tunde
Message Edited by Tunde A on 04-18-2007 02:28 PM
Attachments:
List Windows Application LV8.0.zip ‏55 KB

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

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

Close windows application by Labview 2009

Similar Messages

Maybe you are looking for