Multiple Limit Values in AML but Equipment Aggregate Alarm Only Driven By One?
We have an end user that I think wants something that is impossible, but I am wanting to see if anyone has a way to do this.
In their system, they have a series of binary indicators that they want to have trigger AML messages on both assertion and deassertion for acknowledgement, but that are only really in an Alarm in one state. They also want these points to each have unique Limit Value Text (which I believe rules out Reaction Matrices). These behaviors together are fine; you just have two limit values and set both to log in AML.
The additional request which I believe makes this impossible is that they also want aggregate alarms for areas (such as by tagging points to Equipment Modeling) which are based on only the "real" alarm state. As far as I can tell, since these points are in "alarm" in both states, then that means that the aggregate alarm for an equipment will always be active. You cannot separate the Limit Value with the "In Alarm Message List" behavior from the Limit Value behavior which drives the Equipment since the Equipment is attached to the entire variable.
Alarm Groups do not have any aggregate alarm behaviors as far as I can tell.
We are already using Alarm Classes on all of our limit values to set alarm priorities. As such, I don't think that I can use the Alarm Area functionality since that links to Alarm Classes, and each Limit Value can only have a single Alarm Class.
Does anyone have ideas for this sort of behavior? Or are we going to have to choose between "generate AML instances in both states" and "have aggregate alarms based on real alarm state"?
Disclaimer
This document governs the use of our Community Forum. By registering and using the platform, you accept these conditions.
The COPA-DATA Community Forum serves to encourage the exchange of information and experience about the zenon software between forum users respectively zenon users.
Please mind that any published information on the Community Forum is the subjective opinion and view based on the experience and the level of knowledge of the author. COPA-DATA does not overtake any responsibility for the content and the accuracy of the shared information.
Users of the Community Forum are encouraged to share only well-founded experiences and to point out any risks associated with the implementation of proposed solutions to problems. COPA-DATA at its absolute discretion, reserves the right to moderate the forum. In this connection COPA-DATA may remove any information containing false facts, potentially dangerous solutions, bad language or content that may insult, degrade or discriminate others. COPA-DATA may block a non-complying user from forum access if the user violated this provision.
COPA-DATA reserves the right to change this document from time to time at own discretion.
Ing. Punzenberger COPA-DATA GmbH
Karolingerstraße 7b · 5020 Salzburg · Austria
www.copadata.com