<?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>nRF52 saadc current vs acquisition time</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18556/nrf52-saadc-current-vs-acquisition-time</link><description>I am using SAADC with TIMER3 and PPI, sampling 12bits at 250Hz.
When I use 10uS acquisition time, the average current consumption is 300uA lower than when using 3uS or 5uS acquisition times.
What could explain that shorter acquisition time takes more</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 23 Dec 2016 12:01:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18556/nrf52-saadc-current-vs-acquisition-time" /><item><title>RE: nRF52 saadc current vs acquisition time</title><link>https://devzone.nordicsemi.com/thread/71614?ContentTypeID=1</link><pubDate>Fri, 23 Dec 2016 12:01:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c508054-1242-4283-8c89-0b3f33c4c5d1</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This can be related to &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.Rev1.errata/anomaly_832_74.html?cp=2_2_1_0_1_14"&gt;PAN 74&lt;/a&gt;, potentially there is not workaround for this implemented in the SAADC driver. It has been reported internally and should be fixed in future releases.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>