geekhack

geekhack Community => Keyboards => Topic started by: Fragil1ty on Fri, 21 November 2014, 16:47:24

Title: Keychattering - Info pls.
Post by: Fragil1ty on Fri, 21 November 2014, 16:47:24
Hey guys,

I'm just wondering if there is a solution to find out which keys are actually the chattering keys? I've used applications such as: "Switch Hitter" and although I did this program under different settings over and over again? I just couldn't find any errors what so ever, so it begs the question, how do I find out which are the chattering keys?

I don't really want to go out and de-solder all of my keys, remove the cherry keys, buy new cherry keys and then re-solder them, it would just be easier to buy a new keyboard.

So what are the options that I have? just note down the key that chatters and hope for the best?

Someone suggested that I buy some lubricant and insert it into the keys and hope for the best? but wont that damage the board? I've never done anything like that before, would love some advice.
Title: Re: Keychattering - Info pls.
Post by: jacobolus on Fri, 21 November 2014, 16:58:53
When you say “chatter”, are you talking about bounce in the electrical signal, or the sound the switch makes?
Title: Re: Keychattering - Info pls.
Post by: Computer-Lab in Basement on Fri, 21 November 2014, 17:55:53
Isn't keychattering when you press a key once but it records multiple keystrokes (i.e. pressing "p" and getting "pp").

 
Title: Re: Keychattering - Info pls.
Post by: jacobolus on Fri, 21 November 2014, 19:09:03
Isn't keychattering when you press a key once but it records multiple keystrokes (i.e. pressing "p" and getting "pp").
That’s what I mean by bounce in the electrical signal.

Fragil1ty: what’s the keyboard, what kind of switches, and what exactly are the symptoms?

I get occasional double actuations on certain switches, in particular Omron B3G-S series switches and to a lesser extent clicky space invaders. Part of the problem is that the actuation point for these switches is slightly above the tactile/click point, but I suspect part of the blame should also be placed with the debounce routine in the keyboard firmware.