crossrulz

schneidley, I think this will work for you. I used two shared variables to start and stop the two parallel processes. You could also use globals. Just make sure you initialize these variables very first thing in your program. If you are passing read data between the two processes, I would highly recommend using queues.

QUOTE (Brian B @ Jul 24 2008, 01:02 PM) Sorry. I should have looked at what versions you had. I just did a save for version 8.0.

Your problem (at least in this example) is that the global variable is only being written to immediately coming into the loop. The loop is then dominated by the subVI. Therefore the global to exit the subVI will never be written to again. The following recommendation is only for GUI stop commands, but it might lead to other ideas for your specific situation. Use another loop with an Event Structure in it. Set an event to "Stop" value changing and then write the new value to the global variable. This will then end the subVI. As long as you don't have a Timeout event case, the event structure uses no cpu cycles until a registered event happens, so performance issues are nonexistant. My edited code for the top level VI is attached.

If I set up Data Binding on an indicator to a network shared variable, how often is the indicator updated? I am using LV 8.5 with the RT module. I am trying to get updates from the RT target to show up on the Windows computer. I would prefer not to constantly poll the shared variables if possible. We don't have the DSC module, so I can't use event structures to update that way. What I am hoping is that the data binding updates is event driven and therefore making it a lot more efficient than the polling I am currently doing.