Perspective - Ignition 8.1.18
I’ve noticed the act of creating or modifying certain alarms has caused them to trigger despite never being in alarm condition. After editing an alarm, a cleared and acknowledged state alarm will generate. The alarm was never in an active or unacknowledged state before this.
The alarm is based on a derived tag that uses a case structure in the read expression:
The alarm uses the “On Condition” mode with a string comparison in the “Is Active” expression binding:
The alarm operates as expected after the first erroneous alarm is generated.
Is this false alarm expected behavior? Is this a known bug? Do the expression bindings somehow leave room for a momentary true command?
Thanks for any assistance!