The OPCUA32 client driver causes long (~40s) delays during reload of the runtime and closing of the runtime under specific circumstances

• Related Articles

• FAQ: How can I create long term Wireshark sniffs?

  In this example it will be used OPC UA protocol as example to show how to use and configure a long term Wireshark captures. This is the best option when troubleshooting a connectivity/network issue occurring sporadically and it is not possible to ...

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

• 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 process gateway may close unexpectedly under specific circumstances when reloading the runtime

  Summary With an OPCUA process gateway with a larger number of variables cofigured and an OPCUA client connected to the OPCUA server having one or more subscriptions, the OPCUA server may close unexpectedly under specific timing conditions if the ...

• The OPCUA server in the process gateway stops updating variable values from the runtime under specific circumstances

  Summary When the runtime is reloaded following changes to the driver configuration, while the OPCUA server in the process gateway is running and a OPCUA client is connected, subcribing to value changes (Data Access) for variables (nodes) in the OPCUA ...