From: Christian Trefzer <ctrefzer@gmx.de>
To: Pau Garcia i Quiles <pgquiles@elpauer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [IDEA] Poor man's UPS
Date: Mon, 22 May 2006 00:40:12 +0200 [thread overview]
Message-ID: <20060521224012.GB30855@hermes.uziel.local> (raw)
In-Reply-To: <200605212131.47860.pgquiles@elpauer.org>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hi there,
On Sun, May 21, 2006 at 09:31:30PM +0200, Pau Garcia i Quiles wrote:
> [interesting idea with complex implementational problems]
I think it would be cheaper ("costs" for your solutin in terms of
required I/O power and hard disk space) to use two or more lead
batteries which are charged and discharged in a round-robin fashion,
controlled by some smart home-brew circuitry, and connect the beast to
some control/monitoring software via RS-232 ; )
The logic should at least completely drain the battery before
recharging, and maybe even do a quick-and-hot charge-discharge-charge
cycle every now and then to reduce chemical byproducts at the cathode -
or was it the anode? Well, one of them is dissolved over time, and the
other one collects some sulfate or sulfide or something. If you want it
really complicated and robust, you might want to monitor the electric
parameters of the batteries at all times, to estimate the minimum
remaining time once the power is cut. You'd then have to shut down, or
better hibernate, the system cleanly within that time frame to be safe
from data loss.
I'd love to do something like that sort of in-between the PSU for a
single machine, for this would avoid the need to go from AC to DC and
back, but lacking the electrotechnical skills I'm not self-confident
enough to try and waste my PSU. Anyway, this has gone way off-topic by
now.
Kind regards,
Chris
[-- Attachment #2: Type: application/pgp-signature, Size: 829 bytes --]
next prev parent reply other threads:[~2006-05-21 22:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 19:31 Pau Garcia i Quiles
2006-05-21 19:38 ` Dave Jones
2006-05-21 19:46 ` Michael Buesch
2006-05-22 8:19 ` Avi Kivity
2006-05-22 10:54 ` Jan Engelhardt
2006-05-21 22:40 ` Christian Trefzer [this message]
2006-05-22 13:04 ` Jan Knutar
2006-05-22 13:29 ` linux-os (Dick Johnson)
2006-05-22 15:25 ` Christian Trefzer
2006-05-22 15:54 ` linux-os (Dick Johnson)
2006-05-22 19:34 ` Christian Trefzer
2006-05-22 15:13 ` Christian Trefzer
2006-05-22 15:40 ` Alan Cox
2006-05-22 15:48 ` Christian Trefzer
2006-05-22 16:15 ` Matthias Schniedermeyer
2006-05-22 19:40 ` Christian Trefzer
2006-05-22 19:45 ` Avi Kivity
2006-05-23 2:02 ` Martin J. Bligh
2006-05-22 19:46 ` Nuri Jawad
2006-05-22 22:40 ` Christian Trefzer
2006-05-22 17:05 ` Jeff V. Merkey
2006-05-21 23:02 ` Neil Brown
2006-05-22 0:08 ` Chris Wedgwood
2006-05-22 0:23 ` Neil Brown
2006-05-22 1:29 ` Björn Steinbrink
2006-05-22 1:44 ` Neil Brown
2006-05-22 9:29 ` Pavel Machek
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=20060521224012.GB30855@hermes.uziel.local \
--to=ctrefzer@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pgquiles@elpauer.org \
/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
all inboxes | Powered by JetHome®