January 9, 2017 at 1:24 am #5088
I’ve had my board for a few months now. When I first got it, i uploaded the firmware and everything was all fine. Today I tried to change the LED’s as I wanted new colours but get an error: ‘error setting action: communcation error with device’
I’ve tried using a different USB cable, uninstalling the keyboard from device manager, holding U when connecting, holding ctrl when connecting and re-uploading the firmware but nothing seems to be doing anything.
Can anyone help? I can still type on it, would just like to change the LED colours. Thanks!January 9, 2017 at 8:48 am #5089
switched to a different usb port which i never use and works nowJanuary 9, 2017 at 3:55 pm #5094
Hojin.YiJanuary 12, 2017 at 6:18 am #5114
I have the same issue. The keyboard behaves just fine, but unable to connect.
Windows 10. Removed the device from windows (including the full way using the utility), using new cables and not going through a hub. I am still unable to make changes or connect to my keyboard using the bootmapper client.January 12, 2017 at 12:09 pm #5117
Sorry for your inconvenience.
I want to know a few things
– Your order number
– Dose your keyboard work?
– Could you explain when that problem happened?
Hojin.YiJanuary 13, 2017 at 9:41 pm #5127
I don’t have the order number (it was a gift), but I can email you enough details that you could probably figure it out. The keyboard functions as a normal keyboard, but I am unable to change the RGBs, connect to it, or change the key mappings. I can hold left ctrl and plug it in, then firm up, but then it goes back to the previous behavior.January 13, 2017 at 9:49 pm #5128This reply has been marked as private.January 13, 2017 at 10:18 pm #5131
I guess some drivers were installed not properly.
Please check all the drivers for ps2avrGB to be installed like the pic I attached.
After removing ps2avrGB driver, connect your keyboard to a computer again.
Attachments:You must be logged in to view attached files.January 16, 2017 at 10:33 pm #5142
To help anyone else, I had previously deleted the drivers instead of uninstalling the drivers, using USBDeview. Uninstalling is what it took for proper reconnection.
You must be logged in to reply to this topic.