How to debug a reentrant vi.

[alex.]

I dynamically called a reentrant vi. Then, I cannot go into the vi to debug it, only can open the clone copy, except the log file. Can I use some method to debug it? Thanks.

Also I want to know if a vi stopped, will the dynamical vi called by it also auto stop.

Message Edited by turbot on 07-10-2008 10:14 PM

[MikeS81]

Hi turbot,

maybe it´s possible for you to test your vi as a "normal" vi, without the reentrant function. If not you can use a cluster indicator to output import information and debug it from the caller side.

I´m not sure with your second question. In LabVIEW 7.1 the called vi was stopped if the last vi which has open it was stopped, except the called vi has open a vi from itself.

Hope it helps.
Mike

[alex.]

May I know what is your meaning of "If not you can use a cluster indicator to output import information and debug it from the caller side."

Also the "except the called vi has open a vi from itself.", thanks.

[MikeS81]

Hi turbot,

if it is not possible for you to test you vi without the reentrant function, then you can use a cluster to get import data to the point from where you call this vi. And because this position shouldn´t be reentrant you get exactly the data from this instance and not from another one.

If a vi opens their own reference then it will not stop if the caller stops, because there is still an opened reference of this vi.

Hope it helps.
Mike

Message Edited by MikeS81 on 07-11-2008 09:18 AM

[alex.]

Can i look into the running reentrance vi itself.

I am still not get the meaning of "If a vi opens their own reference then it will not stop if the caller stops, because there is still an opened reference of this vi.", May you explain in details, thanks.

[MikeS81]

Hi turbot,

i think you can´t look into the reentrant vi. If you want to open it, you will get a new instance of it.

Please see the attachment. If you run "Main.vi" it will call "Unbenannt 4.vi" (it is not visible). If you double click on "Unb..4.vi" you see the vi is running. If you close it and open it again it is still running. If you close it and you then stop the "Main.vi", "Unb..4.vi" will also be stopped (but only if it is not visible). To avoid this, you can use the "Open VI reference" function in "Unb..4.vi", because then "Unb..4.vi" creates a reference from itself.

Mike

[alex.]

1. After run the main5.vi, I double click the "Unb..4.vi" and see it is running. Then I stopped main.vi and "Unb..4.vi" is still visible and running. may I know why in this case the "Unb..4.vi" will not stopped.

2. May I know "you can use the "Open VI reference" function in "Unb..4.vi", ", thanks.