Re: [foxboro] FoxAPI issue.
- From: "Ghiglione, Alessandro" <Alessandro.Ghiglione@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 08:44:26 +0100
Hi,
We are suffering the same problem: every 6-8 hours MessageDisplay window
is flooded by hundreds of "LBUG IADriver read failed for C:B.P (AIS =
mreaidx)"
messages.
The problem persists since the Batch Suite 8.0 first installation =
(redundant).
It happens when batch server lost communication on the nodebus: operator
sees -for few seconds- cyano measurements on graphic displays.
I don't count events associated to CP checkpoints....
Apart some hardware enhancements, we recently focused on software:
1) foxapi changed to 4.2.8
2) Read and Write delta (EnvEdit/IADriver)changed from default (1.0) to =
0.49
3) QF2000627 installed
Really, we expected more benefits: the problem still exists, but no =
impact on production.
Unfortunately, in the last months we suffered other BatchSuite problems, =
one of them is
when some tags are correctly read, but not evaluated: recipe execution =
waits until=20
manual force occurs.
Local Foxboro support is involved, EMEA included.
Any suggestion is welcome.
2 AW51 style E, rev.6.3
3 WP51 style D
10 CP40s, CP60, 3 ModGtw
DM used (transition to FV)
Alessandro
=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On Behalf Of Wilbur Ho
Sent: mercoled=EC 18 luglio 2007 22.24
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FoxAPI issue.
Hi All,
=20
I am running FoxAPI 4.2.6 on IA version 6.4. I am also running I/A =
Batch
8.0 which gets its data from the FoxAPI. I keep getting the message =
"ERROR
read failed C:B:P (AIS mreaidx)" in the Batch logger. The tags, however =
can
be seen in foxspy, and ProcStatus of Batch.
=20
Any suggestions?
=20
Wil
=20
=20
=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
- Follow-Ups:
- [foxboro] RE : FoxAPI issue.
- From: Patrick VALENTIN
- References:
- [foxboro] FoxAPI issue.
- From: Wilbur Ho
Other related posts:
- » Re: [foxboro] FoxAPI issue.
- [foxboro] RE : FoxAPI issue.
- From: Patrick VALENTIN
- [foxboro] FoxAPI issue.
- From: Wilbur Ho