[time-nuts] Precision Time Protocol – Windows 10 implementation
Adam Kumiszcza
akumiszcza at gmail.com
Sat Aug 10 06:58:09 UTC 2019
On Fri, Aug 9, 2019 at 1:01 PM shouldbe q931 <shouldbeq931 at gmail.com> wrote:
> On Thu, Aug 8, 2019 at 4:07 PM Adam Kumiszcza <akumiszcza at gmail.com>
> wrote:
>
> Although there is one method using WSL, there is also the "native" method
>
> https://techcommunity.microsoft.com/t5/Networking-Blog/Top-10-Networking-Features-in-Windows-Server-2019-10-Accurate/ba-p/339739
> "Precision Time Protocol - Try it out!"
>
Thanks! The link at the bottom is to a .doc file, which gives some
explanations. I'll try it out more thoroghly later. (
https://aka.ms/PTPValidation).
Some of the required links do not work, though, so it all seems a long way
till stable I guess.
I have run PTP on a rPi 3B without any kernel modifications as a
> grandmaster (with a ublox GPS to provide time and PPS), and experimented
> with different NICs (intel, broadcom and solarflare, all with HW
> timestamping) as clients in x64 hosts.
>
What type of PTP did you use? ptpd (https://github.com/ptpd/ptpd) or
linuxptp (http://linuxptp.sourceforge.net/)?
I've tried the latter, and used the following ntp.conf (part of it here):
#PPS Kernel mode
server 127.127.22.0 minpoll 4 maxpoll 4
fudge 127.127.22.0 time1 +0.000000 flag3 0 refid PPS
tos mindist 0.002
#GPS (NMEA)
server 127.127.20.0 mode 89 minpoll 4 maxpoll 4 iburst prefer
fudge 127.127.20.0 flag1 0 flag3 0 time2 0.059089 refid GPS stratum 2
#local PTP reference
server 127.127.28.0
fudge 127.127.28.0 refid PTP
/etc/linuxptp/ptp4l.conf has the following lines:
clock_servo ntpshm
ntpshm_segment 0
priority1 10
priority2 10
(the rest was left as default)
/etc/linuxptp/timemaster.conf is as follows:
# Configuration file for timemaster
[ntp_server localhost]
minpoll 4
maxpoll 4
[ptp_domain 0]
interfaces eth0
delay 10e-6
[timemaster]
ntp_program ntpd
[chrony.conf]
include /etc/chrony.conf
[ntp.conf]
includefile /etc/ntp.conf
[ptp4l.conf]
[chronyd]
path /usr/sbin/chronyd
[ntpd]
path /usr/sbin/ntpd
options -u ntp:ntp -g
[phc2sys]
path /usr/sbin/phc2sys
[ptp4l]
path /usr/sbin/ptp4l
But I think this shows it does not really interact with ntp:
pi at zegar:~ $ ntpq -c "cv &3"
associd=52436 status=00f1 15 events, clk_no_reply,
device="SHM/Shared memory interface", timecode=, poll=1850, noreply=1850,
badformat=0, baddata=0, stratum=0, refid=PTP, flags=0
(maybe because there's nothing connected on the other side, but I guess
noreply means no reply from PTP daemon?)
Best regards,
Adam
More information about the Time-nuts_lists.febo.com
mailing list