OPCUA32: Changes in the OPCUA32 client driver

• Related Articles

• The OPCUA client driver sets variables INVALID in the runtime after 20 seconds with specific settings for publishing interval and MaxKeepAliveCount and no value changes in the OPCUA server.

  Summary When the OPCUA client driver uses settings with a publishing interval and a MaxKeepAliveCount that result in a value of more than 20 seconds, and the OPCUA server sends no value changes (publish responses) for all the variables in the ...

• Variables of the OPCUA client driver do not have the the INVALID status set when the OPCUA server returns a value with a bad quality.

  Summary When a variable of the OPCUA client driver gets a bad status code, the zenon variable does not set the INVALID status bit for this variable in the runtime. Description When a variable of the OPCUA client driver gets a bad status code, the ...

• Fast value changes in the OPC UA server are not correctly sent to the runtime by the OPCUA32 client driver

  Summary When a value is changing rapidly in an OPC UA server, not all value changes may be available in the zenon runtime even though the OPCUA32 OPC UA client driver is correctly receiving the PublishResponses with the value changes. DescriptionWhen ...

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

• OPCUA32 client driver should adapt to specified behaviour for short connection losses to the OPCUA server

  Summary In version 1.02 of the OPCUA specification, reconnect behaviour for OPCUA clients for short connection losses has been further specified. The OPCUA32 client driver should be adapted and act according to this specification. Description In ...