Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Patrick Maupin <pmaupin@gmail.com>
To: esr@thyrsus.com
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Mon, 12 Mar 2012 16:22:29 -0500	[thread overview]
Message-ID: <CAPz3yKdf6yuSoRS9f2y+nB_eti0JzfF83FqcYoA6eRan3kT0GA@mail.gmail.com> (raw)
In-Reply-To: <20120312210345.GC17357@thyrsus.com>

On Mon, Mar 12, 2012 at 4:03 PM, Eric S. Raymond <esr@thyrsus.com> wrote:

> I'm still skeptical about custom builds for production - means one of us
> would have to do the soldering, keep inventory, ship the results.  I'd rather
> develop a design and talk SparkFun or Dangerous Prototypes into fabbing it.

But if you work with somebody like this or like seedstudio, they will
order parts for you and assemble according to your instructions.  If
you simply view the dongle as a part to be ordered and the assembly to
be "take it apart, add this blue wire, put it back together" you will
realize that the same process could apply, at least for a company that
does more than basic board assembly.

> But an advantage of starting with this $23 module is that we don't have
> to make that decision yet.

Exactamundo!

> [Test system] sounds like a larger project than just reverse-engineering the dongle,
> though.  Do you have the capability, personally, to design and build such
> a thing?

This is more what I do on a daily basis.  Use a bunch of readily
available off-the-shelf thingies to make a few units.  In this case, I
would buy a third party FPGA board, make a couple of smaller PCBs to
talk to it with a socket for an OCXO, maybe a connector to accept a
clock from a rubidium time source, headers for some USB modules and
some GPS modules and do some FPGA coding to allow reliable high
resolution timestamps.  There are a couple of levels of this.  The
first is just to do some one-off futzing around looking at various
devices.  The second is to get serious.  You could probably build 3
identical units with really good resolution and stability (expensive
OCXO) for under $2K total.  Maybe a lot less if you can find some good
surplus stuff on ebay.

> And this makes complete sense.  Seems like a good way to start that doesn't
> require excessive time commitment up front on your part.

In that case I'll start ordering and plotting out what I'm going to
do, and will sign up for the project to start putting out information
on the test setup for people to throw rocks at.

  parent reply	other threads:[~2012-03-12 21:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18   ` tz
2012-03-12 21:26     ` Eric S. Raymond
2012-03-12 21:28       ` Patrick Maupin
2012-03-12 21:39         ` Eric S. Raymond
2012-03-12 22:10           ` Patrick Maupin
2012-03-12 22:23             ` tz
2012-03-12 22:33               ` Patrick Maupin
2012-03-13  2:29               ` Ron Frazier (NTP)
2012-03-13  2:39                 ` Chris Kuethe
2012-03-12 22:45             ` Eric S. Raymond
2012-03-12 23:01               ` Dave Taht
2012-03-13  1:43                 ` Eric S. Raymond
2012-03-13  2:04                   ` Chris Kuethe
2012-03-13  2:13                     ` Eric S. Raymond
2012-03-13  2:40                       ` Dave Taht
2012-03-13  2:53                         ` Chris Kuethe
2012-03-13  4:54                         ` Eric S. Raymond
2012-03-13 13:23                           ` Dave Taht
2012-03-13 14:35                             ` tz
2012-03-13 16:04                             ` Eric S. Raymond
2012-03-13 16:22                               ` tz
2012-03-13  2:38                 ` Ron Frazier (NTP)
2012-03-13  2:42                   ` Chris Kuethe
2012-03-13  3:00                     ` Ron Frazier (NTP)
2012-03-13  3:04                       ` Dave Taht
2012-03-13  3:06                         ` Chris Kuethe
2012-03-13  3:16                           ` Dave Taht
2012-03-13  3:31                             ` Chris Kuethe
2012-03-13  4:49                               ` Dave Taht
2012-03-13  4:55                               ` Eric S. Raymond
2012-03-13  4:16                     ` Eric S. Raymond
2012-03-12 21:40         ` tz
2012-03-12 21:27     ` Patrick Maupin
2012-03-12 21:22   ` Patrick Maupin [this message]
2012-03-12 21:37     ` Eric S. Raymond
2012-03-12 21:45       ` Patrick Maupin
2012-03-12 22:02         ` 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=CAPz3yKdf6yuSoRS9f2y+nB_eti0JzfF83FqcYoA6eRan3kT0GA@mail.gmail.com \
    --to=pmaupin@gmail.com \
    --cc=esr@thyrsus.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