I had just received the keyboard today and the first time I plugged it in everything was fine. When I went to update the firmware on the keyboard first using the software and then on google both times they crashed and gave me an error saying the connection had timed out. I have tried different cables and ports so far, none of which have worked. The inputs and lights do not work, but when connected the device is being shown as wooting restore but so far what I have tried has not worked.
#wooting 60he connection time out during firmware update
hidden hare
royal peak
How is your USB setup structured, like how is the Wooting connected to the PC? For example are you using a USB hub or switch or so.
hidden hare
So the motherboard im using is an asus z-390a and I’m using the cable it came with which is plugged in to a dark blue usb port by itself
royal peak
So the Wooting is directly connected to the I/O port of the mainboard on the back of the PC?
royal peak
Please provide all error logs of the desktop Wootility. You can find these at the end of the troubleshooting section in the settings menu.
In the case you own a USB hub please test if it works with that. Please also try it on a different PC.
I'm currently investigation into a rare edge case related to USB connection issues. These are limited to specific systems. So the device is normally working fine on other systems.
hidden hare
Do you want me to try updating the firmware on a different pc too or just test to see if the keyboard works?
royal peak
It's recommended to update the firmware to the newest version. So far I sadly don't know why it's not working on some systems.
Two use cases where I had the chance to deeper look into where related to the usage of USB hubs.
Possible that the system where it don't work have an internal hub. To rule that out it would be nice if you can share picture of the device manager on the none working system where the node of the Wooting is selected but the view is changed to connection.
Like this:
hidden hare
ill have to restart my pc to get the troubleshoot log files because the program crashes
royal peak
You have not selected the Wooting node first and also not changed the view to connections afterwards. So I don't know how the system chain looks like.
To identify the Wooting node it's best to change the view to container, that way you can find it by the name.
hidden hare
royal peak
You now need to select one of the two nodes in the "Wooting restore" tree and then change the view to connections.
hidden hare
royal peak
ill have to restart my pc to get the troubleshoot log files because the program ...
You can start the app without a keyboard connected. But because the device is in restore mode now anyway it should not cause issues anymore.
I will check the logs tomorrow in the case you provide them.
hidden hare
the device was always in restore mode
after plugging it in for the first time and then trying to update the firmware it crashed, after that it continued to register as wooting restore
ill send the logs now then
hidden hare
Tried to update firmware again today, still crashed
hidden hare
I was able to update the firmware using my friends computer and it works now when I plugged it into my pc, I am now unable to use profiles
royal peak
Was the Wooting always registering as "Wooting Restore" or did it work normally when connected to your friends PC?