800xA 5.1, Advant Master MB300 network disturbance
some day ago at one of our customer site was a problems with MB300.
Suddenly all live data have loosed from the Operator Station, than some data have appeared on the screen. They are showed for some time and lost again.
Customer restarted connectivity servers one by one and both in the same time, but without results.
When they are power off main MB300 switch all live data appeared on the screen. They power on switch and all worked normally. That's we think that some problems was with the switch.
There is no other devices (exept controllers and PU410) in MB300 network.
In the attached files there is a lot of errors, but unfortunately i can't find any information about it. Messages regarding this problem market by the green.
Could you please explain this messages?
Your best shots are:
1. System Messages in OnLine Builder connected to the controller (in this case, serial connection on front of CPU is preferred)
2. System Messages RTA Board Maintenance connected to the PU410
3. The [Workplace Structure]Web System Workplace:System Event List
4. Switch management log (lost when restarting it unless configured with transmission to a remote syslog server)
Of what model and make is the switch?
This could also be MB300 overload or what we use to call "channel back pressure" followed by some deadlock.
If you restart the switch, new MB300 data transport connections will be established and the communication will start to flow again.
What version do you have on the AC400 controllers ?
The attached document is the System Health Check I have been typing on for the last decade+.
Chapter 8.4 contains check items for OPC DA Connector; too many clients, items or improper use of Advant Master OPC items can lead to overload and backpressure (as mentioned by Jan-Erik in his answer previous to this).
Chapter 12 is targeting 800xA for Advant Master. Items 12.5 and 12.6 are of special interest here as they bring high detail about the transport mechanisms that will hurt big time from poor OPC client behavior.
Please revert with comments and data.