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

• Related Articles

• MODBUS ENERGY: Support for RTU frames over TCP/IP

  Summary The Modbus Energy driver supports communication of RTU frame via TCP/IP. Description For this purpose, the new Modbus TCP/RTU frame via TCP radio button has been implemented in the Settings tab of the driver configuration dialog. Item ID: ...

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• S7TCP32: Timeout for TCP connect timeout on Linux too short

  Description For the S7TCP32 driver the default timeout for TCP connections under Linux is too short. The preconfigured timeout of 10 ms is often exceeded. The connection can therefore not be established. This behavior has been modified. The default ...

• Modbus_Energy driver: Status of TCP/IP connection is not displayed

  Description For variables from the Modbus Energy driver, the status of the TCP/IP connection is not displayed in the Service Engine for suitable elements. This behavior has been changed. The connection status is now displayed. To benefit from this ...

• 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 ...