LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems using the Exit vi

Hello!
 
I am a beginner using LabVIEW and have now experienced a strange problem (at least for me) while using the exit vi. What I want to happen is that when a button is pressed on the front panel, LabVIEW shall close completely. It used to work without any problems. But then I modified my program just a little bit, I added som vi:s, but didn't change the part using the exit vi. Now when I am running the program all windows close, BUT the LabVIEW "tab" on the lower "menu" on the screen is still there! As long as it is there I cannot start LabVIEW  againg. And I must close it using the task manager.
I did an executable for this program and the problem was gone, it worked fine. But when I moved the executable to anyother computer, the problem shows up again!
Can anyone help me?!
 
Best regards,
Helena
 
0 Kudos
Message 1 of 5
(2,737 Views)

Is it possible to post your code.

Paul

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 2 of 5
(2,731 Views)
Hi Helena
Have you not a back up of your orginal VI?( OK horse has bolted its to late to close gate !!!-Future reference make a back up copy Smiley Wink)
Are you are sure that it is the exit icon you are using ? Not abort.
With reference to your vi's have you adjusted properties so that Front panels close after running ?
Are you sure that it is not runtime engine  that is still loaded .
Check via task mananger.

If you are still having problem  then please either upload code or a jpg or png picture of your block diagram.

chow
xseadog


0 Kudos
Message 3 of 5
(2,728 Views)
Try double-clicking on a VI from Windows Explorer. If the VI opens, start troubleshooting form there; e.g. open the Hierarchy window to see what is loaded. Did you add an App Exit filter to an event structure in some VI perhaps?
 
Roy
0 Kudos
Message 4 of 5
(2,703 Views)
Sounds like one of the vi's you added is staying stuck in memory.  Perhaps the rogue vi remains open because it has called some DLL or other function that has not completed its task.  So the vi sits there waiting for something it has called to finish.  Remove the vi's you added one at a time until you find the culprit, then troubleshoot from there.
- tbob

Inventor of the WORM Global
0 Kudos
Message 5 of 5
(2,699 Views)