How to use Notifiers in LabVIEW

[@kothamahesh100]

queues are N to 1 and Notifiers are 1 to N is the superb line that helps users to avoid confusion..awesome vedio bro

[@cmedina9088]

Hi, i still don't get it, can you explain that line, please

[@matussedivy4372]

@@cmedina9088 Queues you use to send messages (data) form multiple producers (transmiters) to single consumer (reciever). Notifiers are vice versa.

[@cmedina9088]

@@matussedivy4372 Thanks mate

[@MohitKumarSingh-l4m]

Is this method no longer working in new LabVIEW versions?

[@panda192012]

Thank you, this is greatly appreciated

[@sunilsgowda210]

Can you please tell how notifier works with respect to memory allocated and erasy

[@sunilsgowda210]

Could you please make vedio on pydaqmx and how to install package on both sides

[@ydino5215]

2:16 queues are... i don't understand what was said here, did anyone understand what was said here?

[@LabVIEWADVANTAGE]

N:1

[@king0vdarkness]

@@LabVIEWADVANTAGE thanks :)

[@king0vdarkness]

@@LabVIEWADVANTAGE what does n to 1 mean? Is it that you can send multiple values to a queue, whereas with notifier you send 1 value to multiple loops?

[@LabVIEWADVANTAGE]

N:1 means N locations to single location

[@DotyFuzz]

Can't I do the same using local variables?

[@lidarman2]

Yes you can but sometimes a race condition can occur where you read the stale local variable value right before it is updates. If you don't care about this synchronization, then use them. Basically a local variable is a register that only changes when the original variable is changed so the data is persistent, A notifier is a value passed but when it is read, it is removed and cannot be read again. It also stops the loop that is waiting for the data so it saves resources. Notifiers are great for sharing data with many other resources. Queues are kinda opposite of a notifier in that they are good and collecting data from many resources that will be used from a single resource without having race conditions.

[@MetallKnighT]

i never saw an app with 3 stop buttons !

[@LabVIEWADVANTAGE]

This is just a use case example for notifier to send Data into multiple locations from one place.

[@ericbrenner690]

While I know this was a tutorial, there are some bad coding practices here that I hope no one uses specifically how the error wires are ran and multiple stop buttons. Those three stop buttons are not needed.

[@Spintronics]

Would you please talk more about avoiding the use of multiple stop buttons? Are u suggesting using local variable? Thank you.

[@LabVIEWADVANTAGE]

grafitects.com/courses/labview-for-beginners/

[@ericbrenner690]

@@Spintronics No, just wire the error wire directly to the "stop when true" on the two obtainer loops and get rid of the merge error primitive. What will happen is when the release notifier is ran, the other two wait on notifier loops will generate an error and stop the loops.

[@ydino5215]

why use a notifier in the real world application?

[@LabVIEWADVANTAGE]

for 1 writer and multiple readers requirements. for example you want to stop multiple loops at once.

[@king0vdarkness]

@@LabVIEWADVANTAGE thank you for reply, why not use local variable in this case? Is it because of race conditions?

[@LabVIEWADVANTAGE]

Yes