Alarm deadband binding does not work

Ignition
1

Hello everyone,

we have an issue with the binding of the alarm deadband of tags.
In past, for every tag we used the alarm, we created a custom property for deadband. This property is used in the view, so the user is able to define the deadband.
Since one of the last updates, this does not work anymore. So I made some tests and I found out the following:
If I write a number in "Deadband" of the alarm configuration in the tag editor, the deadband will work as expected. But when I make a binding in "Deadband" to a custom property or another tag, it is like the deadband is zero.
We also use binding to a custom property for setpoint. Here everything works fine! I can change the setpoint via the custom property and the setpoint realy changes.
So it only seems to be an issue with "Deadband".

image
image933×601 56.3 KB

image
image936×553 50.5 KB

Is this an issue in the current versions of Ignition (we use 8.3.10) or has anything changed in one of the last versions?

Thanks a lot for helping!

2

Historically, alarm properties with bindings would only evaluate on alarm events or UDT parameter changes, not at other times. Some effort has been put into recent versions to evaluate at least the setpoints more aggressively, but other properties probably haven't been addressed.

The most reliable method is to NOT use bindings in tags other than with UDT parameters. Use scripted writes to change other tag properties.