The OPCUA client driver does not properly evaluate a timeout response from the OPCUA server and logs an error regarding a malformed telegram.

• Related Articles

• Checklist: OPCDA Server

  Time estimate: 20 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. Do NOT use DCOM in combination ...

• The OPCUA client driver should increase the grace period to establish if a server is no longer responding

  Summary If under specific circumstances an OPCUA server is not capable of sending a publish response with a keep alive message in time the OPCUA client may assume that the OPCUA server is no longer available. A grace period is applied of 1000ms. ...

• OPCUA Client Driver: Extension Objects "Switching Time" in "Schedule" do not work properly

  Description In the OPCUA client driver, setting a value other than 0 for "Switching Time" in "Schedule" leads to an error. All variables become invalid. These variables can be set to 0 again with another OPCUA client. They are then spontaneous again. ...

• Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

  Time estimate: 45 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] ...

• The OPCUA client driver may cause the runtime to stop responding under specific circumstances

  Summary The OPCUA client driver uses the due time for publish responses (keepalive) to check if the OPCUA server is still responding. Normally if the connection to the OPCUA server is lost, the connection is closed at the TCP level. If however no ...