Re: [foxboro] Annunciator Keyboard Slow Response
- From: "DUNHAM, KENNETH J" <kdunham@xxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 18 Oct 2011 16:09:00 +0000
Thanks David, excellent suggestion. There are so many alarm acks, it's
definitely a possibility.
And yes, we have dried out and the river is back below flood stage. The site
was covered with 1 to 4 feet of water for almost 3 months.
On the plus side, the rice crop did quite well.
Ken
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of David R. Johnson
Sent: Monday, October 17, 2011 9:12 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Annunciator Keyboard Slow Response
Hey Ken.
You guys dried out yet?
Usually a slow response is due to the annunciator trying to do an almack on a
non-existant, or non alarming block. It times out. If you have a display and
are trying to do a page ack, you probably have configuration issues there. If
the response is slow, that is what I would look for first.
Regards,
David
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of DUNHAM, KENNETH J
Sent: Monday, October 17, 2011 11:33 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Annunciator Keyboard Slow Response
List,
We are installing an annunciator keyboard for the first time and I have a
question related to the slow response time on opening a configured display.
On a few of the buttons, we have configured numerous STATE and REALM alarms to
light the LED and acknowledge the alarm. In one particular case, it takes
almost 6 minutes to open the designated display. On the button where only two
alarms are configured, it takes about 6 seconds.
Is there any way to speed this up or is this just a limitation based on the
running scripts? Seems kind of useless this way.
Any advice would be appreciated.
Ken Dunham
DCS System Engineer
Fort Calhoun Station
----------------------------------------------------------------------
This e-mail contains Omaha Public Power District's confidential and proprietary
information and is for use only by the intended recipient.
Unless explicitly stated otherwise, this e-mail is not a contract offer,
amendment, or acceptance. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.
_______________________________________________________________________
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
_______________________________________________________________________
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:
