Quit LabVIEW

I have 3 exes, all built from LabVIEW VI's.
2 of them run for a long duration, but for one of the exes, when it is called, it just needs to run once, then it can close.
I am calling it from the command prompt, through a batch file:
eg. start path/program.exe
If I put a 'Quit LabVIEW' function at the end of the code, will it just close this exe, or all of them?
Or is there a better way to accomplish this task?
Cory K
Solved!
Go to Solution.

From my experinece the Quit LabVIEW will only affect the application that contains it. So if you have a built application it will only exit that one application. If you use it in the development environment LabVIEW itself will shutdown.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Similar Messages

How to open labview program with Quit Labview function inside?

Hi Any idea how to open labview program with Quit Labview function inside?
I forgot to add and set the condition of the type for this program.
If the program is an application, it would close straight away.
If it is still labview work, it will go straight to editing program without closing.
So I need to recover, open it and make some changes.
Clement
Solved!
Go to Solution.

Put the VI in a project and open it from there, then it shouldn't autorun. You can use App.kind property of application to decide whether to close or not.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Quit labview does not work in executable

I recently upgraded my labview and application builder from version 7.1 to 8.2 and then 8.2.1.
An executable that I created contains the quit labview function.
With version 7.1, a true input to that function would close down the executable completely, including the run-time engine, which is what I wanted.
However, when I build a similar executable in version 8.2.1, this same call to the function causes the executable to stop running, but the front-panel is still there waiting to start-up again. The run button appears, even though I specify it not to appear under the Window Appearance in VI properties.
The other thing that happens is that during panel close, the program hangs for several seconds, then the Task Manager says that the program is not responding, and then it closes completely a few seconds later. I would prefer it to stop right away.
From reading knowledgebase articles, this seems to suggest that there are some unclosed references, but I can't really find any.
Anyway, it's pretty much the same code as 7.1, and I did not see this same problem there.

Could you at your shutdown code.
I haven't seen this!
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Quit LabVIEW function doesn't work when called from Actor Framework

This is related to a known bug. Details can be found in a discussion we had with LV R&D here: https://decibel.ni.com/content/docs/DOC-28012
I need a functional workaround to this bug because my application's top-level panel is an Actor Core.vi override. Can the AEs please help, as suggested by Aristos_Queue (LV R&D member) in the link above?

Hi David,
Were you able to try the workaround AristosQueue gave you? Below is the workaround he suggested.
Not sure, but I think that it will work just fine if you start a VI running using the Run VI method and have it invoke the Quit LabVIEW node. Not the Call By Reference node, but just wire a Static VI Reference to the Run VI method with FALSE wired to the terminal for whether to wait for it to finish. That subVI will then be running as a top-level VI on its own... and the only thing on its diagram would be the Quit LabVIEW node. I think that will work. Haven't tried it, but based on the description in the CAR, I think it will work.
Carl W.
Applications Engineering
National Instruments

Calling Quit LabVIEW function in a callback VI is not working

calling Quit LabVIEW function inside a Callback VI (of an activeX component) is not closing the current instance of LabVIEW.
does anyone else have this issue?
RENN
LV2012SP1 64bit
Kudos always welcome for helpful posts

Sounds similar to this - https://decibel.ni.com/content/message/48506#48506
The bug is that the Quit LV function does not work when called from a VI launched through Asynchronous Call By Reference
AQ said that that bug was resolved in the 2013 beta, so you could try joining the beta to see if that solution also works for your case.
Try to take over the world!

Quit LabVIEW function generates crash report in executable

Hello,
I am using the Quit labVIEW to close down an application when the VI is built into executable. If stop LabVIEW is used the application just stops and leaves the window open. When the Quit LabVIEW function is used in an executable the application closes down completely.
In the current app I am developing (Windows 7 - LV2014SP1) I have isolated the Quit LabVIEW function as the source of the Crash Report I am receiving after I exit the application. I inpsected the crash report and there was mention of a thread that did not have appropriate access. So I ran the same executable with Adminstrator privledge and the error went away. It appears the application I am developing does not have sufficient privledge to close itself down and this is generating the Crash Report.
I have used the Quit LabVIEW function for many applications in the past without issue. I have not confirmed yet whether the problem is specfic to the current application I am developing or to LV2014SP!.
thanks for any help with resolving this issue,
- Troy
Solved!
Go to Solution.

TroyR wrote:
Wasn't there previously some issue with using Invoke Node in executables?
Not that I am aware of. But here is my trick for shutting down an application. I put the FrontPanel Close method inside of a Conditional Diagram Disable. The invoke node only goes into the RunTime Engine == True case. This way, the front panel is not closed if you are in the development environment.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Stop and Quit LabVIEW Vi

I don't fully understand why I need the stop and quit labview vi. When a program finish running, doesn't it stop automatically? Why is the stop vi needed? If vi stops automatically when it is done, couldn't the programmer write the program in such a way that would cause the vi to stop when needed without using the stop vi?
When a program is running in exe, why is quiting labviw needed? Doesn't everything quit at the end of the program? In development, there is really no reason for the developer to want the LabVIEW to quit automatically, right?
Kudos and Accepted as Solution are welcome!
Solved!
Go to Solution.

