What is best practice for disabling alarms?

Ignition
1

Hi :slight_smile:

I was planning on using the enable property for hiding the alarm based on some logic -but this seems not practical because the alarm appears in the alarmlist whenever it is re-enabled.
-What would be the best practice to disable an alarm based on some condition -other than using the .Enabled property?
-Or am I missing something?

Is there any workaround?
-Would it be possible to somehow detect the transition to .Enabled == True in order to automatically acknowledge the alarm? :thinking:

to reproduce:

  1. Make sure the alarm condition is false
  2. Observe how it is not listed in the alarmlist
  3. Disable the alarm
  4. Enable the alarm
  5. Observe how the alarm now appears as cleared, Unacknowledged
    image

I was investigating a little deeper and found some interesting deviation between the result after a tag restart and an alarm enable:
Tag restart: Alarm.IsAcked = True
Alarm enable: Alarm.IsAcked = False

Tag restart:
image

Alarm enable
image

Is this intentional? Or would it make sense to initiate a just-enabled-alarm to .IsAcked = True?

(Ignition 8.1.35)
j.

2

Hi Johannes,

We've submitted a bug ticket related to the alarm state moving from "Cleared, Acked" to "Cleared, Unacked" when an alarm is disabled, and then re-enabled on 8.1.33+. This should be moving back to "Cleared, Acked" assuming the alarm value doesn't change to an active state.

Thank you!

1 Like
3

Can you tell me when this is slated to be fixed?

4

image
image803×841 34.2 KB