Hi, maybe this is some sort of user error, but I noticed that the TAI offset never gets set for either the system or in the announce messages.
In my Wireshark captures, a Statime grandmaster never sets originCurrentUTCOffset, leaving it at 0, PTP_UTC_REASONABLE is also False; even though Chrony has set ADJ_TAI to 37 on the grandmaster device. I would expect originCurrentUTCOffset to be equal to ADJ_TAI (37).
Even if originCurrentUTCOffset is not 0, e.g. 37, such as with a LinuxPTP grandmaster. Statime never sets the system's ADJ_TAI resulting in the UTC time being 37 seconds ahead.
I also have concerns that leap seconds might not be working, as set_properties is responsible for both setting ADJ_TAI and leap seconds, however I haven't tested it.
Thanks,
Steve
Hi, maybe this is some sort of user error, but I noticed that the TAI offset never gets set for either the system or in the announce messages.
In my Wireshark captures, a Statime grandmaster never sets
originCurrentUTCOffset, leaving it at0,PTP_UTC_REASONABLEis alsoFalse; even though Chrony has setADJ_TAIto37on the grandmaster device. I would expectoriginCurrentUTCOffsetto be equal toADJ_TAI(37).Even if
originCurrentUTCOffsetis not0, e.g.37, such as with a LinuxPTP grandmaster. Statime never sets the system'sADJ_TAIresulting in the UTC time being 37 seconds ahead.I also have concerns that leap seconds might not be working, as
set_propertiesis responsible for both settingADJ_TAIand leap seconds, however I haven't tested it.Thanks,
Steve