From: tz <thomas@mich.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Tue, 13 Mar 2012 10:35:36 -0400 [thread overview]
Message-ID: <CAFv7OignxpqSmqbCgV1D6_PrVbX4KcNf9FexkBX1ix7ZYSnk0A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6xSjRJnRFs-RSP=rZBa7J1DA+rsj9abE2ey4tvp5-BEg@mail.gmail.com>
A re-radiator is possible, I had one for my car but this adds to the
complexity and expense.
You can do SPI or I2C - I have the EVK so can do some firmware
customization for the SkyTraq 628 - I can only do 10Hz but I can put
data out over SPI or I2C, but that is not the problem.
The newest Arduinos use a second Atmel chip (reprogrammable!) to
translate USB to serial - it replaces the FTDI, but we would have all
the source and it should be common enough to have drivers everywhere.
I don't remember if it has an ICP. I have a different sparkfun USB
breakout Atmel chip that can be a serial adapter but has a high
resolution timer input capture the PPS could be run into.
http://arduino.cc/forum/index.php?topic=111.15
www.atmel.com/Images/7799S.pdf
The 32u2 would have space for extra things if we wanted to do things
like maintain a synchronized internal clock. We could theoretically
add I2C sensors (gyro, baro/temp, accel, magnetic compass). I had
something like this on a breadboard already 2 years ago (logged data
from a skytraq plus all these).
Note: The Skytraq chips have options to save configurations into FLASH
and SRAM or just SRAM. It also has a "ROM" option if you screw things
up but I don't know if the right pins are on the breakout.
Most other chipsets have an option save to FLASH or EEPROM
(Non-Volatile storage). We could add an EEPROM if we do our own USB
micro and do a soft reset and upload the configuration if needed.
next prev parent reply other threads:[~2012-03-13 14:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18 ` tz
2012-03-12 21:26 ` Eric S. Raymond
2012-03-12 21:28 ` Patrick Maupin
2012-03-12 21:39 ` Eric S. Raymond
2012-03-12 22:10 ` Patrick Maupin
2012-03-12 22:23 ` tz
2012-03-12 22:33 ` Patrick Maupin
2012-03-13 2:29 ` Ron Frazier (NTP)
2012-03-13 2:39 ` Chris Kuethe
2012-03-12 22:45 ` Eric S. Raymond
2012-03-12 23:01 ` Dave Taht
2012-03-13 1:43 ` Eric S. Raymond
2012-03-13 2:04 ` Chris Kuethe
2012-03-13 2:13 ` Eric S. Raymond
2012-03-13 2:40 ` Dave Taht
2012-03-13 2:53 ` Chris Kuethe
2012-03-13 4:54 ` Eric S. Raymond
2012-03-13 13:23 ` Dave Taht
2012-03-13 14:35 ` tz [this message]
2012-03-13 16:04 ` Eric S. Raymond
2012-03-13 16:22 ` tz
2012-03-13 2:38 ` Ron Frazier (NTP)
2012-03-13 2:42 ` Chris Kuethe
2012-03-13 3:00 ` Ron Frazier (NTP)
2012-03-13 3:04 ` Dave Taht
2012-03-13 3:06 ` Chris Kuethe
2012-03-13 3:16 ` Dave Taht
2012-03-13 3:31 ` Chris Kuethe
2012-03-13 4:49 ` Dave Taht
2012-03-13 4:55 ` Eric S. Raymond
2012-03-13 4:16 ` Eric S. Raymond
2012-03-12 21:40 ` tz
2012-03-12 21:27 ` Patrick Maupin
2012-03-12 21:22 ` Patrick Maupin
2012-03-12 21:37 ` Eric S. Raymond
2012-03-12 21:45 ` Patrick Maupin
2012-03-12 22:02 ` 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=CAFv7OignxpqSmqbCgV1D6_PrVbX4KcNf9FexkBX1ix7ZYSnk0A@mail.gmail.com \
--to=thomas@mich.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