Drop Mech Keys Meetup Recap - Thanks for Visiting!
As you may have seen, we just hosted our first meetup in quite a while here at Drop HQ (Corsair HQ, but they seem to like us enough :) )! It was a blast to get to meet so many enthusiasts local to the bay area—it had been 10 years since I was last hanging out with keyboard nerds in the bay, at KeyCon 2014. We had a great time hosting everyone at the offices, checking out all the very nice boards y'all brought, and sharing some of our own projects/spaces! I knew it would be fun to host in the Game Room when I first saw it in person, but seeing it come to fruition was still so cool. Alright, I'll stop blabbering on now. xD Picture time! (Oh, real quick - there will be more of these! Stay tuned for more info and to catch the next one!)
May 15, 2024
Just to let y'all know, we're debugging your issues now;
1) We've fixed the config save/load issue and are re-building now. We should have an auto-update with you in the next few hours.
2) We've identified an issue with firmware loading in certain scenarios on MacOS, it seems either a piece of software or security setting is preventing firmware upload to the keyboard. As far as we've tested, it appears to be an issue across anything that uses the 'dfu-programmer' utility (which both the Configurator & QMK Loader tool currently use to my knowledge). We're working to find out exactly what setting or piece of software is preventing it from running correctly and we'll update you here when we narrow it down.
3) The driver installation guides on both mine and Rama's websites are a little out of date, the boards shipped from Massdrop with a bootloader called 'ATm32U4DFU' rather than 'LUFA' as it appears in the guides, fortunately both bootloaders should be compatible with one another, so it's just a naming difference - we're going to amend our guides to clear up any confusion on that front.
I just wanted to say a quick thanks to @paintwalls @ASCII @kitfm & everyone else who have been helping users work through issues here, it's very much appreciated!
Again guys, sorry you're having issues, we're going to get them solved as soon as we can and get you back up and running!
Cheers,
-JBL
Anyway, Thank you for the update. I am looking forward to using my Pad and not having to return it.
The OS X issue, is that only Sierra? I have a external with several different versions from Lion (10.7) to Sierra and If it works on older versions, I can quickly flash it and wait for an update.
At the moment, I have the perfect config and If I could just get this flashed, I would be super happy with this thing.
For the driver installation guides, can you please make sure the testing is done on Windows 10 Creators Update? Since this update is going to be pushed out to everyone and you can force update yourself right now, I believe testing on this would be the rest. My current Windows 10 (before creators update) and Windows 10 Creators Update will automatically install the generic driver and recognize it as the "M10-A" in Settings > Devices but in Device Manager its just a "HID Keyboard" device.
Thanks for the reply and I am looking forward to using this Pad :D.
"As far as we've tested, it appears to be an issue across anything that uses the 'dfu-programmer' utility (which both the Configurator & QMK Loader tool currently use to my knowledge). We're working to find out exactly what setting or piece of software is preventing it from running correctly and we'll update you here when we narrow it down. "
So OS X is noticing it as a default keyboard and will type a-j if you press the keys, but the minute you press reset, its not noticing the board in DFU mode. The above covers this so It should be fixed soon.
Just a quick note I am experiencing a problem that is not listed in this update. Several other users have described a similar problem in below threads.
Here's a description of the problem, and more info can be found in comment threads below:
- On Windows 10 device shows up as an HID keyboard rather than ATm32U4DFU in the device manager.
-No option available to install the provided drivers in Windows.
-Device returns letters 'a-j' in OS X and Windows 10, after asking for a standard keyboard config keypress.
-Configurator won't recognize device
Thanks for looking into this! Looking forward to getting the device working, it looks great!
I just wanna ask; Do you have a preference on where/how you would like to see the majority of bug reports and suggestions? Would direct emails be best, or would you prefer a forum where others can give there opinion?