Alarm areas: wrong value of status variables of linked Alarm Classes when number of alarms exceeds the size of ring buffer
Summary
If the number of alarms exceeds the size of the ring buffer, the status variables of linked Classes in Alarm areas are calculated wrong.
Description
If the number of alarms exceeds the size of the ring buffer, the status variables of linked Classes in Alarm areas are calculated wrong.
Solution
Now number of unacknowledged alarms is decremented when an alarm is removed from ring buffer.
Information
Issue Number: 29732
Fixed on Date: 25.6.2014
Versions: 7.11 0 BUILD 13121
Related Articles
FAQ: How can I monitor and react on the communication status of my devices with zenon?
Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...
Under specific circumstances the XML-import of alarm areas result in a wrong class linking in the editor.
Summary It may happen that the XML-import of alarm areas between two sub projects result in a wrong alarm class linking in the editor, so that the alarm areas class linking in the target sub project are shifted to the next alarm class, previously ...
Runtime closes unexpectedly while printing the AML with an overstepped ring buffer limit.
Summary Runtime is not able to handle printing the alarm message list when the number of alarms has overstepped the size of the ring buffer. Issue only occurs when the ring buffer size is overstepped and the ring buffer settings are set to either ...
Distributed Engineering. Alarm Areas linked to an Equipment Model get lost after synchronization.
Summary At the zenon Editor (x86 & x64) with a multiuser global and standard project, alarm areas in the standard are lost after synchronization if they are linked to a global equipment group. Description At the zenon Editor (x86 & x64) with a ...
Numerical prefixes of Alarm groups/classes/areas are not correctly sorted in AML filter
Summary Alarm groups/classes/areas in lists in AML filter are sorted as text. But as they starts with the number (property "No.") the order is not correct: 1, 10, 11,..19, 2, 20, 3 etc. When converted to string the numbers 1..9 should have leading ...