-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redragon K552RGB-1 -- Testing #12
Comments
You can use wireshark to capture the USB communication from the official software and rgb_keyboard for options that don't work. This would allow a direct comparison of the relevant packets, thus giving the best chance to fix these problems. Here is a brief explanation of the process, here are more detailed guides: |
Interestingly, my Redragon K552RGB-1 reports the following under
|
@darrynjordan The keyboard is identified by its vendor and product id (0c45 and 5004), the name is taken from the udev hardware database. Multiple keyboards have the same ids, but only one is entered into the hardware database, therefore you see the wrong name. The hwdb(7) manpage has the details if you are interested, or you can edit the entry at https://usb-ids.gowdy.us/. |
Interesting! Thanks @dokutan. I didn't know about this database. Please note that I have found the following erroneous mappings from label to physical key:
For testing I use I'll be happy to capture the output of the Redragon software using wireshark for these keys. |
@darrynjordan Did this affect remapping of the keys or or custom led patterns? Instead of directly using wireshark, it might be easier for you to simply edit the labels or remove entries in one of the If you attach the fixed map or usb captures i would add a new layout for the K552 (of course you are welcome to do it yourself if you want). |
@dokutan I have not tried any remapping, this was simply for custom led patterns. Thanks, that was a great suggestion. I managed to find the required hex values by running through all of the ANSI keycodes.
It would be great to know if the required values are different for the |
@darrynjordan Thanks for figuring out the correct values, i have added a new layout |
Yep, that works for me @dokutan. Thanks. |
Tested on: Kubuntu 20.10
1. Set active profile 1, 2 or 3
As long as you set profile once and leave it at that, these work fine, great job!
I can set modify them from the original software on Windows and they persist as they are stored on the keyboard.
2. Manual options, e.g.
rgb_keyboard --color 00ff00
It doesn't take any new color.
3. Freeze/Crash
What happens every 3rd or 4th command is it freezes keyboard, which makes the keyboard not work until restart (with only half of the lights on). The last time it also somehow changed the color to green after restart.
Is there a way track any logs to find something out?
The text was updated successfully, but these errors were encountered: