geekhack
geekhack Community => Keyboards => Topic started by: Turbo Slaab on Tue, 29 January 2013, 22:07:01
-
Every so often (once or twice a match) my new Poker's buttons seem to stick in bf3. Doesn't seem to happen with run (Shift) or jump(space bar) but it has happened going forward, back, and side to side. What is odd to me is that the only way to stop it, is to double tap the button. It doesn't feel like a mechanical issue. It's almost like a software thing. Has anyone else experienced this?
-
Every so often (once or twice a match) my new Poker's buttons seem to stick in bf3. Doesn't seem to happen with run (Shift) or jump(space bar) but it has happened going forward, back, and side to side. What is odd to me is that the only way to stop it, is to double tap the button. It doesn't feel like a mechanical issue. It's almost like a software thing. Has anyone else experienced this?
did you try running the usb at 1000hz?
-
Every so often (once or twice a match) my new Poker's buttons seem to stick in bf3. Doesn't seem to happen with run (Shift) or jump(space bar) but it has happened going forward, back, and side to side. What is odd to me is that the only way to stop it, is to double tap the button. It doesn't feel like a mechanical issue. It's almost like a software thing. Has anyone else experienced this?
did you try running the usb at 1000hz?
I've never tried. It wasn't an issue with my Filco or CFR. Is it inherent in the poker PCB?
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
Hmm. Well that makes me feel better it's not just mine, but it still sucks. I wonder if there's a way to remedy this......
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
Hmm. Well that makes me feel better it's not just mine, but it still sucks. I wonder if there's a way to remedy this......
Another KBC victim.... damn them...
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
Hmm. Well that makes me feel better it's not just mine, but it still sucks. I wonder if there's a way to remedy this......
Another KBC victim.... damn them...
I blame the layout......and the price. 60% for $100? Sounds good to me! But the fine print never mentioned it'll lead you right in the line of fire. K/d be damned!
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
Hmm. Well that makes me feel better it's not just mine, but it still sucks. I wonder if there's a way to remedy this......
Another KBC victim.... damn them...
I blame the layout......and the price. 60% for $100? Sounds good to me! But the fine print never mentioned it'll lead you right in the line of fire. K/d be damned!
well you should try up-ping the usb poll to 1000, see if that helps. And check for flex in the PCB
-
I had that problem as well when I had my poker. It even happened to the other keyboard when I plugged it in and played around with it while the poker was plugged in. Without the poker in, it never happens.
Hmm. Well that makes me feel better it's not just mine, but it still sucks. I wonder if there's a way to remedy this......
Another KBC victim.... damn them...
I blame the layout......and the price. 60% for $100? Sounds good to me! But the fine print never mentioned it'll lead you right in the line of fire. K/d be damned!
well you should try up-ping the usb poll to 1000, see if that helps. And check for flex in the PCB
I'm actually using the keyboard port (the proper term escapes me) with an adapter from my filco.
-
PS2?
-
PS2?
YES. Thank you!
-
PS2?
YES. Thank you!
The problem is in the keyboard controller. Point blank, it's broken, the end. There is no argument here. For those of you who are playing along at home, let's review:
AT and PS/2 Key Stroke = Key Depressed -> Make Code -> Key Released -> Break Code
USB Key Stroke = Key Depressed -> Make Code -> Key Released -> Stop Sending
The symptoms you describe are, no surprise, consistent with the controller failing to send Break code. So the Poker's sending a proper or spurious Make and never sending a Break in PS/2 mode. (Oh, and the scancodes are completely different between the two.) There's any number of potential causes, from badly written code to hardware failure to uh.. badly written code. An i8042 will, by design, continue to transmit the keystroke until the Break code is sent. I'm suspecting it's firmware because frankly, the i8042 should see a second Make followed by a Break, and Break all for that scancode. (Since you can't hit "W" again while it's still held and the second Make should be considered spurious.)
My hunch given Sinzz had an identical problem is that it's bad firmware or bad clock generator or uC - because timing absolutely matters. A lot. If it's intermittently or reliably sending a Break code on the RISING edge of clock? The i8042 will reject it. If the pulse rise is less than 5 microseconds? Rejected. Could also be that it's seeing inhibiting of transmission and NOT retransmitting. And even sniffing wires with an oscope will only confirm/disprove - won't give you root cause.
Also doesn't entirely rule out host - but it'd have to be two identical i8042 implementations with identical BIOS. The identical i8042, not so uncommon - probably ITE SuperIO on both. Identical BIOS? Highly unlikely since KBC's still somewhat frequently modified by ODM. Short of that, it'd have to be a problem common to the keyboard - which means identical failure mode in hardware or firmware bug. Either way, need more data.
-
Humm, I use multiple Pokers and none of them shows that behavior...
But then again Im running them on USB, not PS2, so PS2 compatibility could be the problem.
-
I also have 2 Poker, but use them on USB, I never have this stupid problem. Use usb instead. PS/2 is not official feature as far as I know, it just happen to 'work' in PS/2 so you can't really be upset if it don't work right as it was not advertised to as far as I know.