Page 1 of 1

Model M repair - Unicomp Membrane replacement

Posted: 01 Jul 2017, 21:20
by PancakeMSTR
Hi,
So relatively recently I got a model M that I decided to bolt mod. When I put it all back together, a number of keys didn't work, presumably because the original membrane has broken traces. I don't honestly know if this is the case but it's my assumption.

Anyway I bought a new membrane from unicomp, and followed [this guide](http://imgur.com/a/8Oyc9) for modifying the unicomp membrane to fit in the older model Ms.

So I cut off the strip I needed to, very carefully, and plugged the membrane into the controller. I then tried keyboard tester and get nothing at all out of the new membrane. With the old membrane, I could at least rub my hands on it and it would set off some switches, but I get literally nothing with the new membrane.

What the fuck? Is there something I'm missing? Could use some help please! Thanks.

**BTW** the only response I do get is the following: I can press anything I want and after a press or two the scroll lock LED lights up. Aside from that, nothing.

Posted: 02 Jul 2017, 15:08
by Wingklip
Hmm. Check the barrel plate, sometimes the barrel plates are cracked and don't hold the flippers in properly. That happened to me and I had troubles with pressing escape and /, *

Otherwise looks like its electronic. Check the grounding cable if its been screwed into the right hole (usually metal to metal or to the connector), after that see if the old membrane still works if you press it with your fingers. To be quite honest I think that there might just be a bit of dust in the old membrane as traces don't tend to break that easily.

Otherwise rip controller? I would still assume its contacts first

Posted: 02 Jul 2017, 19:04
by PancakeMSTR
So actually I got the membrane to work. However, I'm still getting weird responses from the keyboard. For example, pressing F1-F4 Sends F12, and a bunch of keys either send no signal or send unidentified signals to the computer. Both membranes have the same behavior regarding this. I'm assuming this is a firmware issue, any ideas?