Durability of non original cherry switches

[dragonken]

In the old days, a keyboard with original Cherry switches (red, blue, brown, black, and white switches) could last for years without any issues.
After the expiry of the MX cherry switch patent, the market is flooded with so many cheap OEM switches
They look prettier, better switches feel, and better sound profile....
I built 5 boards with these new non-original Cherry MX switches, and none of these can last over 6 months without issues like key chattering or not registering keystrokes.
I built a 61-key 60% board with a set of famous tactile switches.
It started malfunctioning (missing keystrokes/chattering) after 3 months of use.
I replaced the problematic switches (re-soldering) whenever I found one, and later, I found I had to repair the broken switches every week.

I have Orion TKL and lightsaver with 62g white / red switches for over 10 years, and they still work great right now without any key issues.

I would like to know is it a common issue with non-original MX switches?
Is it switch brand specific? or switch type specific(tactile/linear)?
or lubricant specific (205g0/Tribosys 3203)?






 

[zegonix]

i had a similar problem last year, when various switches started to activate twice, or miss the press every now and then. my keyboard use qmk firmware and my fix was to increase the debouncing filter.
(if you don't know what switch bounce is: https://www.allaboutcircuits.com/technical-articles/switch-bounce-how-to-deal-with-it/)

if changed the filter to 8 ms, haven't had a problem since. my oldest switches have around 1 to 1.5 years of extensive use (i am a programmer).

[jcoffin1981]

I feel the durability of switches is a non-issue.  Whether a switch is rated for 10 million, 20 million, or 50 million actuations I really don't care.  I guess most switches nowadays are "cheap Chinese," but I most often use Khail, Gateron, or Cherry.  I RARELY have to replace a switch, and in fact it is more common for me to have to repair a solder joint instead than the switch.  If you are having issues with key chattering, I wonder if it's more of a problem with the firmware/controller in the keyboard than it is the switches themselves. 

Years ago I had an issue with a KBParadise V60, and I had so many of the switches chattering.  Sure I messed with the debounce interval, but ultimately it was a problem with the board itself instead of the actual switches.  I think they were Cherry switches, Cherry or Gateron. 

[zegonix]

until you prove me wrong with actual measurements of the switches bouncing times, i am convinced, that the debouncefilter is set to short, because someone wanted a little bit better response time..

[TheSoulhunter]

Got chatter problems on multiple boards...
Some switches, like my beloved Zealios v2, seem to be very prone to chatter.
The fix for me was a free and lightweight software called "Keyboard Chatter Blocker"


Ol'ChatterSwitch


The Fix

[zegonix]

i don't like to use third party software to solve an issue that could and should be fixed at the source.
when using qmk (zmk too presumably) firmware it is quite easy change the debounce filter. easy and permanent fix that does not rely on software that might suddenly loose support.

[TheSoulhunter]

i don't like to use third party software to solve an issue that could and should be fixed at the source.
when using qmk (zmk too presumably) firmware it is quite easy change the debounce filter. easy and permanent fix that does not rely on software that might suddenly loose support.

Fair point! Fixing it at hardware-level (well, technically still software) is the best way...

But the program has the advantage that it will fix the problem for ALL keyboards (and other devices that output keystrokes).
The firmware fix is only a fix for that one keyboard you modify, and only replicate-able for keyboards that allow this firmware alteration.

Also, you don't have to worry about support. It is open-source (MIT license) on GitHub...
So, if some future versions of Windows does not want to run it, and the one who coded it does not care, you can fix it yourself (or, if not able to, ask someone who is able to)