the reconnection behavior will be of "type A": if the network is lost, but power stays ON, and the network comes back. The socket is kept. - details ---------- the network socket (tcp/ip) with it's lxi session is NOT reconnected on the PLH side, even when a lxi_disconnect followed by a lxi_connect is made. This stems from the aimTTi firmware. On the server, when doing a lxi_(re-)connect, the new session blocks on a mutex on the tcp/ip lxi comm layer, which means basically that the PLH does not reply. After a long (unknown) time the PLH might drop the session and wait for a new request. The session-expiry delay is not documented for the PLH. If the opcua-lxi makes a new session request when the PLH is not ready then the server thread for that PLH concerned is stuck forever on the (tcp/ip-) session mutex. With the new "behavior A", the opcua-lxi server ignores transmission errors and does not close/reopen the socket (lxi disconnect, connect) and just KEEPS the session it has. The communication with the PLH comes back after about 30secs when network is restored. If the socket is not used for a longer time the server's OS might clean it up somehow and the communication would be entirely lost. Then a server and PS restart is needed: this corresponds to a full power cycle anyway. It is recommended to connect the PS power throuugh a PDU in any case so that the power cycling can be done remotely.