Is a notifier implicitly destroyed with the 'master' VI?

[maturgbg]

I have two VIs SendNotification and ReceiveNotification (see attachments) which are working perfectly.

The problem occurs when I'm stopping and restarting the VI that was started first (master😞 A new notifier is created though the slave is still using the old notifier.

The other way round, when restarting the slave - no matter wether this is SendNotification or ReceiveNotification - everything works fine.

Has anyone an explanation or solution for this problem? I'm working with LabView 6.0.

[Mads]

That seems to be the case with the 6.X notifier yes.

It's been changed with the new notifiers in LV7, in LV7 the notifier is alive even when the creator is not...There you have to run a release notifier with the force destroy flag set to true if you really want to destroy the notifier...

[Alberto]

Hi,
your main problem is that when you stop and re-start the server you create a new notifier with a different reference than the previous, while the client is still using the previous therefore they can't share data.
You can check it by adding probes on the notifier references on both vis.
A workaround is to check on the client when an error occurs (the sever has stopped and destroyed the previous reference), in that case a new notification is created.
See modified examples.

Alberto

[maturgbg]

Thank you very much! Your workaround performs very well! I even learnt that an error can be directly wired with a case structure.

Matthias