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

• Related Articles

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

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

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

• The OPCUA client driver continues to send a publish request for a subscription even though the OPCUA server reports that the subscription is no longer valid.

  Summary The OPCUA client driver sends publish requests for a subscription even though the 3rd party OPCUA server reports that this subscription is no longer valid. (0x80280000, BadSubscriptionIdInvalid, teh subscription id is not valid) Variables of ...

• Checklist: Driver(s) cannot establish a reliable communication

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