From: tz <thomas@mich.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 17:18:04 -0400 [thread overview]
Message-ID: <CAFv7OigwG=YhXbg1Jek=nP=uLhxh4Xpt0gOjLowJY0sVjxZkOA@mail.gmail.com> (raw)
In-Reply-To: <20120312210345.GC17357@thyrsus.com>
On Mon, Mar 12, 2012 at 5:03 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> Reason #2 is that it's probably a single-layer board (can't think of
> any reason they'd have gone multilayer for a simple interconnect like
> this). Which in turn means we may very well be able to
> reverse-engineer a workable PCB design and parts list just by looking
> at this thing.
The board is probably minimum 4 layer.
Every USB chip and every GPS chip I've seen in dongles are fine-pitch
surface mount.
You CANNOT do this with anything less than 2 layers with lots of vias,
and if the pitch is fine enough you will need at least 4.
Also the RF section for the GPS - antenna to the input - is critical.
You aren't just going to put some copper out there and have it work
well.
http://www.prolific.com.tw/eng/downloads.asp?ID=23
The prolific is 28 pin ssop with scattered power and ground pins.
GPS chips (except for highly integrated modules) are worse as far as
the pins you need to get to the right places.
next prev parent reply other threads:[~2012-03-12 21:18 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 [this message]
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
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='CAFv7OigwG=YhXbg1Jek=nP=uLhxh4Xpt0gOjLowJY0sVjxZkOA@mail.gmail.com' \
--to=thomas@mich.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