First of all, for the proper functioning of the servers, it is necessary to use only one (1) time-synchronization implementation!
Only the integrated clients from versions Windows 10 1607 / Windows Server 2016 or newer offer an accuracy of up to 1 ms, otherwise, other software tools are required.
Keep in mind that the build-in time sync clients in IBA software will also change the system time of the server, so there is no need to use activate the Windows time sync client.
NTP <> PTP is described below, generally speaking, NTP was used for servers to synchronize with 1 master server (most of the time the domain controller) for 'raw' synchronization where the 'system time' needs to be correct.
PTP is better suited for installations where specific systems needs to be synchronous, for example, 2 different IBA servers.
ibaClock is mainly used for installations without a link between the 2 'locations'. See example below offshore substation <> onshore substation.
By using ibaClock on the 2 locations the .DAT files are synchronized without a (data)link between each other.
This is used because it is often not allowed to have other traffic than the power control signals.
This is used because it is often not allowed to have other traffic than the power control signals.
ibaClock can also be used for other non-IBA systems to synchronize the time.
Precision :
GPS <150ns
NTP <1ms
PTP <100ns (ideal network architecture, fully IEEE1588 compliant)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article