I’ve just tried my brand new Keyboardio out of the box into (two different) Windows 10 computers. Both of them have popped up the USB “Device Not Recognized” error. I can safely say power is making it to the keyboard–the LED button works, and the lightshow is lovely–but I would also love if keystrokes made it back to the PC.
Any suggestions for how to debug? (Also posted to Twitter; feel free to reply in either venue)
Hey Danyel! didn’t know you were getting a Keyboardio! Welcome.
I finally resurrected our household ASUS pc last night with the latest Windows 10, and the keyboardio just worked when I plugged it in. I haven’t tried flashing it yet, but if you’re not getting keystrokes there is definitely something unusual going on with your setup.
If you can’t get it sorted, would you like to bring it down here and we can check it out? I’d offer to come to your place for a visit, but I’m stuck here for a while. The accident has really slowed me down. I’m sure we can figure it out, though. First thing I’d try is plugging mine into your setup to see if there’s something off with your Model 01 or cable.
@Jen, thanks for the offer! And, yes, trying it on a machine that isn’t managed by my employer might be a useful comparator, too.
Ok, just did a little test, inspired by Jen’s note, and plugged it into my Pixel phone. (I happened to have the USB-C to C converter here). It works fine on the pixel, as far as I can tell – I was able to type characters – so I think I’d feel ok saying that we’ve ruled out the physical device.
@FisherDanyel: Based on the .corp internal hostname, I’m going to assume my guess about your Redmond-based employer is correct. I worked in Building…43? for about a year in '99.
I know that everything has changed since then, but my recollection is that at the time internal Windows builds were…just a bit different than shipped builds.
I also know that local domain policies can lock down a lot of behavior that would be perfectly acceptable on a vanilla install.
Sadly, since I was in the Exchange org an not the Windows org, I never actually learned that much about the internals.
I 100% believe we’re doing something that Windows sees as weird (and the Code 43 error does give me some hints), but I’d love to be able to repro before I start blindly trying to fix it.
The good thing is that I’m 99.99% certain this can be fixed over USB with a firmware update.
The USB VID and PID aren’t showing up as what we send, but if Windows is flipping out and refusing to talk to the device, that’s not too surprising.
If you hold in the Prog key when you connect the keyboard, you should see it start to glow Red. That’s the bootloader mode. I’d love to know if that throws the same errors. If it does, this is potentially more serious, but not necessarily insurmountable.
And I presume the bad cable was the one we shipped you? That’s still worth reporting. We’re happy to replace it with another, if you want. For that, shoot us email at firstname.lastname@example.org and we can start to figure things out.
Out of curiosity, does the cable work “upside down”? (It might be only one set of bad pins.)
And just to double-check, does the good cable still work “upside down”?
Yup! I’m working out what I can do while still post-concussive and mostly prone. So far, I’ve never really learned to touch type, so that’s one of the things I have been able to do. Also chattering on forums, and listening to audiobooks.