Starting with our V3 keyboards released February 2019, the firmware is upgradeable. Older keyboard models such as the V2, V2.5, and V1 keyboards are not upgradeable to V3. You can check your keyboard's model number via the sticker on the bottom of the keyboard.
V3 Firmware Updates
Version 0.15 (November 20th, 2019)
WASD V3 and CODE V3B
- Windows Updater: FW_015_FN.exe
- Mac Updater: MAC_FW_015_FN.zip (please follow this tutorial here) *Note: currently having issues with the very latest MacOS release (10.15 Catalina), our devs are working on it. Updating on Mojave works as it should.
Patch Notes:
- V3 v0.14+ Manual
- Adds Macro programming
- Adds RGB LED indicator light programming
- Updates DIP settings to v0.14 specs
- Fixed - Indicator LED randomly turning off issues
- Fixed - Pgm key relocation
- Fixed - Issues with Fn as a macro
Known issues:
- PS/2 not supported due to programming functions, if you need PS/2 please use our legacy V2.5 firmware below
Reverting to 2.5 firmware on a V3 keyboard
Some customers have requested the ability to revert back to the V2.5 firmware on their V3 keyboards, so we are offering this downgrade. The main reason you'd want to do this if you want Dvorak or Colemak on a dipswitch, but you will be giving up the macro and led indicator programming functions at this time.
We will be offering the ability to program a full Dvorak or Colemak layout in a future firmware release, but if you need on-board Dvorak and Colemak and don't want to wait for that release, please use this in the meantime.
You can always flash back and forth between 2.5 and V3 0.14.
WASD V2.5
- Windows Updater: v2.5-7692.exe
Updating on Linux using a Windows Virtual Machine
- Download VirtualBox for your OS (https://www.virtualbox.org/wiki/Downloads)
- Install VirtualBox using default settings
- OSX users may get security prompt for Oracle during installing. Be sure to click Allow on your Security & Privacy Settings window.
- Download a Windows 7 test image from Microsoft (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/)
- Select Virtual Machine: IE8 on Win7
- Select Platform: VirtualBox
- Load the Windows 7 Virtual Machine
- You can open the .ovf file directly from Finder OR
- Open VirtualBox, click Import, select the .ovf file, and click Continue
- After Windows loads, from the VirtualBox Menu bar, click on Devices >USB > SONiX USB Keyboard
- Open Internet Explorer and goto https://support.wasdkeyboards.com/hc/en-us/articles/360018518874-Keyboard-Firmware-Updates and download the appropriate update file.
- Run the update file as instructed on our Firmware Updates support page.
Comments
28 comments
There are no links in the article. How are we supposed to update the firmware? More detailed instructions would be nice.
I download the right executable file and run it, but it show that "Can't Find USB HID Device".Unplug and reinsert is also useless.And then I run it as Administrator, it works. That's great.
Hey folks, just a heads up that if you upgrade the firmware, be sure to download the .9 manual listed above- the DIP switch settings change a bit from what was sent out in the box (which I'm now seeing is labeled V2/V2B).
Hey I installed the firmware which indeed fixed the ~ issue. But now even after I set both switch 1 and 2 to ON, Mac mode is still not activated, i.e. the Command key and Option key is not swapped. Any idea?
[UPDATE]: Ok I have to do a factory reset and then the new settings can be applied. The instructions can be clearer, or the firmware installer should flush the settings.
You are requiring a windows virtual box to upgrade the firmware of a keyboard? Who greenlit that as a work around? That is just plain lazy.
I agree with Scott above. This is ridiculous, to say the least. I'm downloading a FOUR GIGABYTE WINDOWS VM to run to fix a bug ..... in a keyboard. Where one single key doesn't work right. You must be kidding me. WASD just shot from my most favorite to least favorite keyboard vendor.
Scott - It's just a temporary workaround until our devs can release the mac updater tool. We apologize for the delay, we just didn't want to leave our mac bros hanging with nothing. This page will be updated as soon as the mac updater tool is released.
Paul - if you're just trying to fix the tilde bug, please just turn off "mac mode" (SW1 off) and use your OSX keyboard settings to swap command/option locations, this is going to be a much easier option than installing windows in a VM. This is the best option in the interim while awaiting the mac updater.
Thanks!
Thanks David! Sorry I flipped out so fast. My expectations got pretty high after so much love and success with my other WASD keyboard. The first thing I did on my new keyboard was flip up DIP 1 & 6 after double checking the reference card. I didn't know this tilde key problem was only in Mac mode. The OSX setting is a great workaround, and as a bonus it does not affect the actual laptop keyboard. I suspect it affects all other USB keyboards, but of course, my only other wired keyboard is CODE Brown in my locker at my favorite co-working space. ;-) Will flip down DIP 1 there too!
May I suggest, here above, you lead Mac users directly toward this fix? And that the Windows VM workaround is probably going to make them pull their hair out, and is only temporary while you guys develop a native firmware updater for OSX? Thank you for your quick and professional support.
P.S. If Slack, github, Bear, and so many other tools weren't so into markdown mode with ` and ``` used so much, this would never have been such a big deal! 8^)
It's really ok Paul, I totally understand the frustration; especially if something "should" be working correctly and it's something as simple as this.
OSX actually assigns the flip to that specific keyboard so it should remember which keyboard you have plugged in and which settings go with that keyboard ID. It also should not affect the onboard laptop keyboard map, there should be a drop down so you can select which keyboard these settings are applied to :)
This bug was only introduced to a very small amount of keyboards, all versions prior did not have this bug and all versions after have newer firmware, it's just a small batch of keyboards that got out with this bug while we were dealing with development of the V3 firmware. We're very sorry for the headaches that this has caused.
One should not ever have to code without the tilde key! Thank you.
I was told at the 29th of April that a new firmware release would be out "soon" that may (or may not) fix the LED bug that I have on my Code V3 keyboard. Would this be the page that firmware will become available? When is "soon"? :-)
Hello Bas,
I'm sorry but the LED bug will not be fixed on the next release (at least from my understanding of the new firmware at this moment), we are expecting it to be fixed in the release after.
We are finished with the 1.0 release, we're just making the one-click updaters right now and then we will post them up on this page.
Thanks!
I came here to ask/check about the LED bug status... but apparently we are out of luck for the time being. Hopefully the next version, with this bug fixed, is not that far away.
I didn't think I would miss/need the Caps Lock indicator, but I was wrong :-/
Hey David,
Reading your post two weeks ago, has moved me to the edge of my seat! There I have sat. Every day. All day. All nights.
Today is Day Thirteen. My feet have become some intellectual construct. My back hurts as bad as it did on day 4 (one of the bad ones). And though my jeans have been worn away by my wooden chair; i'm yet to lose skin (thanks for the woollen boxers Mom!). Before the end, I hope to feel the sun on my face. Just Once would be enough.
My fear of missing the firmware update by just one click, has made travelling to The Outside unthinkable (as I trust it has for so many others). But I'm afraid that if I don't make the journey in a week, I probably will not make it back. I want these thoughts of the sun to melt! Like the silly little dreams they are (so don't worry).
Hence this post. David, I ask you: am I justified in my unwavering belief ‘Any second now’? Or, will the update take a few more days, and I can thus safely (try to) reach The Outside to be back in time?
Thank you either way! From Holland with love, Jente
Hello Jente,
I apologize for the delay, we do have the updaters for two PIDs, but we need the third before I can put them up. As soon as I can get that last one I will put them up.
Please email us info@wasdkeyboards.com and I can help you out. Thanks!
Hello David,
I see that there is a new firmware available. I downloaded it and tried running it but the updater always fails with an Error: Can't Find USB HID Device!!
Is an updater missing? Previously there were two (I don't remember if the last time I updated I used the first one or the second one)
Thanks!
Hello Rodrigo,
If you had previously updated to the V3.09 update, please do the downgrade to 2.5 first, then use the V3.14 (7691 version) and that should get you set on the latest version. I'll see if I can get a 7692 version for the customers that had updated to the V3.09. Sorry for troubles! Thank you. :)
Hello David
Thanks for the info. But now it's worse. By all accounts I have a bricked keyboard.
I used the 2.5 updater, it finished Ok. I unplugged the keyboard, waited for 10-15 seconds, plugged again, and now it doesn't work. At all. I have turned the computer off completely, tried re-running the 2.5 (and the 3.14) versions but now both say they don't find the USB HID Device. Windows also complains that it doesn't recognize the plugged device.
I have tried also resetting the keyboard but it doesn't do anything.
Help!
So, a little bit more info. I plugged the keyboard into my Mac and it works. I couldn't use the reset DIP switch (it didn't do anything, I don't know if with version 2.5 it's another setting?)
Then I plugged it again on my PC, the first LED turned on for a couple of seconds, then off, and the same: the keyboard is not working. Any ideas?
Edit: I deleted again the devices in Device Manager that said weren't recognized, plugged it again, and now it works. But I had already done that before... strange. :-/
Edit 2: The v3.14 updater still doesn't work. Tried the 2.5 again and it gave me the same error about not finding the HID device. Unplugged and plugged again and it doesn't work again...
Edit 3: Ok, after noticing that to upgrade to v3 again I had to use the CODE fw updater, and doing that on another computer, it appears to be working correctly now. Hopefully the LED issue is solved for good!
Thanks!
Thanks for trying so many things Rodrigo and I'm glad you were able to get it working :)
Yes, if you're on the 3.09 firmware, you need to first go down to 2.5 firmware, then you can flash to the 3.14 firmware by using the 7691 file (regardless if you have a V3 or a CODE V3). Once V2.5 is flashed, the PID is 7691, so the V3.14 7691 version is the only one that will work (as you have found out).
We will be getting a 7692 version so you can flash direct from V3.09 to V3.14 without having to downgrade first.
Sorry for the troubles, but I am glad you were able to get it to the latest version.
Hi @Weyman,
I'm trying to run the firmware update with a handful of errors.
First, here's some details of my setup:
- WASD V3 Cherry MX Clear
- MBP 13" 2016 (Four Thunderbolt 3 ports)
- Apple official multiport adapter (https://www.apple.com/shop/product/MJ1K2AM/A/usb-c-digital-av-multiport-adapter?fnode=8b)
- macOS 10.12.6
- VirtualBox 5.2.30
- Win7 VM suggested on this Support article
- FW_014_PGM.exe from the link in this Support article
I'm facing 2 issues:
a) even though the keyboard is useable in the Win7 VM the SONiX firmware updater fails to locate a valid device and doesn't complete
b) eventually the Win7 VM crashes (I think this is unrelated to you process but could be a symptom of the actual issue)
Any ideas or workarounds will be very helpful.
Thanks!
Hello Ignasi,
I'm sorry to hear that you're having trouble updating your firmware. The only thing I can think of that may be causing an issue would potentially be the multiport adapter you're using? I'm thinking this is possibly changing or translating the PID number of the keyboard on the windows VM. One way to rule this out is if you have a simple passive a-to-c adapter.
I'm not sure why the entire VM would be crashing, but you may want to try a different version of windows - I would try the win 10 1806 stable version from the MS link above next.
The best (fastest/easiest) workaround would be to find a friend, family member or coworker that has a windows machine that would let you borrow it for a minute to do the upgrade. Our VM workaround is really for the people that sincerely do not have access to any windows machine, or to where the effort it takes to get access to one is greater than going through the steps to install a VM on their mac. We're still working on the mac updater tool, and I just want to reiterate that this is a temporary solution to updating our firmware on a mac.
We'll leave no mac left behind, so if you can try a different adapter that would be my first guess. If you don't have that or can't get access to one, email me (info@wasdkeyboards.com) and I have a tool to where you can manually enter the PID and I'll show you how to find it on the VM and that will work. Worst case scenario I will send you a return label and update your keyboard for you here.
Please let me know, thanks!
So, I've been looking with interest at the Code V3 programmable features and waiting for the firmware changes to settle down since I want to purchase it in working condition—I don't have time to muck around with firmware upgrades or downgrades for a keyboard.
I have two Code V2s, one a 104 key and the other an 87 key, and both working perfectly, but one is set up on the family computer and the other I move between work and home. I want to have one to leave at work.
However, I rely heavily on the DIP switch 3 functionality to change the Caps Lock key to an extra control key. Having that functionality missing from the Code V3 is a deal breaker for me.
Are there any plans to restore that functionality?
Hello Mike,
At the moment if you need hardware caps / control swap the only way is using our V2.5 firmware on a V3. Running V2.5 fw on a V3 will disable the programmability and LED indicator customization, so you'd need to consider that. We're working on a new build of fw that should allow correct modifier remaps, so you can swap caps / control as if it were on a dip.
Thank you.
Thanks. I don't suppose there is an open (i.e. public) issue tracker for designs/plans/bugs/suggestions for the firmware, is there? (Would be really awesome if there were.) Looking over what's controlled by the DIP switches in the old V2 manual versus in the V3 manual, I feel your firmware design team could benefit from some more open discussion and ideas.
You do a fantastic job on hardware, but there are some oddities (bloopers) in the DIP switch design choices...e.g., SW6 to control whether the Pgm key is enabled or disabled, but that's a bit redundant because SW1 and SW2 *already* control whether you're in programmable mode or not. (I do understand that you might want to program the keyboard and then prevent accidental reprogramming, but it seems a bit of a niche case.) And the layer switching requires the function key, so why have a whole DIP switch devoted to enabling or disabling the Fn key (SW5)?
I submit that the Caps Lock to Control swapping is sufficiently widely needed that it is *far* more deserving of a dedicated DIP switch than the Fn key or especially the Pgm key.
However, maybe all these suggestions are exactly what you're already working into the new build of the firmware. :)
-----
On a separate note, as a backup plan, would it be possible for me to order a new V3 and request that it come with the old firmware? I would guess so but just want to verify. (I'm hoping the new firmware will allow for super simple Caps->Ctrl mapping.) :)
Hello Mike,
Unfortunately we don't have any public view or way to interact with the development of the firmware, I agree it would be very awesome if it were. I think having an open source firmware in the future would solve this issue, which is something I have spoken to our CEO about implementing in the future.
We made it so you could enable/disable the Pgm key because some users won't use and won't care about having programmable functions on their keyboard, but would care to have their Right Ctrl key functionality, and without a hardware dipswitch to enable or disable this wouldn't be possible. This is the same for the Fn key, some users really want to have their Menu key and don't care for the onboard functions using Fn.
I understand that you believe that Caps to Ctrl should be on the dipswitch, but I could see other users arguing that Caps to Esc should be the one, or Caps to... etc. The point of the programmable keyboard is to make it so you can just program what you want and not need the dipswitch for things such as this, which was the goal from the start and that mark was missed with this initial release. Our newer build will have it so you can program caps to ctrl without any issue.
Yes, we certainly can ship you a new V3 with our older V25 firmware on it by request, all you'd have to do is email us your order number after checkout and we can make sure you get this firmware on your board before shipment.
Thank you.
Please opensource the firmware ASAP.... you sell keyboards not firmware :) I would love to be able to tinker around in the firmware and run custom firmware on my keyboard :D The programming interface is very primitive imo, let the community improve it :D its like free value added . . . I have a feeling i am not the only programmer who bought one of these and would love to mess with the firmware
I totally agree with you! As an electronics engineer and firmware developer (it's my real job) I'd be absolutely excited by the possibility to modify the firmware and improve the macro programming!!! Maybe also developing a SW utility which enables to do all the macro creation with a visual interface on the PC and then simply download it to the keyboard... just an example!
Hello Kaitlyn and Maurizio,
Thank you both for your feedback :) I will pass it along to our CEO. We most likely will have an open source firmware in the future, just not sure of an ETA on that.
Thank you!
Please sign in to leave a comment.