1. They all have to be currently running.
2. They all have to have the reference to the same Notifier.
What I like to do is have an Action Engine that holds the reference and then whoever needs to listen for the notification can get the reference. I typically have a Send command in the Action Engine for the process that needs to send the notification.
Crossrulz has one valid solution.
Alternately, when you use the "obtain notifier" VI in two parallel VIs, as long as you're not using an unnamed VI and the same exact data type, you'll get the same reference from each.
Kyle97330,
Your suggestion works when building the vi, but once I compile it to an .exe file, it doesn't work anymore. Not sure if I did it correctly.
VI's running within the LabVIEW development environment exist in the same application space and can share data like notifiers. If you go and make two different executables out of those two VI's, they now exist in different application spaces. You can share data through notifiers like that. You'll want a different mechanism for sharing data like TCP/IP or UDP, network shared variables, or a relatively new addition to LabVIEW called network streams.
@RavensFan wrote:
You can't share data through notifiers like that.
I think RavensFan meant to say
Dohhh!. You are right. You can't share notifier notifiers through different application spaces. I was thinking one way and typed the other.
Thanks Omar.
?
Have you considered wrapping the notifier action in an Action Engine that is served via VI Server?
While I have not done it with notifiers I have exposed queues on one machine to another by wrapping the Queue operations in a AE that was served. Aside from a bug in LV 6i-RT tht would kill the queue if the connection was closed, that type of operation has been around for a long time and works well.
Ben
Ben