Hmmm....sounds familiar :) So let's take a poll: who would like to see connectable alarm destination group (*GP) parameters? Corey Clingo BASF Corporation "Armour, Alan" <aarmour@xxxxxxxxxxxxx> Sent by: foxboro-bounce@xxxxxxxxxxxxx 12/19/2006 04:14 PM Please respond to foxboro@xxxxxxxxxxxxx To <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter Good one Michael, The annoying thing that I find is that as soon as you use INHIB or INHALM to configure logically driven alarm suppresion the block automatically appears as "inhibited" on the inhibited alarms report. What I have done is to use INHALM for logically supressing alarms, so that the operators can still overide the logical inhibits by using INHIB. I have walked away from the Foxboro inhibited alarms reports and used a script which looks for INHIB =3D1, and combined with another script which extracts alarm inhibiting actions from the operator action logs. This gives me a time stamp of when an alarm was operator inhibited. The other annoying thing is as part of my overall alarm philosopy I want to reduce alarm traffic to the operator during abnormal situations. There is important data which can be used in post event analysis which would be lost if a blanket inhibit of non immediately important alarms are suppressed, so I have a desire to divert many alarms to an "historian only" alarm group. This would be easy to do if the alarm group paramaters on any block which produces alarms was connectable, but....(hope Alex is looking!). At the moment what I am doing is run two blocks, one for the operators, and one for historian, and use block names which are as close as possible to each other. regards, Alan =20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Kessler Sent: Wednesday, 20 December 2006 12:22 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter > 2. You can send a HEX pattern to the AIN's INHALM parameter. Again=20 > this =3D parameter is connectable and settable, so any display or=20 > program can set =3D the hex pattern if there is no connection. For=20 > example a pattern 0x0003 =3D will inhibit HIGH and LOW alarms. > You can also toggle the HEX bits individually from block detail in Select. For example, to inhibit only the HI alarm, 1. Call up block detail for the AIN. 2. Click Alarms 3. From Select pick the HIABS parameter. 4. Click Toggle A black INHIBITED should appear indicating that the HEX bit to disable HIABS has been set. mk =20 =20 ______________________________________________________________________ _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave