<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nrf52832: Modifying the prescaler value to save battery life</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24070/nrf52832-modifying-the-prescaler-value-to-save-battery-life</link><description>Hello, 
 I&amp;#39;m currently running our RTC using the default resolution of 32.768 kHz (30.517 micro-seconds), which means that we are not prescaling. If I desire to have a larger resolution (less overflow in the 24-bit counter) of say, 0.5ms (instead of</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 04 Aug 2017 12:07:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24070/nrf52832-modifying-the-prescaler-value-to-save-battery-life" /><item><title>RE: nrf52832: Modifying the prescaler value to save battery life</title><link>https://devzone.nordicsemi.com/thread/94785?ContentTypeID=1</link><pubDate>Fri, 04 Aug 2017 12:07:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88a2eb75-ea50-4cec-a800-4673533dd1ef</guid><dc:creator>John</dc:creator><description>&lt;p&gt;Good points&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832: Modifying the prescaler value to save battery life</title><link>https://devzone.nordicsemi.com/thread/94786?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 23:45:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ca838b9-a1e1-4cdc-ba2a-d1c6d8f0e603</guid><dc:creator>Roger Clark</dc:creator><description>&lt;p&gt;The OP has not said what advertising interval or power level etc they are using.&lt;/p&gt;
&lt;p&gt;Changing the advertising interval would most likely have a much bigger impact on total power consumption.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve also heard of solutions that use an external device to do the lower power timing.&lt;/p&gt;
&lt;p&gt;e.g put the MCU into its deepest sleep mode when its not being used and let the external (ultra low power) timer device, wake it via interrupt.&lt;/p&gt;
&lt;p&gt;But the OP would need to model their individual set of circumstances to see what would give the minimal power usage.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832: Modifying the prescaler value to save battery life</title><link>https://devzone.nordicsemi.com/thread/94784?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 20:06:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e09d02c-4e32-4343-bcee-235c2a296023</guid><dc:creator>John</dc:creator><description>&lt;p&gt;I don&amp;#39;t imagine that there is a lot of power savings to be gained by the prescaler unless it changes how often you come out of IDLE mode. Once the RTC peripheral is on I think it would burn about the same amount of power regardless of the prescaler. The data sheet indicates that it&amp;#39;s typical power consumption is 0.1uA so there isn&amp;#39;t a lot to gain there.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>