<?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>Why my adc handler is never triggered?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24244/why-my-adc-handler-is-never-triggered</link><description>Hello, 
 I am making a battery service to report the battery that is sampled by the SAADC, so far I am am able to compile it and debug it, however I see how my saadc_event_handler_interrupt is never triggered. Which means to me that the ADC never samples</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Aug 2017 13:00:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24244/why-my-adc-handler-is-never-triggered" /><item><title>RE: Why my adc handler is never triggered?</title><link>https://devzone.nordicsemi.com/thread/95448?ContentTypeID=1</link><pubDate>Fri, 11 Aug 2017 13:00:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:197980e4-13d0-45ac-a8f4-2a655fb6b56b</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;It seems that you are using saadc example code from the Thingy SDK. As mentioned in &lt;a href="https://devzone.nordicsemi.com/question/162957/am-i-not-configuring-right-my-saadc-handler-for-low-power/"&gt;this post&lt;/a&gt; I recommend using the SAADC code from the ble_app_proximty example, as this code is a bit simpler, is targeted for the nRF52-DK and also simpler to integrate to other SDK examples. We can continue the discussion in &lt;a href="https://devzone.nordicsemi.com/question/162957/am-i-not-configuring-right-my-saadc-handler-for-low-power/"&gt;that post&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why my adc handler is never triggered?</title><link>https://devzone.nordicsemi.com/thread/95447?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2017 14:07:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91bcd2b6-722d-4050-bf4f-494d5b0e40b5</guid><dc:creator>ndarkness</dc:creator><description>&lt;p&gt;ON the example the do so, I think it is because you have to wake up the ADC (in case it is  on low power)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why my adc handler is never triggered?</title><link>https://devzone.nordicsemi.com/thread/95446?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2017 13:59:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a918400-a90d-4821-8d48-7d479936f3b7</guid><dc:creator>anasimtiaz</dc:creator><description>&lt;p&gt;Why do you call the saadc_init() function every time after 5s? Afaik you only need to config ADC initially.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>