An alarm that has previously occurred and whose activation limit has been altered was once again displayed by E3Alarm, with a new date and below the other alarms. Can this behavior be avoided?
Solution:
Alarms in E3Alarm are sorted out by DateTime (Input) only, but you can use up to four sort fields.
The alarm’s limit has changed since the last read, but the tag’s timestamp hasn’t; therefore, the alarm was displayed in E3Alarm at the bottom of the list, as seen in the previous image.
In addition to the alarm’s limit changes, an active alarm condition can also be generated if the area is enabled or disabled.
The solution for this case would be to use three sort fields: first, Active Condition (descending); second, Acknowledged (ascending); and finally DateTime (Input) (descending), as seen in the figure below:
Therefore, any active, unacknowledged alarm is always at the top of the list, while inactive alarms will be at the bottom even when unacknowledged, as seen below:
