OPCUA32: driver crashes silently on closing the runtime under specific circumstances

• Related Articles

• 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 causes long (~40s) delays during reload of the runtime and closing of the runtime under specific circumstances

  Summary When the runtime running a a project using the OPC UA client driver in combination with a specific OPC UA server is closed, the OPCUA32 client driver delays the close of the runtime. With the specific OPC UA server there may also be a long ...

• OPCUA32: driver crashes on driver start command under specific circumstances

  Summary The OPCUA32 driver closes unexpectedly under specific timing conditions when the driver is stopped and started using driver command functions. Description The OPCUA32 driver closes unexpectedly under specific timing conditions when the driver ...

• OPC UA driver crashes during Runtime reloading

  Summary OPC UA driver crashes during Runtime reloading Description The OPCUA32 driver may produce an unhandled exception while reloading the Runtime after changing settings in the driver configuration 'Operation Limits' tab. Issue Number: 218438 ...

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