Serge Bets wrote:
> Hello Thierry,
>
> On Tuesday, February 12, 2008 at 10:39:21 +0100, Thierry MARTIN wrote:
>
>
>>It seems that the Radio clock has 50ms offset compared to the GPS
>>source, which leads a failure in synchronisation.
>
>
> Radio clocks may need a fudge factor, typically aroun
Hello Thierry,
On Tuesday, February 12, 2008 at 10:39:21 +0100, Thierry MARTIN wrote:
> It seems that the Radio clock has 50ms offset compared to the GPS
> source, which leads a failure in synchronisation.
Radio clocks may need a fudge factor, typically around 20 ms, to report
the right time. T
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 i
Hi Thierry,
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 failu
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
