Re: [foxboro] CAD not updating
- From: "Gunter, Matt" <Matt.Gunter@xxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 3 Jun 2013 16:43:02 +0000
Thanks Russ, but this has not corrected the problem.
Checking the cs_dm.current file indicates "TYPE: GRAPHICS STATUS: OK PR
NONE" for the boxes whose CAD is not updating, which I assume means that the
Device Monitor recognizes them.
I tried recreating the AM files and distributing them accompanied by a reboot,
but still no change. I wondered if the problem might be an ast issue, but
would have expected that to clear up with the reboot.
I've continue to look for the solution and have been prodding at it without
positive results. Any other ideas?
Thanks,
Matt
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Friday, May 31, 2013 7:04 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CAD not updating
Need to run dm_recon.......devmon must have marked some of the destinations as
failed...
Solution
Current Alarm Display (CAD) Does Not Update on Several Stations March 10, 2009
Problem Description
The plant was in control shutdown to upgrade a UPS. During the startup, several
stations do not receive alarms. Many alarms are being generated, and we can see
them at a different part of the plant.
Fix/Resolution
The Device Monitor Master was moved from a v4.3 WP51, installed with an older
System Definition Commit. The destination for the Device Monitor Master is a
v7.1 AW70, installed with the newest System Defintion Commit. The following
commands were run on the AW70 to move the Device Monitor and to update all
Control Processor APRINT device tables.
/usr/fox/cs/dm_recon t
/usr/fox/cs/dm_recon
To view the current status of monitored devices, enter the commands:
cd /usr/fox/cs
dm_recon d
more cs_dm.current
Note the cs_dm.current file will only be created on the station which is
currently the Device Monitor Master.
Supporting Information
See also HH658, HH832, HH843, SOL594.
Troubleshooting
Suspect the Device Monitor Master is not updating the CPs with the status of
all the configured stations. We first found the address of the Device Monitor
Master using /opt/fox/bin/tools/glof -p DEV_MONITOR, which returns nsap and mac
of the station. We used glof <letterbug> to find the station that matches the
master. A WP at v4.3 was the master, and we telneted to it and ran the Device
Monitor commads to find what it thought the current status is of all the
devices.
cd /usr/fox/cs
dm_recon d #generates a cs_dm.current table of statuses The WP did not have all
the stations in its table. This occurred because a previous committed software
install adding new stations was not passed through this WP. It was then
necessary to change the Device Monitor Master to a more update station.
Customer selected a station, and we logged into it and entered these commands:
cd /usr/fox/cs
#to take Device Monitor Master here.
dm_recon t
#to look at the status in cs_dm.current file.
dm_recon d
#to request Device Monitor Master to re-determine device statuses #in its
configuration, and update all Device Monitor Slaves' APRINT #service.
dm_recon
All stations are now alarming.
Operating system
Unix
DOS
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Gunter, Matt
Sent: Friday, May 31, 2013 4:44 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] CAD not updating
Here is something for those with some I/A history.
By way of reminder, we are a Solaris shop and are running I/A 7.5 with FV/FD
9.0.4. We have some WPs that will not update their Current Alarms listing when
displayed alarms are either acknowledged or cleared. However, once
acknowledged or cleared from the non-updating current alarm display, the alarms
are successfully ack'd/cleared from the displays on other stations. I have
been through the process of checking the definition via the Alarm/Display
Manager Configurator numerous times and have not found the difference between
the working and non-working CADs. Nor have I been able to identify anything in
B0193RV that gives me a clue. Can anyone out there point me in the right
direction?
Thanks in advance!
Matt
_______________________________________________________________________
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
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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:
