From: Dave Hart <hart@ntp.org>
To: "Ron Frazier (NTP)" <timekeepingntplist@techstarship.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] "Plain Jane" timing GPS is working!
Date: Tue, 3 Apr 2012 16:07:17 +0000 [thread overview]
Message-ID: <CAMbSiYAAwkj_Nmb9fg8z51bW4o5deomFH6LqLKpL9cL1YAad7A@mail.gmail.com> (raw)
In-Reply-To: <4F7B1041.4070303@techstarship.com>
On Tue, Apr 3, 2012 at 14:59, Ron Frazier (NTP)
<timekeepingntplist@techstarship.com> wrote:
> I had my Sure board working a couple of weeks ago connected SERIAL ->
> Prolific adapter -> USB, with PPS patched to DCD, running NTPD on Windows
> using Dave Hart's new binaries, without running GPSD. It was working fine
> within + / - 1 ms of GPS time. It was definitely reacting to the pulses.
> Maybe you could try with NTPD only. I was using the "20" NMEA driver with
> the PPS flag 1 active. I don't know for sure if the Linux version of NTPD
> has all the features necessary to do this.
The Windows port of ntpd is the only one which has the crude user-mode
PPS hack needed to use PPS without PPSAPI. On Linux, gpsd is the way
to achieve the same. Incidentally that user-mode PPS hack will be
moving from ntpd's Windows serial I/O layer to a separate PPSAPI
provider DLL before long, so that it will be disabled by default and
enabled only when desirable by administrator action. It will also
behave better via PPSAPI, so that for example NMEA's fudge time1 is
used to offset PPS timestamps as designed, rather than fudge time2
(which is intended to control only NMEA timestamps, but the user-mode
PPS hack substitutes the first NMEA timestamp each cycle with the PPS
timestamp. Also currently the fact that PPS is used is invisible, but
when it's done with a PPSAPI provider DLL, ntpd will show the 'o'
tally code for the PPS-enabled refclock rather than '*'.
Cheers,
Dave Hart
next prev parent reply other threads:[~2012-04-03 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:34 Eric S. Raymond
2012-04-03 14:59 ` Ron Frazier (NTP)
2012-04-03 15:35 ` Eric S. Raymond
2012-04-03 16:31 ` Dave Taht
2012-04-04 13:36 ` Eric S. Raymond
2012-04-04 15:41 ` Dave Taht
2012-04-04 18:42 ` Eric S. Raymond
2012-04-03 16:07 ` Dave Hart [this message]
2012-04-03 15:15 ` Patrick Maupin
2012-04-03 17:20 ` [Thumbgps-devel] [gpsd-dev] " Håkan Johansson
[not found] ` <20120403114922.28f4bc81.gem@rellim.com>
2012-04-03 19:44 ` Håkan Johansson
2012-04-04 13:38 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMbSiYAAwkj_Nmb9fg8z51bW4o5deomFH6LqLKpL9cL1YAad7A@mail.gmail.com \
--to=hart@ntp.org \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=timekeepingntplist@techstarship.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox