From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I find which VIs are actively running?

How can I find which VIs (among thousands) are actively running (not just reserved)?  (Exec.State property is not enough)

Message 1 of 36
(3,807 Views)

DETTSmiley Surprised

 

Yes, if you need to do that dynamically- do it!

 

the Desktop Execution Trace Toolkit, Its not something I have needed to play with but, if I am understanding you correctly you might need to check it out.

 

Post back, I'll learn something!


"Should be" isn't "Is" -Jay
Message 2 of 36
(3,775 Views)

Or the less expensive way (not needing the DETT) would be something like this


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 3 of 36
(3,744 Views)

@crossrulz wrote:

Or the less expensive way (not needing the DETT) would be something like this


I think @FermWorks is already aware of this property node, and what she meant to ask here is: any method to get the list of VIs, which are actually running at a given instant of time.
Your solution will all the VIs in memory and has state as 'Running', which mean "VI is reserved for execution by one or more active top-level VIs". 


I am not allergic to Kudos, in fact I love Kudos.

 Make your LabVIEW experience more CONVENIENT.


Message 4 of 36
(3,730 Views)

I would really enjoy an extensive dialog on this subject. I have found the "running" Exec.State a little confusing. Right now I'm looking at a "Main" vi that is just sitting there waiting for an input to an event structure. It shows 500+ vi's "running" - except the Main vi. Smiley Indifferent

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 5 of 36
(3,715 Views)

@PaulG. wrote:

I would really enjoy an extensive dialog on this subject. I have found the "running" Exec.State a little confusing. Right now I'm looking at a "Main" vi that is just sitting there waiting for an input to an event structure. It shows 500+ vi's "running" - except the Main vi. Smiley Indifferent


That's because Main.vi is now "Run Top Level" not "Running"

Message 6 of 36
(3,697 Views)
I'll give DETT a try when I get a chance. I'm troubleshooting on a LV 8.6 system but could load all in LV 11, if necessary. I'll let you know if I figure it out, thanks.
0 Kudos
Message 7 of 36
(3,675 Views)

Thanks for the clarification. Doh!

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 8 of 36
(3,671 Views)

Can you try this...

 

http://zone.ni.com/devzone/cda/epd/p/id/2612

 

Show Running VIs VI:

 

showrunningvis.png

 

Hope this might help!

Cameron T
Applications Engineer
National Instruments
0 Kudos
Message 9 of 36
(3,658 Views)

@CamThornton wrote:

Can you try this...

 

http://zone.ni.com/devzone/cda/epd/p/id/2612

 

Show Running VIs VI:

 

 

 

Hope this might help!



Not quite.  Meg wants "Is Run Arrow Black?" to filter out the reserved vis


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 36
(3,646 Views)