Re: [foxboro] alarm acknowledge question
- From: Mike_Adams@xxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 16 Oct 2007 11:35:38 -0400
> Yup, but what I meant was that besides those 3-4 blocks in alarm
> (showing a priority in FoxSelect) there might be blocks which are no
> longer in alarm but haven't been acklowledged yet (i.e., block was in
> alarm, alarm went away but no one acknowledged).
Ah, now I see what you mean. There could definitely be blocks that
returned from alarm but are still unacked. But wouldn't ACKing at the
compound detail display take care of that situation? Per the block book
B0193AX rev.N on a compound's UNACK bit, page 457:
"The UNACK alarm acknowledge output parameter allows you to propagate alarm
acknowledge actions to all blocks in a compound."
Mike Adams
Mitsubishi Polyester Film, LLC
Greer SC, USA
864-879-5231
_______________________________________________________________________
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:
