<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How should embedded systems handle battery failures?</title>
	<atom:link href="http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/</link>
	<description>Shedding Light on the Hidden World of Embedded Systems</description>
	<lastBuildDate>Mon, 28 Jul 2014 16:18:37 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: A. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10920</link>
		<dc:creator>A. @ LI</dc:creator>
		<pubDate>Fri, 23 Dec 2011 00:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10920</guid>
		<description>Money talks - the economics of production would say that if battery is not replaceable then one can design all protection and capacity estimation using model of layers and hid all implementation in an expensive rechargeable battery. However, if the battery is relatively cheap and disposable then it needs to be relatively inexpensive (low device service cost) and it does make sense to keep the logic with he embedded system that consumes the energy rather than to throw away another small embedded system each time you replace a battery. Of course, protection against critical failure (explosion) should be included with the battery because it is safety critical. 

On the side comment I haven&#039;t seen a &quot;gas&quot; car battery with such protection and one such car battery did explode on me some twenty years ago. Fortunately, without causing permanent damage to me at that time. /* I know, car as a whole is not an embedded system. */</description>
		<content:encoded><![CDATA[<p>Money talks &#8211; the economics of production would say that if battery is not replaceable then one can design all protection and capacity estimation using model of layers and hid all implementation in an expensive rechargeable battery. However, if the battery is relatively cheap and disposable then it needs to be relatively inexpensive (low device service cost) and it does make sense to keep the logic with he embedded system that consumes the energy rather than to throw away another small embedded system each time you replace a battery. Of course, protection against critical failure (explosion) should be included with the battery because it is safety critical. </p>
<p>On the side comment I haven&#8217;t seen a &#8220;gas&#8221; car battery with such protection and one such car battery did explode on me some twenty years ago. Fortunately, without causing permanent damage to me at that time. /* I know, car as a whole is not an embedded system. */</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10919</link>
		<dc:creator>B. @ LI</dc:creator>
		<pubDate>Fri, 23 Dec 2011 00:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10919</guid>
		<description>@Barry Kogan: I think that the approach you suggest is usable in embedded systems that have no user interaction at all, and no control from other devices, BUT, any system can use more significant battery information to extend the battery lifetime.

From the cost perspective, embedding more intelligence in the battery pack moves a cost factor out of the BOM control of the embedded system developer, so that all systems would need to pay, or there would be an explosion of battery types, each with there own level of battery control/protection... As I stated previously, it makes a lot of sense to have protection included in the battery/cell against catastrophic failure modes, but I believe that it makes more sense to have &#039;gas gauges&#039; and lifetime estimates done in higher-level software and hardware... The world is open to many opinions :-)</description>
		<content:encoded><![CDATA[<p>@Barry Kogan: I think that the approach you suggest is usable in embedded systems that have no user interaction at all, and no control from other devices, BUT, any system can use more significant battery information to extend the battery lifetime.</p>
<p>From the cost perspective, embedding more intelligence in the battery pack moves a cost factor out of the BOM control of the embedded system developer, so that all systems would need to pay, or there would be an explosion of battery types, each with there own level of battery control/protection&#8230; As I stated previously, it makes a lot of sense to have protection included in the battery/cell against catastrophic failure modes, but I believe that it makes more sense to have &#8216;gas gauges&#8217; and lifetime estimates done in higher-level software and hardware&#8230; The world is open to many opinions <img src='http://www.embeddedinsights.com/channels/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10816</link>
		<dc:creator>B. @ LI</dc:creator>
		<pubDate>Tue, 20 Dec 2011 15:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10816</guid>
		<description>I think in the embedded system batteries has to be treated as a black box providing energy with the indication to the software with substantial accuracy when energy supply is going to end, sort of progress bar. This will give software the way to do its own maintanence, optimization and learning how to stay longer. The complexity of a battery implementation should be completely confined to the battery. The system which uses it should have no knowldege other than when the energy will end exactly.</description>
		<content:encoded><![CDATA[<p>I think in the embedded system batteries has to be treated as a black box providing energy with the indication to the software with substantial accuracy when energy supply is going to end, sort of progress bar. This will give software the way to do its own maintanence, optimization and learning how to stay longer. The complexity of a battery implementation should be completely confined to the battery. The system which uses it should have no knowldege other than when the energy will end exactly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10677</link>
		<dc:creator>S. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10677</guid>
		<description>Hi Barry,

It was your name attached to this topic that triggered my attention. And I couldn&#039;t resist. I have so many stories related to batteries. My interest grew significantly after I purchased a hybrid car in 2007. And, yes, there is a story attached to this car and... some frustrations. As I said, I will return with details because my story has something to do (indirectly) with our own jobs. But I need more time to order the facts and put it in the context.

I agree that batteries are &quot;smarter&quot; every day. There is a danger here as well: being smart means being more complex and being complex means being more exposed to &quot;soft&quot;(ware) failures. Are we relying too much on the intelligence we embed into all these devices? Is this slowing the penetration of other technologies that may not require sophistication to solve the same problem?

When I asked this question I had in mind MRAM vs flash memory: despite of all its qualities, MRAM has not been widely adopted by the market but companies rather spend a lot of resources and effort on error correction and wear leveling algorithms (see the latest news regarding Anobit that developed very complex algorithms that would allow unreliable MLC NAND to be used, well... more reliably!!!). Aren&#039;t we in the same situation with Lion batteries? Maybe we just lost the ability to see (and to search for) more fundamentally simpler solutions...

At 3 am in the morning I&#039;m becoming too emotional :-)</description>
		<content:encoded><![CDATA[<p>Hi Barry,</p>
<p>It was your name attached to this topic that triggered my attention. And I couldn&#8217;t resist. I have so many stories related to batteries. My interest grew significantly after I purchased a hybrid car in 2007. And, yes, there is a story attached to this car and&#8230; some frustrations. As I said, I will return with details because my story has something to do (indirectly) with our own jobs. But I need more time to order the facts and put it in the context.</p>
<p>I agree that batteries are &#8220;smarter&#8221; every day. There is a danger here as well: being smart means being more complex and being complex means being more exposed to &#8220;soft&#8221;(ware) failures. Are we relying too much on the intelligence we embed into all these devices? Is this slowing the penetration of other technologies that may not require sophistication to solve the same problem?</p>
<p>When I asked this question I had in mind MRAM vs flash memory: despite of all its qualities, MRAM has not been widely adopted by the market but companies rather spend a lot of resources and effort on error correction and wear leveling algorithms (see the latest news regarding Anobit that developed very complex algorithms that would allow unreliable MLC NAND to be used, well&#8230; more reliably!!!). Aren&#8217;t we in the same situation with Lion batteries? Maybe we just lost the ability to see (and to search for) more fundamentally simpler solutions&#8230;</p>
<p>At 3 am in the morning I&#8217;m becoming too emotional <img src='http://www.embeddedinsights.com/channels/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10674</link>
		<dc:creator>B. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10674</guid>
		<description>Hi Stefan!
RE: constant-power laod curves: I wasn&#039;t trying to intimate that most loads are constant-power, but that constant-resistance loads are not at all common, and other types of battery discharge information presentation can yield useful, indeed critical, insight... anyway...

It&#039;s a nice point about a system being so tightly-designed around a particular energy cureve that it can&#039;t handle an &#039;unforeseen&#039; battery chemistry (or quality) being used, especially if the batteries are replaceable, standard-sized cells like AA/AAA, et al ... I would have hoped that under-voltage detect would be used, but seems that someone forgot that aspect in your radio; maybe saved 3 cents ;-)

In cell phones, the volumes are so high, the cells are built-to-fit, and every milli-Joule needs to be dragged out, plus safety concerns, plus user expectation, that we really design a lot of the circuitry to maximise energy use in just that narrow band of specifications... and, now, with digital interfacing being built into the cells, it&#039;s possible to get quite intimate knowledge of a cell that is plugged in. That, again, goes to the earlier comments on putting protection and monitoring at the &#039;right&#039; layer of the hardware/software stack.</description>
		<content:encoded><![CDATA[<p>Hi Stefan!<br />
RE: constant-power laod curves: I wasn&#8217;t trying to intimate that most loads are constant-power, but that constant-resistance loads are not at all common, and other types of battery discharge information presentation can yield useful, indeed critical, insight&#8230; anyway&#8230;</p>
<p>It&#8217;s a nice point about a system being so tightly-designed around a particular energy cureve that it can&#8217;t handle an &#8216;unforeseen&#8217; battery chemistry (or quality) being used, especially if the batteries are replaceable, standard-sized cells like AA/AAA, et al &#8230; I would have hoped that under-voltage detect would be used, but seems that someone forgot that aspect in your radio; maybe saved 3 cents <img src='http://www.embeddedinsights.com/channels/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>In cell phones, the volumes are so high, the cells are built-to-fit, and every milli-Joule needs to be dragged out, plus safety concerns, plus user expectation, that we really design a lot of the circuitry to maximise energy use in just that narrow band of specifications&#8230; and, now, with digital interfacing being built into the cells, it&#8217;s possible to get quite intimate knowledge of a cell that is plugged in. That, again, goes to the earlier comments on putting protection and monitoring at the &#8216;right&#8217; layer of the hardware/software stack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10673</link>
		<dc:creator>S. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10673</guid>
		<description>I&#039;m not an expert in batteries and I don&#039;t work in such industry, but I&#039;ve been curious and I also had to implement some power management algorithms in my projects. 
Here are some resources that I found useful:

http://batteryuniversity.com/ 

The guy who keeps this site started his own company - Cadex- years ago. The company produces battery analyzers, chargers and testers. 

I would also recommend &quot;Linden&#039;s Handbook of Batteries&quot; - the 4th edition was released in 2010 (see http://www.amazon.com/Lindens-Handbook-Batteries-Thomas-Reddy/dp/007162421X ).

I hope it may help someone.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not an expert in batteries and I don&#8217;t work in such industry, but I&#8217;ve been curious and I also had to implement some power management algorithms in my projects.<br />
Here are some resources that I found useful:</p>
<p><a href="http://batteryuniversity.com/" rel="nofollow">http://batteryuniversity.com/</a> </p>
<p>The guy who keeps this site started his own company &#8211; Cadex- years ago. The company produces battery analyzers, chargers and testers. </p>
<p>I would also recommend &#8220;Linden&#8217;s Handbook of Batteries&#8221; &#8211; the 4th edition was released in 2010 (see <a href="http://www.amazon.com/Lindens-Handbook-Batteries-Thomas-Reddy/dp/007162421X" rel="nofollow">http://www.amazon.com/Lindens-Handbook-Batteries-Thomas-Reddy/dp/007162421X</a> ).</p>
<p>I hope it may help someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10672</link>
		<dc:creator>S. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10672</guid>
		<description>And many loads are anything but constant power - if we consider cell phones, laptops, tablets or... hybrid vehicles. Problems are far more complex and I know enough stories of apparently straightforward designs that went wrong from various reasons. I will return with one at another time. I will stop now at the discharge problem.

The rapid discharge phenomenon is rather visible in the case of NiMH or NiCad chemistry. The following story is just an example -- this is when I became aware of it.

I have a relatively old and cheap digital radio (~15 years old design) that was probably designed for alkaline batteries; to change the batteries you have to turn off the radio (digital on/off that put the electronics in standby) and rely on an internal capacitor capable to maintain the settings for about 1...2 minutes (depending on the battery voltage at the replacement time).

Because alkaline batteries have lower capacity than modern NiMH rechargeables, I switched to NiMH but with a &quot;side effect&quot;. When the battery is discharged enough to make the radio barely usable on AM and unusable on FM, I cannot turn it off (put it in standby) anymore and I cannot change the batteries without losing all the settings because the internal capacitor gets drained quickly by the still active electronics.

It is obvious that the designer never had in mind such a sudden voltage drop (usually from 1.2V to 0.9V in 10...15 seconds) and the controller that handles the user keys (including the on/off button) does not respond to any user actions anymore. So, I end up reprogramming the settings after changing the batteries (i.e. setting the clock/alarm and 15 stations).

So, as designers we need to anticipate far more than our educated minds tell us in the first place. Users are always unpredictable and very inventive. Conditions may vary a lot as well in patterns that may never be anticipated enough (see the Chevy Volt case).

Like most of the current software that we have to deal with every day (see patches, updates, upgrades, etc) - perfection is an almost unachievable goal. Designing embedded systems, especially those used in safety critical applications, becomes a daunting task that very few are willing to appreciate. It is probably one of the most difficult jobs in the high-tech industry - and I&#039;m not saying this because I am an Embedded Engineer.

The battery management problem is just another issue that we have to deal with. A really challenging one...</description>
		<content:encoded><![CDATA[<p>And many loads are anything but constant power &#8211; if we consider cell phones, laptops, tablets or&#8230; hybrid vehicles. Problems are far more complex and I know enough stories of apparently straightforward designs that went wrong from various reasons. I will return with one at another time. I will stop now at the discharge problem.</p>
<p>The rapid discharge phenomenon is rather visible in the case of NiMH or NiCad chemistry. The following story is just an example &#8212; this is when I became aware of it.</p>
<p>I have a relatively old and cheap digital radio (~15 years old design) that was probably designed for alkaline batteries; to change the batteries you have to turn off the radio (digital on/off that put the electronics in standby) and rely on an internal capacitor capable to maintain the settings for about 1&#8230;2 minutes (depending on the battery voltage at the replacement time).</p>
<p>Because alkaline batteries have lower capacity than modern NiMH rechargeables, I switched to NiMH but with a &#8220;side effect&#8221;. When the battery is discharged enough to make the radio barely usable on AM and unusable on FM, I cannot turn it off (put it in standby) anymore and I cannot change the batteries without losing all the settings because the internal capacitor gets drained quickly by the still active electronics.</p>
<p>It is obvious that the designer never had in mind such a sudden voltage drop (usually from 1.2V to 0.9V in 10&#8230;15 seconds) and the controller that handles the user keys (including the on/off button) does not respond to any user actions anymore. So, I end up reprogramming the settings after changing the batteries (i.e. setting the clock/alarm and 15 stations).</p>
<p>So, as designers we need to anticipate far more than our educated minds tell us in the first place. Users are always unpredictable and very inventive. Conditions may vary a lot as well in patterns that may never be anticipated enough (see the Chevy Volt case).</p>
<p>Like most of the current software that we have to deal with every day (see patches, updates, upgrades, etc) &#8211; perfection is an almost unachievable goal. Designing embedded systems, especially those used in safety critical applications, becomes a daunting task that very few are willing to appreciate. It is probably one of the most difficult jobs in the high-tech industry &#8211; and I&#8217;m not saying this because I am an Embedded Engineer.</p>
<p>The battery management problem is just another issue that we have to deal with. A really challenging one&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10671</link>
		<dc:creator>B. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10671</guid>
		<description>@Michael; thanks for that link... one thing I noticed, immediately, is that the discharge graph is not shown in modes that are more useful to modern designers: instead of simple fixed-resistance discharge-volatge curves, they should be showing energy-available discharge curves, or constant-power discharge curves, both discharge time/voltage and discharge-time/remaining energy or percentage life.

Many loads that are in use today are likely to be constant-power; even LED flashlights, typically, have a DC/DC converter to deliver constant power to the LED over the discharge voltage of the cell/battery pack.</description>
		<content:encoded><![CDATA[<p>@Michael; thanks for that link&#8230; one thing I noticed, immediately, is that the discharge graph is not shown in modes that are more useful to modern designers: instead of simple fixed-resistance discharge-volatge curves, they should be showing energy-available discharge curves, or constant-power discharge curves, both discharge time/voltage and discharge-time/remaining energy or percentage life.</p>
<p>Many loads that are in use today are likely to be constant-power; even LED flashlights, typically, have a DC/DC converter to deliver constant power to the LED over the discharge voltage of the cell/battery pack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10670</link>
		<dc:creator>M. @ LI</dc:creator>
		<pubDate>Sat, 17 Dec 2011 15:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10670</guid>
		<description>The best place to get information on good quality alakaline batteries is on the manufacturers website, eg www.duracell.com (follow the B2B trail). Or you can get to the same information via distributors like Farnell.
I don&#039;t fully agree with Franz about the sudden loss of voltage - take a look at the Duracell data for standard alakaline AA at 
http://professional.duracell.com/downloads/datasheets/product/Simply/Simply_AA_MN1500.pdf 

In my experience the big problem is that even f you provide a good quality battery holder and electronics that works correctly down to 0.8V per cell the end user then defeats all your efforts by using rubbish batteries from some no-name source. These are not backed up by any specification and may very well fail as Franz describes.</description>
		<content:encoded><![CDATA[<p>The best place to get information on good quality alakaline batteries is on the manufacturers website, eg <a href="http://www.duracell.com" rel="nofollow">http://www.duracell.com</a> (follow the B2B trail). Or you can get to the same information via distributors like Farnell.<br />
I don&#8217;t fully agree with Franz about the sudden loss of voltage &#8211; take a look at the Duracell data for standard alakaline AA at<br />
<a href="http://professional.duracell.com/downloads/datasheets/product/Simply/Simply_AA_MN1500.pdf" rel="nofollow">http://professional.duracell.com/downloads/datasheets/product/Simply/Simply_AA_MN1500.pdf</a> </p>
<p>In my experience the big problem is that even f you provide a good quality battery holder and electronics that works correctly down to 0.8V per cell the end user then defeats all your efforts by using rubbish batteries from some no-name source. These are not backed up by any specification and may very well fail as Franz describes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/11/30/how-should-embedded-systems-handle-battery-failures/#comment-10640</link>
		<dc:creator>B. @ LI</dc:creator>
		<pubDate>Fri, 16 Dec 2011 22:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=663#comment-10640</guid>
		<description>Thanks very much for the comments on Alkaline... Can you point me/us at some solid information on alkaline cell performance &amp; characteristics?</description>
		<content:encoded><![CDATA[<p>Thanks very much for the comments on Alkaline&#8230; Can you point me/us at some solid information on alkaline cell performance &amp; characteristics?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
