-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teensy 4.1 (kint41) - Two key inputs with single key press #39
Comments
Which version of the firmware are you using? https://github.com/kinx-project/qmk_firmware/commits/kint41-upstream-ref already contains a debounce time of 20ms, which should work well. Likely you’re on an older version? QMK defaulted to 5ms. Edit: specifically, debounce config happens here: https://github.com/kinx-project/qmk_firmware/blob/f0eec9f74e22fccbed1d52a3045f5fe5766de8f4/keyboards/kinesis/kint41/config.h#L80-L85 |
I forked your kint41 branch ~2 weeks ago. |
I take it bumping the debounce time to 20ms fixed the issue for you, yes? |
yes, 20 ms debounce time fixed it. |
related to kinx-project/kint#39 related to qmk#12626
related to kinx-project/kint#39 related to #12626
related to kinx-project/kint#39 related to qmk#12626
related to kinx-project/kint#39 related to qmk#12626
related to kinx-project/kint#39 related to qmk#12626
related to kinx-project/kint#39 related to qmk#12626
Hi,
first of all thank you very much for your great work and support on the kint project.
I have two kinesis advantages 2 and have built three kint pcbs in total. Two of them with Teensy 4.1.
My advantage with the cherry mx quiet red switches works totally fine and I could develop a bone like layout (close to neo) for it.
But when I use the same firmware build on my second advantage with cherry browns, I get a weird behavior when typing mostly on my pinkies and ring fingers.
1 out of 10 I see two key inputs with a single key press. Seems to be related to the 'bump' of the tactile switches.
Is there a way to increase the debounce time? Or is there another way to fix this?
This behavior is really disturbing, but I cannot use the native kinesis controller with the bone layout.
greetings
Tim
The text was updated successfully, but these errors were encountered: