S7TCP32: Timeout for TCP connect timeout on Linux too short

• Related Articles

• T5BusEIPS: Idle TCP connections are not automatically closed.

  Description The EtherNet/IP Adapter (T5BusEIPS ) does not close TCP connections when these are idle and do not send any data. This can lead to a denial of service for valid EtherNet/IP Adapter when the maximum number of 124 TCP connections are used ...

• When creating a MODRTU32 Driver, in the "Settings" tab of the Driver when selecting "TCP/IP", the TextBox "Connection timeout" is greyed out.

  Summary The TextBox "Connection timeout" under the "Settings" tab of the MODRTU32 Driver gets greyed out when selecting "TCP/IP" as Connection. DescriptionThe TextBox "Connection timeout" under the "Settings" tab of the MODRTU32 Driver gets greyed ...

• The OPCUA32 client driver does not resume communication after short network connection loss under specific circumstances.

  Summary When the network connection between the OPCUA32 client driver and the OPC UA server is lost for a specific short period where TCP retransmits may still reach the server after the connection is established and where the connection loss is long ...

• FAQ: What can I do when I run into a timeout while creating a project backup?

  In the zenon6.ini file it is possible to define timeouts for database access and for backup creation. Maybe the default configuration is too low. This could happen when backing up more complex projects or if the project includes many graphics and ...

• T5BusEIPS: EtherNet/IP Adapter does not make use of TCP Keep Alive

  Description The EtherNet/IP Adapter (T5BusEIPS) does not make use of TCP keep alive messages to check if the TCP connection from an EtherNet/IP Scanner is still OK. The issue has been addressed and the T5BusEIPS enables a TCP keep alive for the ...