OPCUA32: The driver calls createmonitoreditem every 100ms when a monitoreditem could not be created

• Related Articles

• OPC UA client driver cyclically sends a createmonitoreditem request with node ID "0" for variables that do not exist on the server

  Summary When the browsename for variable of the OPCUA client driver is incorrect or does not match an item in the OPCUA server, the TranslateBrowseNameToNodeId request of the OPCUA client driver in the runtime results in an invalid NodeId "0" ...

• The OPCUA32 client driver may close unexpectedly under specific circumstances when CreateMonitoredItem fails due to an invalid persistent NodeId.

  Summary When the option to use persistent NodeIds is activated in the OPCUA32 client driver and a variable is requested by the runtime from the driver, the OPCUA32 client driver sends a CreateMonitoredItemRequest to the OPCUA server. When the NodeId ...

• The OPCUA client driver stops sending service requests for a subscription when no variables are needed in the runtime and attempts to reuse the no longer existing subscription when a variable is needed again.

  Summary When momentarily no variables are used in the runtime from a connection in the OPCUA client driver, the OPCUA client driver no longer sends service requests for the subscribtion that was previously created for these variables. The OPCUA ...

• Checklist: Communication to TwinCat via BeckhoffNG driver

  Time estimate: 30 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. TwinCAT ADS communication library ...

• The CPU usage of the OPCUA client driver in the runtime gradually increases over time

  Summary The CPU usage of the OPCUA client driver in the runtime gradually increases over time. When using multiple OPCUA client drivers, the system may eventually stop responding when all CPU cores are running on full load. Description The CPU usage ...