Re: [foxboro] Equipment Power Status in SMDH
- From: "Kevin Fitzgerrell" <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Sat, 15 Dec 2007 18:34:37 +0900
Tom,
Turning system monitor information into useful alerts has always been
a weak point in the IA system. So far I've found exactly 2 ways of
doing what you request.
1) For events that generate a system monitor message, you can collect
those messages, either directly by using a logging application at the
printer port or periodically by collecting system monitor messages
from the historian or /opt/fox/sysmgm/sysmon/smon_log files. Assuming
you know what messages you want to watch for, you can parse these
messages for the ones you're interested in and write that back as an
object manager variable.
2) Another option is to use the remv/remd utilities from foxwatch to
periodically collect all system monitor data and then parse the
results for the information you are interested in. I run these weekly
and generate a report (see below) based on the particular data from
the system monitor report I'm interested in.
Regards,
Kevin FitzGerrell
Weekly System Monitor status report.
(This is email and it's contents are generated automatically)
GW AB205C is failed to single
GW AB206C is failed to single
LAN CB0801 is failed to single
CM FW101D is Off Line
GW GW3AB9 is Off Line
CM FW101D has alarms inhibited
GW AB0101 has alarms inhibited
GW AB0103 has alarms inhibited
CM CM101D has failed attached device(s)
GW AB0103 has failed attached device(s)
GW AB207C has failed attached device(s)
GW AB0101 AB0101 device is marked as failed
GW AB0103 AB0103 device is marked as failed
GW AB207C AB207C device is marked as failed
GW AB207C PLCAB1 device is marked as failed
CP CP307F 5F0308 device is not communicating
CP CP101D 1D0202 device showed LAST CABLE ACCESS : A Fail / B Okay
CP CP101D 1D0203 device showed LAST CABLE ACCESS : A Fail / B Okay
CP CP101D 1D0209 device showed LAST CABLE ACCESS : A Fail / B Okay
AW AW001B TT99 device has alarms inhibited
CM CM0703 LP12 device has alarms inhibited
CM CM0703 LP13 device has alarms inhibited
CM CM0703 LP14 device has alarms inhibited
AW AW001B TT99 device is Off Line
CM CM0703 LP12 device is Off Line
CM CM0703 LP13 device is Off Line
On Dec 15, 2007 12:36 PM, Tom VandeWater <tjvandew@xxxxxxxxx> wrote:
> Hello to All,
> Just finished two weeks in Fox Mass working my new job, a Bailey to Fox
> IA MESH migration for Tesoro Hawaii. Hawaii is a lot nicer than Foxboro
> this time of year, as a matter of fact, any time of the year. We had 10
> inches of snow on Thursday in FoxMass.
> My question is:
> "Does anyone out there know how to retrieve power status information from
> System Monitor and transform it into a Global Object Manager Variable?"
> As many of you probably know, the System Monitor displays Primary and
> Secondary Power status for 200 series FBM's as well as for ZCP/FCP
> controllers. I don't think this was available on 100 Series FBM's. When
> dual power sources are applied SysMon displays OK for Primary and Secondary
> power for each module. If a source is lost/removed the appropriate source
> shows as failed in SMDH. Loss of only one source doesn't generate a System
> Alarm. It only updates the text displayed status. Any help or information
> about how to retrieve the power status information and transform it into
> something useful is greatly appreciated.
> Cheers,
> Tom VandeWater
> Control Conversions Inc.
> Tesoro, HI
>
>
>
> _______________________________________________________________________
> 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
>
>
_______________________________________________________________________
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
- Follow-Ups:
- [foxboro] FBI10E giving Fieldbus B error
- From: Kashif Ijaz
- [foxboro] COMM 10 not rebooting
- From: Kashif Ijaz
- [foxboro] COMM 10 not rebooting
- From: Kashif Ijaz
- Re: [foxboro] Equipment Power Status in SMDH
- From: Ghamdi, Bander M
- References:
- [foxboro] Equipment Power Status in SMDH
- From: Tom VandeWater
Other related posts:
- » Re: [foxboro] Equipment Power Status in SMDH
- » Re: [foxboro] Equipment Power Status in SMDH
- » Re: [foxboro] Equipment Power Status in SMDH
- [foxboro] FBI10E giving Fieldbus B error
- From: Kashif Ijaz
- [foxboro] COMM 10 not rebooting
- From: Kashif Ijaz
- [foxboro] COMM 10 not rebooting
- From: Kashif Ijaz
- Re: [foxboro] Equipment Power Status in SMDH
- From: Ghamdi, Bander M
- [foxboro] Equipment Power Status in SMDH
- From: Tom VandeWater