As you may have seen in my previous posts, I am implementing two ‘analog’ alarms for a single digital tag, one for 0 and one for 1.
Now, if the tag has a value of 1, it is in the alarm state defined by the alert entry in sqlt_as with high=1 and low=1 (both inclusive). When I run the query to update the configuration for this tag (UPDATE sqlt_core SET configchange = CURRENT_TIMESTAMP where id = 36), I see that a new alarm is generated, but sometimes two alarms are generated, and this isn’t the behavior I am looking for since this will send out two notifications to anyone in the distribution list. I have verified this using the MySQL query analyzer to update the sqlt_core configchange field and the problem still exists.
Is there any way to prevent this from happening?