Re: [foxboro] Alarm Clearing
- From: Terry Doucet <doucet427@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 16 Dec 2011 12:54:45 -0500
Corey,
If INHOPT = 1 then the alarm is supposed to be cleared when INHIB is set true.
Have not tried this.
Terry
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Alarm Clearing
> From: corey.clingo@xxxxxxxx
> Date: Fri, 16 Dec 2011 11:27:30 -0600
>
> What parameter would that be? I'm interpreting Chris's email to say that
> the alarms he wants to remove (from the Alarm Manager, I presume) are
> still active, so acknowledging them by itself will not remove them from
> the AM. Wouldn't he have to do something with the AM as well, if it's
> possible at all?
>
> As a side note, I'm not putting much configuration effort into eliminating
> so-called "stale" alarms because I/A does allow removing them from the AM,
> unlike some other systems. I may rethink that from a HMI standpoint if it
> becomes an issue, though.
>
>
> Corey
>
>
>
> From:
> Terry Doucet <doucet427@xxxxxxxxxxx>
> To:
> <foxboro@xxxxxxxxxxxxx>
> Date:
> 12/16/2011 11:09 AM
> Subject:
> Re: [foxboro] Alarm Clearing
> Sent by:
> foxboro-bounce@xxxxxxxxxxxxx
>
>
>
> Chris,
>
> In a word, yes; it can be done. But in anther word, carefully - because an
> error can cost you big time depending on the risk assessment of your
> process.
> You could create something as simple as an ascii list of compounds and
> blocks to be cleared, then write a script or program that reads the C:B
> and then slowly (1 write per second) writes to the parameter to clear the
> alarm. You could run the script when the shutdown is happening (likely a
> manual pick by your Operator from a screen). You can maintain the ascii
> list with one C:B per line and add or delete C:B as required. If your
> instrument people delete a block, you need to be informed so that you can
> delete the line in the ascii file.
> Terry
>
>
>
>
>
>
> _______________________________________________________________________
> 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:
