I was the one Charles had said was having the same issue. I thought initially it had to be the controller, because in my case, it would type the correct character, THEN type an incorrect character. Example is 'u' and 'backspace'. It would type a U, then backspace it.
I and enter do the same thing...if you hit an I, it'll type an I, then hit the return key.
Now that I've thought about it, it's actually the microcontroller just scanning the rows and columns, and executing them in order, based on thier position and the rows/columns being scanned in order to find the key being hit.
So, I took the key caps off of the offending keys and blew them out, i'm still having issues with the keypresses...issues persist. None of the keys themselves seem to behave "shorted" together, yet I do see continuity between keys where they aren't on the same row or column. the X/Y for U has continuity with the backspace key, even though they're on different rows and columns. Could the coupling caps go bad, causing this behavior?
I and enter do the same thing...if you hit an I, it'll type an I, then hit the return key.
Now that I've thought about it, it's actually the microcontroller just scanning the rows and columns, and executing them in order, based on thier position and the rows/columns being scanned in order to find the key being hit.
So, I took the key caps off of the offending keys and blew them out, i'm still having issues with the keypresses...issues persist. None of the keys themselves seem to behave "shorted" together, yet I do see continuity between keys where they aren't on the same row or column. the X/Y for U has continuity with the backspace key, even though they're on different rows and columns. Could the coupling caps go bad, causing this behavior?