From: Patrick Maupin <pmaupin@gmail.com>
To: tz <thomas@mich.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:33:23 -0500 [thread overview]
Message-ID: <CAPz3yKc-P2XssRR33KPtr_V-23ajwSjhaEbdMMUpQ0adhhX_vA@mail.gmail.com> (raw)
In-Reply-To: <CAFv7Oij-_DeihHyqWm3L2s=TJZMtqUOdSanYgqEQ96Z+DMZAWg@mail.gmail.com>
On Mon, Mar 12, 2012 at 5:23 PM, tz <thomas@mich.com> wrote:
> OK, it is a 2 sided board, but you would have to find the 1PPS pin
> (and it looks hard to solder to),
The module is documented, the pin doesn't look in that difficult a
place. Seriously, my tech could probably do at least 50 of these an
hour.
> Since the GPS patch antenna is on the board, the board would have to
> be in the sky view so you would have to run the PPS all the way to the
> router if one of the pins isn't DCD, CTS or some other line.
This is what I'm less sanguine about. When I thought it was a "real"
Prolific chip, I assumed that there would be at least a CTS. And
maybe there is, but I'm concerned about the handling of it. I've gone
off the idea of this module a bit simply because the chip is not
documented, but if it really is just a single blue wire from the
module to the USB converter, it would make a great solution.
next prev parent reply other threads:[~2012-03-12 22:33 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 [this message]
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=CAPz3yKc-P2XssRR33KPtr_V-23ajwSjhaEbdMMUpQ0adhhX_vA@mail.gmail.com \
--to=pmaupin@gmail.com \
--cc=thomas@mich.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