I was going through the specifications & OPC-UA Portal Reporting Tool for A&E. There are many things which a client should have; to support this feature. I found some mandatory & optional services on Portal as well.
But, since there is no test case defined for A&E & have 1-2 lines of description for each services e.g., Monitor Client Events & Monitor Client Event Filter from Event Subscriber Client Facet. I was facing difficulties in understanding the actual expectation from an OPC client for A&E feature.
Could you please help me in understanding below thing in context of Events & A&C Facets:
- What all things I should follow ?
- What is expected by a client at minimal ?
- Is it required to have all types of events available in OPC Specifications, a client should allow to subscribe ?
- There was one more point which says, an OPC client should be able subscribe to base events. Does this means a client should be able to capture Status, Severity, EventId, EventType, Time & Message in addition to the custom event information ? What does base event means here ?
One more question I've, when we look at this from Profile perspective, in which profile Event & Alarm&Condition Facets belongs to ?
I was somewhat confused by the original post, A&E is a classic concept, In OPC UA it is Alarms and Conditions. Are you asking about the OPC Classic A&E client? Are you asking about the mapping of OPC Classic (A&E) to OPC UA (A&C) and testing for this mapping? Or are you looking for information about an OPC UA Alarm & Condition Client?
[OPC Classic is fairly old DCOM based technology, OPC UA is the current service oriented architecture]