AC800 Event Collector
We have one 800xA ASCS1 v6.0.3 and one AC800M controller on site. So recently we added the redundant (ASCS2) server. In the company, we made an ASCS1 virtual machine, installed system installer on ASCS2, connected ASCS1 VM and ASCS2 to network and deployed ASCS2 from System Console Configuration on ASCS1. During this the ASCS1 system stopped working, so we performed this process again through Configuration Wizzard and it worked without crashing ASCS1.
Now colleagues are on commissioning, and they've sucessfully added ASCS2 to system but Event Collector (AS800SG) on ASCS2 is constantly in state "Sybchronizing". Colleagues tried to: restart both computers, restart services, delete and then again create service group, but nothing works. When ASCS1 is shut down, ASCS2 event collector normally works, but the ASCS2 Event Collector Service Provider is constantly in "yellow Synchronizing" state.
My colleague said that in order to resolve this problem on other plant, they had to make an AC800M cold restart. Do you have any idea how to resolve this?
Thanks in advance,
Voted best answer
To assist, I sincerely recommend to take "golden" drive images of all your computers while they still are in "delivery state" before adding any ABB software.
Such image can be safely restored on a compatible hardware and used to clone new computers into a system. The state ASCSx are in now might prevent any new software to be added or existing to be upgraded. A possible way out is using the System Installer's Replace Node function, with it you can safely (and rather effortless) rebuild any node from scratch.
About the Event Collector stuck in Synchronizing state - have you used the real System Status Viewer aspect (located in the Service Structure) and drilled down to the status object (located below each Event Collector service provider object) and checked what OPC Server Status the AC 800M OPC Server exposes?
For the Event Collector to enter Service state, the OPC server must expose "OPC_STATUS_RUNNING".
Common reasons for an AC 800M OPC AE server to *not* expose OPC_STATUS_RUNNING:
- No controllers are connected on the Alarm & Event tab
(only red sad faces, or no faces at all)
- MMS AE connection with the controller is rejected because the AE Max Number of Subscribers is depleted
(or left at default value 1) permitting only one OPC server to connect at a time)
- Old MMS AE connections prevail in the controller even though the OPC server has restarted.
Check for this state by going online with the controller from Control Builder M and open the SystemDiagnostics block of the Program3.Slow task. Then select Advanced > Alarm & Event and examine the subscribing systems. If a stale connection does not get cleaned out, you must reset the controller or download "+1" on the previous mentioned setting as a workaround.
There is also a Product Alert published on ABB Library for 5.1, I believe it is still applicable for 6.0.3