lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B28AAFC.5010108@warmcat.com>
Date:	Wed, 16 Dec 2009 09:40:12 +0000
From:	Andy Green <andy@...mcat.com>
To:	Stanislav Brabec <utx@...guin.cz>
CC:	Aras Vaichas <arasv@...ellan-technology.com>,
	Bill Gatliff <bgat@...lgatliff.com>, thommycheck@...il.com,
	Linus Walleij <linus.walleij@...ricsson.com>,
	linux-embedded@...r.kernel.org, lenz@...wisc.edu,
	dbaryshkov@...il.com, Brian Swetland <swetland@...gle.com>,
	arminlitzel@....de,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	LKML <linux-kernel@...r.kernel.org>, Dirk@...er-online.de,
	cbou@...l.ru, rpurdie@...ys.net, omegamoon@...il.com,
	Pavel Machek <pavel@....cz>, Cyril Hrubis <metan@....cz>,
	eric.y.miao@...il.com, dwmw2@...radead.org,
	zaurus-devel@...ts.linuxtogo.org,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [POWER] battery calibration parameters from sysfs

On 12/15/09 23:32, Somebody in the thread at some point said:

Hi -

>> Yes, but in that case you might as well just purchase a coulomb
>> counter with a built-in accumulator and an I2C/SPI/microwire interface
>> save yourself some PCB space and cost (maybe)
>
> Well, Pavel attempts to implement a "poor man's Coulomb counter" or at
> least "poor man's Ampere meter" for devices that are not equipped with
> any of it.

I think the "poor man's Coulomb counter" is a loser, the errors will 
overwhelm you too rapidly.  The estimated rate of discharge could work, 
based on what clocks, regulators and so on are running, but I am not 
sure how useful that number is really given you can't realistically 
integrate it due to the big error it is bound to have.

I didn't see it mentioned yet but the biggest problem I saw with battery 
state monitoring by voltage alone is what happens during charging: the 
charger is artificially raising the voltage by an amount depending on 
current limit in the charger and battery capacity level.  That's what 
you see when you go and look at battery voltage during charging.

Otherwise for L-ion batteries, looking at the voltage level alone, 
filtered to remove GSM transmit slots etc, is really quite workable for 
estimating charge status.

-Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