How to share references?

[altenbach]

Did you wire a number to the timeout terminal?

[punkmonkey]

Never Mind. Figured it out. Attached is the final rendition.

Thanx for all the help.

[punkmonkey]

didn't see your reply as I was typing mine. That was the problem. Again thanx.

[altenbach]

Still not quite there:

Main VI:

1. Why do you create the VI reference twice? You still have the reference from inside the loop, so just wire it to the node in the second sequence frame.
2. Now you have a data dependency and the sequence is no longer needed.
3. The timeout event is useless. Change it to "stop button:value changed". No need to spin the loop without reason.
4. Use a stop button for "stop" (latch action).
5. create the reference outside the structure. It needs to be done only once.

SubVI:

1. Use a local variable instead of the value property node.
2. if you would use a 100ms timeout, the CPU use would be only 1/100 without any difference in useability.
3. How do you stop the subVI if the panel is closed and the main VI no longer runs?

In my opinion, there are probably much better ways to do all this. It seems so convoluted. 😉

Message Edited by altenbach on 02-27-2008 02:18 PM

[Pnt]

A simple solution, without stop button. I was in a hurry.

[punkmonkey]

How do you stop the subVI if the panel is closed and the main VI no longer runs?

I take it this implies that the invoke FP.Close does not stop the VI. So I have no idea. That was why I was using the FP.Close.

I found the Abort VI method and the help seems to indicate that this is what I want to do.

Message Edited by punkmonkey on 02-28-2008 07:45 AM