Re: [foxboro] PI question about FXBAIS

Good info, but what normally happens is that the flatlining has gone on 
for some period of time, and someone finally notices it.  They call you, 
and they are irritated enough already that they don't have any history, so 
you bounce the one list to get it back up and make them happy, and take as 
little time as possible in the process.  And it's not frequent enough 
where if we performed the obvious first-step solution (upgrade FoxAPI and 
CIM-IO), and we still had the problem, that CSC would be able to reproduce 
it.


If I have time the next time this occurs, and it's not something that 
operations wants back right away, I'll go poking around with some of these 
tools.


Thanks,
Corey Clingo
BASF Corporation






"Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
11/29/2006 02:35 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] PI question about FXBAIS






If you have points that aren't moving in IP.21 or PI, there are things
to check.

FoxAPI has tools to examine the values in its datasets to see if they
are moving.

The OM has tools to examine the values in its lists to see if they are
moving.

Knowing where the failure is helps identify the correct solution.=20

The CSC can help if you give them a call or you can do it if you know
how to use things like foxspy, foxdsp, som, rsom, etc.


Regards,
=20
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Wednesday, November 29, 2006 8:30 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PI question about FXBAIS

It's similar with Aspen IP.21.  We've routinely restarted FoxAPI and=20
removed point list files on AWs to get the collection to come back up=20
cleanly after restarts.  I think even Aspen got tired of dealing with
the=20
collector support issues because they outsourced development and support

of the collector software to Matrikon.


The weirdest thing we've seen, though, is points flatlining in IP.21
when=20
they are moving on the system.  Usually only one or two out of an entire

list will do it, but it takes at minimum a list restart to get them
going=20
again.  It's infrequent, but hard to detect.  I think I'll try Alex's=20
checkpoint-the-CP trick next time it happens.  [Now see, how else would
we=20
find out this stuff if this list didn't exist?]


Corey Clingo
BASF Corporation






"Balmer, Robert D." <rbalmer@xxxxxxxxxxxxxxx>=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
11/29/2006 01:06 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
Re: [foxboro] PI question about FXBAIS






We have had to do the complete stop and start to get the list updating
for what seems like ever. Welcome to PI.

Robert Balmer

Senior Applications Analyst/Programmer
ISA CCST
Fort Madison Iowa
319 463 2206
rbalmer@xxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of brad.s.wilson@xxxxxxxxxxxxxx
Sent: Wednesday, November 29, 2006 12:55 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PI question about FXBAIS

OK, all is right with the world again.  Normally, when one or more PI
lists
stop updating, I would stop and start the PI interface and hope that
fixed
it.  However, I have never touched FoxAPI before.  So, I stopped &
started
both PI and FoxAPI ... and everything came back.  All lists are updating
and my users are happy once more.

Is there a way to start & stop individual lists?  I don't like stopping
the
interface for just a couple of non-updating points, because it breaks
the
continuity of ALL points.

Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx



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