From: "Eric S. Raymond" <esr@thyrsus.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] "Plain Jane" timing GPS is working!
Date: Wed, 4 Apr 2012 09:36:15 -0400 [thread overview]
Message-ID: <20120404133615.GA15404@thyrsus.com> (raw)
In-Reply-To: <CAA93jw5rYW_A=snyqj4_ObMLxsufBYdXBw=GNPaeHQ0vL78zzg@mail.gmail.com>
Dave Taht <dave.taht@gmail.com>:
> Expect light participation from me here through may 5. I would certainly be
> open here to a discussion of 'now that we have good time, and geolocation,
> what can we effectively measure with it, and with what tools'...
Good time isn't quite a done deal yet. There are some relatively minor
changes to gpsd and a bit more hardware testing between here and there.
I'd say two weeks, assuming we don't run into any boojums. And I won't
sign off that the job is *really* finished until we can document hard bounds
on the jitter using something like the test rig Patrick Maupin is trying
to build.
By the way, I've had a third GPS vendor - a U.S. outfit called Parallax
Systems - get back to me with interest in the Plain Jane timing-GPS mod
(connect 1PPS to DCD in a stock design using SiRF+PL2303 or functional
equivalents). Had a long, friendly phone conversation with one of
their design guys.
For those of you not paying full attention recently, I have
engineering samples of Plain Jane from UniTraq - not yet verified that
these work because I have to mod gpsd so it won't time out the PPS
thread before it gets sat lock.
Meanwhile, Unitraq's test engineers in Shenzhen have shown me a gpsd log
including PPS events seen over USB. But we need to tell gpsd's noise
filter to be a bit less picky; for some reason it doesn't like the
pulse width and is rejecting those.
So we have two vendors actively cooperating on Plain Jane product
development and may have a third shortly. This is all good; my
ideal outcome would be multiple sources, with other vendors starting
to pick up that they need to supply 1PPS to stay competitive and it
becoming a stock feature on all new low-end GPS mice within a year.
Actually, it still kind of blows my mind that I've been able to
social-engineer all this with a handful of emails. Woulda been the
stuff of cyberpunk novels before the century turned...
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-04-04 13:36 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 [this message]
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 ` [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=20120404133615.GA15404@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dave.taht@gmail.com \
--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