Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Gary E. Miller" <gem@rellim.com>
Cc: thumbgps-devel@lists.bufferbloat.net, gpsd-dev@nongnu.org
Subject: Re: [Thumbgps-devel] Progress on Plain Jane
Date: Tue, 1 May 2012 19:09:17 -0400	[thread overview]
Message-ID: <20120501230917.GE10188@thyrsus.com> (raw)
In-Reply-To: <20120501151027.44487e16.gem@rellim.com>

Gary E. Miller <gem@rellim.com>:
> As you can see the NMEA/USB short term jitter is about 2 milliSec and
> the PPS/USB time is about 0.5 milliSec jitter.  Long term NMEA/USB drift
> is quite a bit larger, maybe 100 milliSec or more.
> 
> So the jitter of PPS over USB is about 50x worse than PPS over GigE, but
> I think for the purposes at hand pretty good.  Of course I expect the
> results to be worse when run on a single core router.

That's excellent news.  0.5msec jitter is as good as we could have
expected and exactly what one would predict from a max error of 1msec
due to polling interval. The long-term NMEA/USB drift is consistent
with previous observations by Hal Murray and myself.

Do you consider the GR-601 with this mod to be ready for production?
Should we give Navisys the green light on GPSD compatibility?  I see
no reason not to at this point, but you're doing the testing so you
make the call.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  parent reply	other threads:[~2012-05-01 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 12:17 Eric S. Raymond
2012-03-20 17:45 ` Gary E. Miller
2012-03-20 21:49   ` Eric S. Raymond
     [not found]   ` <20120501151027.44487e16.gem@rellim.com>
2012-05-01 23:09     ` Eric S. Raymond [this message]
     [not found]       ` <20120501163302.575890f8.gem@rellim.com>
2012-05-02  1:32         ` Eric S. Raymond
2012-05-02  2:13           ` tz

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=20120501230917.GE10188@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=gem@rellim.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