LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

simple way to pass a signal between independant VIs

Solved!
Go to solution

Yes - I see now what you mean about producing to multiple consumers (even when the data transport mechanism is different for each consumer).

 

So to pass the user event reference from the Create User Event.vi to the 'other' vi... (assuming the two event loops are in two separate vis)

 

...can you just use Create User Event.vi again in the other vi with the same datatype and name to get the same event (like you can with queues and notifiers)?

0 Kudos
Message 11 of 13
(826 Views)

@Stuart.Parkinson wrote:

Yes - I see now what you mean about producing to multiple consumers (even when the data transport mechanism is different for each consumer).

 

So to pass the user event reference from the Create User Event.vi to the 'other' vi... (assuming the two event loops are in two separate vis)

 

...can you just use Create User Event.vi again in the other vi with the same datatype and name to get the same event (like you can with queues and notifiers)?


No: User Events are not named like Queues and Notifiers, and you cannot retrieve them from a global list in the application environment.  They did consider this when deciding on the exact names for things, which is why there is "Obtain" Notifier and Queue, technically implying that you may be getting it from a global name list, and only "Create" User Event.

 

It is adviseable to avoid using named Queues, Notifiers, etc. in most cases, as using names provides a global access point for your resources.



Message 12 of 13
(818 Views)

Makes sense. Thx.

0 Kudos
Message 13 of 13
(808 Views)