Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 342 conversations about:
massdrop27percent
120
Machine Industries
Apr 17, 2017
bookmark_border
THFC
1
Apr 17, 2017
bookmark_border
massdrop27percentI just plugged mine into my Mac (10.12.4). I got the pop up asking for key next to shift. I just closed out without doing anything. Configurator shows disconnected. I've hit reset, restarted, unplugged, etc. Nada. Is this part of the known issue? I have a very pretty rose gold paperweight that is starting to frustrate me. Thanks.
Sikh
9
Apr 17, 2017
bookmark_border
massdrop27percentMy reply didn't save :(.
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.
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.
Sikh
9
Apr 17, 2017
bookmark_border
THFCI believe it is specifically this part
"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.
"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.
Qphilkv
21
Apr 17, 2017
bookmark_border
massdrop27percentThanks for the update, and thank you so much for your efforts to resolve these issues.
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!
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!
massdrop27percent
120
Machine Industries
Apr 17, 2017
bookmark_border
THFCHey there @THFC, could you shoot me an email to josh@machineindustries.co, I'll give you a hand getting you set up, hopefully we can get your pretty rose gold paperweight working :)
KCCoffeegeek
18
Apr 17, 2017
bookmark_border
THFCSame here. I found if I press a key several times on the "press the key next to the shift key" popup on the Mac then it will allow me to use the M10a for letters A through I. Unfortunately my 2u key at the bottom does nothing and that's also the key that isn't clicky like the rest of the Blues I ordered. Not sure if that key is messed up or if it's a non-issue. Either way, I can't get the Configurator to work, either, even with pressing the reset button and etc. Hopefully Configurator updates will fix it and that weird non-clicky switch ends up working!
paintwalls
13
Apr 17, 2017
bookmark_border
massdrop27percentI appreciate the shout out. And I'd like to thank you for all the hard work you both have put into all this. And a very special thank you, on top of that, for fixing the save/load function! The relief I feel right now...sooo much better.
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?
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?
Related Products
Drop Refurbished
Like-new products you can trustDrop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collectionCollaborate With Us
For Brands & DesignersFollow Drop
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