Raspberry Pi NTP config with fudge factors

[Frank Nicholas]

> On May 5, 2016, at 8:48 PM, Gary E. Miller <gem at rellim.com> wrote:
>> 
>> I don’t know enough to answer regarding “coarse time”.  Here’s my
>> output (FreeBSD-10.3-RELEASE):
> 
> yeah, that's a problem with refclock #20, important data is hidden.

What was missing from my ntpq -p output?  I’ve included it again below:
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
oGPS_NMEA(0)     .GPS.            0 l    6   16  377    0.000   -0.002   0.003
*tock.usshc.com  .GPS.            1 u   26   64  377   32.138    4.606   0.901
+clock.isc.org   .GPS.            1 u   21   64  377   70.356   -0.027   0.995
-tick.apple.com  .GPS.            1 u   47   64  227  147.752   40.539 163.016
-ntp.wdc1.us.lea 199.102.46.72    2 u   47   64  377   49.799   20.090   3.552
-leeloo.scurvyne 173.162.192.156  2 u   47   64  377  142.869   16.063  34.157
-2001:19f0:8000: 132.163.4.101    2 u    2   64  377   65.329   -7.336   0.499
+67.212.117.78   128.138.141.172  2 u   46   64  377   38.889   -4.778   0.341

> When you hide important data from the user, as #20 does, you have over
> simplified.

Please help me understand what’s missing.

>>> time1 adjusts the PPS derived time, time2 adjusts the NMEA derived
>>> time.  
>> 
>> So for type 20 (NMEA local) & PPS, time2 would be the correct place
>> to put the fudge factor (assuming time1 (PPS) is dead nuts).
> 
> Yes, except you'll need to disconnect the PPS to see it…

I don’t follow you here…

Thanks,
Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160505/5287bc1f/attachment.html>