LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How does Wait on Notification on Multiple Work

I am trying to figure out how the Wait on Notification on Multiple works with the ignore previous. I assume if ignore previous is set to false, that it would return whenever a notification appears. I have found that after the first wait, it will return any notification that occurs. Subsequent calls to the VI, it will wait until it detects a new message, and subsequently return the notifications. In my example, I found that the notification is generally broken into 2 waits, the first will have a single notification, and the second will return the rest of the notification.
 
Could someone explain how this VI is suppose to actually work. I sort of expected it to return all notifications that have been sent when it returns and not parts of it. I have included my example. There are many additional VI, they are not really used. They are part of the polymrphic version of the VI I am using.
0 Kudos
Message 1 of 3
(2,521 Views)

The Wait on Notification from Multiple VI is used to listen for notifications from more than one notifier.  If both of the notifiers send their notification at the same time, then you will "lose" one of the notifications.  To prevent this, I found the attached example within our KnowledgeBase.

 

David_B
Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(2,488 Views)

Unfortunately, your example is incomplete. It calls a test.vit.

What you brought up is another issue that I will have to look at. I may switch to a rendezvous to fulfill my needs. But doesn't the bug you mention defeat the purpose of a notifier? What version is this workaround suppose to be for?

Another issue, the notification being sent is not simultaneous. I have a simplified version at this time dealing with two sets of a single notification where I do the second notification (requires manually intervention), thus simultaneous notification is not an issue. My first guess, it has to deal with the actual referencing of the notification or execution. It seems that the obtain notifier is not getting the correct reference or is not monitoring it properly. If you have to start an execution trace to make it work sounds a bit of a problem. Remember, it works okay with a different order of execution. If I reverse the order, it works correctly.

0 Kudos
Message 3 of 3
(2,464 Views)