LabVIEW application don't closed by shutdown or logout

Hallo,
here one small question.
LabVIEW application running under Windows2000.
Now Ctrl+Alt+Delete pressed, then "Log Off..." choosed.
LabVIEW application closed, but Windows don't logging of and Ctrl+Alt+Del must be pressed again for logging of. The same situation with "Shut Down...".
If two application are running, then only one received AppExit event, and second - not.
How can I avoid this situation?
My goal is following: by Ctrl+Alt+Del->LogOff/ShutDown all LabVIEW application must be closed. Do you have any _simple_ solution?
Thank you.
Some examples in attachment. Just start these application, then try to logging of or shutdown.
Attachments:
AppShutdown.zip ‏100 KB

See http://zone.ni.com/devzone/cda/epd/p/id/4394 for windows_messaging_que.zip and use it to listen for WM_POWERBROADCAST, but, note this DOES NOT WORK UNLESS THE LabVIEW APPLICATION IS COMPILED INTO AN EXECUTABLE (.exe)! When running within the development environment, the message is never caught. We didn't successfully catch WM_QUERYENDSESSION this way either, but in our case, we did not care, and so did not pursue it further.

Similar Messages

Application crashes after closing LabVIEW instance with Scilab 5.2.2

I use LV 8.21 with the LabVIEW to Scilab Gateway software Version 1.1 (new version from NI homepage)
I have Scilab Version 5.2.2 installed. We will do some calculation with the LabVIEW Scilab script node.
Mainly use a call "exec (functionA,-1) Scilab script node. The functionA is a scriptfile outside of the application.
So far everything is working fine, I can build a LabVIEW application with the application builder.
If I run the application the calculation inside the Scilab script node are proceeding; I can call
it many times in a loop without no problem.
But if I close the instance (the VI with the Scilab script node inside) the application crashes.
The same problem I have in the LabVIEW development environment
Is there a way to "unload" Scilab before I close the VI without a crash. After the Scilab
calculation I have to close the calling VI and call some other VIs for further calculation
(but this VIs have no Scilab call)
I tried with the "exit" and "quit" command in Scilab script node, no success
any suggestion
Attachments:
scilab.GIF ‏5 KB

Hello
thanks for the advice. I tried with version 5.1.1 ... but no success!
So I went straight back to version 4.1.1 and it works fine, of course I had to remove the comments from the script node
So fare I can work with this version.
So what are the time schedule to fix this problem? It is a very useful tool an I would like to use the latest version of scilab and not an old version.
Thank you

I can't install ADE on my PC, because as I try to open it a message of error appears to me: The application will be closed. I've already try with different browsers and also with the manual installation, but nothing..

I can't install ADE on my PC, because as I try to open it a message of error appears to me: The application will be closed. I've already try with different browsers and also with the manual installation, but nothing..

1
Close all iWork applications
2
Uninstall Keynote; this must be done with an application remover tool to delete the installation properly. Appcleaner is known to work correctly for this purpose, it is free and can be downloaded from here: Appcleaner Download
3
empty the trash
4
shutdown the Mac and restart. After the start up chime, hold down the shift key until the apple logo appears
let the Mac complete the start up procedure completely, it will take longer than usual as the hard drive is being repaired
5
Reinstall Keynote by logging into the Mac App Store using download / install

What kind of function(s) (in dlls) have to be call by a Labview application to be able to manage the PC's power supply

Assume that a Labview application is running on a PC. The PC has a DC battery. When a "power off" is detected on the AC line, data should be saved, Labview application and Windows should be closed.
What kind of function(s) (of which dll) should be called by a Labview application to realize this data and system management in a safe manner ?

UPS (Uninterrupted Power Supply) systems can send messages to the PC through the serial port when the AC is lost and when battery is low. I'm not sure how this message is sent but I suspect they use Windows Messaging. If you could find this out, you could write your vi to constantly look for this message and shutdown when it sees the message.
- tbob
Inventor of the WORM Global

Labview Application Error

