Caps Lock issue
I purchased my custom keyboard a few months ago, and have been VERY happy with it, with one exception:
The Caps Lock indicator light turns itself off about once or twice a day. When I unplug, then reconnect the keyboard cable, the light is fixed, but then a few hours later, it shuts itself off again. Any suggestions to fix this? (I'm on a Mac running High Sierra).
-
Hi, If you haven't already, try a factory reset on the keyboard. Unplug, enable dip switch 4 on the back, and plug back in. The indicator LEDs will flash red for about 20 seconds, turn solid blue, then solid green when the reset is complete. The blue phase may not happen, which is fine, just wait for solid green before unplugging. You can then disable dip switch 4 and plug in again.
Another possible fix would be to make sure you're on the most recent version of the firmware. (https://support.wasdkeyboards.com/hc/en-us/articles/360018518874-Keyboard-Firmware-Updates)
If you're still having issues with it, let us know!
-
Hi Paige. Thank you for the tips, but unfortunately they didn't work. Tried both the dip switch 4 factory reset and the firmware update. Both processed exactly as you described, but the caps light indicator light still stops working once or twice a day it seems. Do you have other suggestions by chance?
-
Interesting, I'm sorry to hear the issue persists. Are you using Karabiner, by chance? There should be some setting allowing it to take control of LEDs and disabling that may do the trick. Beyond that, I'd have to do some digging. It is possible the unit is defective, please do email us and we can get an RMA started if that ends up being the case.
-
Hi Paige. No, I am not using Karabiner (didn't even know what that was until you mentioned it - had to Google it.).
The issue is frustrating, though it's not the end of the world. Apart from that, I am extremely satisfied with the keyboard. Yes, I need to unplug it, and then replug it in pretty much once a day, which isn't ideal but it's not catastrophic either.
My mac is still running High Sierra OS (I can't update to Mojave or Catalina because the editing software my company gives me won't work on those systems). Could that be the reason why the keyboard keeps having this issue?
-
Thanks for the additional info. It very well could be a High Sierra issue/conflict, I believe Mojave was current when the V3 models came out and every macOS update since has required an update to the firmware installer.
One last possibility I can think of is to revert to the legacy v2.5 firmware, if you're not using the programming functionality of the keyboard. We don't have a mac updater for it, since it is used far less frequently, but if you have access to a PC it may be worth a shot.
We can certainly take a look if you were to send it in. If the conflict is with High Sierra we would not be able to do much most likely. If it's something else we'll do what we can to resolve it.
-
Hey Paige. Thank you, but I would rather just live with the issue then send it in and be without my editing keyboard for any length of time. I'm just going to chalk it up to the High Sierra situation. But I appreciate your help with this. It's unfortunate the tips did not work, but I still am very happy with the keyboard. And I can deal with unplugging/replugging it in once per day. Thanks again, and happy holidays!
-
Hi,
I'm having the same issue with a keyboard purchased in september 2020. The capslock LED doesn't fire on anymore after the next restart of my computer, running Archlinux. If I unplug and replug the keyboard, the LED is working as expected, until the next restart.
I've just checked the method to upgrade the firmware, but I don't have enough time for now, to configure a whole virtual machine for this. -
I too have experienced the issue with the Caps Lock LED failing to light on my CODE V3 (received in Novemvber 2021), sometimes multiple times a day, but it would also work fine for a a day or two at a time. My CV3 also occasionally exhibited the key repeat and sluggish response problems mentioned in another WASD support thread (I also had some other known problems which were addressed by flashing from the as received V0.14 to V1.2 firmware.) Since all the remaining problems I was having were already mentioned here and a future firmware update to address at least the key repeat issue was apparently in the works, I was more comfortable living with things as they were and waiting than flashing back to address the repeat issue.
My patience started wearing a bit thin after about 4 months as I got tired of rebooting the PC to get the light working again and found hot plugging-replugging the keyboard would fix the light quickly, I just needed to make it easier to do. I ended up adding a 3.3ft/1m USB A Male to Female extension cable to allow the keyboard to be unplugged and replugged from near the front of the PC without having to slide it out of the hole where it lives and do a reach around. That was about four weeks ago, haven't seen any of the problems or had to replug the keyboard since!
This may help explain why only some people are experiencing these problems. Although all computers and peripheral components are supposed to meet the same industry standard specifications, there are tolerances, and it's possible for a combination of individual in-specification (but possibly borderline) components to "stack up" to yield an out of specification system, and cable capacitance can be a factor too. The PC I'm using the CV3 on is an always up to date Win 10 Dell XPS 8930 and I still have the OEM WASD supplied USB C to A cable attached to the keyboard. None of my ("several") other keyboards exhibit these particular problems on the same compuiter, but I can't use them any more because they don't have a full complement of Cherry MX Greenies and I'm now hopelessly addicted.
Please sign in to leave a comment.
Comments
9 comments