zenPG ICCP as client: closes connection while received an InformationReport with segmented COTP sections

• Related Articles

• zenPG ICCP TASE.2: when remote ICCP-Server refuses association then the Client constantly attempts to reconnect.

  Summary zenon Process Gateway ICCP TASE.2: If remote ICCP-Server is available via TCP but rejects the socket connection, then the Client constantly attempts to reconnect (every ~50ms). When succesfully associated connection is broken then the zenPG ...

• zenPG ICCP-TASE.2 Server does not respond to READ request from Client

  Summary zenPG ICCP-TASE.2 Server does not always respond to READ request from client when domain specific addressing is configured. Description zenPG ICCP-TASE.2 Server does not always respond to READ request from client when domain specific ...

• zenPG ICCP responds with malformed frame when a remote ICCP-client sends MMS.Read request with flag specificationWithResult=true.

  Summary zenon Process Gateway ICCP-TASE.2 responds with malformed frame when a remote ICCP device requests a MMS.Read with flag specificationWithResult=true. This optional flag demands that the response will contain not only values but also names of ...

• While type mismatches zenon Process Gateway ICCP-TASE.2 as client on data set reception is corrupting value of not mismatched variables

  Summary zenon Process Gateway ICCP TASE.2 is mismatching received values - all (or some) of zenon variables linked in ICCP-client. It transfers to the Runtime values of another received data points or random. It happens only when by one (or more) ...

• AccessICCP: high cpu load on startup and high cpu load on connect of an ICCP client results in no connection being established

  Description When connecting via the ICCP/TASE.2 protocol, the connection will not be established if a high CPU load occurs when starting the Process Gateway or when connecting an ICCP client. This can happen due to the initialization of a large ...