Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 342 conversations about:
Qphilkv
21
May 2, 2017
bookmark_border
johnham
54
May 7, 2017
bookmark_border
Qphilkvit shouldn't type anything at that point. Download the latest drivers, download the LATEST configurator. Plug it in, hold down the reset button for a few seconds, go to the device manager and install the drivers you downloaded how the instructions tell you. After that, unplug it and plug it back in. Reset it again with the configurator open. It should show up. Not all those steps are necessary but just to be certain. With the M4-A, i had an issue with it not being recognized on an old line of hp computers and could not fix it.
The most updated configurator is here: https://github.com/MachineIndustries/configurator/releases/tag/v1.1.6
Instructions here: http://www.machineindustries.co/guides/configurator-manual
The most updated configurator is here: https://github.com/MachineIndustries/configurator/releases/tag/v1.1.6
Instructions here: http://www.machineindustries.co/guides/configurator-manual
Qphilkv
21
May 8, 2017
bookmark_border
johnhamThanks for your help. I read the windows drivers installation instruction in detail. The problem is that the on Windows 10 device shows up as an HID keyboard rather than ATm32U4DFU in the device manager. Plug in and play installs the device and the device automatically becomes an a-g HID keyboard.
I never have the opportunity to install the drivers because it won't register as an ATm32U4DFU device.
Pressing the reset button doesn't help, the device reappears as an HID keyboard in the device manager.
I've replicated this problem on three different machines, including a brand new Surface Pro 4.
I'm going to try Linux and see if I have better luck.
Any advice for windows users?
I never have the opportunity to install the drivers because it won't register as an ATm32U4DFU device.
Pressing the reset button doesn't help, the device reappears as an HID keyboard in the device manager.
I've replicated this problem on three different machines, including a brand new Surface Pro 4.
I'm going to try Linux and see if I have better luck.
Any advice for windows users?
johnham
54
May 8, 2017
bookmark_border
QphilkvI have done it on windows 10 and windows 7 both worked fine. Did you try and change the drivers in device manager even though it installed as an HID keyboard? I vaguely remember mine not installing as the AT device. Just trying to help - from my frustrations with the M4-A it was tough. A last option would be to reach out to machine industries and see if they can send you a new pcb.
JFKroflcopter
39
Sep 1, 2017
bookmark_border
QphilkvHi Qphilkv,
I just bought an unused Rama kit from another user and I'm experiencing the same exact issues that you described. Did you ever find a solution and get your device running as intended? If so, could you share what steps you took to fix it?
Thanks!
I just bought an unused Rama kit from another user and I'm experiencing the same exact issues that you described. Did you ever find a solution and get your device running as intended? If so, could you share what steps you took to fix it?
Thanks!
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
Here's a description of the problem:
- 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 Windows 10.
-Configurator won't recognize device
Thanks for looking into this!