Unified Automation Forum

Hello,

we are evaluating the UAgateway to translate OPC UA Alarm&Conditions into OPC Alarm and Events.
We are experiencing this issue: we configured properly all the stuffs according to the manual, and we are able to browse all the event categories with many different free OPC A&E clients, performing subscriptions with no errors. The problem we have is the alarm and event data data collection. The only OPC A&C client which properly receive the alarm and event strings is th Matrikon OPC Explorer.
All the other OPC A&E clients do the connection and Subscription with success, but after that no update is received from the UA Server /UA Gateway even if we see new string in parallel coming to the Matrikon Explorer.

We already checked the event categories and the attributes configured client side, the user, the firewall settings (totally disabled) etc...

The OPC DA part works properly with all the OPC DA clients

One more information: if we disconnect the UA data source from the UA configuration panel we get the string in all the clients, but nothing from the UA data-source.

Any suggestions ?
Thank you
Ernesto

Hello,

if the Matrikon can show the A&E message, there can be only 2 reasons why the other clients can not show the message:
1) the other AE Clients have "filters" set and accidently filter out the messages (Matrikon uses "no filters")
2) the other AE Clienst are blocking the event because of their DCOM settings (Matrikon uses "open" DCOM settings)

Note: check the DCOM settings and user credentials of the A&E Client process and compare to those of the Matrikon.

Thank you for your reply.

Both UA Gateway and A&E clients are on the same server.
We checked the user credentials and DCOM settings
We checked the configuration of category filtering enabling all but... no way to have it working.

We also enabled the log tracing, we can see the connection but no errors appear.

Any other suggestion?

Thank you a lot
Ernesto

Hello,

from your description it seems to be 1) the filtering. Our recommendation would be to leave the filter "empty" in order to "get everything". The e.g. Softing COM Client is doing that, and works fine. Other free clients read out all categories (which could be quite a lot) and create a huge filter (containing every single one of them). The effect is same: "get everything", however the extreme large filter may create issues with the underlying server.