LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to find which sub-vi is running in highlight execution mode?

Solved!
Go to solution

Hi there,

 

It sometimes happens that while debugging you program you open a lot of sub-vis put probes in many places turn on highlight execution in dirrerent sub-vis and then forget to turn it off.

You close all sub-vis and run software and it runs SLOOOOW. Then you need to go and find that sub-vi that runs in highlight execution mode.

 

I was just wondering if there is an easy/automatic way find which vi has highlight execution mode turned on?

 

 

0 Kudos
Message 1 of 13
(9,028 Views)

This might not be the most helpful reply but personally I limit the use of highlight execution to almost never. Probes and breakpoints usually give me the debugging information I need.

 

One idea would be to use breakpoints to "stall" the program in, say, a specific sub vi. Then temporarily turn highlight execution on. All the info you need should then be there and you can immediately turn highlight execution off again. I don't see a reason to ever leave it on, especially when you are "done" with a sub vi and are going to close it...

 

I guess its just a matter of turning the lights off when you leave a room Smiley Very Happy

 

Cheers,  

- Jolt
0 Kudos
Message 2 of 13
(9,021 Views)

After you turn highlite execution on, look for a green arrow in the subvi that is presently being executed.  Notice the items after are greyed.

 

22028iD8E89F9BF4FFA6EC

- tbob

Inventor of the WORM Global
0 Kudos
Message 3 of 13
(8,987 Views)
Solution
Accepted by Yakov

Here is a small utility to switch off Execution Highlight mode off all opened subvis. Drop it into the Project subfolder in the LabVIEW application folder, then restart LabVIEW. A new item "Stop Highlight mode..." will appear in the Tools menu. Enjoy !

Chilly Charly    (aka CC)
Message 4 of 13
(8,975 Views)

Chilly Charly,

 

Thanks a lot. This is exactly what I was looking for.


I had to change FP.State to Standard instead of Closed to make it work.

 

My only question is how did you managed to get to vi's property "Diagram" and "Highlight" property?

 

In LV2009 that I'm using these properties don't show up on the list, may be they somehow hidden.

 

P.S..

I ran your program to find out that unfortunately my program's sudden slowdown wasn't due to highlight execution turned on in one of sub-vis. 😞

Now I have to dig in and try to find the problem, but it was worth a shot. 🙂

 

 

0 Kudos
Message 5 of 13
(8,929 Views)

Any property nodes with a blue bar at the top means they are a part of LabVIEW scripting.  For LV 2009, you need to install and register for LV scripting.  For LV 2010, you just need to enable scripting.

0 Kudos
Message 6 of 13
(8,922 Views)

 


Yakov a écrit :

My only question is how did you managed to get to vi's property "Diagram" and "Highlight" property?

In LV2009 that I'm using these properties don't show up on the list, may be they somehow hidden.

 


These properties are part of the LV scripting tools

Chilly Charly    (aka CC)
0 Kudos
Message 7 of 13
(8,920 Views)

I found this through a search and it looks to be exactly what I needed...  I have a tendency during debug to open a lot of sub-vis, highlight execution, find and fix the problem, but then don't remember all of the sub-vis that were highlighted.

 

Unfortunately, I cannot get this to work at all?

 

I tried opening it in both 2010 and 2011 and it just pops up the "Save Before Closing" dialog. I can't see the front panel or the block diagram to even try to find what might be the issue.

 

Any suggestions?

 

0 Kudos
Message 8 of 13
(8,475 Views)

It was created in LV 8.5, so if you open it in a newer version, it will automatically recompile for the newer version and will be flagged as needing to be saved.

 

It was also saved as Run When Opened.  So it automatically runs, does its thing and closes itself.  Since it has changed because of recompiling for a newer LabVIEW version, it asks to Save or Discard changes.

 

If you want to see it, save a copy of the VI to your hard drive.  Open a blank VI and drop this VI in as a subVI.  Now when you open it, it will open for editing and won't run.

0 Kudos
Message 9 of 13
(8,467 Views)

Thanks Ravens Fan,

 

The first two I kinda figured...  I always forget about pulling a VI into a new blank VI as a sub so that I can open it for reading...  I just don't need to do that that often.

 

The main thing that I was going to try to figure out, is I placed the VI in the Project folder under C:\Program Files\National Instruments\LabVIEW 2011, but when I run a VI in debug mode, I don't see the icon in the tool bar. Am I missing something else?

 

BTW...  GO PACK GO!!!  (oh, maybe I shouldn't say that until after all questions are answered...)  Smiley Very Happy

 

Dan

0 Kudos
Message 10 of 13
(8,455 Views)