From: tz <thomas@mich.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net,
veronica <veronica@navisys.com.tw>,
tcf@navisys.com.tw, Jau-Yang Chen <cjy@navisys.com.tw>,
gloria@navisys.com.tw, lily <lily@navisys.com.tw>
Subject: Re: [Thumbgps-devel] Article -- Macx-1: GPS receiver with standard USB connector and PPS support
Date: Wed, 9 May 2012 13:12:06 -0400 [thread overview]
Message-ID: <CAFv7OihBDpT20Rnqy4J4_GvGzJwzU==H1KWy2fAVX24A7nwP=Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6gVxEg+gHC66n3p4kf-2X7eMMGO6OW1toY6htx1HBSsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
For a given size (and circuit board footprint) a supercap will have much
less capacity and it has an exponential voltage decay curve, so it might
have plenty of charge but not at a voltage that will hold the data. This
usually means hours, not days of backup.
A good rechargeable lithium will last several years, maybe longer as there
will be no charge/discharge, maintains voltage until it is nearly
exhausted, and can hold the data for days or weeks.
On Wed, May 9, 2012 at 12:55 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Wed, May 9, 2012 at 9:47 AM, Eric S. Raymond <esr@thyrsus.com> wrote:
> > Dave Taht <dave.taht@gmail.com>:
> >> What would be the change in cost and delay in manufacturing to switch to
> >> using a supercap, rather than battery?
> >
> > Why would a supercap be better?
>
> Effective lifetime of... forever. no need for replacement. insanely
> fast recharge. smaller (probably). What's not to like?
>
> I am not in a huge hurry to get into manufacturing, and I merely
> wanted to cost out what what it would do to the bom, any changes to
> the PCB, and get an estimate for the time it would take to do. I think
> it will bump the unit cost up slightly,
> but what price, forever?
>
> > --
> > <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
> _______________________________________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/thumbgps-devel
>
[-- Attachment #2: Type: text/html, Size: 2509 bytes --]
next prev parent reply other threads:[~2012-05-09 17:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 6:43 Jau-Yang Chen
2012-05-09 15:23 ` tz
2012-05-09 16:39 ` Dave Taht
2012-05-09 16:47 ` Eric S. Raymond
2012-05-09 16:55 ` Dave Taht
2012-05-09 17:02 ` Eric S. Raymond
2012-05-09 17:12 ` tz [this message]
2012-05-09 17:50 ` Ron Frazier (NTP)
2012-05-09 18:21 ` tz
2012-05-09 18:35 ` Dave Taht
2012-05-09 20:41 ` Ron Frazier (NTP)
2012-05-09 20:46 ` Dave Taht
2012-05-09 20:58 ` Ron Frazier (NTP)
2012-05-09 20:59 ` Dave Taht
2012-05-09 22:57 ` Ron Frazier (NTP)
2012-05-09 21:14 ` Eric S. Raymond
2012-05-09 22:30 ` tz
2012-05-09 19:43 ` Dave Hart
2012-05-09 20:37 ` Eric S. Raymond
2012-05-09 21:03 ` Dave Hart
2012-05-09 21:18 ` Ron Frazier (NTP)
2012-05-09 21:38 ` Eric S. Raymond
2012-05-09 22:02 ` Dave Hart
2012-05-10 6:31 ` Eric S. Raymond
2012-05-10 7:28 ` Dave Hart
2012-05-10 14:55 ` tz
2012-05-10 17:59 ` Eric S. Raymond
2012-05-09 21:20 ` 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='CAFv7OihBDpT20Rnqy4J4_GvGzJwzU==H1KWy2fAVX24A7nwP=Q@mail.gmail.com' \
--to=thomas@mich.com \
--cc=cjy@navisys.com.tw \
--cc=dave.taht@gmail.com \
--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