From: Dave Taht <dave.taht@gmail.com>
To: esr@thyrsus.com
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] the serial alternative/radio noise
Date: Mon, 12 Mar 2012 15:59:40 -0700 [thread overview]
Message-ID: <CAA93jw5dyt0RhEY2bSthmqcpggVkTvdPOdb0Bo4bZGR-cuhGBA@mail.gmail.com> (raw)
In-Reply-To: <20120312220623.GB18256@thyrsus.com>
On Mon, Mar 12, 2012 at 3:06 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> Dave Taht <dave.taht@gmail.com>:
>> I AM curious if there is one of the gps boards we've looked at than
>> can 'just fit' on this header. Or, for that matter, a RTC.
>
> How often do I have to sing the "this kind of customization won't scale"
> song?
Cats, herding.
I note that in the early stages of any project, I tend to appreciate
all sorts of blue-sky thinking, rather than tie down to any one goal,
and try to encourage such in others. I guess in part what drives me in
suggesting alternatives (and please note my alternative above was
intended as a lead-in into the noise question more than an actual
suggestion), is that I would like to find markets for a 'new device',
that 'does new stuff', that justifies the manufacturing run, more than
a 'usb gps with hyper-accurate pps and time output' may, as a
differentiator.
To give an example I've long had an interest in climate change, in
particular, in the lack of good data from equatorial zones. I had
intended while I was still working on my mesh project in Nicaragua to
co-locate weather stations with at least some nodes, (multiple open
source and open hardware alternatives are available, google for them),
and in that case - given that the network might be down or
non-existent, having good time for the samples also seemed good (as
well as a good location indicator! See
http://www.teklibre.com/~d/b4barrios10.kml for an interactive map of
the sites I'd surveyed with my handheld gps below san juan del sur,
Nicaragua).
http://oscirrus.see-do.org/schematics/schematics.html for one weather
station (this isn't the one I was thinking of at the time, tho)
Anyway, this is a potential market use-case for the hardware as
discussed thus far. There are no doubt others.
>
>> Now, I actually brought this up because in looking at this I realized
>> anew what a huge radiator of various forms of electronic noise this
>> is. - 2.4ghz and 5.x ghz radios, and a variety of possible waveforms
>> from the cpu - and I'm curious as to what extent gps is affected by
>> these frequencies.
>
> You and I have observational evidence that it's not an issue even for
> low-end, poorly-shielded hardware,
I have observational evidence that we have problems with many kinds of
hardware and the cause is undefined, and varies by manufacturer.
> --
> <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-03-12 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 21:54 Dave Taht
2012-03-12 22:01 ` tz
2012-03-12 22:06 ` Eric S. Raymond
2012-03-12 22:59 ` Dave Taht [this message]
2012-03-12 23:22 ` Dave Taht
2012-03-12 23:51 ` Dave Taht
2012-03-13 1:31 ` Eric S. Raymond
2012-03-13 1:26 ` Patrick Maupin
2012-03-13 2:46 ` Ron Frazier (NTP)
2012-03-13 1:28 ` 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=CAA93jw5dyt0RhEY2bSthmqcpggVkTvdPOdb0Bo4bZGR-cuhGBA@mail.gmail.com \
--to=dave.taht@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