OPCUA driver: incorrect value for ConnectionStates variable if connection failure

• Related Articles

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

• Writing a variable of the OPCUA client driver in the zenon logic via externally visible does not set the value correctly

  Summary With an OPCUA client driver in zenon and a variable that is set to "externally visible" writing this variable in a zenon logic program does not correctly send this value to the OPCUA server. Instead of the correct value, the value "0" may be ...

• Modbus Energy driver: Wrong value of status variable for connection state in case of 'secondary connection failed'

  Summary Modbus Energy driver: Wrong value of status variable for connection state if connection state is secondary connection failed Description Modbus Energy driver: Wrong value of status variable for connection state if connection state is ...

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