LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to access the history of notification?

Solved!
Go to solution

I am using notifer as event tigger but suffering the missing notifications. Do I have any way to access "all the history" of notifications instead of just the latest one like what we can do in "queue"?

BTW, I tried to figure out what is the difference between the following two functions: "wait on notification" and "wait on notification with history". It makes no difference to me especially with the existing parameter-"ignore previous" in both of these two functions.

Thank for your help.

 

0 Kudos
Message 1 of 10
(3,143 Views)

Queues and Notifiers are essentially the same, except queues have a buffer and notifiers do not.

 

If you are missing notifications, maybe use a queue instead of notifiers? 

 

 

0 Kudos
Message 2 of 10
(3,131 Views)
yes thank you for your reply. However, queue doesn't notify actively, that's why I use notifier.
0 Kudos
Message 3 of 10
(3,124 Views)

@longboy wrote:
... However, queue doesn't notify actively, that's why I use notifier.

Hi,

can you please explain this?

 

Mike

Message 4 of 10
(3,120 Views)
Dear Mike, hmmm... With queue, I have to query by myself instead of been notified when event occured. Regards, ChingLung
0 Kudos
Message 5 of 10
(3,115 Views)
Solution
Accepted by topic author longboy

@longboy wrote:
Dear Mike, hmmm... With queue, I have to query by myself instead of been notified when event occured. Regards, ChingLung
How is that?  A Dequeue Element will sleep while waiting for something to enter the queue.  I guess I don't know what you mean be "notified".

GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 6 of 10
(3,095 Views)

@Phil_ wrote:

Queues and Notifiers are essentially the same, except queues have a buffer and notifiers do not.

 [...]

 


There is an additional difference:

Queues allow multiple writers but a single reader, the Notifier a Single writer and multiple reader.

 

You CAN use them differently, of course, but then you really need to know what you are doing (otherwise: welcome to the hell of debugging race conditions!)

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 7 of 10
(3,084 Views)

Dear Mike

oh, yes! I tried and it works well. Thank you for your patient and rescuing me from the two-day suffering.

Regard,  ChingLung

0 Kudos
Message 8 of 10
(3,071 Views)

Norbert_B 已寫:

@Phil_ wrote:

Queues and Notifiers are essentially the same, except queues have a buffer and notifiers do not.

 [...]

 


There is an additional difference:

Queues allow multiple writers but a single reader, the Notifier a Single writer and multiple reader.

 

You CAN use them differently, of course, but then you really need to know what you are doing (otherwise: welcome to the hell of debugging race conditions!)

 

Norbert


Dear Phil and Norbert, 

  Thanks for your explaination. It seems clear to me now. It works well now. Thanks again!!

Regards,    ChingLung

0 Kudos
Message 9 of 10
(3,066 Views)

Notifier can be many to many. They are not restricted to a one to many relationship. The important part is that unlike a queue notifiers can have multiple listeners.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 10 of 10
(3,049 Views)