-
-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
[Bug] kinesis w/ stapelberg ghosting on certain keys #18014
Labels
Comments
rockybulwinkle
added a commit
to rockybulwinkle/qmk_firmware
that referenced
this issue
Aug 12, 2022
14 tasks
Just submitted a pull request. I hope to test my hypothesis of why this is happening this weekend. I'll hook up the lines on my 'scope to see how long the rise/fall times are. |
zvecr
pushed a commit
that referenced
this issue
Aug 13, 2022
* [Keyboard] Increase kinesis/kint41 unselect delay Fixes #18014 * Update kint41.c Use correct si-abbreviation for micro in comment.
imhoffman
pushed a commit
to imhoffman/qmk_firmware
that referenced
this issue
Aug 20, 2022
* [Keyboard] Increase kinesis/kint41 unselect delay Fixes qmk#18014 * Update kint41.c Use correct si-abbreviation for micro in comment.
nolanseaton
pushed a commit
to nolanseaton/qmk_firmware
that referenced
this issue
Jan 23, 2023
* [Keyboard] Increase kinesis/kint41 unselect delay Fixes qmk#18014 * Update kint41.c Use correct si-abbreviation for micro in comment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I press a key in the top row of one of the key wells, and a key in the next row down in a neighboring column, I get ghosting. For example:
2+q => key "1" ghosts
2+e => key "3" ghosts
3+w => key "2" ghosts
3+r => key "4" ghosts
It only happens for me with these sorts of combinations of the top two rows (that I've noticed so far anyway).
It appears the issue is an insufficient delay after unselecting the row in matrix_output_unselect_delay. For my combination of hardware, it seems to need around 20 microseconds in order to get rid of this ghosting, up from the original 10 microseconds.
My keyboard is a kinesis KB600LF.
Stapelberg's kinT v2020-06-30.
Teensy 4.1
My best guess as to why I'm experiencing this, is perhaps the capacitance is a bit higher in either the LF variant of the kinesis KB600, or perhaps it is higher in this older revision of Stapelberg's board.
I've already applied and tested a fix that I will submit a pull request for shortly.
The text was updated successfully, but these errors were encountered: