Wild Time Swings
This post is undoubtedly not as cool as the title may imply, but I am observing occasional time swings on my 800xA for DCI Connectivity Servers by as much as 280 seconds. This may be related to another post I created about an hour ago regarding occasional network connectivity losses on these same 800xA for DCI Connectivity servers.
Typically the time difference on these servers hovers around +/-0.01 seconds off from my site's SNTP server (as observed by the command w32tm /stripchart /computer:SNTPSVR), however occasionally the time drifts, stabilizes at an incorrect time, then drifts back to being synchronous with the SNTP server (see attached screen shot of a recent event). I have attached my Time Synchronization diagram for my system (which was designed with guidance from ABB document 3BSE034463-510), but I will attempt to further describe how the DCI Time Synchronization portion of my system is configured:
-The Domain Controllers synchronize to the SNTP server over the Client-Server network using W32Time every 15 minutes.
-Two out of four of the 800xA for DCI Connectivity Servers synchronize with the Domain Controllers using W32Time every 15 minutes. These DCI nodes have a DCI Time Synchronization Priority of 10 (the highest priority), meaning they are the time masters in the DCI control network. All other DCI nodes have varying Time Synchronization priorities of 9 or less. The AfwTime Service is disabled on these 800xA for DCI Connectivity Servers.
-W32Time is disabled on all other nodes in my DCI system including the other two 800xA for DCI The other two 800xA for DCI Connectivity Servers. The AfwTime Service is also disabled on these servers. The time on these servers is managed by ABB's DCI TsychDD Daemon.
I do not yet use my AC800M controller(s) as time masters (via 800xA for AC800M Connectivity Servers) for my 800xA for DCI system because they are still in development.
It would appear that the W32Time and ABB DCI TsynchDD Daemon may be conflicting and potentially causing these time swings, but I am not sure of this or even how to remedy this circumstance if this is indeed the case. Any guidance would be greatly appreciated.
Did you turn off the Afw Time Client in the nodes where you are running W32Time?
The AfwTime synchronization is split over two features:
1) The AfwTime Service (per system)
2) The Time Server Client Configuration (per node)
In the drawing you attached I can see AfwTime Service running on AC800 Connectivity servers, depending on configuration, it may pick up controller time (via CNCP) and broadcast it to all 800xA nodes having "Time Sync Running" enabled. The nodes receiving Afw time are also listed on the Time Differences tab (see item 1), be sure to verify that you do not see your DCI CS nodes there.
On a default system, Afw Time Service (the service) is running on ALL server nodes, all are potential Afw Time master keepers. This is in most cases not desirable, I recommend to delete the AfwTime Service from all server nodes but 1-2 servers who's time shall be used as source for the 800xA nodes. Preventing a node from slaving to Afw Time is done by clearing the "Time Sync Running" checkbox.