Not Equal Alarm evaluation for each change

Ignition
1

I have a status integer tag that I need to trigger alarm for all the values except on healthy value (eg. 1), also I’m generating the Display Path dynamically according to value, using another expression string tag that convert the integer status to string. I’m able to achieve that using Not Equal, however, if the alarm is Active and the status changed to another unhealthy status, the alarm Display Path does not reevaluate and keeps showing the initial Display Path with initial status that originally triggered the alarm in the first trigger.

I know that the alarm properties bindings will not evaluate again unless the alarm is cleared then triggered again, however, I wonder if there’s something like “Any Change?” property in Above Setpoint mode, or any work around that can be implemented to achieve the requirement.

2

If you have values 1, 2, 3... would it work if instead of a single alarm triggering not equal to 1 you simply made an alarm for 2, alarm for 3, etc and each of them are only active when it equals their respective values. So transitioning from 2 to 3 would clear the 2 alarm and activate the 3 alarm. If that works for your application then that may be an easy solution.

3

Unfortunately, in my case I had to create a udt for the this kind of multi-stat values and make it as dynamic as possible with a parameter that maps each value to its description (status string)