Re: Two time sources with offset => fails to synchronize

Thierry MARTIN wrote:
Hi all,

I am running ntp 4.2.0 on FC5.
Two time sources:
- embedded GPS board(Meinberg board)
- remote Radio clock synchronized ntp server (stratum 1)

It seems that the Radio clock has 50ms offset compared to the GPS source, which leads a failure in synchronisation.

I am looking for some documentation that explain why it fails.
Which parameter(s) in the configuration triggers that behaviour?

I used the "prefer" keyword in the GPS configuration line, with the same result. Is there a way to make it work better?

Thanks for you help
Thierry MARTIN



You could add a third and even a fourth source of time. You could also account for the offset in the Radio Clock due to propagation delay. I don't remember the syntax but you can specify the delay in ntp.conf.

.

Relevant Pages

  • Two time sources with offset => fails to synchronize
    ... Two time sources: ... remote Radio clock synchronized ntp server ... It seems that the Radio clock has 50ms offset compared to the GPS source, which leads a failure in synchronisation. ...
    (comp.protocols.time.ntp)
  • Re: CLKADJ?
    ... a PPC with naviation system, which reads the time from GPS. ... Today, I have measured 2.2 s difference to my radio clock, ... Casio or Seiko watch, and for some watches the 49G is ...
    (comp.sys.hp48)
  • Re: CLKADJ?
    ... into a calculator? ... which reads the time from GPS. ... Today, I have measured 2.2 s difference to my radio clock, ... always enjoy as stable a temperature as a watch or clock typically ...
    (comp.sys.hp48)
  • Re: Bizzare half second disagreement between ntp hosts
    ... with external time sources in the form of sistematic offsets to the = ... clocks outside. ... That is the machine that has the pps (from a GPS 18LVM) signal. ... Note that tick.usask.ca typically has a .2 ms offset, ...
    (comp.protocols.time.ntp)
  • Re: Two time sources with offset => fails to synchronize
    ... It seems that the Radio clock has 50ms offset compared to the GPS ... time sources is the worst configuration you can have. ... have configured a local GPS clock and 3 external servers then the external ...
    (comp.protocols.time.ntp)