<?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>Switch Debounce</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9054/switch-debounce</link><description>I have a switch connected on the nRF51DK Board. The switch is connected on PIN25 and PIN 28. I try to read the state of the switch. 
 My setup: 
 -nRF51DK 
 -SDK8.1 
 -SoftDevice 8.0 
 I defined PIN 25 and 28 as Inputs(PULLDOWN). The button_event_handler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 28 Sep 2015 10:55:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9054/switch-debounce" /><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33352?ContentTypeID=1</link><pubDate>Mon, 28 Sep 2015 10:55:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa2d39a2-4560-46e3-aed2-6ee69b91c500</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;No. not necessary ;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33351?ContentTypeID=1</link><pubDate>Mon, 28 Sep 2015 10:33:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3aeced46-c03d-4fde-9d66-5ddcfac48c5d</guid><dc:creator>Lakerno</dc:creator><description>&lt;p&gt;ok. with this timer solution, do you still use the RC debouncer??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33350?ContentTypeID=1</link><pubDate>Mon, 28 Sep 2015 08:57:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d2c726d-3b4c-4ebb-8fde-25b7ad0ed9d8</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;Well I think the debouncing could be the only logical issue. Because the most of the time it works. But now I have an other solution which works great. I have timer and in the timeout handler of the timer I will just read the pin of the switch. Now I will always detect if the button is pressed or not&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33349?ContentTypeID=1</link><pubDate>Sun, 27 Sep 2015 16:39:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88493c43-84f2-44f5-a616-e5b74d638b24</guid><dc:creator>Lakerno</dc:creator><description>&lt;p&gt;Hi Inspectron,
how did you conclude that this is an issue regarding debouncing?? Even without the RC debouncing logic, shouldnt the switch when connected to DOWN eventually settle to 3.3V? so if you poll the pin for a few seconds, couldnt you fix the issue with debouncing??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33348?ContentTypeID=1</link><pubDate>Mon, 14 Sep 2015 08:22:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01a288a3-b215-4125-bb89-f0fadcd28888</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;I&amp;#39;m using the softdevice and I&amp;#39;m generating a pwm signal. I also use ADC. Only the down position seems not to work. The up position isnt missing interrupts. And yes I&amp;#39;m sure that the circuit is the same for up and down.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33347?ContentTypeID=1</link><pubDate>Mon, 14 Sep 2015 07:40:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:946aa3a5-052a-4fbf-9485-67da06e623ed</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Do you have a lot of other stuff going on in your application? A Softdevice running etc?&lt;/p&gt;
&lt;p&gt;You said in your initial post that it didn&amp;#39;t work in the down position, is that still the case? Are you sure that the &amp;quot;down position-circuit&amp;quot; is exactly the same as the up-position? Same components values etc?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33346?ContentTypeID=1</link><pubDate>Fri, 11 Sep 2015 14:06:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:862993f8-a763-4891-9983-8c2bd29d5b47</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;So NRF_GPIOTE -&amp;gt;EVENTS_IN[0] = 0; is for clearing the interrupt? I tried it out. It works better, but still not perfect. Now when I try it 20 times, once the interrupt will not occur).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33345?ContentTypeID=1</link><pubDate>Fri, 11 Sep 2015 06:49:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ff27a51-7184-480a-a7b8-f5065a7e6e25</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Have a look at these two threads: &lt;a href="https://devzone.nordicsemi.com/question/1590/how-to-write-gpiote-interrupt/"&gt;1&lt;/a&gt; &amp;amp; &lt;a href="https://devzone.nordicsemi.com/question/17440/gpiote-interrupt/"&gt;2&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33344?ContentTypeID=1</link><pubDate>Thu, 10 Sep 2015 14:11:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5e3dba2-a07c-4e39-a632-129a3f08d1ef</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;I do not clear the signal between the interrupts. How does the clear interrupt function looks like?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Switch Debounce</title><link>https://devzone.nordicsemi.com/thread/33343?ContentTypeID=1</link><pubDate>Mon, 07 Sep 2015 11:24:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ede92b1-8cd8-4cc8-a601-01a165110b6e</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi. I have never seen a debounce circuit like this, but I assume it works. I don&amp;#39;t see any reason why pin 25 would behave different than pin 28 either. Could it be that your DETECT signal is not cleared between the interrupts? &lt;a href="https://devzone.nordicsemi.com/question/38976/missing-interrupts-on-gpioe-port-events/"&gt;Link&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/question/3504/radio-activity-causes-gpiote-interrupt-missing/"&gt;link&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>