> -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
e).
>
> Have you configured that?
>
> Regards
> Dennis
>
> -Original Message-
> From: Elder Costa
> Sent: Wednesday, May 24, 2023 1:20 PM
> To: linuxptp-users@lists.sourceforge.net
> Subject: [Linuxptp-users] Offset between TAI and PHC
>
> I a
ither from config or from the announce
message).
Have you configured that?
Regards
Dennis
-Original Message-
From: Elder Costa
Sent: Wednesday, May 24, 2023 1:20 PM
To: linuxptp-users@lists.sourceforge.net
Subject: [Linuxptp-users] Offset between TAI and PHC
I am getting the result
I am getting the result below with the check_clocks utility.
downloaded from:
https://tsn.readthedocs.io/timesync.html#checking-clocks-synchronization
cve@cve-sbc-flt2:~/work$ sudo ./check_clocks -d enp3s0 -v
Dumping timestamps and deltas
rt tstamp: 1684764184805696608
tai tstamp: 168476418480569