Dropped key inputs, occasional lag
I have a V3 on the newest firmware, and I'm experiencing pretty frequent issues with key inputs not registering or taking about half a second to go through.
Others have mentioned a similar issue, is there going to be a firmware update or hotfix that can be applied to fix this any time soon?
-
Derek Konigsberg I haven't been able to reproduce this on any of our computers here, until I can replicate this we won't be able to determine the cause or fix the issue. This seems to be happening only with specific systems, some troubleshooting steps so far that you should try;
1. If you're running through any hubs / switches / monitors / kvm, etc.. try plugging directly into the computer and let me know if that changes the behavior (some customers updating the USB drivers for their specific device fixed it)
2. Please try different USB ports, if you have 2.0 ports these might be preferable to try first (some customers this fixed the issue for them)
3. Try updating your chipset drivers and USB drivers if applicable (known to have fixed with the largest number of customers)
4. If you're not using the programmable features of the V3, please try flashing to the V2.5 firmware (https://support.wasdkeyboards.com/hc/en-us/articles/360018518874-Keyboard-Firmware-Updates) (this fixes the issues 100% of the time)
5. Oddly - flipping the USB-C connector over at the keyboard port fixes the issue for a few days, but it comes back
6. Try updating the firmware to the latest 1.20 release
Thank you -
Derek Konigsberg V2.5 will fix it, most likely some other option will fix the issue for V3 firmware however.
Can you let me know your dipswitch settings? Also Isaac can you let me know your dipswitch settings when you were on the V3 firmware with this issue. I previously couldn't find any correlation/pattern with dipswitches, but would be good to get more data.
Thanks
-
My dip switch settings were the default (I believe that's all off). After downgrading to v2.5, I toggled the one switch needed to get the backlight control keys working again.
If I had to speculate as to what's happening with v3, I'd think something stalls/freezes, hits a watchdog timeout, triggers a reset of something, and then dumps a buffer. But without any knowledge of how the hardware/firmware works, or what makes v3 different from v2.5, that's just a wild guess.
-
Thanks Derek Konigsberg,
So far my understanding of what is happening is that the USB connection is being interrupted off/on very quickly. I'm not sure what is causing this interruption, or why updating the drivers seems to fix it for most people. Every solution that works for some negates the leads for cause in others so I don't have a definitive pattern to even solve it so far. It's something with the V3 firmware but also paired with certain USB controllers software/firmware.
I don't believe it's hardware related as I have received keyboards back experiencing this issue that I cannot reproduce on my systems. -
Bumping this thread to say that my new V3 had these issues. TL;DR flashing to firmware 2.5 fixed it. I was even able to do it from Parallels, you just have to pipe the keyboard directly to the VM by doing Devices > USB > Keyboard in the menu bar.
I have a Mac mini (2018), and plug the keeb in via a USB-C to USB-C cable directly into the machine. I did try USB-A, but it did not help.
-
Robert E. O. Speedwagon V2.5 should fix this issue, also if you want to use the V3 programmable features, I have found through testing that 0.16 also fixes this issue, you can get it here: https://support.wasdkeyboards.com/hc/en-us/articles/4414920068119-Firmware-Past-Releases
Something about the 0.17 fix (and up) that causes this issue for some systems. Our devs are currently working on it for the latest firmware. If anyone has any system that is exhibiting these issues that they can send us for testing purposes it would speed up that process. So far with my testing on many different machines I cannot reproduce this key repeat / lag problem.
-
So the machine I've been using with this keyboard (Intel NUC11TNH /w Win10) has also had a share of non-keyboard-related issues that could also be attributed to USB weirdness. This included a USB barcode scanner that would sometimes stop working, and (perhaps unrelated) a case where RDP would stop accepting connections. I suspected it was the fault of power management misbehavior, so I went into the Windows device manager and explicitly turned off power management on every single USB device node I could find the checkbox on.
Since then, I've upgraded back to the V3 firmware, and (fingers crossed) its been behaving thus far. But its really too early to be certain its a real fix, since some of the affected things are occasional-use, and it still feels like a bit of a kludge.
I am somewhat curious if all these wonky behaviors would change if I upgraded to Win11, but since the whole reason I'm even running Windows on that box is "max compatibility with poorly-maintained desktop apps", I'm not too eager to do that just yet.
-
Hello Derek,
From my experience, power settings do not affect this at all.
If you want V3 programmable features, I have found through testing that 0.16 also fixes this issue, you can get it here: https://support.wasdkeyboards.com/hc/en-us/articles/4414920068119-Firmware-Past-Releases
Please note that backlight timeout was not implemented this far back so it does not have this feature. We're still working on figuring out what this problem even is, once we can do that we will issue a new firmware update with the latest.
If anyone has an old computer that exhibits this behavior that they can send to us to borrow for testing it would be greatly helpful.
Thank you.
-
I'm just writing to say I have a similar issue with the keyboard seemingly "restarting" in the middle of typing. Using macOS 12.3.1, latest V3 firmware, and the keyboard is connected through a hub in my Dell monitor. Things were working fine for months with this setup, but I'll start by removing the hub from the equation, then try another cable, and then maybe flash an older firmware. I, too, really enjoy the backlight timeout and would like to keep it. Otherwise this has been a great keyboard, and thanks to WASD for continued development!
-
Thanks @Matt Shirley
It could be the hub, also could be a new Mac update that caused it. Hopefully bypassing the hub will work, but if not please try the older 0.16 firmware (specifically that version). My devs are still working on trying to figure out this issue, so far we cannot identify any pattern, but we're still testing things. As soon as we can isolate and solve this issue there will be a firmware update to fix it.
If you're still having issues, please open a support ticket with us and I can help you drill down with more troubleshooting steps.
-
Hello @Ty most likely it's because you have your dipswitches set incorrectly; please check by referring to the 0.16 instructions regarding dipswitches, please set them accordingly: https://support.wasdkeyboards.com/hc/en-us/articles/1500006158881-V3-CODE-V3-Comprehensive-User-Guide-Firmware-0-13-0-17-
Thank you.
-
I have recently been experiencing such lag as well. I've had the keyboard for a while before it started but this isnt an isolated issue. Just before this started happening I had a minor issue with my caps lock led not lighting up sometimes. a simple reconnect of the usb cable fixed that. This however is a bigger issue. At first i tried flashing to different firmwares, trying out the V2.5 and even one of the first firmware updated (the 0.14) yesterday. When that didnt work i got to updating all the drivers i could. I updated the chipset drivers, flashed a new BIOS version on my motherboard and tried flashing the 0.14 firmware again. It worked till the end of the day. Until today when it suddenly started up again. At first it was fine and i even enjoyed the multiple key rollover but after leaving the computer unattended for about an hour and a half (didnt go to sleep cuz i left a YT video running by mistake) and then coming back i once again experienced input lag. I then tried reflashing to the newest version of the firmware and that also didnt fix the issue. All i am left with is to try the 0.16 suggestion. I am currently on V2.5 firmware and as of writting this comment havent experienced this issue. The only "fix" that i found was restarting the PC and hoping that it wont happen again 30 minutes into heavy typing usage.
Edit: As i am writing this edit the keyboard has begun to lag again (it took me a while to write this edit). I am now on 0.16 and there is no difference. I already tried the keyboard on usb 2.0 ports and the lag was happening there as well (i am currently plugged into a 3.1). There is only one other version of USB ports on my board but i don't think the issue is in the connection. When hitting CAPS twice in rapid succession the keyoard led lights up and shuts down with a seconds delay. The issue appears to be internal to the keyboard. I have a Ryzen 9 5900x with an Aorus x570 master motherboard and 64 gb of ram and i am running windows 11. I now no longer know what to do. Once again i restart my PC and hope the issue doesn't persist
-
Given that WASD clearly has no idea what they're doing with firmware for these keyboards, I honestly just gave up on the whole thing. Last spring I put my CODE keyboard in a bin, and bought a brand new backlit TKL keyboard from Razer instead, and it just works. No problems, no constantly flaky USB issues, nothing really to complain about (beyond desktop software updates being just a bit too frequent).
-
So after much deliberation, i decided to open up the keyboard. As it appeared to be an internal issue i opened it without any issues. Then after removing the pcb and turning it over i found a few things. One, a bug, small flying one, had been fried on one of the switch contacts. Removing the bug was not simple as some of the burned residue was stuck to the pcb. After removing the bug i inspected the chips on the pcb. The big chip (Sonix SN8F22E88BFG) along with the smaller sonix chip seems to have a dot in one of the corners. The dots are (im assuming) supposed to have paint smeared in them. The smaller one has blue paint but the big chip doesnt. Now it could be a factory fault and they forgot to smear it, but around the dot was a bit of residual bronze paint and some white-ish unknown residue. The hole itself was paintless. Im not sure if it can be assumed that chip bruned through and melted the paint away, but its one of the options. And lastly i found 2 soldering contacts without a capacitor(?) on them. Next to them was the mark R206. Im not sure if this is correctly manufactured or not as i cant find any pcb schematics online. Everything else on the pcb seems to be in order. Im not suspecting the usb connection to be at fault here as per the delay on the LED state changes i mentioned in my previous comment. I have not gotten the chance to try the keyboard yet but i would appreciate any insight with these findings.
-
So my issue seems to have been resolved. I've had 2 days without any lag or other problems. What seems to have done it was setting up Safe Boot in my BIOS. The new BIOS version apparently reset it. This is the only thing that comes to mind when the issue stopped. I hadn't changed firmware versions since i flashed the 0.16 one. Hopefully this now becomes history and i dont have to bother with it again.
Edit: Ok after 3 days of no problems the lag came back after i forgot to shut off my PC through the night. After a weird no input upon wake up issue being resolved by unplugging the keyboard i found myself with the issue again. This time i did the following: i reset the keyboard with the dip switches then reflashed the 0.16 firmware and right after that restarted my PC. This seems to have done it. I had tried all of these by themselves multiple times but never in rapid success. Hope this helps someone.
Please sign in to leave a comment.
Comments
20 comments