Hi,
A while ago, I tried to change the build-in AI read from NIDAQ6.9.1. On way or the other, the build in AI read was replaced by My AI read, which in fact was exactly the same as AI read. Because of problems when transporting the file to other PC's, I tried to fix this. That is where everything started to go wrong.
When I save a file, I cannot reopen it: "labview application error" while opening. When I click OK, it sometimes adds something like "cannot find all necessary files or llbs". The funny thing is that exactly the same file, but saved on an other PC works fine.
I then reinstalled everything containing the word labview or ni daq, but still the same problem: every file saved on my PC does not open anymore. Sometimes,
let's say one out of 25, the file opens, but then craches closing.
Can somebody help?
Thank you.

> Checking the disk did not help, and because I did not know what to
> look for, I have done a fresh install of my system, complete with
> formatting and so on. The problem is now reduced to the larger files.
> The small files do not crash if I save them immediately after opening
> them. With the larger files, there is not always a problem, sometimes
> I can manipulate them for over 20 times, and then suddenly, crash and
> no way to open them anymore.
> When I speak about larger files, this is something between 700kB and
> 980kB. Is this maybe to big for Labview to handle? I have 256 MB RAM
> on my computer.
There is no size limit. The limit is probably something like two
gigabytes or so. I have customer VIs on my computer that are fo
ur or
five MB.
You say that it crashes. It would be helpful if you could be more
specific. Is there a dialog? What does it say? If the dialog is a
Failure dialog, then LV also creates a LabVIEW Failure.txt file that you
can file with technical support along with a description and this will
help to track down the problem.
Greg McKaskle

LabVIEW application run on Windows XP Embedded

I'm doing a Embedded system based on Windows XP Embedded operating system.I want to make a LabVIEW applications which can run on it.I see a lot of paper that show the LabVIEW does not support Windows XP Embedded.I want to know whether the official has already solved this problem?Or someone has done the same thing successful?

Who is the official? NI? If it isn't supported, NI is unlikely to be trying to solve the issue as we are a bit beyond XP. You'd need to find unsupported methods to hack it a bit. I'm not sure you'll enjoy this process

Using a LabVIEW application as default program for opening files

Google has returned nothing useful on this. I want to use a built LabVIEW application to open data files from the Windows desktop. It is easy to edit the Windows registry to set the application as default program - but I'm not sure how to set the event in LabVIEW to open the file. Any suggested reading?
Solved!
Go to Solution.

I have done this before...I have a small LabVIEW .exe which looks at the version of a VI and selects the appropriate version of LabVIEW to open it with if available. It also adds explorer context menu items for allowing you pick a specific version of LabVIEW to open the file with.
This is a rough idea of the registry keys for adding a program to handle specific file types and to add items to the shell menu in the installer:
Add your own 'LabVIEWOpenWithVersion' key and then add the key name to the OpenWithProgids for the file extensions you want to be able to open with your application. The command part looks like this:
Look at the Windows/MSDN help for what the different keys mean and how they are used, I think you can also set a key to make one of your handlers (e.g. Open, openWithLV) the default for the file type.
For getting the file that was opened 'with' your application, use the App.Args property, ignoring the first item (which is always LabVIEW) in the array.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

PID control in a windows CE Labview application

Hi there,
I want to build an application that will control the temperature in some ovens, using PID control. The application will be running in a controller (or a touch panel computer) with windows CE OS. I have Labview 8.6, PID control toolkit 8.6 and Touch panel module 8.6. The problem is that the PID vi's don't seem to work in touch panel module.
Is there any way to implement PID control in a windows CE Labview application?
Thanks in advance.
Solved!
Go to Solution.

I think with a timed loop you can run reasonable good timing down to 1 mSecond. I think 1 mSecond is the lower limit for non realtime systems like Windows/windows CE. And if you have the PID toolkit this will supply you with the functions you need. You do not need an extra CE PID toolkit. This because the touch panel module run under your standard Labview environment. But I do not know if all the functions in the PID tool like fuzzy logic are compatible with CE. Have you also considered Windows Embedded as OS for your module. With windows Embedded you can run standard Labview built exe files
Both Windows Embedded, and XP Embedded can be trailed
http://www.microsoft.com/windowsembedded/en-us/products/westandard/default.mspx
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Passing strings to a LAbVIEW application from Visual-C++ using ActiveX

