Re: [foxboro] Guidelines for issuing customer advisories

Corey,
        I understand and echo your frustration.  This loss of ability to
make changes to controllers from the HMI is, in my estimation, a pretty
significant issue that customers need to know about.  We struggled with
this problem for a long time before we were able to realize that our
problems always occurred when the, (MOTIF), Alarm Manager Window, was
open in conjunction with a Display Manager, (we don't use Foxview).  By
default the Alarm Manager couldn't be "Dismissed", and thus, the techs
couldn't recover from the lock-up.  Once we changed the AM's to be
quitable and told the techs if they lost use of their keyboard functions
on the DM to close the Alarm Manager Window, they at least had a way to
recover. =20
        I don't think the quick fix described below is the root of our
problem because our oajlog historian is always active and continues to
collect data from other WP's at the same time another one is
experiencing keyboard lockup.  BTW all of our operator actions are being
sent to the same historian sitewide. In addition, it wouldn't explain
why we immediately regain use of the keyboards ability to enter values
in the DM just by closing the Alarm Manager application.  I've had a CAR
in the system for many years and CSC wants to close it out now that they
have a fix for the oaj logging issue.  There are actually 3 QF's:

            QF1005887 for 6.3

            QF1005888 for 6.4

            QF1005305 for 6.5 and above.

        I'm not sure if the 6.3 QF could also be installed at my current
6.2.1 rev.  If so, I would install it to see if it makes a difference.
I'd be surprised if it solves our problem but anything is worth a try.
        Did you install the QF yet?  Did it solve your problem?

Thanks for any info.  Are other users still having problems with this?

Tom


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Monday, July 25, 2005 2:16 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Guidelines for issuing customer advisories

I'm curious: under what circumstances does Foxboro issue customer=20
advisories?

The reason I ask is that we were turned on the operator action journal
on=20
one system here the other day, and after that had two=20
loss-of-operator-control issues due to the Foxviews locking up.  It
turns=20
out there is a quick fix, QF1005305, for this, with the following=20
description:


"When the Operator Action Journal is enabled and is unable to=20
communicate to the historian and/or printer, messages to the=20
historian and/or printer will be queued up to the point where=20
resources are used up. This results in the calling application
to be locked out. In the case of Display Manager, all operator's=20
actions during the lockout period are queued and will be executed=20
when the lockout period ends. The lockout period may be in excess=20
of a minute. Reasons for the inability to communicate may include
but not limited to the historian being turned off, printer off-line,
invalid printer and/or historian name. "


Since this involves loss of (manual) control, I would think that this=20
would have been broadcast.  Even though OAJ is not on by default, I
would=20
imagine it to be a commonly-used feature.


I guess I'll have to start looking through the QFs periodically...


Corey Clingo
BASF Corp.

=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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=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

Other related posts: