Notification output at timeout, without notification arriving

[sirnell]

Hi!

I have a couple of probably simple questions:

What can I expect the notification output to be at timeout of 'Wait on notification', if:

1) no notification has yet been sent using that notifier reference?

2) the last notification sent was received by the same 'Wait on notification' at the previous iteration (i.e. no new notification available)?

Default value of notifiers datatype? The last value sent through notifier? Value used as input to 'element data type' of the 'obtain notifier'? Random garbage?

Thanks for your help!

/Michael

[tst]

In these cases, it's usually easiest to put together a quick test (which is what I did).

2 loops - one constantly waiting with a timeout, the other sending only when a button is pressed. This clearly shows that in both cases, when a timeout occurs, the data coming out is the default data type of the notifier - an empty string, an empty array, a false boolean, a 0 numeric and so on...

[sirnell]

Thanks for helping me!

I would have done. Being at home, I only had a printout of the code I was debugging and no labview.

I'm new posting in this forum. Did I somehow make my first message, my question, a reply? Does that mean I can give you credit for your answer? Is there a way around it?

[sirnell]

Doh. Found it myself, I was just not logged in earlier when trying to give credit.

[tst]

The liscensing agreement for LabVIEW allows you, under certain conditions, to install your version of LabVIEW at home, so you can be twice as anti-social as before ("Honey, I'm just answering this one last question. Your parents can wait...").

[tst]

Since you're new here, if you're looking for some fun, try the BreakPoint.