You can use the DataHub program to convert data between the OPC UA Alarms and Conditions (A&C) and OPC Classic A&E protocols. A DataHub instance can connect to any number of A&C and/or A&E servers or clients, and keep a copy of all of their registered points in a single, universal data set. Each connected server sends or receives data value updates in its own protocol. The only requirement for this conversion is that you configure each participating client or server feature within the DataHub instance to share the same data domain (by default, OPCAE).
OPC A&E client and server configuration
OPC UA A&C client configuration
OPC UA A&C server confguration
There are a few differences between the two protocols. however. To support conversions, the following guidelines have been used:
A&C branched alarms are not supported by the DataHub program. A DataHub instance will track branched conditions internally but will not expose the branches to client applications. When a primary condition is acknowledged or confirmed, the DataHub instance will apply the same acknowledgement or confirmation to all the associated branched conditions.
A&C acknowledge and confirm are maintained in communication between A&C servers and clients. An acknowledgement from an A&E client will be sent as both an acknowledge and confirm to A&C servers and clients. Either an acknowledge or confirm from an A&C client will be transmitted as an acknowledgement to A&E servers and clients.
A&C alarm types such as Two-State, High-Low, Multi-State, etc. are not supported. The DataHub program converts all of these to generic acknowledgeable alarms.
A&E attributes are converted to A&C properties. A&C properties are selectively converted to A&E attributes.
A&E sub-conditions are ignored in A&C.