OPCUA32 Driver crash / advising variables

• Related Articles

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

• Variables from the OPCUA client driver that have a bad statuscode on startup will never get a value.

  Summary If the value of a OPC UA variable has a bad status code when OPCUA client driver starts, the variable will never get a valid value in the runtime, even when variable gets a good statuscode in the OPCUA server. Description If the value of a ...

• OPCUA driver crashes when reading variables in background

  Summary The OPC UA driver is terminated unexpectedly. This error has been fixed. Description The OPC UA driver is terminated unexpectedly when reading the PLC variables in the Engineering Studio via the command “Read PLC variables in background”. The ...

• When a variable in the OPCUA server has a bad quality (no value), the OPCUA client driver does not offer this variable in the list of variables after online import in the editor.

  Summary After online import in the editor for the OPCUA client driver, the list of variables does not contain variables that have bad quality and no value. When the variable value has a valid, the online import does correctly offer the variable in ...

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