Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: tz <tz2026@gmail.com>
To: esr@thyrsus.com
Cc: thumbgps-devel@lists.bufferbloat.net, gpsd-dev@nongnu.org
Subject: Re: [Thumbgps-devel] Progress on Plain Jane
Date: Tue, 1 May 2012 22:13:13 -0400	[thread overview]
Message-ID: <CAFv7OigCsn0PYnH3Fby2uNiBjOKA3_5OPWkUMjCsQJLTAPB7UA@mail.gmail.com> (raw)
In-Reply-To: <20120502013215.GB11394@thyrsus.com>

[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

If you start to go too exotic, then an Arduino with ethernet shield
emitting a packet right at the pps starts to look good, and the parts are
at Radio Shack.  But any such not in quantity would be more expensive.
There are plenty of generic usb 2.0 chips and acm or cdc is just a set of
bit and endpoint specs.  And any 2.0 chip would need to use an existing
linux driver unless someone plans to do a lot of libusb coding.

The base problem is hardware lameness.  Polling instead of an interrupt pin
that can immediately respond, much less something like an input capture.  I
could probably sync a 2ppm dallas semiconductor i2c real time clock's 1Hz
output, but even then there is nothing to sync that with the internal
clocks.  (I was already inspired to use pps to create an accurate synced
timestamp for j1850 data off my motorcycle - oh, and batchpcb.com can do
small quantities of small boards themselves cheap, but you still need to
build them).

If you have a 2nd usb port and want to get tricky, the pnp/insert/remove
event is likely higher priority, so with a FET...
 On May 1, 2012 9:32 PM, "Eric S. Raymond" <esr@thyrsus.com> wrote:

> Gary E. Miller <gem@rellim.com>:
> > > 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.
> >
> > Nice when theory and practice agree.  I wonder if there is a USB 2.0
> > equivalent of the PL2303 which would give us a 125 microSec poll?
> >
> > Might be worth asking navisys about that.
>
> Maybe.  But that would require that they qualify a new and probably more
> expensive adapter part. We should get this puppy shipping and let them
> see some ROI before we push that.
> --
>                <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
> _______________________________________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/thumbgps-devel
>
>

[-- Attachment #2: Type: text/html, Size: 2767 bytes --]

      reply	other threads:[~2012-05-02  2:13 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
     [not found]       ` <20120501163302.575890f8.gem@rellim.com>
2012-05-02  1:32         ` Eric S. Raymond
2012-05-02  2:13           ` tz [this message]

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=CAFv7OigCsn0PYnH3Fby2uNiBjOKA3_5OPWkUMjCsQJLTAPB7UA@mail.gmail.com \
    --to=tz2026@gmail.com \
    --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