the endpoint of the server to connect to ( i.e "opc.tcp://machine.name:3434/name" )
causes client to close and disconnect the communication with server
this Event is raised when the initial connection has succeeded
this Event is raised when the initial connection has failed
this Event is raised when a failing connection is about to be tried again
this event is raised when the client has encountered a connection failure and and is going to reconnection mode. You can intercept start_reconnection event to pause your interaction with the remote OPCUA server.
this event is raised when the client has failed one attempt to reconnect to the server This event will be raised if the socket has successfully being created to the server but if something went wrong during the reconnection process.
this event is raised after the client has successfully managed to re-establish the connection with the remote OPCUA Server. You can intercept after_reconnection event to resume your interaction with the remote OPCUA server.
the event is raised when the connection has been aborted by the remote OPCUA Server
this event is raised when the connection is closed
this event is raised when the client is sending a message chunk to the server (advanced use only)
this event is raised when the client has received a new message chunk from the servers (advanced use only)
this event is raised when the current security token has reached 75% of its lifetime and is therefore about to expired.
this event is raised after the (about ) security token as been renewed and renegotiated with the server.to expire
this event is raised when the connection has been broken
this event is raised when a broken connection with the remote Server has been reestablished
This event is raised when a request sent to the remote OPCUA server has reach it's timeout value without a Response from the server.
Generated using TypeDoc
certificate Manager