<html><head></head><body><div class="ydpac62c1deyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div><br></div><div><br></div>
</div><div id="ydpfd043954yahoo_quoted_7147545745" class="ydpfd043954yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, September 12, 2024 at 02:39:06 PM PDT, James Browning via users <users@ntpsec.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">> On 09/06/2024 9:07 AM PDT Jim Pennino via users <<a href="mailto:users@ntpsec.org" rel="nofollow" target="_blank">users@ntpsec.org</a>> wrote:<br></div><div dir="ltr"><br></div><div dir="ltr">> I have a precision time and frequency device that provides, among other things, a serial port outputting NMEA data and pps with a specified accuracy of +/- 1 ns.<br></div><div dir="ltr">> <br></div><div dir="ltr">> This has been working just fine for many years.<br></div><div dir="ltr">> <br></div><div dir="ltr">> After an upgrade to Ubuntu 24.04.1 I found legacy ntp had been replaced by ntpsec-1.2.2 and the reference clock no longer works. The output of ntpq -pn is:<br></div><div dir="ltr">> <br></div><div dir="ltr">> xNMEA(0) .PPS. 0 l - 16 377 0.0000 -96.9056 0.5170<br></div><div dir="ltr">> +192.168.0.100 .PPS. 1 u 24 1024 377 0.1328 -0.8315 0.7548<br></div><div dir="ltr">> *192.168.0.101 .PPS. 1 u 332 1024 377 0.1171 -0.8703 0.8439<br></div><div dir="ltr">> +192.168.0.21 .PPS. 1 u 137 1024 377 0.1565 1.5477 0.7258<br></div><div dir="ltr">> <br></div><div dir="ltr">> The relevant lines from ntp.conf are:<br></div><div dir="ltr">> <br></div><div dir="ltr">> server 127.127.20.0 mode 16 minpoll 4 iburst<br></div><div dir="ltr">> fudge 127.127.20.0 time1 -0.0007 flag1 1 flag2 0 flag3 1 refid PPS<br></div><div dir="ltr">> <br></div><div dir="ltr">> In going through the documentation I found that it says the 127.127.x.y is replaced by a new symbol notation but is still recognized, so that should not be an issue. I did not find anything else that needs to be changed other than the location of the statistics files which I process to provide graphic status, but I may have missed something.<br></div><div dir="ltr">> <br></div><div dir="ltr">> So, can anyone tell me what I need to do here to get it working again with ntpsec?<br></div><div dir="ltr"><br></div><div dir="ltr">I would suggest squashing the contents of the fudge line into the server line contradicting what I write below, changing the mode to 0x10f and adding 'baud 9600'.<br></div><div dir="ltr"><br></div><div dir="ltr">If been saying some randomish things about this at <a href="https://gitlab.com/NTPsec/ntpsec/-/issues/826" rel="nofollow" target="_blank">https://gitlab.com/NTPsec/ntpsec/-/issues/826</a><br></div><div dir="ltr"><br></div><div dir="ltr">If reasonable I would like a couple seconds of serial output from the gpsdo(?).<br></div><div dir="ltr"><br></div><div dir="ltr">> Also, is it a true statement that all I have to do to change to the new naming scheme is to change 127.127.20.0 to nmea?<br></div><div dir="ltr"><br></div><div dir="ltr">No, it is not a true statement, and if you were to change back to classic ntpd at some point, it would be a minor obstacle. As it would be if changing to a copy of NTPsec built for strict compatibility.<br></div><div dir="ltr">_______________________________________________<br></div><div><br></div><div dir="ltr" data-setdir="false">I have been away for a week and in that time unattended updates upgraded the kernel twice as well as a lot of packages.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I had changed the config to use separate nmea and pps refclocks just before the updates, which still had all sorts of issues, and after the updates all the symptoms have changed.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div>refclock nmea flag1 0 baud 9600 minpoll 4 time1 0.000<br>refclock pps minpoll 4 flag2 0 time1 0.000<br></div><div><br></div><div dir="ltr" data-setdir="false">ntpq now reports:</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div>xNMEA(0) .GPS. 0 l 9 16 377 0.0000 -96.4123 0.5949<br>xPPS(0) .PPS. 0 l 8 16 377 0.0000 0.4051 0.0235<br>+192.168.0.100 .PPS. 1 u 58 128 377 0.1102 0.6766 0.6207<br>*192.168.0.101 .PPS. 1 u 131 128 377 0.1251 -0.2381 0.8949<br><br></div>Adjusting time1 appears to do nothing.</div><div dir="ltr" data-setdir="false"><br></div><br></div></div>
</div>
</div></body></html>