NMEA refclock

[James Browning]

On Wed, Dec 2, 2020, 4:12 PM Fred via users <users at ntpsec.org> wrote:

> Trying to setup NMEA refclock.  I'm seeing the following error in ntpd.log:
> 2020-12-02T16:58:12 ntpd[705]: PROTO: NMEA(0) 804b 8b clock_event
> clk_no_reply
> 2020-12-02T16:58:13 ntpd[705]: PROTO: NMEA(0) 805b 8b clock_event
> clk_bad_format
> 2020-12-02T16:59:16 ntpd[705]: PROTO: NMEA(0) 806b 8b clock_event
> clk_no_reply
> 2020-12-02T16:59:17 ntpd[705]: PROTO: NMEA(0) 807b 8b clock_event
> clk_bad_format
>
> ntpq -p does not change from:
> NMEA(0)                                 .GPS.            0 l    -   64
>  0   0.0000   0.0000   *1.9531*
> + server pool
>
> *ntp.conf*
> server 127.127.20.0 mode 1 prefer
> fudge 127.127.20.0 flag1 1 flag2 0  refid GPS
>
> server 0.us.pool.ntp.org iburst
> server 1.us.pool.ntp.org iburst
> server 2.us.pool.ntp.org iburst
> server 3.us.pool.ntp.org iburst
>
> + ntpstat lines
>
> Any insight would be helpful.
>

Without looking at all, I would guess that your GPS is not sending the
NMEA0183 sentences ntpsec was expecting. My course of action would be to
check the output of that GPS and look at the source to see what else could
trigger those messages. Also IIRC gpsd is the preferred interface to GPS
receivers and the pool directive should be used instead of the four server
directives. Better answers might come later.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/users/attachments/20201202/6c5f4a8a/attachment.htm>