Hello.

Ad 1. This is a sign of the fact that the component is trying to reconnect, and it is by design. As long as the connection attempts keep failing, you will keep receiving these events. This way, if you are observing the notification for any particular, the last notification you received reflects the current status. If we had suppressed the notifications after first failure, observing the notifications wouldn't tell you *when* the last reconnect failed - you would only know about the first disconnect. And the precise reason/status can also change - while still being in failure. The fact that there are two of these is the only detail that was not designed into the software intentionally, but instead came out of the implementation- it would be better if there was just one, I agree, and we know about it (the second one you listed is the one that has the usual information in it, which can bring insight into the problem; the first one is kind of unnecessary). Maybe in future this will improve.

By default, the component tries to reconnect very frequently - every 10 seconds (in the end it can be somewhat more, but this is the main number). You can change it using this property: opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User's...onParameters~RetrialDelay.html .

Ad 2. This is manifestation of the same process - the reconnection attempts. You should be seeing state changes from Disconnected to Connecting - but then, back to Disconnected when it fails. And finally from Connecting to Connected, when the device is plugged in. That's how it should work. The frequency depends on the same setting as described above.

Best regards