<?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>Deboune time of keyboard matrix</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/163/deboune-time-of-keyboard-matrix</link><description>Hi
In Desktop 2 v1.0.4, did you consider the debounce as keyboard buttons were pressed or released?
How long is the debounce confirming time? Thanks. 
 Jeffery</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 25 Jul 2013 08:12:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/163/deboune-time-of-keyboard-matrix" /><item><title>RE: Deboune time of keyboard matrix</title><link>https://devzone.nordicsemi.com/thread/911?ContentTypeID=1</link><pubDate>Thu, 25 Jul 2013 08:12:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97b38cb9-c43f-46bc-a5db-e1480295fa84</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is no minimum value, this is only the polling rate for when to send key and release key. A normal tap from a person is ~200 ms.
You can do a tighter timing, but I do not think it is going to have a huge effect on the response time. Having a lower polling rate will give a higher current consumption as you are firing the interrupt more frequently.&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deboune time of keyboard matrix</title><link>https://devzone.nordicsemi.com/thread/910?ContentTypeID=1</link><pubDate>Thu, 25 Jul 2013 08:01:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31e72073-e2c4-49c5-bcee-a9d767bee6fd</guid><dc:creator>Jeffery</dc:creator><description>&lt;p&gt;Hi Håkon
Thanks for your reply. Can we modify M_KEYBOARD_DEFAULT_POLLRATE to 5ms or less?
What is the minimum value?&lt;/p&gt;
&lt;p&gt;Jeffery&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deboune time of keyboard matrix</title><link>https://devzone.nordicsemi.com/thread/909?ContentTypeID=1</link><pubDate>Thu, 25 Jul 2013 07:46:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:293697af-8852-44d3-ba1c-868414da84e7</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Jeffery,&lt;/p&gt;
&lt;p&gt;The default debounce (or polling rate as it&amp;#39;s named in the keyboard) is 15 ms.
It&amp;#39;s setup with this define in m_keyboard.h:
M_KEYBOARD_DEFAULT_POLLRATE&lt;/p&gt;
&lt;p&gt;How this happens is that the keyboard uses the GPIOTE PORT event as a wakeup source.
When the device is awake, it starts a timer, and when it times out, it scans the matrix.&lt;/p&gt;
&lt;p&gt;When the button is released (see: matrix_scan_timeout_handler), the timer is stopped and a &amp;quot;release&amp;quot;  command is sent.
Then it&amp;#39;s back to sleep.&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>