Re: [foxboro] Node Troubles????

Hi Terry

1)      We don't have any sequence blocks at all on this NODE.
2)      I've outputted Text Files of all our displays  and found no
instances of a .MA parameter that should not be there.  Tann Trin had
also done the same of Foxboro Montreal some years ago.
3)    And we don't use FoxAPI or AIMAPI for anything offline.  PI
accesses our system through a FD30 INT and serial Modbus setup.  AIM is
running on the AW51D Box which is the host for this NODE.

I believe I'll have to go through the displays once more...maybe
manually to be absolutely sure of nothing being connected to the blocks.

Thanks again


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Doucet, Terrence
Sent: Tuesday, November 13, 2007 9:59 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Node Troubles????

Dale,

If there does not seem to be a sign of a reboot, then it is not likely
that the extender is causing this problem, unless there are peer
connections into these blocks with some specific logic to force to
Manual given OOS, or BAD, etc.

So if you don't have peer or specific logic, then I would look at=3D20

1. Sequence blocks using some infrequently used logic. If you have
sequence logic I would put all the .s files in a directory and search
for the .MA of some of your blocks.

2. Displays, again some infrequently called display that might have some
DM commands imbedded (somebody builds a test display and forgets to
delete it) that toggle the.MA parameters of some blocks.  Here I would
"strings" through the display files and "grep" for the .MA of your
blocks.  You can easily build a script to check all files in a directory
and output the name of the displays that have .MA imbedded.

3. Is there any off-node access via AIMAPI or FoxAPI where someone might
have a spreadsheet (for example) that can "poke" your blocks .MA
parameter?

Your problem seems to be a very specific action and if you can rule out
initialization it seems impossible that a random event generating noise
can toggle this specific action.

Terry
=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: