open62541: unable to receive events after update

Description

At the moment I work on a client that must connect to a server that is running on a robot form another team in our company. This team is writing the server in C++ with the open62541 library. And we are using the .Net library from OpcFoundation.NetStandard 1.4.371.96.

The robot team has updated their library to the newest version because they need it for the HMI of the robot system. After this update the events are not working anymore. Before the update everything was working. open62541 v1.2.2 (events are working) open62541 v1.3.6 (not working)

I need to figure out how I can change the client in such a way that I can receive the events again.

Is someone familiar with this issue? Can someone think of some possible hints that are use full? are there any changed made in the event system?

regards Patrick

Background Information / Reproduction Steps

UAExpert still receives the events from the server after the update.

If I create a plc (B&R) that fire opcua events than our software is still working.

our .Net client is not working anymore with the updated version of the open62541 library.

Checklist

Please provide the following information:

  • [ X] open62541 Version (release number or git tag):1.3.6
  • [ X] Other OPC UA SDKs used (client or server): client OpcFoundation.NetStandard 1.4.371.96. and UAexpert
  • [ X] Operating system: Linux and Windows
  • Logs (with UA_LOGLEVEL set as low as necessary) attached
  • Wireshark network dump attached
  • Self-contained code example attached
  • Critical issue

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 17 (7 by maintainers)

Most upvoted comments

Building with NS0 = full fix the error only in Prosys OPC UA Browser (not in Open62541 OPC UA Client)

Update: The error in Open62541 OPC UA Client apparently it’s mine.

I tried to simplify the source codes client_eventfilter.c and server_random_events.c and it seems that I made a mistake. Using the files without modifications the code just works. Now I can receive events.

In conclusion NS0 = full completely fixes the error for v1.3.6

@maucm92

Hi Mauro, We have the build option NS0 set to FULL. It was already set to this option. This is still not solve our issue. The issue that we are facing is only with events. With monitored items we do not have any issues.

regards Patrick