Summary

• Projects where the setting for alarms "use reactivated time" is used, are not supported
• Alarms are now derived from a user defined AMLConditionType (ConditionType -> AcknowledgabeConditionType -> AlarmConditionType) where additional information from the zenon alarm list can be provided.
• Alarms are now project specific. Under each project folder node, an AML node (NodeClass Object) exists, supporting SubscribeToEvents and HistoryRead
• CEL entries are project specific. Under each project folder node, a CEL node (NodeClass Object) exists, supporting SubscribeToEvents and HistoryRead
• For each alarm variable, one alarm node resides under the AML node, instead of one node for each limit or reaction matrix condition (the option of having the limit text as the node name is no longer supported)
• The variable node under the AML node represents the last alarm state
• The variable node under the AML node allows creating an event notifier for a single variable
• Where clauses in the filter by the OPC UA client are currently not supported / ignored
• The CEL nodes has no sub nodes
• Only alarms for which varibles are configured are available through the OPC UA server
• It is possible to acknowledge alarms through an OPC UA client
• It is possible to enter a comment for alarms through an OPC UA client
• It is not possible to enter an alarm cause through an OPC UA client. Alarms that require an alarm cause shall not be used in the OPC UA server or shall not be acknowledged through the OPC UA client

Description

• Projects where the setting for alarms "use reactivated time" is used, are not supported
• Alarms are now derived from a user defined AMLConditionType (ConditionType -> AcknowledgabeConditionType -> AlarmConditionType) where additional information from the zenon alarm list can be provided.
• Alarms are now project specific. Under each project folder node, an AML node (NodeClass Object) exists, supporting SubscribeToEvents and HistoryRead
• CEL entries are project specific. Under each project folder node, a CEL node (NodeClass Object) exists, supporting SubscribeToEvents and HistoryRead
• For each alarm variable, one alarm node resides under the AML node, instead of one node for each limit or reaction matrix condition (the option of having the limit text as the node name is no longer supported)
• The variable node under the AML node represents the last alarm state
• The variable node under the AML node allows creating an event notifier for a single variable
• Where clauses in the filter by the OPC UA client are currently not supported / ignored
• The CEL nodes has no sub nodes
• Only alarms for which varibles are configured are available through the OPC UA server
• It is possible to acknowledge alarms through an OPC UA client
• It is possible to enter a comment for alarms through an OPC UA client
• It is not possible to enter an alarm cause through an OPC UA client. Alarms that require an alarm cause shall not be used in the OPC UA server or shall not be acknowledged through the OPC UA client