communcation between projects?

[EOF]

Hi all,

I am wondering how to send messages between different projects. It seems (from little testing I tried) that notifiers and semaphores cannot be passed between projects (maybe I have to change some of the project properties). So I am wondering what is the mechanism for doing this, or should I develop everything that would want to communicate within the same project.

Thanks,
EOF

[parthabe]

It is quite interesting to know that you wish to communicate between projects.

May I know why do you wish to do so?

Is it because that you are NOT going to build an application for your or your customer's use?

[EOF]

Dear Partha,

I am glad that you are interested.

It would obviously be possible to put everything in the same project, but it feels a bit rigid to me, so I am wondering if there is something like sockets in Labview that will allow any running VI to communicate with any other.

Thanks for your help, I am not very familiar with the archotecture of Labview.

EOF

[parthabe]

---

EOF wrote:

I am wondering if there is something like sockets in Labview that will allow any running VI to communicate with any other.

---

Prabably Datasockets... ?!

Did you try this yet or at least have a look into it?

[parthabe]

Also, Shared Variables?

[EOF]

Thanks, this looks like it could be the way forward.

[BrianInTheForest]

If I was trying to communicate with VI's on different platforms I would use shared variable.

If I was trying to communicate with VI's on the same platform I would use a functional global.

[parthabe]

---

BrianMcLean wrote:

If I was trying to communicate with VI's on different platforms I would use shared variable.

---

Do you mean OS or N/W by this term 'platforms' ?

[CMal]

EOF,

Please take a look at this thread, which discusses the same topic.

Chris M 

[RER]

Hey guys,

Global shared variables are certainly one way of communicating between applications, but they do open the door to certain issues, such as (the dreaded) race condition. The pitfalls of overusing glabal shared variables is discribed in the following document.

Are LabVIEW global variables good or bad, and when is it OK to use them?

This document also suggests the use of glabal functional variable to combat this issue. Admittantly, they do require a little work work to set up. But the could reduce hours of headache in the long run. If you are new to the concept of "functional globals", please navigate to the following links to some excellent example code on the community pages.

http://decibel.ni.com/content/docs/DOC-2143

http://decibel.ni.com/content/docs/DOC-5403

Kind regards to you all