Re: [foxboro] What causes System Alarms and What doesn't??
- From: "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 3 Jun 2002 13:33:37 -0400
Yes ..there is Tim......just goes to show you how many people have used
it....
The file name is too long for file2dsk usage.........once you extract the
zip...you will find:
file2dsk.exe
Smon_ech_NT.dsk
Smon_ech_251.dsk
QF990104B.txt
The 2 .dsk files one for NT and one for solaris 2.5.1 are too long.
Just rename them to something less than 7-8 characters...
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx@CORP On Behalf Of "Lowell, Tim:"
> <tlowell@xxxxxxxx>
> Sent: Monday, June 03, 2002 1:01 PM
> To: 'foxboro@xxxxxxxxxxxxx'
> Subject: Re: [foxboro] What causes System Alarms and What doesn't??
>
>
> I just tried to download and apply QF990104B, and it keeps saying that
> file2dsk cannot open the file. Is there something wrong with this QF
> file?
>
> Tim Lowell
> Control Systems Engineer
> Phillips Petroleum Company, Trainer Refinery
> Phone: 610-364-8362
> Fax: 610-364-8211
> tlowell@xxxxxxxx
>
>
> -----Original Message-----
> From: Hicks, Gaylon F. [SMTP:gfhicks@xxxxxxx]
> Sent: Monday, June 03, 2002 10:02 AM
> To: 'foxboro@xxxxxxxxxxxxx'
> Subject: Re: [foxboro] What causes System Alarms and What
> doesn't??
>
>
> Hi Gary,
>
> Are you using your horn.cfg file to drive an external annuciator on
> a system
> alarm? If so, and you are running you System Monitor on a 50 or 70
> series
> box, you can get Quick Fix
> QF990104B. This QF will make a CP going single a system alarm. The
> short
> description of this QF is
>
> "Changes were made to the System Monitor process, "smon_ech". If the
> file
> /usr/fox/sysmon/ftblink_red.cx is present and one side (or both
> sides) of
> Fault Tolerant station fails, the SYS bar will fail red"
>
> This should take care of your problem. We unfortunately can't do
> this. We
> are running our System Monitors on PWs (20 series), and Foxboro
> won't
> implement this QF for the 20 series (I've written a CAR and gotten
> the
> standard nicely worded "No" answer). What we do is have a script
> file that
> looks at recent system monitor messages every 6 hours, parses the
> messages
> for scary keywords (such as "Single", "Reboot", etc.), and emails
> myself and
> several other engineers if there are any hits. Give me a call or
> email off
> list if you want a copy of these scripts or any other information.
> This is
> something that will be well received (I hope) when INPO comes to
> visit.
>
> I completely agree that is pretty silly to have a printer
> out-of-paper
> alarm, but not a loss of fault-tolerance alarm.
>
> Thanks,
>
> Gaylon Hicks
> TVA - Browns Ferry
>
> -----Original Message-----
> From: Anderson, Gary T(Z02256) [mailto:GTANDERS@xxxxxxxx]
> Sent: Friday, May 31, 2002 1:50 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] What causes System Alarms and What doesn't??
>
>
>
> Hello All
>
> We were recently surprised to discover that upon a fault of a single
> CP in a
> fault-tolerant pair that our 6.1.2 IA System did not annunciate the
> problem
> and only the System button in Foxview started blinking green (as if
> an alarm
> had reset). I'm amazed that cable faults annunciate but the fault
> of a
> FT-CP pair doesn't.
>
> I'd appreciate some discussion on what other hardware failures do
> not
> annunciate and/or just blink, together with how you handle system
> alarms.
> I'm now aware that Foxboro has a solution to turn the binking green
> to
> blinking red for this situation. What else will surprise us?
>
> It appears that Foxboro has no plans to provide an upgrade for the
> SMDH or
> the ICC - these are just available on new systems. I wonder why
> they can't
> provide an upgrade.
>
> Thank you,
> Gary Anderson
> Arizona Public Service
>
>
>
>
>
>
> _______________________________________________________________________
> 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
>
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
_______________________________________________________________________
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:
