• Not Answered

History on horn silence

Is there a way to go back on an operator station and see when the horn was silenced by a key press? I can go on the historian and see when the alarm was triggered and when it was acknowledge but I was looking to see when the horn was silenced in our case the up arrow key press.

3 Replies

  • Hi,

    If silencing the horn using Key Press uses VB script, then you could add to write to a parameter then historise it?. just an idea
  • The Horn Parameter is a parameter that you can reference from a control module (External Reference). You can read the HORN value from a module, assigned to possible the Application station.
    I forget the values, but when the horn is off, its value is 0. The value reflects the priority of the alarm that set the horn(but changes if a higher priority module comes it before it is silenced), but if the value is Active/Unack, Active/Ackn, or Inactive/Unacknowleded, I think the value goes 15, 115 or -15 for the Critical priority, or something like that. It goes to 0 when the horn is silenced.

    We used this to create an external horn DO output, changing the Horn pattern based on the alarm priority. When you see the Horn go to 0, you can create a Log Event to log in the Event Chronicle. The event description would include the name of the Workstation. such "Workstation X Horn Acknowledged" were X is the name of the workstation.

    Please excuse any inaccuracies in the HORN value as it's been a few years since I looked at this in detail.

    Andre Dicaire

  • In reply to GeloCortez:

    Although alarms are acknowledged form various places in DeltaV Operate, the Horn is acknowledged from the alarm Banner script. If you add a parameter to this that resides in a module, and perform an FRS Write command, the DetlaV system will automatically record a parameter write even in the Event Chronicle, documenting the Workstation, and the user. The Text Description will be "New Value = ___". You could make this a text parameter and write something like "Horn Silenced priority X", or similar so that you could record the priority silenced. You would then be able sort on the module/HORN parameter and see all the Operator actions to silence the horn.

    If you read the Horn value, you can customize the text message, but you don't see the User information.

    Andre Dicaire