Well this is another project that I've really let go. I got back around to trying out the keyboard with CommonSense this time, since I figured it would give me more control than xwhatsit. I ran into so many issues. Believe it or not, I rebuilt the converter from scratch 4 times before I finally convinced myself to try something else.
Whenever plugged into the keyboard into the PC, FlightController would complain that it's insane and stop scanning.
Finally I decided to ask DMA what the deal was and he pointed me to a section in the readme that has been there all along. This is what it says:
If something is wrong - you can still use matrix monitor using the following trick:
- open matrix monitor,
- make sure the mode is "Now"
- click "Start!"
- go to main window
- click "Scan"
So essentially, this enables you to start the matrix monitor and see which rows/columns are having the problem. In my case, there was one row where all the keys were showing as pressed.
Now I swear I went through and tested all the traces before, but somehow I missed this. This time when I went back and retested, the multimeter confirmed what I was reading on the screen.
So I followed the trace from its beginning to its end looking for the problem spot. This was challenging since there are so many spots where it looks
like the trace is cut/corroded but it's really fine. I did eventually locate the issue; a spot on the PCB where I don't know exactly what happened.
I did my best to repair this little cut using a thin strand of wire.
I covered this repair with a small piece of electrical tape.
Now when I plug it into flight controller, I have no issues.
But it does beg the question: what happened to that trace? It didn't look like it had been slashed or cut. It looked to me like it wore away for some reason. There are so many spots on the PCB that look identical. Are those eventually going to wear away as well? Is my poor keyboard on borrowed time?