08-24-2010 07:09 AM
The application code is very complicated, requires some hardware to run, is confidential and I can not release it to 3rd parties.
Perhaps a can construct a project with a similar structure and can post that.
I was looking to see if there was some simple way to get LabVIEW 2010 to list the VIs that it says are running, rather than trying to debug my application to see why, or if in fact, they are still running.
If my Main.vi that invoked these subVIs has stopped executing, how could there possibly be any subVIs still running?
If none are running, why does LabVIEW 2010 says that some are?
08-24-2010 07:11 AM
THe only way that I know is to trun on the light bulb and look for the green arrow. Turn on the light bulb before you push the stop button and watch what happens.
08-24-2010 07:39 AM
@aeastet wrote:
THe only way that I know is to trun on the light bulb and look for the green arrow. Turn on the light bulb before you push the stop button and watch what happens.
I have done that and all subVIs stop and their green arrows goes away, Main.vi stops executing, all highlighting stops, as you would expect.
But LabVIEW 2010 still says some VIs are running if I close the project.
I just want to know what VIs are running and why (how)?
08-24-2010 07:44 AM
I understand what you want. But without code to troubleshoot I can only guess.
The only other things that I would suggest is to take the coditional disable and start isolating code until you do not have this problem anymore. Then you know where to start. Disable on vi at a time until th problem goes away.
08-24-2010 10:58 AM
Have a look at
abort vi.vi
http://forums.ni.com/t5/LabVIEW/Darren-s-Occasional-Nugget-08-11-2008/td-p/760429?query.id=7241
and
vi task manager.vi
Rod.
08-24-2010 11:41 AM - edited 08-24-2010 11:43 AM
You could run the attached VI. It'll give you a list of your running VIs (click on them to force them to close). I wrote my version of Abort.VI after learning a bit about scripting. Mine has an unlocked BD if you're interested in how it works.
02-26-2012 07:59 PM
Um, sorry to be dense jcarmody. Could you please be more specific about how to use Abort_82.vi?
02-27-2012 04:53 AM
First of all, there is only one dense jcarmody, an you're not him.
I keep a copy of the abort VI in my home directory so I can get it from any computer I log in to. I also keep a copy on the desktop of my main computer so I can minimize everything and get at it quickly. When I get stuck in a VI that won't let go, I minimize (or use Windows Explorer) to find abort82.vi and execute it from there.
02-27-2012 09:47 AM - edited 02-27-2012 09:50 AM
Thanks I didn't realize LV would let you start a second vi. Told you I was dense jcarmody.
No wait..