From: tz <tz2026@gmail.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Progress in Shenzhen
Date: Sat, 17 Mar 2012 17:23:09 -0400 [thread overview]
Message-ID: <CAFv7OijGw9_0wQfm_hT_M0hDOriF2NP6PN-E4t=LFYCfMyAOxQ@mail.gmail.com> (raw)
In-Reply-To: <20120317141911.1E54D4081F@snark.thyrsus.com>
[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]
Note the 731-r is venus 5, the ones I've used are venus 6, but skytraq
seems consistent.
Would you happen to know if the unitraq is 20hz (venus 638) or 10hz (634)?
Note they could have a populateable 0 ohm jumper if they wanted it
optional, but dcd or ri shouldn't interfere with generic gps software.
On Mar 17, 2012 10:19 AM, "Eric S. Raymond" <esr@thyrsus.com> wrote:
> Of the 5 companies I contacted, two - NaviSys and UniTraq - have
> gotten back to me, confirmed that their USB GPS dongles do not ship 1PPS,
> and expressed interest in the possibility of customizing a product for
> us. A third, Xucai Technologies, responded without bringing up the
> possibility of an OEM/ODM product. This is as good a response rate
> as I was expecting.
>
> Three devices are under discussion.
>
> One NaviSys device is the GR-300, bsed on uBlox 6 with integral USB
> interface. I think this one is actually a non-starter as it would
> require fiddling with the uBlox firmware to get the chip to ship
> 1PPS notifications.
>
> The other NaviSys device is the GR-300: SiRFIII + PL2303. The UniTraq
> device is the UD-731R: SkyTraq + CP-2102. Both adapters have full
> Linux support and have DCD pins. Both chipsets emit 1PPS. Neither
> device connects the 1PPS pin to the adapter DCD.
>
> I am pitching both companies the idea that with one added PCB trace
> they could sell to a sizeable untapped market of people with
> applications like network tomography and Stratum 1 NTP servers.
> I've told them we're willing to help them test and qualify the
> product if they'll sell the results back to us at a price
> that is reasonable for a hundred-unit deployment.
>
> It's early in the negotiations yet, but things look promising. These
> outfits are clearly used to doing ODM/OEM business - the only real
> difficulty I'm having is explaining why I think this mod will work,
> because these people don't know the odd corners of the USB spec
> involved.
>
> In the process of writing my explanations I've done more research
> (including reading the Linux PL2303 driver source code and grokking
> how USB handshake control messages are handled there) and my
> confidence that the mod actually will work has increased.
>
> I think I have at least one more plausible company - GlobalSat - to
> poke about this if neither NaviSys or UniTraq follows through. More
> might be findable through alibaba.com
> --
> >>esr>>
> _______________________________________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/thumbgps-devel
>
[-- Attachment #2: Type: text/html, Size: 3268 bytes --]
prev parent reply other threads:[~2012-03-17 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 14:19 Eric S. Raymond
2012-03-17 21:23 ` 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='CAFv7OijGw9_0wQfm_hT_M0hDOriF2NP6PN-E4t=LFYCfMyAOxQ@mail.gmail.com' \
--to=tz2026@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