Hello all,
I have built a LabVIEW application with ActiveX server enabled. I can
start the application, and can read and set simple control values like
numerics.
But now I want to pass (SetControlValue) strings and read (GetControlValue) strings from controls.
After searching a whole day for examples or HowTos I found nothing. Can
anyone give me tip where I can find something about that?
Examples are also appreciated.
Best regards
Heinrich Eidloth

The problem you are running into is that a BSTR is not a normal string (%s in the printf), but a wide character string (i.e., two bytes per character) string with the size stored in it. If the string contains ASCII characters, such as Hello World, then the one of the bytes per character is 0 (for example, 'H' would be 0x48 0x0).
When printf sees this, it thinks that it is a normal, null terminated string of "H". That is what you are seeing. You might try the %S (capital S) since that tells it the string is a wide character string.
Also note that BSTR's are part of the COM (Automation) system and so are don't freed with a delete or free() statement. Instead you need to release the memory with a SysFreeString() call.
If you aren't very familiar with C/C++, then you've taken on an advanced topic on top of a complicated language. If you can, you might want to try using either VB6 or .NET (C# or VB.NET). Those languages handle all of this for you automatically and you don't have to worry about freeing the memory.
If not, the book I started with to learn COM programming was this one (http://www.amazon.com/gp/product/1572313498/104-3574382-6511132?v=glance&n=283155&n=507846&s=books&v...).
Brian Tyler
http://detritus.blogs.com/lycangeek

LabView Application program crashses randomly

Hi,
I have developed an application for a monochromator system using LabView 2012 (32-bit version) as my programming language.
My application performs calibrated scan using the Calibrated Photodiode from 300 nm to 1100 nm and then perform Device Under Test (DUT) scan from 300nm to 1100nm at an interval for 5nm.
My application crashses randomly when inside a for loop that goes from 300 to 1100nm at an interval of 5nm, whether it is performing a Cal Scan or DUT scan.
The one thing that is consistent is that it crashes whenever LabView executes my supplier’s .NET DLL/ function call. Once the application program goes into the monochromator function call, it does not give LabView the control back. The application is stuck inside the function call.
On Good days I am able to scan up to 30 parts with no crashing, while some days it can barely scan 5 parts. It is very inconsistent.
I am not sure if anybody have seen any problems using dll to interface with Labview 2012.
I have attached an image of problem I am encountering, where the LabView application is stuck in the DLL and it does not give control back to LabView.
I would appreciate any assistance on this subject.
Thank you,
Nirav
Attachments:
Cal Scan LabView Stuck.jpg ‏390 KB

About the only thing I can determine from that jpeg is that you could benefit greatly from this and especially this. Please upload the actual code, if possible, so we can help you decipher it.
thanks!
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Can I convert a Lookout application into a labview application?

We here are seriously thinkig to migrate to Labview. There is a complex application done with Lookout 6.0 that we want to convert to a labview application. Having the proper Labview, is there a way of compiling it, open and save, or convert the Lookout application into a Laview application?
Excuse my ignorance in this matter.
Best regrads.
Rudy
Solved!
Go to Solution.

Rudy,
First of all I hope you first question regarding lookout is solved. If so then mark my answer as solution.
For the next time, if you have other questions, which are not related to the one you started the thread of, then open a new thread!
And no, National Instruments don't has drivers for Non-NI Products, so LabVIEW has no driver for your motion card. Anyhow National Instruments has it's own Motion Hardware and Software (ni.com/motion).
And for LabVIEW and Linux just go to ni.com/linux, and you will find supported hardware/software and the linux derivates it works on.
Christian
Message Edited by Christian_M on 11-20-2009 01:28 AM

Labview application very runs poorly on better PC hardware

What could cause a Labview application to run extremely poorly when deployed to a new higher performance PC verus the 4 year old one at my desk? I'm using an Intel Core Due 2 on my desktop (2 cores), whereas my application is being deployed to an Intel Xeon (4 cores). I've tried running both the old LV8.6 version of the software and the newer LV2011 version, and both are crawling to the point the application cannot be used. The GUI isn't updating at the 4x per second, the mouse pointer is extremely jumpy when moved around the screen, and tabs/menus take several seconds to a couple minutes to be responded by the application. On my desktop PC, the application runs smooth using the same executable file. Both have the same OS (32-bit XP SP3) and both are running the same anti-virus software.

ExarK,
- Can you supply additional information on what your application is doing?
- Do you have the source code available with the LabVIEW Development Environment? It sounds like LabVIEW is either hogging your resources (insert Wait functions into any loops you are running to periodically free up your processor) or that there is a memory leak (make sure you are closing your references correctly).
- Try building one of our shipping examples to run with your DAQ device (a simple analog input will do). See if this runs slowly on the target PC as well.
Andrew T.
National Instruments

Is it possible to hide the LabView Data folder through the labview application?

I really want to get rid of the LabView Data folder in the My Documents Folder that is created when the built labview application is run. Since it does not seem to be possible to remove or relocate it, i was wondering whether it is possible to at least hide it - but I want it to be done automatically, i.e. through the program itself when it is executed.
Thanks
Tim, Van

Hi,
you cannot delete the "LabVIEW Data" Folder since your application is active!
It's possible that you change the attribute (hide) for the whole folder before you start the compile process!
If you want to do this automatically, you should ask microsoft which dll is relevant for this scope!
regards,
Thomas Sandrisser
NI Germany
http://www.newgistics.com

Stand alone labview application (.exe file) does not run properly

Hi all,
I am trying to make a stand alone labview application to run on another computer ( I have never done this before).
I went through the tools->build application prompts and was able to build an exe file.
the program is supposed to control a power meter and make power measurements then save them to a text file.
When I run the exe file, on the same computer I compiled the exe file on, the program generates a text file to save data to but it can not communicate with the power meter.
There are some sub-VIs and a dll file that are used to communicate with the power meter. Could it be that I am not telling labview to correctly
include these files when I create an executable?
What are some common problems that occur when generating stand alone applications that could be causing my issues?
And does anyone know of any good tutorials on generating stand alone applications in labview other than the NI help files?
Thanks for your help,
Solved!
Go to Solution.

edCubed wrote:
Hi Bill, thanks for your suggestions.
I haven't tried to run this app on another computer yet. I'm just trying to run it on the computer it was developed on.
The computer I developed it on has all the drivers/resources I need to control the power meter.
Also, I don't know how to include the VISA runtime with my installer. could you explain how this is done?
This is the first time IV tried to turn any labview programs into stand alone exe files so I don't anything about how to do it other than what I've seen in youtube videos and help files.
If you know of any good tutorials that will help me figure this out I would appreciate it.
Thanks,
My fault - I didn't read that this was the same computer. I know the very end of Core 3 studies shows how to build an executable and installer, but even that is very general. I'm not sure if there exists a tutorial on how to do it.
As for including the runtimes, when you build an installer, you have to include the runtimes that your executable will need. It's fairly straightforward.
Since it won't run on the machine that built it, I'll have to think about it a little bit...
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Minimizing LabVIEW application to system tray or running it as a Windows process

Hi guys,
Is there a way I can minimize a LabVIEW application to the system tray on the right bottom corner of the screen ? My application will run all the time and all I want is a pop-up when errors or information/reports have to be displayed. I have searched exhaustively and now am posting this question. Please let me know if this can be done.
also, Can a LabVIEW application run as a Windows process? Like it starts up automatically on booting the system?
Thanks!
V
I may not be perfect, but I'm all I got!

If you search for System Tray you'll find lots of people trying to do the same thing and a few places with example code to get it working. But the best method I've seen is actually on the Lava forums.
http://lavag.org/topic/14060-put-your-labview-in-the-tray-once-and-for-all/page__p__86042__hl__+syst...
As for starting a application on startup. Again I expect searching you'll find alot of people saying the easiest way is to create a shortcut to your application, then place the shortcut in the Startup folder in your start menu.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

LabVIEW application don't closed by shutdown or logout

Similar Messages

Maybe you are looking for