Event Time Not Synchronized.
Hello,
I have issue where the event list of objects of The BM. There are 9 seconds approximately between first action and return to confirm event. Following the picture attached. The clock sync in my system is taht ok, all the servers and controllers there are with chock synchronized by CNP with the GPS. I restarted the service provider of event collectors and event storage but the issue continue.
I observed too in others kinds objects, for exemple. VLV1, MOT1. In other system the difference the event time is miliseconds and don't have the same insue.
I have issue where the event list of objects of The BM. There are 9 seconds approximately between first action and return to confirm event. Following the picture attached. The clock sync in my system is taht ok, all the servers and controllers there are with chock synchronized by CNP with the GPS. I restarted the service provider of event collectors and event storage but the issue continue.
I observed too in others kinds objects, for exemple. VLV1, MOT1. In other system the difference the event time is miliseconds and don't have the same insue.
Asked 4 months ago
Answers
1
The window adorners indicate Server 2012 or Windows 8 whicb may imply 800xA v6.0.x.
The AC 800M TimeAdaptor of 6.0.x was plagued with an intermittent error until it finally got corrected in 6.1.
Hence there may be a time discrepancy between AC 800M controller's CNCP time and Windows Time. It should be easy to verify this by going online with the controller application and open the TimeSet function block part of the default Application_1.Slow program and compare with Windows Time.
In lack of a reliable AC 800M TimeAdaptor I recommend having your AfwTime Server node to slave to the GPS instead of CNCP. You should also DISABLE the AC 800M TimeAdaptor in Windows when doing so to avoid having more than one time slaving protocol enabled simultaneously in a node.
I have too little application knowledge to interpret the content of the event list image attached to the photo.
With Microsoft Windows you can easily compare time with another SNTP source, e.g. an AC 800M or GPS. Use the w32tm.exe tool's /STRIPCHART function.
C:\> W32TM /STRIPCHART /COMPUTER:ip-address-of-sntp-reference
The AC 800M TimeAdaptor of 6.0.x was plagued with an intermittent error until it finally got corrected in 6.1.
Hence there may be a time discrepancy between AC 800M controller's CNCP time and Windows Time. It should be easy to verify this by going online with the controller application and open the TimeSet function block part of the default Application_1.Slow program and compare with Windows Time.
In lack of a reliable AC 800M TimeAdaptor I recommend having your AfwTime Server node to slave to the GPS instead of CNCP. You should also DISABLE the AC 800M TimeAdaptor in Windows when doing so to avoid having more than one time slaving protocol enabled simultaneously in a node.
I have too little application knowledge to interpret the content of the event list image attached to the photo.
With Microsoft Windows you can easily compare time with another SNTP source, e.g. an AC 800M or GPS. Use the w32tm.exe tool's /STRIPCHART function.
C:\> W32TM /STRIPCHART /COMPUTER:ip-address-of-sntp-reference
Add new comment