Hello,

Reading ENGLE documentation I understand that the ID management that is done internally to relate the standard data and the extension data (which are related) is not managed correctly, so that the way to recreate the IDs again is to unsubscribe and resubscribe once the connection is recovered.

Regards

Hello

Question 1:
The connection between the device and the KepServerEx is lost, the QuickOPC application is working correctly.

To understand my problem, I think it is important to know that the term “OPC Euromap” refers, in a general way, to the standards or technical recommendations that the European association of plastics and rubber machinery manufacturers (EUROMAP) has developed to exchange data between injection molding machines (or other plastics processing machines) and supervisory systems, MES/ERP or automation software.
That is, it has a part that defines variables in a “standard” way (e.g. machine states, process parameters, alarms, cycles, etc.). and then you can add variables as an extension.

Question 2:
Going back to question 2, when you retrieve the connection, you receive notification for the affected elements, reading back correctly the data of the variables that are “standard”, but it does not read the data that have been configured as an extension and that are part of the same subscription

In the ENGEL documentation a solution is given, but first I wanted to know if you have a solution to avoid having to do the management from my service:
For ENGEL machines, it must be taken into account that the node ID can change after the control unit is switched offion. When a client makes a new connection, it should be expected that the node IDs may have changed in the meantime.
Based on this, a good approach would be to traverse the OPC UA information model at the
beginning of a new client session and thus implicitly after switching offion the machine, and to redetermine the node IDs/browse paths. It is not advisable to use the node ID fixed coded.

Regards

Hello,

Yes, with EUROMAP 77/83 protocol, specifically for ENGEL machines.
With OPC DA I have not tested it, but I am working with UA.
Correct, it connects correctly and subscribes receiving data. And once subscribed, if the connection with the OPC is lost, when the connection is reestablished it reads data again, but not the data that are extension.

Regards

Work with OPC Labs 2023.1 and EUROMAP protocols for OPC-DA-UA, which have a specific implementation.

For EUROMAP each device has standard tags that work as normal tags and extension tags (that can be defined in the device + Kepware) that have a different behavior.

The problem has been identified that after losing the communication, the OPC Labs client is not able to reconnect with the extension tags, but it reconnects as with the normal tags.

Have you identified the problem? Do you already have a solution to this problem?

Thanks