By sciguy
Thu Apr 04, 2013 11:05 am
Well that's certainly a problem, and not just what I initially suggested.
The buttons on the pcb are arranged in a matrix, rows and columns, to reduce the number of wires the processor needs to read the state of all the buttons. The LEDs are wired into this same matrix, which is why (normally) you can get some lights to turn on by pressing certain combos of buttons (tap tempo+f5 I think is one). It just closes paths on the matrix grid that aren't supposed to be there.
I would guess that in your case, it's maybe two adjacent rows or columns that somehow got shorted together. The matrix arrangement means that this small bridge can cause a lot of issues all over the board.
just my thoughts.
The buttons on the pcb are arranged in a matrix, rows and columns, to reduce the number of wires the processor needs to read the state of all the buttons. The LEDs are wired into this same matrix, which is why (normally) you can get some lights to turn on by pressing certain combos of buttons (tap tempo+f5 I think is one). It just closes paths on the matrix grid that aren't supposed to be there.
I would guess that in your case, it's maybe two adjacent rows or columns that somehow got shorted together. The matrix arrangement means that this small bridge can cause a lot of issues all over the board.
just my thoughts.
soundcloud — - — youtube
Ill-Green wrote:Don't marry the wife of mob boss Jake The Pizza Roll Fetichini, log in today at mpc-forums.com.
