Dropped key inputs, occasional lag

Comments

16 comments

  • Avatar
    David

    Hello Isaac I'm pretty sure we solved this issue via support email (at least on Windows) can you update this thread? 

    I have tested on our Mac here with the new firmware and haven't experienced any issues, can you let me know what version of Mac OS you're on? 

    Thank you

    0
    Comment actions Permalink
  • Avatar
    Derek Konigsberg

    Would you mind sharing the cause of this issue and what fixed it?

    I've been experiencing horribly flakyness on my CODE Keyboard (connected to a Win10 machine) that could fit under a similar symptom description, and I'm curious what solutions are worth trying.

    0
    Comment actions Permalink
  • Avatar
    David

    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

    0
    Comment actions Permalink
  • Avatar
    Derek Konigsberg

    I'm not using a hub, and I am plugged directly into the computer. (Its a brand-new NUC11TNH running Win10.) The USB port is likely to be USB 3.0.

    In any case, if firmware 2.5 is known to fix the issue for everyone, then that's what I'll try first.

    0
    Comment actions Permalink
  • Avatar
    David

    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 

    0
    Comment actions Permalink
  • Avatar
    Derek Konigsberg

    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.

    0
    Comment actions Permalink
  • Avatar
    David

    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. 

    0
    Comment actions Permalink
  • Avatar
    Robert E. O. Speedwagon

    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.

    0
    Comment actions Permalink
  • Avatar
    David

    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. 

     

    0
    Comment actions Permalink
  • Avatar
    Derek Konigsberg

    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.

    0
    Comment actions Permalink
  • Avatar
    Derek Konigsberg

    And I spoke too soon...  Keyboard just reset itself while I was typing.

    If it gets too annoying, I'll go back to V2.5 again. Its just that I *really* like the backlight timeout feature in V3. If you just backported that, and nothing else, I'd be happy enough.

    0
    Comment actions Permalink
  • Avatar
    David

    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. 

    0
    Comment actions Permalink
  • Avatar
    Matt Shirley

    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!

    0
    Comment actions Permalink
  • Avatar
    David

    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. 

    0
    Comment actions Permalink
  • Avatar
    Ty

    I am also having this problem on a Windows 10 box. When I roll back to 0.16, my Windows CMD key no longer works. How can I re-enable that once I roll back. I have a V3.

    0
    Comment actions Permalink
  • Avatar
    David

    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. 

    0
    Comment actions Permalink

Please sign in to leave a comment.