Fried Keyboard AW510K

[Alex-Galvan]

After being frustrated with trying to customize my AW keyboard and Mouse with AWCC I decided to try out AlienFXtools. I had no problem messing with my AW610M mouse lights and computer lights, but when I started with the keyboard all was going well until I started trying the Reactive Keys / Rainbow FX light features ... when clicking those features my keyboard suddenly turned off and disconnected from the PC (Alienware m15r3) and couldn't start trying to reconnect without success. I tried restoring the PC before installing AlienFXtools and nothing changed, I can almost confirm it damaged the hardware itself ... Users beware!

[T-Troll]

Hmm... I have 410k at my table, same chip. So what exactly you're doing right before it "broken" (in fact not)?

Reactive Keys / Rainbow FX

Such interesting terms... Let me guess, there it comes from...

[T-Troll]

Ok, let's investigate this deeper.

First, it's looks crazy for me, i don't mess with keyboard logic itself, only light chip inside it. So i can break the lights (but i know a way to reset it), but not keys.

So, some questions come:

• Is this keyboard present into device view, even as unworkable? If yes, what exactly it shows in the list?
• If not, do you try to use other port/computer to make sure it's not R3 port fault (this can happen regardless of what i do)?
• I'm interesting to listen what exactly you're doing then it happened.

[jpatchMC]

actually I had the same happen with a 410. made a 5th profile, on 5 went it to change some of the light effects on key press. crash. keyboard disconnect reconnect over and oven. i think "hey maybe its just the drivers on my system" connect to a different system (i want to verify key function i could work on lighting later) same deal with this new system (new system ONLY allows generalized drivers, its corperate)so not drivers but board itself....which i guess is strange, i do know the board can remember about 5 different light configs, if that got corrupted i'm still confused as to why that would break the board entirely. as cool as those button press colors are maybe have turning it on be disabled by default and have a warning about it.....on one hand 2 users isn't many but how many people use it in the way we were. don't take it out, just warn of the possibility of something bad with them.

[T-Troll]

I disable this part at latest release until we check deeper already.

I have 410k too, and use effects as well. It was reset itself a couple of times then i debug it, but still working well. I can provide an app to wipe all light chip settings, if you wish - this may help.

But i need to know what EXACTLY you set right before it happened!

PS: I don't use Alienware drivers, but HID device directly for control. So in case it detected as HID device, it can be accessed.

[jpatchMC]

I don't think I can provide that anymore, I don't remember exactly what happened and deleted it the Hardware profile once I realized how dead it was. also I can't tell what windows detects as it connects and disconnects to fast for me to figure it out

[T-Troll]

Please take a closer look what happened into Device manager - we are interested not in keyboard itself, but into it's HID/Composite device. Keyboard just one element of it, as well as lights.

[jpatchMC]

the period of time that passes between detection and disconnection is about 1.5 seconds

[T-Troll]

First check WHAT device disconnected. Whole hub? Keyboard only?