Communication across VI's

[HeLo]

Hi Community,

in some applications, I would like to give the user the option to leave some windows open that have received data from a master-vi.

As far as I know there are several concepts, for example starting independent vi's that then communicate through shared variables and so on.

However, in order to have full access to all the methods and properties (trigger events by writing a "value signaling" ...) in the independently running vi, I came up with the attached solution.

Do you think this is too complicated and how do you solve such request?

I hope that the code is pretty self explaining and I included a compiled version in order to show that it works also as a compiled application.

Herbert

[akjohn]

Thank you for this post. I have also been looking at various ways to accomplish the task you describe. I will look at your attachment in next three or four days. To me complicated is not a big issue as long as the functionality is there and speed does not suffer significantly.

[jgcode]

QUOTE (HeLo @ Jul 14 2008, 12:01 PM)

Hi Community,

in some applications, I would like to give the user the option to leave some windows open that have received data from a master-vi.

As far as I know there are several concepts, for example starting independent vi's that then communicate through shared variables and so on.

However, in order to have full access to all the methods and properties (trigger events by writing a "value signaling" ...) in the independently running vi, I came up with the attached solution.

Do you think this is too complicated and how do you solve such request?

I hope that the code is pretty self explaining and I included a compiled version in order to show that it works also as a compiled application.

Herbert

Sometimes whatever works - works.

But updating using value property nodes is like using globals.

A better way than using VI server to write to value property nodes is to use Queues for inter-vi communication.

I use a modified version of the QSM-PC all the time, if it fits the solution then it's a great design pattern - check http://expressionflow.com/2007/10/01/labview-queued-state-machine-architecture/' target="_blank">here for more info.