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.

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 zenon variable does not set the INVALID status bit for this variable in the runtime.

Solution

An issue has been addressed in the OPCUA client driver where the statuscode of read responses and publish responses was not correctly evaluated. Now the statuscode is correctly evaluated and the variable status is set to INVALID when the statuscode is not good.

Information

If a variable in the OPCUA server is switched to alternate value, the OPCUA server returns the statuscode "UncertainSubstituteValue" - 0x4091000. The OPCUA client driver sets the INVALID bit. There is NO error or warning entry written by the driver in the diagnosis server.

----------

If a variable in the OPCUA server is switched off, the OPCUA server returns the statuscode "BadSensorValue" - 0x808c0000. The OPCUA client driver sets the INVALID bit. There is NO error or warning entry written by the driver in the diagnosis server.

----------

If a variable in the OPCUA server is INVALID, the OPCUA server returns the statuscode "BadCommunicationError" - 0x80050000. The OPCUA client driver sets the INVALID bit. There is NO error or warning entry written by the driver in the diagnosis server.

----------

If the first value received has one of these statuscodes, the variable in zenon becomes INVALID. When the statuscode changes e.g. to good, the variable in zenon becomes SPONT again.

Issue Number: 30887
Fixed on Date: 20.11.2013
Versions: 7.10 0 BUILD 9356 | 7.11 0 BUILD 10238