Author Topic: Realforce 87USW: key stuck on 'pressed'  (Read 1222 times)

0 Members and 1 Guest are viewing this topic.

Offline Bucake

  • Thread Starter
  • Posts: 945
  • Location: The Netherlands
Realforce 87USW: key stuck on 'pressed'
« on: Wed, 03 June 2015, 00:06:00 »
hi guys,

so i've been using the Realforce 87USW for a while now and, every now and then, after pressing a key, it will just keep spamming the letter (or whatever was pressed).
like just now; i was typing a word with the letter 'v' in it, and it just went 'vvvvvvvvvvvvvvvvv', after i had already depressed/released the key.

unfortunately i don't know why or how it happens, and i can't seem to just reproduce it.
it's happened with a bunch of other keys as well, but i can't remember which keys they were.

the keyboard is pretty new and still entirely clean. i never eat or drink near my keyboard.
the only obvious explanation i could think of is a guest having dumped something on my board, but I sincerely doubt that would've happened without me noticing..
not a single key sticks, so i'm confident it wasn't some drink that got spilled by a guest.

so, my question: has anyone ever experienced something like this with a (realforce) keyboard? maybe it's something that 'can happen' with the topre 'electrostatic capacitive' design?
it happens very little, and thus is not a huge problem, but naturally i would prefer to have this 'fixed', or to at least know what's going on/why it might be happening.

well, at least thanks for reading :-)
cheers

additional notes:
it's never happened on any of my cherry boards.
this is the only topre board i've owned.
« Last Edit: Wed, 03 June 2015, 00:10:11 by Bucake »
IBM Model F XT // Realforce 87U 55g Type-S // HHKBP2 45g Type-S // KBT Pure Pro Cherry MX Red

Offline GL1TCH3D

  • Posts: 1117
  • Location: Quebec, Canada
  • Audiophile, tea lover and now keyboard hugger!
Re: Realforce 87USW: key stuck on 'pressed'
« Reply #1 on: Wed, 03 June 2015, 01:24:42 »
Happens on my 91UDK every now and then. Would be interested in knowing why it happens. I've had to unplug my keyboard to resolve the issue