-
Notifications
You must be signed in to change notification settings - Fork 1k
[CTT] Support A & C #3728
Copy link
Copy link
Labels
complianceAn issue was found which is not compliant with the OPC UA specification.An issue was found which is not compliant with the OPC UA specification.enhancementAPI or feature enhancementAPI or feature enhancement
Metadata
Metadata
Assignees
Labels
complianceAn issue was found which is not compliant with the OPC UA specification.An issue was found which is not compliant with the OPC UA specification.enhancementAPI or feature enhancementAPI or feature enhancement
Currently only ExclusiveLevelAlarmType Input Nodes, NonExclusiveLevelAlarmType Input Nodes and OffNormalAlarmType Input Nodes contain the necessary instances to monitor the corresponding alarms since they are the only available alarm instance types in the address space under the Objects->Alarms Object.
It would be nice to add alarm instances corresponding to AlarmConditionType, DiscrepancyAlarmType, LimitAlarmType , ExclusiveLimitAlarmType, ExclusiveDeviationAlarmType, setpoint Node to monitor for ExclusiveDeviationAlarmType used as reference value, ExclusiveRateOfChangeAlarmType, NonExclusiveLimitAlarmType, NonExclusiveDeviationAlarmType, setpoint Node to monitor for NonExclusiveDeviationAlarmType used as reference value, NonExclusiveRateOfChangeAlarmType, DiscreteAlarmType and SystemOffNormalAlarmType.
These new instances should behave exactly as the existing instances in the sense that they should be triggered by the same --ctt flag passed to the ConsoleReferenceServer.