no block diagram during debugging application

[rfriedr1]

Hello friends,
I'd like to debug a running application.
I'm able to connect to the application with the "debug application tool" of LabView and I can see the frontpanel of all running applications. But I'm not able to open the block diagram. The shortcut "ctrl+E" doesn't work and because I use a custom run time menu there's no menu entry to open the block diagram.
By the way: I tried to include the LabView menu entry "debug application" to my custom run time menu but I could not see the entry in my application. Is this a bug?

Thanks for help.

Ronny

[Tushar_Jambhekar]

Hi

"Show Block Diagram" Menu will not appear in the exe of LabVIEW application, because LabVIEW removes the BlockDiagram during formation of Executable.

go through Documentation for more details

[rfriedr1]

Thanks for answering.
I think it's not really true that LabView removes the block diagram. If I check the option to be able to debug the application then it should be possible to see the block diagram. The manual says that I can use the same debugging techniques that I use during debugging the code in LabView including block diagrams.
???????

Ronny

[RebeccaFo]

Hi Ronny,

I think with "Debug applicaiton tool" you mean one of our new features in LabVIEW 8 to debug applicaitons and dlls. When you build the applciaiton you cann choose under Advanced "Enable debugging".

Have you choose it?

[rfriedr1]

Yes, I did.
I've choosen "Enable debugging". I could see that the size of the application doubled. I think that means that the block diagrams are still in the code.
The I used "debugg apllication..." at the project menu and connected to the running applications. That worked so far. I saw the windows of the applications doubled - a local instance and a remotelly controlled one.
I think this is as it should be. But I could not open the Block diagram. The shortcut was not working and I could not see any "run time menu"-entry.

Ronny

[RebeccaFo]

Hi Ronny,

ok I tried it several times in LV 8 and it´s working...so we should look if there is a "problem" in  your project. Please make a very simple VI with a Random Number and show it in Frontpanel. Put this code into a While Loop. Make an applicaiton of it and try it with this one. When this is not running then install LV new, when it´s running then you should minimze your code and attach it in forum so that I cna try it.

[rfriedr1]

Hi,
I did what you told me to do - and it worked. I was able to debug the little program.
Whats the problem?
Perhabs this: The program that I can not debug was converted from LV7.1. Perhabs something failed during the convertion from the *.bld-file to the project file.
Could it be? (I don't want to created a new project again with about 300 VI's:-) )

Ronny

[RebeccaFo]

Hi Ronny,

a few days ago I get a VI from a customer which has the same problem. We found that he is using VI Server and that he is working with actual path. We think that there is a problem with it and forward it to developer. I think you should minimize your VI step by step to find the problem in your project! Than you can post it in forum so that I can have a look on it.

[rfriedr1]

I use the VI server, too.
What means "actual path"? Does it mean that he uses a path to open a VI refence instead of a the name string of the VI?
If this is the case why is it not possible to debug this?
What do I have toi change in my code to enable debugging?

Thanks for your help!!!!!
Ronny

[RebeccaFo]

It´s only a speculation that this can cause the problem. In LabVIEW there is a constant for Current VI´s Path when using this I´m thinking that LabVIEW gets a problem. When you make VI Server in a SubVI delte it and copy code into Main VI. When this is not helping then it´s necessary that you minimze your VI to find in which VI the problem is and where connection failed.