Re: [foxboro] RE : FoxAPI issue.
- From: "Ghiglione, Alessandro" <Alessandro.Ghiglione@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 10:06:03 +0100
Patrick,
* Batch read error messages are an old problem, WITHOUT impact on =
production.
* No concurrent switch of master/backup role occurs with the same =
frequency (once a month)
* Nodebus network and batch network are separated: each AW51 has 3 eth =
ports: nodebus, batch network and one dedicated to batch redundancy; =
RedCfg file is properly configured to avoid batch programs using =
nodebus.
* Read and Write delta new values were suggested by EMEA (in principle I =
had yr same doubts)
* after switching, new master collects the same read errors
Really, in the last 6 months we suffered nodebus comms failures, that =
made worse BatchSuite problems.
Cyano measurements on graphic displays froze the screen until DNBT =
reset...
Once we replaced DNBTs, some old CPs, copper node extension with fiber, =
then nodebus performance became acceptable.
On the contrary, BatchSuite hasn't got benefit from hardware changes, =
only the mentioned 3 software updates mitigates its problems.=20
Alessandro
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On Behalf Of Patrick VALENTIN
Sent: gioved=EC 19 luglio 2007 10.20
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] RE : FoxAPI issue.
Hi Alessandro,
It's look like a network problem ???
Is your nodebus loading OK ?
Have you got a separation between nodebus network and batch network (on
a second network on second ethernet card) ?
Are you switching from the master batch server to slave batch server
when problem occur ?
If server are switching, I would like to know if the new master (slave
before switch) have got immediately the same problem ?
If it's a network problem, your Read and Write delta value (0.49)
increases the problem.
Patrick VALENTIN
CIMSIDE
-----Message d'origine-----
De=3DA0: foxboro-bounce@xxxxxxxxxxxxx =3D
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
De la part de Ghiglione, Alessandro
Envoy=3DE9=3DA0: jeudi 19 juillet 2007 09:44
=3DC0=3DA0: foxboro@xxxxxxxxxxxxx
Objet=3DA0: Re: [foxboro] FoxAPI issue.
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 =
=3D3D
mreaidx)"
messages.
The problem persists since the Batch Suite 8.0 first installation =3D3D
(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
=3D3D
0.49
3) QF2000627 installed
Really, we expected more benefits: the problem still exists, but no =
=3D3D
impact on production.
Unfortunately, in the last months we suffered other BatchSuite problems,
=3D3D
one of them is
when some tags are correctly read, but not evaluated: recipe execution =
=3D
=3D3D
waits until=3D3D20
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
=3D3D20
=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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » Re: [foxboro] RE : FoxAPI issue.
