A hand-wired USB and Bluetooth keyboard powered by Python
1–10 of 29 posts
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#2Re: A hand-wired USB and Bluetooth keyboard powered by Python
#3This looks cool, however can someone with some electronics know-how explain to me why the connections on most, if not all the keys are crossed? They don't look like insulated wires, though I could be wrong.
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#4This looks cool, however can someone with some electronics know-how explain to me why the connections on most, if not all the keys are crossed? They don't look like insulated wires, though I could be wrong.
https://en.wikipedia.org/wiki/Magnet_wire
The insulation melts away where it comes in contact with hot solder, so it's very easy to work with for hand-wiring projects.
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#5Re: A hand-wired USB and Bluetooth keyboard powered by Python
#6Haha that's amazing. What's the latency on this though? I always assumed firmware written in python would be slow for a use case like a keyboard.
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#7Haha that's amazing. What's the latency on this though? I always assumed firmware written in python would be slow for a use case like a keyboard.
It is a bit slow. It takes 4 ms to scan the matrix once right now. With some optimizations, it may be faster.
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#8Re: A hand-wired USB and Bluetooth keyboard powered by Python
#9Earlier quoted context omitted.
It is a bit slow. It takes 4 ms to scan the matrix once right now. With some optimizations, it may be faster.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)
Re: A hand-wired USB and Bluetooth keyboard powered by Python
#10Earlier quoted context omitted.
It is a bit slow. It takes 4 ms to scan the matrix once right now. With some optimizations, it may be faster.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)