Alarm Journal / Acknowledge Issues

I have some remote alarm journals setup to share to a Main Gateway. Running into two issues.

  1. I cannot Shelve an alarm on the main alarm journal. The edge device (remote) journal can shelve their alarms. How do I allow this to work?

  2. The other issue I am having is, after acknowledging an alarm, it is good until a value change occurs. Which retriggers the alarm. It is becoming a nuisance. I have played with the dead band settings. I want to be able to acknowledge and not look at the alarm again if it is over or under the alarm setpoint. The acknowledged alarm should stay acknowledged.

Service Security is most likely what you are running into for the 1st point:

For this Gateway to shelve alarms on others, this must be set on the remote Gateway.

For the 2nd point, I am going to state how alarm behavior is expected to function:

  • A new live alarm creates an Active, Unacked event
  • Once it exists, a live alarm event can be either Cleared and/or Acknowledged
  • Once an Alarm is Cleared (no longer active), that live alarm is now completed, and the system will keep it in memory based on a few criteria
  • The next alarm event will generate when the alarm triggers

So if a Below Setpoint alarm triggers, and then becomes cleared, then as soon as it triggers again a new active alarm event is generated. If the acknowledgment was on a prior alarm event. The alarm event you acknowledged is still acked, but there is now a new event.

Changing the clear delay is a possible solution.

1 Like

So for some reason, the Allow Shelving was not checked on my edge device. Must have missed that. :man_facepalming:

Thanks!

1 Like