Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: tz <tz2026@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Project clarification
Date: Tue, 13 Mar 2012 23:05:14 -0400	[thread overview]
Message-ID: <CAFv7Oig842U9MYMS0hgBFRnAK3-dbqj85NQGTYaEUWFQx6idZg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw79NC1D25MeCaxmp4x2X8jZByQb9rtZ1Ymy_OA-APzbSA@mail.gmail.com>

A few other observations:

Many of the SoCs used in the cheap routers have other on-chip
perhpherals which can get us past the USB.  I think I can get an
Atmega to be a time-source synced to UTC.

We could send an event OUT the USB host and timestamp it at the
device, returning when it saw it - this might be more accurate if this
is more granular than polling.

We don't know yet if LinuxPPS - kernel interrupt driven timestamping
is needed, but will probably be much more precise.

No one has suggested turning this into a time peripheral, but that
might be easier - if a microcontroller could be synced and made
accurate enough (varactor like the old Heathkit clocks?) then all the
gettime calls could go out to our device and get precise time.  Of
course the kernel could sync its time easily as well.

There are faster than PPS, e.g. the Garmin 18LVx-5Hz has 5 pulses per
second, at each 200mS interval, one of the 5 is the precise UTC, the
others are precise too.

The Sparkfun module plus either active antenna that goes with it makes
it easy to receive GPS - having a dongle with a small strip antenna
that you have to fiddle a lot with to get a good signal defeats the
purpose.  The magnetic mounts with long cables make things easy.  We
haven't talked much about antennas, but it is important.

  reply	other threads:[~2012-03-14  3:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 21:46 Mike Hord
2012-03-13 23:06 ` Eric S. Raymond
2012-03-13 23:30   ` tz
2012-03-14  1:18     ` Eric S. Raymond
2012-03-14  1:10   ` Dave Taht
2012-03-14  1:28     ` Ron Frazier (NTP)
2012-03-14  1:53       ` Eric S. Raymond
2012-03-14  3:08       ` Dave Taht
2012-03-14  3:42         ` Dave Taht
2012-03-14  4:02           ` Ron Frazier (NTP)
2012-03-14  4:32         ` Eric S. Raymond
2012-03-14 12:44           ` tz
2012-03-14  2:28     ` tz
2012-03-14  2:46       ` Dave Taht
2012-03-14  3:05         ` tz [this message]
2012-03-14  4:36           ` Patrick Maupin
2012-03-14  5:00             ` 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=CAFv7Oig842U9MYMS0hgBFRnAK3-dbqj85NQGTYaEUWFQx6idZg@mail.gmail.com \
    --to=tz2026@gmail.com \
    --cc=dave.taht@gmail.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