The network communication switch confirmation is now only on the server for the historian module active. On all other roles (SB or client) or modules(CEL, AML,...), no longer a confirmation for the communication channel switch is performed, and they use the requested channel. The server still supports a confirmation for a channel switch for others, but this can produce the blocked alignment caused by a packet loss.
The net-service log a message for channel 1, about packet loss caused by an not connected channel in the warning level. Not every lost packet is a problem. For AML & CEL, at the startup is that normal.
The network communication switch confirmation is now only on the server for the historian module active. On all other roles (SB or client) or modules(CEL, AML,...), no longer a confirmation for the communication channel switch is performed, and they use the requested channel. The server still supports a confirmation for a channel switch for others, but this can produce the blocked alignment caused by a packet loss.
The net-service log a message for channel 1, about packet loss caused by an not connected channel in the warning level. Not every lost packet is a problem. For AML & CEL, at the startup is that normal.