Check open post of this thread, DEBUG section particularly.
https://geekhack.org/index.php?topic=14290.0

Post in the thread if you need further question.

Hello. I soldered adb-usb converter based on Arduino Pro Micro for Apple Extended Keyboard II.  Works good, its what i wanted to say, but keyboard randomly stop to respond while gaming. Num pad light is shiny which means keyboard is powered, but no button reacts to press. Tried with 1kOhm resistor and 2 parallel 1kOhm (500 Ohm), keyboard behaviour dont change. To fix this behaviour need to unplug-plug keyboard and its works until next random stop. Which solution for my situation can be?

hello everyone, recently i bought an aftermarket keyboard from someone else, and idk what kind of specific model for it but all i know its from tecware phantom TKL. short story when i tested it its working and all the lights are lit up, but the f3, 3, e, d, c, and all botttom rows where the space is located (including Arrow keys) is doesn't work. I've tested to jumper the pin but failed because the space doesn't even turned on.

like for example if i connect a wire to the second pin (the one that are connected to diode) in this case alt-right key and connect it to the top row, the key that will activate is v key, and if i more it to the top once more, the f key activate, repeat this step and the key that actived is r, 4, f4.

 I've do the same thing with space but it doesn't work at all. anyone have any idea?, i think its the traces to the space that are messed up but I've checked using multimeter that are all the rows are beeping and the diodes are beeping. any ideas?

Quote from: Snipeye on Sat, 11 May 2024, 21:14:57

you need about 2K+ scans/second to avoid missing a transition, but that's not too hard to achieve.

That's interesting. How do you debounce them?

Do you report a step on the next change and suppress only the opposite turning direction for the bounce period?
Or do you not need to?

The traditional method for debouncing encoders is to pass the raw outputs through a state machine (I didn't look closely, but I think it's described right in the stackexchange post https://electronics.stackexchange.com/questions/360637/quadrature-encoder-most-efficient-software-implementation).  QMK debounces individual keys in the matrix, and those debounced values are currently getting handled by the state machine so it's sort of double-debounced, which is providing some less-than-graceful results (the default key debouncing is too aggressive/not a good fit for an encoder).

I've written (for the client I mentioned in my previous post, with 32 encoders) a bitfield-state machine that handles all 32 encoders in parallel by performing bitwise operations on uint32_t variables that worked really well - I plan on submitting another PR to QMK to implement this method since it debounces all encoders at once (instead of running a loop that debounces them all individually).