jyang72211 wrote:
When a program finish running, doesn't it stop automatically? Why is the stop vi needed?
You never need the stop.vi. Its function is similar to the abort button, unconditionally stopping the VI, even if it is trapped in a parallel loop that cannot be stopped directly due to incorrect coding. Since the current state of other code parts is random when stop is called, the outcome might be very unpredictable and the program might stop without a proper shutdown sequence, leaving your instrument spinning or the hight voltages turned on.
For more details, read the online help. I never use it!
"Quit LabVIEW" has similar problems. You don't really want to use it during development, because, you might have unsaved changes.
My larger applications don't have a stop button, and can only be stopped with the [X] in the upper right corner. (Like any typical program: When was the last time you had to first "stop" internet explorer or MS word? :d) I use a filtering event to catch it, discard it, initiate a clean shutdown, and after everything is done, either stop in the development system or quit labview in the case of a built application (see code image).
LabVIEW Champion . Do more with less code and in less time .
Attachments:
FinishApp.png ‏4 KB

QUIT LabVIEW.vi works differently in LC8.2

RE: "QUIT LabVIEW" vi behaves differently in 8.2.  Using (essentially) identical application (*.exe) executes a "QUIT LabVIEW" vi function, LV 7.x and 8.0 built code behaves as expected, that is: LabVIEW is completely exited including any and all Front Panels. The application and all remnenats of all VIs disappear from the desktop.   .....With 8.2, the built application "stops" and the front panel of the top VI remains on the desktop.
Did something change in 8.2? What am I missing?

All,
   Thanks for the quick replies. I have three apps that exit normally, and one that does not. Coincidentally, the largest one is the one that doesn't exit normally. I have tried wiring a "true" boolean to it with no change. I have also tried having the first control executed by the app be the "Quit" vi, and it also only Stopped the app. I wire a App.Kind node to a case structure to "Stop" when in devel, and "Quit" all else. There is one other bit of functionality in the default case that is executing, so i know it is executing the correct order, but i have yet to isolate what the difference is between the apps that quit normally and the one app that doesn't. All options under VI Properties are identical (minus name) to the apps that work as advertised. Last night i used a conditional disable loop and commented EVERYTHING except the init and exit code, and it quit normally, so that is where i am looking next...
   I have not looked specifically at the documentation, but the only change initially between 8.0.1 and 8.2 was a mass compile from the main splash screen. The same code worked in 8.0.1 in a production environment.

DLL causes error when quiting LabVIEW 2009 on WIN7

Hello,
I have reduced the problem in my EXE application to the following attached code (see attachment). Somehow the DLL (To User32.dll) calls are creating a problem when quiting Labview 2009. The Application stays resident in the Windows taskbar and after a while an error appears about that there was a problem closing the application and that it can be reported to Microsoft if desired. Then a second error message appears before the application dissapears from the taskbar. If I remove the DLL:calls from the code then the problems dissapear.
Should I unload the DLL calls on a special manner before quiting LabVIEW?
Solved!
Go to Solution.
Attachments:
DLL-WIN7 problem.jpg ‏35 KB

Another potential problem not mentioned in that article is that you have included your user32.dll explicitedly in your built application. Doing that creates 200% for sure trouble as the kernel32.dll, user32.dll and others are always residently loaded into memory anyhow and mapped into the system memory section of any process. If you tell an application to load this DLL again by explicit name, you end up having two copies of it mapped in your process memory space and that will cause very weird problems.
To avoid this problem make sure the library name inside the Call Library Node only specifies the DLL name without any path information. Then close the dialog and save it. If you reopen the dialog it will show the full path but still save the name only until you make a modification in the path control at which time you can end up having a full path again.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW 2013 SP1 Quit LabVIEW

Hello all,
I have a question regarding the Bug 425800 (Quit LabVIEW will not quit if the event 'Application Instance close' is present) in LV2013. According to NI this Bug is fixed in LV2013 SP1.
I have an application, which was converted from LV2011. The application compiled in LV2011 worked well.
After converting to LV2013 I had the issue, that the exe won't quit. I updated to LV2013 SP1 and mass compiled my project. After building the executable again, I have the same issue. My compiled EXE (LV2013 SP1) will not quit.
One VI contain the 'Application Instance close' event, because the PC is connected to an UPS and the application should be terminated in a save way in case of power loss.
Is there any other reason why the 'Quit LabVIEW' will not work?
As a little reminder: The application worked well in LV2011.
Regards
Heinrich Eidloth

Dear Mr Eidloth,
I would like to help you resolve this issue.
Would you mind sending me your program to look into so I can help you better?
Alternatively you could try running the added example to test the functionality of the "Application Instance close" Event and the "Quit LabView" funktion.
Thank you very much in advance.
Best Regards
Veronika Kurz
Veronika Kurz
National Instruments
Applications Engineering
www.ni.com/support
Attachments:
Quit LabVIEW CAR-1.vi ‏10 KB

Close LabView App after exit without Quiting Labview !

I need to close my LabView Application panel after the programm finished WITHOUT QUITING LABVIEW !

Long time ago, this came up before... look at the attached VI (Close Panel.vi) in the attached link. Its the last answer on the link by CapeFl (my old alias).
Good Luck with it, Doug
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000008210000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

Labview application continues to run in taskbar even after quit labview

Hi,
My application is supposed to quit labview upon the press of a 'close application' button. But the application continues to run in the task bar and goes away only if task manager is brought up and the app is killed. Why does this happen? my code is quite heavy (7.45MB after installing)and uses lot of front panel controls (more than 300 since its for a batch testing bay)and also uses many synchronisation elements such as notifier, semaphores etc.
What can I do to make the application go away once the quit labview is true?
thanks!

Hi,
Using a lot of Notifiers and Queues could lead to this behavior, if obtained a lot of times. From the LabVIEW help:
"If you use the Obtain Queue function to return a reference to a named queue inside a loop, LabVIEW creates a new reference to the named queue each time the loop iterates. If you use Obtain Queue in a tight loop, LabVIEW slowly increases how much memory it uses because each new reference uses an additional four bytes. These bytes are released automatically when the VI stops running. However, in a long-running application it may appear as if LabVIEW is leaking memory since the memory usage keeps increasing. To prevent this unintended memory allocation, use the Release Queue function in the loop to release the queue reference for each iteration.."
Check/Verify if/that all references to Queues/ Notifiers ... are closed if no longer needed or used in a proper way.
Otherwise LabVIEW will close all the previously opend references in the end, what could take a while.
Regards,
CMW..
LV 13.0.1 Developer Suite with Automated Test; Win7 x64

Counter change to high when quitting LabVIEW

Hi,
I am using the GPCTR0_OUT output on my PCI-6052E board as a watchdog output. I need this output to be low while my application is running and high otherwise. However I have found that the output switches back to low as soon as I quit LabVIEW. How can I avoid this behavior?
Thanks!

You can apply pull-up resistors to the counter outputs to force their default state to be low or high (depending on your requirements). Take a look at the following KnowledgeBase article (Default State of Counter Output Lines on E Series Data Acquisition Devices). At the bottom, there is a link to another KB that describes how you can change the default power-up state of the DIO lines, and this also applies to the counters.
http://digital.ni.com/public.nsf/websearch/008995633E33E47486256B5F00034436?OpenDocument
David McClelland
National Instruments

I have problems to quit labview 7.x

When i try to close the main window of labView 7.0 or 7.1 nothing happens and the process remains active. If I have any vi open I can close each of them (through the menu 'close') but if I click on menu File-->Exit labView hangs and I must terminate the process with task manager.
Thank you,
Massimo Ponte.

Hello National Instruments
      I have recently discovered an incompatibility between the NOD32 antivirus program and Labview 7.1.   Yesterday I discovered the work around, so I thought I should share it with everyone because NOD32 is becoming more popular on campus and we have a free campus site license for the Labview software.
      The symptom is a very long delay when exiting Labview7.1 or any of the programs (VI's) you create with Labview 7.1 (30-90seconds depending on CPU speed). The CPU is pegged at 100% utilization during this time so it effectively locks up your whole computer for this time period.
      The solution is to change a setting in NOD32 under the "IMON, miscellaneous, exclusions" to include the Labview7.exe program. Normally this is C:\program files\national instruments\labview\labview7.exe .   Labview 7.1 has a connection to internet services that allows it to be remotely controlled and somehow the NOD32 and Labview get into an argument over this connection during Labview7.1's  shut down process.
      As far as I know, this problem does not occur in Labview 5 or Labview 8.
I like NOD32, but I did not seem to have this problem when I was running the Norton-Symantec antivirus program. It probably was not trying to check internet traffic for viruses.
Cliff

How do I make labview quit completely when I close a project?

So in the latest verson of Labview that I have (2012) Labview doesn't quit when you close a project or standalone VI. Instead it opens up a Labview browser that shows recent projects, has links to find drivers, forums, etc.
I want labview to quit when I close a project with the red X. Is there a setting to do that, or do I have to close my project, wait for the Labview browser to finish reloading itself, then quit that?
Ro ma wa ichi ni chi ni shi te na ra zu

apok wrote:
try this...as you press the "red X" , panel closes down with "quit LV" completly shutdown of application only if it is a "stand alone/run time engine" executable
A better way here would be to use the Discard? input. In the RUN_TIME_ENGINE == TRUE case, put in a FALSE constant and a TRUE in the default. If there are no front panels open and there is no code running, the Run Time Engine will shut down. It is a lot cleaner than the Quit LabVIEW function since you can close things down properly.
But from the Dev Environment, CTRL+Q will quit LabVIEW. Otherwise, just close the getting started window when it comes back up. As was said, just because you close your project does not mean you are ready to close LabVIEW.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Quit LabVIEW

Similar Messages

Maybe you are looking for