The following scenarios will cause the Time Synchronization Manager to abort a time adjustment to a client:
• If the adjusting the client’s clock would result in rolling the client’s data back to a previous day, the time adjustment will not occur, as doing so would have a negative effect on data logging, especially at the first day of a month, as the rollback would then be to the previous month.
• The client’s clock will also not be adjusted if the delta from the server is less than some tolerance (relative to the roundtrip time of the request). For example, if a roundtrip takes a whole second, the server’s timestamp will not be very precise, so the client’s clock will not be adjusted unless the delta is > 0.5 seconds.
• The client’s clock will not be adjusted if the roundtrip time exceeds 10 minutes.
• The client’s clock will not be adjusted if the server’s RPC queue (which takes priority) exceeds a user-defined value (as defined by the TimeSyncRPCQMax Config.ini [SYSTEM] section variable).
• No time synchronization will take place if the TimeSyncEnable Config.ini [SYSTEM] section variable is set to 0 (disabled).
Please refer to Config.ini [SYSTEM] Section Variables for the Time Synchronization Manager for information on configurable variables for the Time Synchronization Manager.