Re: [foxboro] Inhibit alarms; NOT
- From: David Johnson <drjohn@xxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 01 Sep 2006 15:48:29 -0500
Well,
I tried this
:C.B.INHALM.FFFF
and I wasn't able to inhibit the alarms. Seems backwards, try it and
let me know.
Thanks,
David
At 03:31 PM 9/1/2006, you wrote:
>David,
>
>Thank you, as this format is acceptable to the Control Configurator, but it
>does not secure the parameter like the INHIB example. I can still prohibit
>the individual block alarms from the select display. Why?
>
>Is my solution even a valid one?
>
>
>Joseph M. Riccardi, Inc.
>DCS Services - Industrial Process Control
>
>North-Central Office (OH, PA, MI, IN, WV Area)
>South-East Office (FL, GA, AL, SC, NC Area)
>
>Joe@xxxxxxxxxxxxx
>
>"To give real service you must add something that cannot be bought or
>measured with money; and that is sincerity and integrity." - Donald A. Adams
>
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
>Behalf Of David Johnson
>Sent: Friday, September 01, 2006 4:12 PM
>To: foxboro@xxxxxxxxxxxxx
>Subject: Re: [foxboro] Inhibit alarms; NOT
>
>Someone probably already answered this
>But
>C:B.INHALM.0000
>It is expecting a 4 digit hex mask
>
>I tried it and it seems to work.
>
>Regards
>David
>
>PS does it show that I am looking for more interesting work than drawing
>displays?
>
>
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
>Behalf Of Joseph M. Riccardi
>Sent: Friday, September 01, 2006 4:01 PM
>To: foxboro@xxxxxxxxxxxxx
>Subject: [foxboro] Inhibit alarms; NOT
>
>Folks,
>
>This plant needs to prevent the inhibiting of certain (critical) alarms from
>the Select Display by operators; period. No way, no one (from an
>operational display), never, ...
>
>I thought it would be easy just to secure the INHIB parameter with
>C:B.INHIB.0. That worked at the block level, but the operators soon
>discovered that they could select the individual block alarms
>(Select/Alarms/HIABS, HHABS, etc.) and Toggle them to INHIBITED.
>
>So to prevent this, I thought I could just secure the INHALM parameter in
>the same way as the INHIB parameter. Since the INHALM parameter is a packed
>boolean (range 0-FFFFFFFF), I thought C:B.INHALM.0 would to the trick, but
>the Control Configurator will not accept it.
>
>What format/syntax is the INHALM parameter expecting? 0 should be a valid
>value; no?
>
>Or any other suggestions?
>
>Thanks in advance for your help ...
>
>PS. Yes, we are on a path to evaluate all alarms, but I need your help in
>the short term ...
>
>Joseph M. Riccardi, Inc.
>DCS Services - Industrial Process Control
>
>North-Central Office (OH, PA, MI, IN, WV Area) South-East Office (FL, GA,
>AL, SC, NC Area) Joe@xxxxxxxxxxxxx
>
>"To give real service you must add something that cannot be bought or
>measured with money; and that is sincerity and integrity." - Donald A. Adams
>
>
>
>_______________________________________________________________________
>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: //www.freelists.org/list/foxboro
>to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
