From: tz <thomas@mich.com>
To: Jau-Yang Chen <cjy@navisys.com.tw>
Cc: thumbgps-devel@lists.bufferbloat.net,
veronica <veronica@navisys.com.tw>,
tcf@navisys.com.tw, gloria@navisys.com.tw,
lily <lily@navisys.com.tw>
Subject: Re: [Thumbgps-devel] Promoting the Macx-1
Date: Thu, 10 May 2012 12:06:54 -0400 [thread overview]
Message-ID: <CAFv7Oij4X0miQNTJxFZUQUG=FNep5V205KYXJQV25Wgo4dgPzQ@mail.gmail.com> (raw)
In-Reply-To: <CAFv7OiimB4_mRAu+M155wijQ8Quqw0nyYZ=g5Mag9PBk3=5q_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4046 bytes --]
Apparently you can't get to any drivers or software without a "login". I
don't know if there are any opensource configuration utilities - but that
doesn't help if you need a driver.
On Thu, May 10, 2012 at 11:57 AM, tz <thomas@mich.com> wrote:
> The Ublox 6 document (page 136) has "Align to UTC" for the messages and
> the option to change the rate.
>
> It would be interesting to compare the jitter and offset with this set and
> not using PPS>
>
> And there is a lot of discussion on dead reckoning.
>
> On Thu, May 10, 2012 at 8:19 AM, Jau-Yang Chen <cjy@navisys.com.tw> wrote:
>
>> Dear Eric,
>>
>> Thanks again for your kind support. It's our responsibility to provide the
>> good performance product with better quality to our customers. It's really
>> the great reward for all of your help to promote Macx-1.
>>
>> For dead-reckoning and 1PPS issue, we will double check and come back to
>> you.
>>
>> The data sheet of GR-601 is also attached. You are much appreciated to
>> review and improve it.
>>
>> Best regards,
>>
>> JY
>>
>> -----Original Message-----
>> From: Eric S. Raymond [mailto:esr@thyrsus.com]
>> Sent: Thursday, May 10, 2012 2:14 AM
>> To: cjy@navisys.com.tw
>> Cc: 'veronica'; tcf@navisys.com.tw; thumbgps-devel@lists.bufferbloat.net;
>> 'lily'; gloria@navisys.com.tw
>> Subject: Promoting the Macx-1
>>
>> >From Jau-Yang Chen <cjy@navisys.com.tw>
>> > It will be great and much appreciated if we could have
>> >a channel to sell this winning product in Amazon.
>>
>> Working on it. But no result yet - I may have to go through several links
>> in a chain of references.
>>
>> > We plan to put an article as attached on our website for advertisement.
>> > Could you please review and comment?
>>
>> Have reviewed. You can quote any of that you like.
>>
>> > It will be helpful to promote Macx-1 USB
>> > GPS receiver if you could also put it in the website of your
>> > SIG/project.
>>
>> Done. Find it on <http://catb.org/gpsd/hardware.html>
>>
>> Also note that once we confirm a U.S. retail partner for you guys I will
>> promote the product on my blog and Google+. As I have over
>> 18,000 blog and G+ followers with a heavy concentration among programmers
>> and engineers who are likely GPS customers, this is exposure many vendors
>> would kill for. I have never plugged a product before; this will be your
>> reward for a job very well done.
>>
>> The market you will be selling the Macx-1 into is much more interested in
>> detailed technical information about the device than you are probably used
>> to. The datasheet for this device should list the exact uBlox chip or
>> module it uses, the NMEA version, and (most importantly!) a link to
>> programming information about the GPS engine - uBlox's technical manual on
>> programming the chip would do.
>>
>> One of our people already mentioned turning off the dead-reckoning feature
>> so the device won't emit PPS after it has lost lock. One reason to link to
>> the technical manual is so we can determine if this is really an issue; it
>> might be the firmware stops emitting PPS in dead-reckoning mode, and
>> that's
>> exactly the sort of detail Macx-1 customers will be interested in.
>>
>> Another one of our people, Dave Taht, has inquired about customized cases.
>> That gives me an interesting marketing idea. Look at the GPSD project
>> logo
>> at <http://catb.org/gpsd/gpsd-logo-small.png>. That's a Linux penguin
>> with
>> GPS satellites orbiting it. You might want to think about doing a batch
>> of
>> these with the logo on the case - with a little promotion they'd probably
>> sell like crazy to Linux fans.
>>
>> My offer to review and improve the English version of your technical
>> documentation is still open.
>> --
>> <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: 5771 bytes --]
prev parent reply other threads:[~2012-05-10 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.391.1336545809.1742.thumbgps-devel@lists.bufferbloat.net>
2012-05-09 18:14 ` Eric S. Raymond
2012-05-09 18:54 ` Dave Taht
2012-05-10 6:19 ` Eric S. Raymond
2012-05-10 6:34 ` Dave Taht
2012-05-10 7:00 ` [Thumbgps-devel] Improving the GPSD logo? Eric S. Raymond
2012-05-10 12:19 ` [Thumbgps-devel] Promoting the Macx-1 Jau-Yang Chen
2012-05-10 15:57 ` tz
2012-05-10 16:06 ` 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='CAFv7Oij4X0miQNTJxFZUQUG=FNep5V205KYXJQV25Wgo4dgPzQ@mail.gmail.com' \
--to=thomas@mich.com \
--cc=cjy@navisys.com.tw \
--cc=gloria@navisys.com.tw \
--cc=lily@navisys.com.tw \
--cc=tcf@navisys.com.tw \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=veronica@navisys.com.tw \
/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