<?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>High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10681/high-power-consumption-with-i2c-g-sensor</link><description>We are using 51822 through I2C to get G-sensor buffer, every 560ms ( sample every 20ms, buffer for 28), then execute for step counter calculation, which should not consume much power. But the current measurement seeing, peak@4mA, rise to peak and down</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 12 Dec 2015 08:36:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10681/high-power-consumption-with-i2c-g-sensor" /><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39878?ContentTypeID=1</link><pubDate>Sat, 12 Dec 2015 08:36:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:baf2263a-e141-4980-8b8d-18ff800294c3</guid><dc:creator>sam zhou</dc:creator><description>&lt;p&gt;OK. Thanks. Will try it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39877?ContentTypeID=1</link><pubDate>Fri, 11 Dec 2015 15:22:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a5090cb2-d4ab-477e-9099-bdc4b2065214</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I have the code of I2C interface, i was playing around and interfaced it with ble_app_uart of SDK10. I can send you that code on monday when i go to office. For now you can close this case and just remind me in PM on monday.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39876?ContentTypeID=1</link><pubDate>Fri, 11 Dec 2015 11:26:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3811f7a8-6ea4-482f-93c3-47944f6070e2</guid><dc:creator>sam zhou</dc:creator><description>&lt;p&gt;Agree. DO you have sample code of this part so I can reference? thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39875?ContentTypeID=1</link><pubDate>Fri, 11 Dec 2015 07:07:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2063bfbd-2333-463d-93d0-6184f9adb2ae</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I think that sensor can handle the max SPI speed on nRF chip (8MHz). If it is still the same 150ms on both I2C and SPI then it is your wakeup routine that is taking so much time to process the data. Nothing is wrong in that, it depends on use case.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39874?ContentTypeID=1</link><pubDate>Fri, 11 Dec 2015 04:16:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:536faa56-47a7-46ce-b56e-7ae89a61e749</guid><dc:creator>sam zhou</dc:creator><description>&lt;p&gt;yes 400k, the 150ms is the key, even SPI mode, the peak lower down but the time period still 150ms. Something wrong with non blocking mode? whats your suggestion?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39872?ContentTypeID=1</link><pubDate>Tue, 08 Dec 2015 05:50:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:560d26ee-4ca9-4044-88ca-bfa9c7560169</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;It am not aware of I2C current consumption numbers, but this 150ms wakeup for just for reading few samples of data does not look right.I Am guessing that you are using 400k speed and non blocking mode in the driver?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39871?ContentTypeID=1</link><pubDate>Tue, 08 Dec 2015 04:47:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d53ed4f-76ab-434b-afe6-37c017571252</guid><dc:creator>sam zhou</dc:creator><description>&lt;p&gt;Don&amp;#39;t think so. As we changed to SPI, the current drop down. So far, we guess it is caused by I2C, I did not see good result in this forum on I2C power. Future, will consider 52 series, with DMA, which wake CPU as less as possible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39870?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2015 09:54:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:056f65cc-3c14-43b5-82d9-699e16b20d10</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Which SDK are you using? it possible that TWI driver has some issues.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39869?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2015 09:39:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:64af8bda-ecd0-4594-8750-b39ca34b5e23</guid><dc:creator>sam zhou</dc:creator><description>&lt;p&gt;We read this and this, think it is not applied to our case, if I/O is turned on, the current will be consistently high not like our case.&lt;/p&gt;
&lt;p&gt;And we just switch SPI and use 8Mb, the current drop to 500uA with same wave. So wonder why the wave is 150ms long, what else causing it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with I2C G-sensor</title><link>https://devzone.nordicsemi.com/thread/39873?ContentTypeID=1</link><pubDate>Sun, 06 Dec 2015 11:48:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f492d99-c305-4517-a018-cd0d6c09fc9e</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Did you go through &lt;a href="https://devzone.nordicsemi.com/question/4220/nrf51822-power-consumption/"&gt;this&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/question/1316/what-is-the-power-and-clock-model-of-peripheral-in-nrf51/"&gt;this&lt;/a&gt;? Is there any RADIO activity while taking this measurements?&lt;/p&gt;
&lt;p&gt;It will be very useful to see your peripherals initialization and wakeup handler code to see if clocks and unneeded peripherals are consuming too much energy. Also which version of the nRF51are you using?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>