S7TCP32: wrong behavior of ConnectionStates variable

• Related Articles

• inconsistant behavior of warnings for unused tags in a phase´s condition´s formula

  Summary Phases in batch Control offer several conditions to configure the behavior of the phase. For every condition you have to create a formula which uses the phase´s tags. The dialog allows to add multiple tags and doesn´t check if they are used ...

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

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

• S7TCP32 driver stops if you read DATE AND TIME variable with wrong time values

  Summary The S7TCP32 driver stops if it reads a DATE AND TIME variable with a wrong time value. That means one of the following Byte values is out of range: Byte 3 - hour - crash with value 30 or higher Byte 4 - minute - crash with a value 90 or ...