Article View: uk.comp.homebuilt
Article #246Re: APC SmartUPS problem
From: Graham W
Date: Sat, 12 Jun 2004 21:51
Date: Sat, 12 Jun 2004 21:51
39 lines
3403 bytes
3403 bytes
jasee wrote: > Graham W wrote: >> "Paul Hopwood" <paul@hopwood.org.uk> wrote in message >> news:4bfkc0tp79ta5cir8nvtjas5hejp6961md@4ax.com... >>> "Graham W" <graham@his.com.puter.INVALID> wrote: >>>> It would be worth checking the terminal voltage under charging >>>> conditions to make sure that the death of its predecessor wasn't >>>> down to over-charging. 13.8V is often quoted as suitable for >>>> sealed lead-acid batteries. >>> >>> According to the PowerChute software the UPS itself reports the >>> voltage at 13.85V. >> If on the other hand, the voltage was 14.2V there would be a >> suspicion >> of batterycide (is that a word? 8�), which would shortly be >> followed the demise of the new replacement. > > I'm not sure about this, provided the maximum current isn't succeeded > then I don't think there is a problem, for instance I've often > revived sealed lead acid batteries by putting the voltage up (with a > variable supply) until it starts drawing current then reduced it as > it rises to about a tenth of its rated current. This can revive dead > batteries. Sometimes I have to wack the voltage up to 20 volts or > more, before the current increases. I think overheating (which is > fatal) is caused by too great a current (when charging). You are not following the discussion! If you take a new battery and impose 14.2V across it (because of a faulty control unit), it will draw a lot of current and drive off the electrolyte. What we are not discussing is abusing *OLD* useless batteries to try and recover some useful service from them. -- Graham W http://www.gcw.org.uk/ PGM-FI page updated, Graphics Tutorial WIMBORNE http://www.wessex-astro-society.freeserve.co.uk/ Wessex Dorset UK Astro Society's Web pages, Info, Meeting Dates, Sites & Maps Change 'news' to 'sewn' in my Reply address to avoid my spam filter.
Technical Details
Message-ID:
<40cba536$0$530$ed2619ec@ptn-nntp-reader02.plus.net>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!nntp-peering.plus.net!ptn-nntp-feeder01.plus.net!ptn-nntp-spool01.plus.net!ptn-nntp-spool02.plus.net!ptn-nntp-reader02.plus.net!not-for-mailReferences:
<jfq9c01kogmrku8hedjt5hrb4k4e8ea1pj@4ax.com> <MPG.1b2f1208d82dee6a989728@news-text.blueyonder.co.uk> <k2vbc016h75ciae8ukukh91oq9kj03e0fv@4ax.com> <abfhc0pjs64qftmbhjnpg1s03ohbrh433u@4ax.com> <40c8f450$0$533$ed2619ec@ptn-nntp-reader02.plus.net> <4bfkc0tp79ta5cir8nvtjas5hejp6961md@4ax.com> <40cad429$0$527$ed2619ec@ptn-nntp-reader02.plus.net> <2j0rcjFrsokeU1@uni-berlin.de>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,CP1252 X-Google-Thread: 1063f0,32a19d7fea2ee17a X-Google-Thread: 1036bc,c36563a0f1637fe5 X-Google-Attributes: gid1063f0,gid1036bc,public Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!nntp-peering.plus.net!ptn-nntp-feeder01.plus.net!ptn-nntp-spool01.plus.net!ptn-nntp-spool02.plus.net!ptn-nntp-reader02.plus.net!not-for-mail Reply-To: "Graham W" <news@g3vpc.f9.co.uk> From: "Graham W" <graham@his.com.puter.INVALID> Newsgroups: uk.comp.homebuilt,demon.tech.pc References: <jfq9c01kogmrku8hedjt5hrb4k4e8ea1pj@4ax.com> <MPG.1b2f1208d82dee6a989728@news-text.blueyonder.co.uk> <k2vbc016h75ciae8ukukh91oq9kj03e0fv@4ax.com> <abfhc0pjs64qftmbhjnpg1s03ohbrh433u@4ax.com> <40c8f450$0$533$ed2619ec@ptn-nntp-reader02.plus.net> <4bfkc0tp79ta5cir8nvtjas5hejp6961md@4ax.com> <40cad429$0$527$ed2619ec@ptn-nntp-reader02.plus.net> <2j0rcjFrsokeU1@uni-berlin.de> Subject: Re: APC SmartUPS problem Date: Sat, 12 Jun 2004 22:51:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4922.1500 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Lines: 40 Message-ID: <40cba536$0$530$ed2619ec@ptn-nntp-reader02.plus.net> Organization: Customer of Plusnet Technologies Ltd NNTP-Posting-Host: 195.166.139.59 X-Trace: 1087087928 ptn-nntp-reader02.plus.net 530 195.166.139.59:1813 X-Complaints-To: abuse@plus.net