geekhack

geekhack Community => Keyboards => Topic started by: rich1051414 on Thu, 02 November 2017, 15:38:59

Title: Strange issue with Code keyboard
Post by: rich1051414 on Thu, 02 November 2017, 15:38:59
I have had my Code TKL V2B with clears for a while now, like 2 years, but I have a lot and switch between them, but recently I have been having a problem, when there is any EMF in the background, like if my cell phone gets a text message, someone turns on the microwave in the next room, I turn on the plasma ball, etc, the keyboard absolutely wigs out. Keys stick, lights flicker, the keyboard disconnects, then reconnects again.

It only does it when there is a lot of EMF noise near it, but I can't trigger it in any other way. I have tried with different USB cables but it makes no difference. I can even trigger it with a HV voltage multiplier module by letting it arc about 5 feet from the keyboard. I have never seen anything like this.

Anyone know what could be causing this behavior?

Right now it is serving as a wonderful EMF detector, but that's about it, since it will randomly wig out through the day as soon as some stray EMF hits it.

I remember seeing this behavior a long time ago, but it didn't happen often, so I am not sure if it has always had it or not, as I could have a new appliance or something triggering it now that I didn't have before.

Before you ask, it doesn't happen to any of my other keyboards, so it isn't my PC. I am certain the issue is internal to the Code keyboard.
Title: Re: Strange issue with Code keyboard
Post by: rowdy on Wed, 03 January 2018, 00:53:42
I have a CODE TKL that I use at work.

There is a microwave about 3m away, and two mobile phones within 1m.

I have not noticed any abhorrent behaviour from it in any way.
Title: Re: Strange issue with Code keyboard
Post by: pixelpusher on Wed, 03 January 2018, 01:18:09
Have you tried another usb cable?   Also have you tried a cable with a ferrite bead on it?  I believe thats what they are for.  Not that it solves the question of why it just started acting up, but it may fix the issue.