[BUG-13866] Expression isAlarmActive : Invalid relative tag path

[mazeyrat]

Hi @James.Lorenz,
I've upgraded to the last 8.0.6 nightly build.
The issue with isAlarmActive is ok...But I have another issue with this expression tag.

I think the issue occur for the result of isAlarmActive when there are disabled alarms (or perhaps all disabled) in the path of isAlarmActive("path")

I confirm this bug is too in 7.9.12

perhaps the same bug as:

isAlarmActiveFiltered throws REFERENCE_NOT_FOUND when alarms not enabled

Howdy, I’m trying to implement a client-configurable alarming system within Ignition 7.9.10. I have configurable setpoints and ‘enable’ tags that the alarmed tag references in its configuration. I also have some expression tags that attempt to summarize the current alarm information for a given tag. The issue I’ve found is that the isAlarmsActiveFiltered expression throws a REFERENCE_NOT_FOUND exception if there are no alarms enabled on the given tag. I can see why this would be the default …

Example:

I have one alarm for these expression tag value:
[default]TVG/SYS/ESX01/00001/TA/DEF_CPU_USAGE
Value expression:

isAlarmActive("[.]../TM/CPU_USAGE")

Enabled properties of the alarm is bind to an expression

!({[.]../TC/INHIBER_ALARMES} || {[.]../TS/COND_INHIB_ALARMES})

If the enable expression return True, the value is OK.

If the enable expression return False, the value go to Bad_NotFound !

I use the same pattern to disable alarm based on other expression tag with no problem.

I think the issue occur for the result of isAlarmActive when there are disabled alarms (or perhaps all disabled) in the path of isAlarmActive("path")