Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: thumbgps-devel@lists.bufferbloat.net
Subject: [Thumbgps-devel] quake sensing
Date: Mon, 4 Jun 2012 09:09:40 -0400	[thread overview]
Message-ID: <CAA93jw4SqU3XNZDo8YeZsup16q97YHL=tt9FGjC-sYRvoUnmTg@mail.gmail.com> (raw)

I have obtained one of the onavi-B sensors to play with

The quake sensor stanford is distributing is the
onavi-A and onavi-B, shown here:

http://qcn.stanford.edu/sensor-performance?lang=en

It uses a KXRB5 MEMS accelerometer from Kionix.

My intent, originally, was to see if I could find a way to combine
it with a ublox GPS over the internal i2c bus. It looks
like that will require using a different ublox-6 chip than in
the macx-1 with rewritable firmware and a firmware license, and...
well... maybe going some other route like leveraging
an arduino would be saner(?)

At the moment however, I'm trying to figure
out if there are any better MEMS sensors out there, or
better ways to hook them up than this device
which appears to have it's own protocol, running over
serial...

http://qcn.stanford.edu/join-qcn/request-a-sensor/sensor49-php

The qcn.stanford.edu idea is pretty neat. it's designed for boinc
after the fact analysis (and there is linux support)

The USGS has got a fairly decent looking prototype of an early warning system,
but their outside estimates for warning time is 20 seconds, presently, after
what they've designed is fully deployed. (and they are 100m short on funding)

http://blogs.laweekly.com/informer/2012/04/earthquake_warning_los_angeles_usgs.php


-- 
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/

             reply	other threads:[~2012-06-04 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 13:09 Dave Taht [this message]
2012-06-04 14:25 ` tz

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='CAA93jw4SqU3XNZDo8YeZsup16q97YHL=tt9FGjC-sYRvoUnmTg@mail.gmail.com' \
    --to=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