800xA 5.1: certain services occasionally leave/reach service state
Occasionally (maybe once a day, on average) I get the following events from the AfwServiceManager:
"17:05:44 Event Collector (...) Service provider left service state CONN2"
"17:05:43 Time_(...) Service provider left service state CONN1"
"17:05:42 Time_(...) Service provider reached service state CONN1"
"17:05:36 Event Collector (...) Service provider reached service state CONN2"
Sometimes many times in a row. Why does this happen?
Answers
The OPC DA Connector and OPC AE (Event Collector) services in 800xA are constantly monitoring the connected OPC DA/AE servers for their health using the GetStatus() function of the OPC protocol specification.
The state can be viewed with some OPC DA and AE clients.
Unfortunately, no OPC AE test client is shipped with System 800xA. You may ask your
regional ABB support center for help with obtaining a test client.
If any of the connected OPC DA or AE servers report an error state, or fail to report at all, the related Afw-services will abort and restart.
Hint: copy the Service Event List from the root of the Service Structure down to the Event Collector service, or group or dedicated service provider. Abnormal states are reported in conjunction with the abort/restart.
You can also perform a search for Message with filter "*server state*":
Event Collector_BATCH_ABBIT53 Failed to Setup EventCollector, OPC AE server state: Failed
IM_Event Collector_ABBIT53 Failed to Setup EventCollector, OPC AE server state: Failed
The abortion is intentional to force clients over to a redundant service provider (if existing).
The AfwTime Service may failover in case a better Master Candidate appear. Typically all service providers depart service state while negotiating the new master after they return to either "Service" or "Standby".
Network disturbances, failover may also trigger disconnected / reconnected services to re-negotiate their mastership. Check the System Event List, RNRP Monitor and RNRP log file (C:\ProgramData\RnrpEvent.log) for more information about network disturbances.
Add new comment