changing the default scan rate to 100Hz

Thanatermesis (via email) told me that this worked for him, fixing his
issue of having some keys unexpectedly double tap (though, I think he
might have gone down to 50Hz, or something).  since he mentioned it,
i've been noticing my keys double tapping sometimes (on one of my brown
boards, with an acrylic case... it didn't seem to happen at all with my
blue caseless board...), so i decided to give this a try :)
partial-rewrite
Ben Blazak 2014-05-23 09:53:03 -07:00
parent 881bdf6f94
commit c50b98922c
2 changed files with 4 additions and 4 deletions

View File

@ -22,11 +22,8 @@
// firmware/main
// ----------------------------------------------------------------------------
#define OPT__DEBOUNCE_TIME 5
#define OPT__DEBOUNCE_TIME 10
// in milliseconds
// TODO: it should probably be noted in a separate document that sometimes
// changing this to a higher value, say 20, is a workaround to fix keys that
// seem to unexpectedly double-tap (thanks Thanatermesis!).
// ----------------------------------------------------------------------------

View File

@ -28,6 +28,9 @@
*
* Notes:
* - Cherry MX bounce time <= 5ms (at 16 in/sec actuation speed) (spec)
* - From experience (after having this issue brought to my attention by
* Thanatermesis), waiting longer can sometimes fix the issue of having some
* keys unexpectedly seem to double-tap.
*/
#ifndef OPT__DEBOUNCE_TIME
#error "OPT__DEBOUNCE_TIME not defined"