Keyboard Firmware Updates

Follow

Comments

28 comments

  • Avatar
    Andrew

    Thanks for this great firmware update! I noticed that the 5-second backlight timer option seems to be missing. I don’t need it but it is listed in the user guide so I thought I’d mention it here. For me, there are 8 backlight timer settings (including OFF). The lowest one is 10 seconds.

    1
    Comment actions Permalink
  • Avatar
    Warren

    Thanks for the firmware update and for listening to our requests!  :)  I had actually reprogrammed an entire layer to Colemak before the update and I'm very happy that I can now simply toggle Colemak with a dipswitch.

    The backlight timer function is also a great feature.  However, I can confirm with Andrew that the 5-second backlight timer is indeed missing and that the lowest setting is 10 seconds.

    1
    Comment actions Permalink
  • Avatar
    h49yj8cpbfq3okrb5txem9c55954w63n

    Hi David, thanks so much for listening to what was probably a very niche request from a vocal minority!

    I’ve managed to test the backlight timeout feature further and have come across a bug. The ‘countdown’ for the timeout is started by the first key press and is not reset by any subsequent keypresses. I can reproduce this consistently across timeout lengths.

    For brevity, if I focus on the 10 second timeout length and let the backlight turn off, pressing a key will turn on the backlight, 8 seconds later if I press another key (multiple times even), the timeout countdown is not reset and the lights turn off after 2 seconds.

    If I keep typing, the countdown should keep getting reset back to 10 seconds so that the backlight doesn’t actually turn off. What’s happening at the moment even as I hammer out this comment is that the backlight blinks off briefly every 10 seconds.

    Is this something that can be addressed?

    Thanks so much for your patience and help!
    1
    Comment actions Permalink
  • Avatar
    David

    Thanks guys, I can confirm that there is some issues with the consistency of the backlight timer and I will have our devs check it out. 

    0
    Comment actions Permalink
  • Avatar
    David

    Ok I can confirm that there is no 5 second setting, 10 seconds will be the smallest increment. I'm very sorry for any confusion. Everything else is correct, just that it starts at 10 seconds, I have updated the comprehensive manual to reflect this change. 

    As for h49yj8cpbfq3okrb5txem9c55954w63n I wasn't able to replicate this issue, Warren and Andrew were you having this issue in any of your experiences so far? 

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Warren

    Hey David.  Yes, I experienced the same thing.  If I set the timer to 10 seconds, it turns off at 10 seconds regardless of how many keys I press.  So while keystrokes will wake the back light, they will not reset the timer.

    1
    Comment actions Permalink
  • Avatar
    Andrew

    Yes, I am also experiencing the issue. It is extremely strange.

    With the timeout set to 30 minutes, all I noticed was that occasionally the backlight would just turn off way too early. Like, there’s no way 30 minutes had passed since I typed something. It had maybe been 10 minutes, not sure. This happened multiple times.

     

    Set to 10 seconds, I can replicate the issue every time. Wait for backlight to turn off, press key and start stopwatch, press a key at any point before the 10 second mark, backlight turns off at 10 seconds.

    If I really go at it (like smash my hands on the keys for 8 seconds), I can make it work as expected, and there will be a full 10 seconds of gap before the backlight turns off. And (super strange!) there seems to be a ‘transition period’ where if I type a moderate amount (say 35 keystrokes), it extends the backlight timer a bit. So instead of turning off at 10 seconds, it’ll turn off at 12 or 13 seconds (even when I stop typing at 8 seconds). And if I type a ton (say 100+ keystrokes), it will go a full extra 10 seconds after I stop typing. It’s like a game. 

    Hope that somehow helps.

    1
    Comment actions Permalink
  • Avatar
    David

    Andrew and Warren great, thanks so much guys, I will do more testing on my own and also with our firmware developer, I appreciate the feedback! 

    1
    Comment actions Permalink
  • Thanks very much David! Selfishly for my purposes, 10 seconds as suits me perfectly as the lowest increment.

    Thanks for confirming my suspected insanity Andrew and Warren. I can consistently replicate this, rapidly, with the 10 second timeout. The only time I noticed an inconsistency with this was with the scenario Andrew described. I make many keypresses within 10 seconds, it will occasionally go for longer to about 12 seconds from the first keystroke. I’m unsure if this is just inconsistent behaviour or intentional logic in the firmware.

    The cleanest solution would be drop any ‘games’ and make it a straight reset of the timer for any keystroke with the backlight is on.

    Thanks very much for looking at this David!

    0
    Comment actions Permalink
  • Avatar
    Isaac

    I'm experiencing a fair amount of buggy inputs on a V3 with the new firmware, keypresses are being ignored, delayed, or repeated. Usually each effect takes place over about half a second.

    This is unfortunately a rather frequent issue, occurring multiple times a day. Is this something that you're aware of, and approximately how long would it take for a fix to become available?

    3
    Comment actions Permalink
  • Avatar
    David

    Andrew and h49yj8cpbfq3okrb5txem9c55954w63n I have a new firmware build to test for backlighting consistency, I will send it to you guys to test as well. 

    Isaac and Luke Hamburg I have seen this issue randomly before -unrelated- to the new firmware, I don't believe this is the cause, but if we can have you test the old firmware again (not V2.5 but the older V3 firmware 0.17 version) and isolate that would be great. I have some troubleshooting steps to fix this issue but so far I haven't been able to find the exact cause, as it's intermittent and only affecting a very small number of users. If you don't already have a ticket with us (I believe Isaac does), please email us so I can help you work through this particular issue. 

    Thank you 

    0
    Comment actions Permalink
  • Avatar
    Luke Hamburg

    David thanks, I don't have 0.17 (I flashed down to 0.16). Not sure how to email you directly.

    0
    Comment actions Permalink
  • Avatar
    David

    Hi Luke Hamburg you can just email info@wasdkeyboards.com and I'll find your email :)

    0
    Comment actions Permalink
  • Avatar
    Fernando Vieira

    Hi,

    I've version 1.20 firmware, and I'm having same problems as reported by Isaac and Luke Hamburg.

    Beside those issues I've another one, related with Caps Lock, Scroll Lock and Num Lock LED lights. Those are allways off. This is this something that you're aware of?

    0
    Comment actions Permalink
  • Avatar
    Andrew

    David, have you sent the test firmware yet? I don’t have an email from you.

    0
    Comment actions Permalink
  • Avatar
    David

    Luke Hamburg I think this issue may be mac related specifically, as I did get one other email about this particular issue. Fernando Vieira please view Luke's thread here; https://support.wasdkeyboards.com/hc/en-us/community/posts/1500000868402-Firmware-1-20-V3-anyone-having-problems- I asked some questions and it would be good to get your input as well. I'm assuming you are also on Mac? 

    Andrew I sent you an email with the new firmware to test, so far it's working well. 

    0
    Comment actions Permalink
  • Avatar
    Andrew

    For what it’s worth, I just used 1.20 on Mac for a few hours and never noticed any stutters or missed/double presses.

    0
    Comment actions Permalink
  • Avatar
    David

    Andrew It may take a while longer to see any issues, so please let us know if you encounter it with more use. Luke Hamburg did you see this issue immediately after flashing? 

    0
    Comment actions Permalink
  • Avatar
    Fernando Vieira

    David, sorry not to mention before, but I have the keyboard connected to a PC, and the dip switches are SW1 off, SW2 off, SW3 off, SW4 off, SW5 on, SW6 on. Main purpose is to have a basic keyboard setup/experience. I'll read Luke's thread and give you feedback.

    0
    Comment actions Permalink
  • Avatar
    David

    Fernando Vieira Ok thank you, most likely this is a separate issue - I have helped Isaac fix his similar issue either changing to a 2.0 port or updating the 3.0 or chipset drivers. With Mac it's a different story as this is probably more depending on system version than individual drivers. You can also email our support and I can walk through some troubleshooting with you. Thanks 

    0
    Comment actions Permalink
  • Avatar
    Fernando Vieira

    David, thanks for your immediate feedback. I've read Luke's thread, and as he mentioned the Mac firmware, I've guessed the PC equivalent (https://www.wasdkeyboards.com/media/wysiwyg/support/firmware/FW_016_MOD.exe). I flashed the keyboard. I've again Caps Lock, Scroll Lock and Num Lock LED lights working, and no lag when writing this post.

    0
    Comment actions Permalink
  • Avatar
    David

    Fernando Vieira I haven't heard any other reports of the new firmware making any difference like this, please email us so I can see if we can replicate this issue. Thank you 

    0
    Comment actions Permalink
  • Avatar
    Danny Lovell

    Hello. I'm using a Code V3B on Windows 10, and trying to learn how to use and program the macro layers. Since the update to 1.20, I cannot even switch between layers using FN+[M|<|>|?]. I tried plugging/unplugging the keyboard with dip switch 3 ON and OFF (all other switches OFF), and the third LED always serves as a scroll lock indicator. Any ideas what I could be doing wrong? I was at least able to switch layers before updating, even though I couldn't get the Prgm key to do anything.

    0
    Comment actions Permalink
  • Avatar
    David

    Hello Danny Lovell with the 1.20 firmware you'll want to make sure SW3 is "on" so you can see the layers being switched. You'll also want to make sure you have the Fn key enabled as well, or you won't be able to switch layers. 

    Can you let me know your dipswitch settings? 

    You might want to reset the board and see if that fixes any issues as well. 

     

    0
    Comment actions Permalink
  • Avatar
    Warren

    Is there any update on the fixes?  Thanks.

    0
    Comment actions Permalink
  • Avatar
    David

    Warren all bugs are fixed, working on one last backlight bug a customer found, it's for the most part inconsequential to most users, but we will fix it. I have the latest release with 99% fixed, email us and I can give it to you. Thank you. 

    0
    Comment actions Permalink
  • Avatar
    Warren

    Thanks David!  I'll shoot you guys an email.

    0
    Comment actions Permalink

Please sign in to leave a comment.