> -w
> If it's not, you can configure the offset locally on the client end with -O
>
> Regards
> Dennis
>
> -Original Message-
> From: Miroslav Lichvar
> Sent: Wednesday, May 24, 2023 3:51 PM
> To: Elder Costa
> Cc: linuxptp-users@lists.sourceforge.ne
Elder Costa
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] Offset between TAI and PHC
On Wed, May 24, 2023 at 08:19:37AM -0300, Elder Costa wrote:
> phc latency: 7472
> phc-rt delta: 3739320
> phc-tai delta: 3739035
>
> phc-tai delta is greater than 50
On Wed, May 24, 2023 at 08:19:37AM -0300, Elder Costa wrote:
> phc latency: 7472
> phc-rt delta: 3739320
> phc-tai delta: 3739035
>
> phc-tai delta is greater than 50 usec !
> TAI offset set in kernel is not correct !
I think you need to set currentUtcOffsetValid and timeTraceable on the
Hello, Dennys, thank you for chiming in.
From my understanding of the documentation, I assumed
the offset would be taken from ptp4l with the '-w' command
argument. Obviously I am missing some config or doing
something wrong I am not figuring out.
I tried some variations but either they desynchroni
Hi,
I'm not exactly sure what this tool is doing, but most likely explanation for
the difference between those clocks is due to leap second offset (currently 37
seconds).
I believe RT should be UTC, and the PHC should be TAI (37 seconds in front of
TAI). phc2sys should add the offset (either f
