Questions about Part A&C - ConditionClasses & Branches

[swamper123]

Hello everyone,

I am reading and trying to understand now for the 5th time the A&C and I am going nuts. (┛◉Д◉)┛彡┻━┻

While the Part with the Alarms seems to be understandable what everythin shall do, I am still not understanding some Condition stuff.

What I had understand of A&C so far (please correct me if I'm wrong):

• They inherit from BaseEvent
• From there the SourceNode property identifies the ConditionSource and if there is no Node in the addressspace, it is NULL
• a Condition shall have a unique ID, independent if they are exposed (via Instance) or not (via References) in the Addresspace (HOW they can be made unique is not mentioned and we can only use the NodeId in case of instances)
• A (basic) Condition has two states: Enabled or Disabled
• Switching between those states causes Condition Events (and only in Enable state, subsequent Events are generated)
• A Subtype of Condition can be Ack Conditions, which contain a "Statemachine" in an enabled State with either Ack or Ack&Confirm substates.
• the NodeId of a Condition Instance shall be used as ConditionID...
• (some smaller stuff like Quality I don't want to list now)

What I still don't understand is:

• What are ConditionClasses and how are/shall their IDs exposed? I know that there are multiple Subclasses of ConditionClass for special domains (like Training, Maintainance, Safety...). How are they managed? Is there a List like for Namespaces in the server or how? How shall these IDs look like? Where and how shall that work?
• Same with the SubClass stuff.
• How shall that branching work? From the example, provided by AnnexB1.3 a Branch is created, if an Alarm ends, before it is Ack. So now in the Branch the Alarm is a different one than in Current State which can be Ack&Confirmed? And Branches just disapear, if they are Ack&Confirmed?
• How does the Identification works for Non-Instance Conditions? When I understand the Specs right, the ID can be requested by a SimpleAttributeOperand in context with an EventFilter...where typeId is the NodeId of the conditiontype and attributeID the NodeId where it belongs?

Well this may not even be all I don't/know, but I guess this is enough for one Discussion at the moment. I am glad for every enlightening to that topic. How this stuff can be transfered into Pythoncode then, is another topic.