Ntp is the standard for Internet (WAN) time. With all its filters and fancy
math calculations, it shouldn't be too difficult to add 1588 IEEE operations on
the LAN. I know the protocols for exchanging the data is different but the
principles are very similar.
Any thoughts on merging the two?
I've been monitoring this thread for a while and i have a few comments.
1) I think on average the TX queue delay inside an ethernet card is going to be
way smaller than the delay observed on the general internet. NTPd's primary
algorithms compensate really well for jitter and delay already so
Normally, the GPRMC gets sent every second even when the puck doesn't have
a
fix. There is a field that says OK vs no-fix. ntpd checks that field.
10 satelite fix indoors. GPS is operating.
Normal timing setup is to have the device send only one NMEA GPRMC message
at 1s interval, and tweak
Hi,
I have a globalsat BU-353-S4 GPS receiver that I would lie to use as a source
for NTPd. When looking at the messages that it produces, unlike the periodic
messages I would expect every second, I get messages in bursts of threes
followed by a pause. If the face of an analog clock
-
From: Mike Cook <michael.c...@sfr.fr>
To: Leon McCalla <leonmcca...@hotmail.com>, questions <questions@lists.ntp.org>
Sent: Sat, 26 Dec 2015 3:55 PM
Subject: Re: [ntp:questions] custom NMEA messages
If you look at the doc
<<https://www.eecis.udel.edu/~mills/ntp/html/dri
