Execution highlighting not working

[kc64]

I have a sub-VI with the following properties set:

Allow debugging

Reentrant execution

Share clones between instances

When I run the main VI with execution highlighting turned on for both VIs, the sub-VI never shows any action.  What is going on here?

[Mark_Yedinak]

When you have a VI configured to be reentranant you need to open the specific instance of the subVI to use execution highlighting. Turning it on in th ebase suBVI has no effect because it is not referring to the specific instance in your application. Before you run open the subVI from the application itself, not the project. You should see a number appended to its name. Once you have the specific instance you will be able to use execution highlighting. One way to ensure you get the rightinstance is to put a break point in the calling VI right before you would execute the subVI. Then simply step into the subVI and turn on execution highlighting.

[kc64]

Mark--

Thanks for the tip.  I was aware of the clone issue and did  not see that when I opened it either from the project or from the VI.  However, now when I open the sub-VI by stepping into as you suggest, the clone number does appear.  Nevertheless, execution highlighting still does not work.  The light bulb is yellow but no data flow markers appear.  If I release the pause on the execution, the execution highlighting simply returns to the calling VI.

Thanks.

[Mark_Yedinak]

Can you post your code? I have not experience the behavior you are describing unless I was opening the master copy of a reentrant subVI as I mentioned earlier.

[kc64]

Mark--

I wish I could but no.  I guess that compromises my chances of getting help.  Actually, I don't see how seeing the code helps since it does work presently and the problem is not related to a code issue but a development environment issue but who am I to say.

I will try to remember to post an answer here if I discover it on my own.  For now, I'll be out of the office till Monday.

Thanks,

[JeffL]

Hi kc64,

Putting a breakpoint in the subVI works for me in LabVIEW 2009. What version of LabVIEW are you using?