LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I tell which VI is stopping my EXE from closing

Solved!
Go to solution

Hello all

 

I have developed a test system which needs to control 4 different test stations simultaneously using the same IO hardware, so some of my VIs are re-entrant (pre-allocated). My loops are all controlled by Loop.vi (see "A Software Engineering Approach to Labview") and Loop2.vi. My exit process results in the main VI exiting and all the loops closing, but the main VI stays running. I am fairly confident that there are no hardware operations in progress, but I think there must be a sub-VI somewhere which is still running.

 

I will transfer the project back to my development environment with the debugger. How can I track down which VI is still running? Is there a call tree tool somewhere?

 

Thanks for any help

 

Ray

0 Kudos
Message 1 of 5
(2,745 Views)

I think that viewing the VI heirarchy will show you but I can't remember. If that doesn't help you then check out the LabVIEW Task Manager on Lava.

=====================
LabVIEW 2012


Message 2 of 5
(2,741 Views)

Does the attached VI help you?

Message 3 of 5
(2,735 Views)

My Abort.vi will find it for you.  I keep a copy on my desktop in the event that I have a VI that won't respond to UI commands to close.

Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

Message 4 of 5
(2,720 Views)
Solution
Accepted by Radiator

Hello all

 

Thanks for the responses. I have found the Task Manager tool quite useful and the Abort VI is now on my desktop and in regular use as you suggested!

 

The tools showed me that only my main VI was running, and so I thought I had a loop running somewhere... This turned out not to be the case - I could not find anything using the debugger - there was nothing running and the VI was still not closing. However, I then discovered that a second click of the exit button would allow the VI to close, so I guessed it was events related. Eventually I found that the Wait on front panel activity VI was blocking the exit and that wiring the loop closing VI to the Do not wait terminal on the Wait for front panel activity fixed the problem, as this was no longer waiting for a second click. And of course, this does not show in the debugger!

 

Thanks again,

 

Ray

Message 5 of 5
(2,694 Views)