In M251 it is not possible to enable or disable the Keep alive feature on the default SoMachine modbus TCP server.
The M251 TCP Server have the following behaviour when the Client does not close the socket correctly or not keep alive message was received:
The following behaviour is the same when the PLC is in RUN or in STOP state.
1. Default configuration:
The socket will be closed after 35 seconds.
2. Using a ModbusTCP Slave Device
The socket will be closed after the configured TimeOut ( only the socket opened by the configured Master)
The M251 TCP Server have the following behaviour when the Client does not close the socket correctly or not keep alive message was received:
The following behaviour is the same when the PLC is in RUN or in STOP state.
1. Default configuration:
The socket will be closed after 35 seconds.
2. Using a ModbusTCP Slave Device
The socket will be closed after the configured TimeOut ( only the socket opened by the configured Master)
Released for:Schneider Electric India
In M251 it is not possible to enable or disable the Keep alive feature on the default SoMachine modbus TCP server.
The M251 TCP Server have the following behaviour when the Client does not close the socket correctly or not keep alive message was received:
The following behaviour is the same when the PLC is in RUN or in STOP state.
1. Default configuration:
The socket will be closed after 35 seconds.
2. Using a ModbusTCP Slave Device
The socket will be closed after the configured TimeOut ( only the socket opened by the configured Master)
The M251 TCP Server have the following behaviour when the Client does not close the socket correctly or not keep alive message was received:
The following behaviour is the same when the PLC is in RUN or in STOP state.
1. Default configuration:
The socket will be closed after 35 seconds.
2. Using a ModbusTCP Slave Device
The socket will be closed after the configured TimeOut ( only the socket opened by the configured Master)
Released for:Schneider Electric India
