All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Christian Trefzer <ctrefzer@gmx.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jan Knutar <jk-lkml@sci.fi>,
	Pau Garcia i Quiles <pgquiles@elpauer.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [IDEA] Poor man's UPS
Date: Mon, 22 May 2006 11:05:55 -0600	[thread overview]
Message-ID: <4471EF73.1030100@wolfmountaingroup.com> (raw)
In-Reply-To: <20060522154830.GA5344@hermes.uziel.local>

Christian Trefzer wrote:

>On Mon, May 22, 2006 at 04:40:58PM +0100, Alan Cox wrote:
>  
>
>>Lead acid batteries should be kept well charged to avoid sulphation and
>>always full charged when recharging, preferably using a charger that
>>will do proper three step charging. "Cycling" a lead acid battery is a
>>great way to destroy it.
>>
>>    
>>
>
>So it is better to use only one battery (or an array thereof) which is
>sort of charged and discharged at the same time, or is this idea just as
>screwed..? I don't have a degree in electronics, mind you : )
>
>Might be easier to build something that keeps a battery well maintained
>and switches in case of power outage. With large enough condensors to
>bridge the gap, which would also iron out any peaks and stuff, this
>should work pretty well.
>
>Kind regards,
>Chris
>  
>
You know, these old lead acid batteries are a fire hazard, not to 
mention they produce free hydrogen gas when discharging to charging.

Guys, stick to nicads or a fuel cell to avoid burning down your house or 
the neighborhood.  Ever see a lead acid battery explode?  I have.  It 
throws sulphuric acid all over the place.

Jeff

  parent reply	other threads:[~2006-05-22 16:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 19:31 [IDEA] Poor man's UPS 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
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 [this message]
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=4471EF73.1030100@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ctrefzer@gmx.de \
    --cc=jk-lkml@sci.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.