From: "Håkan Johansson" <f96hajo@chalmers.se>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: thumbgps-devel@lists.bufferbloat.net, gpsd-dev@nongnu.org
Subject: Re: [Thumbgps-devel] [gpsd-dev] "Plain Jane" timing GPS is working!
Date: Tue, 3 Apr 2012 19:20:32 +0200 [thread overview]
Message-ID: <alpine.DEB.2.00.1204031909530.13879@bridge1.fy.chalmers.se> (raw)
In-Reply-To: <20120403143402.GA7338@thyrsus.com>
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
Is it the pulse shape (i.e. length) or the pulse repetition that gpsd
rejects? As I recall, a SiRf-III GPS delivers a PPS pulse that is only 1
us long, so does not record a full state change, but this is handled.
Timing over USB is distored by the inherent USB polling interval of 1 ms,
so could make the inter-pulse interval fail those tests. (They actually
allow +/-1 ms, so should make it?). Logfile?
Due to the USB effectively downsampling the measurement to the USB
'polling clock', such a setup might be prone to seeing jumps. I.e. if the
USB polling frequency is close to a multiple of the PPS signal, then it
for long times drifts slowly (which will not be detected), and then jumps
one polling cycle. (Possibly even usable. Unhandled it could make life
miserable for chrony/ntp.)
Cheers,
Håkan
On Tue, 3 Apr 2012, Eric S. Raymond wrote:
> A few minutes ago I received mail from the test engineers at NaviSys.
> They have tested the "Plain Jane" concept (take a stock SiRf-III GPS
> chip plus PL2303 USB adapter, connect the 1PPS pin on the former to
> DCD input on the latter) with GPSD, and are actually seeing PPS pulse
> messages in the logs.
>
> The filter in GPSD doesn't like the pulse shape and is rejecting it, but
> that can be fixed. The essential point is that the hardware mod works
> exactly as expected and is producing events visible on USB.
>
> I'm expecting my samples from UniTraq today or tomorrow and may soon have
> more good news about our second Plain Jane variant.
> --
> <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
>
next prev parent reply other threads:[~2012-04-03 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:34 [Thumbgps-devel] " 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
2012-04-03 15:15 ` Patrick Maupin
2012-04-03 17:20 ` Håkan Johansson [this message]
[not found] ` <20120403114922.28f4bc81.gem@rellim.com>
2012-04-03 19:44 ` [Thumbgps-devel] [gpsd-dev] " 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=alpine.DEB.2.00.1204031909530.13879@bridge1.fy.chalmers.se \
--to=f96hajo@chalmers.se \
--cc=esr@thyrsus.com \
--cc=gpsd-dev@nongnu.org \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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