-
Notifications
You must be signed in to change notification settings - Fork 36
M990 Legend (not RGB/Chroma) support #5
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
Comments
Hello and thanks, i just saw this issue and had a brief look at the captures. From the official software, that you posted, the USB PID appears to be 0xfc0f, and therefore different to the other M990. I have added the PID to the list of known PIDs, this should hopefully allow you to open the mouse and maybe change the profile with the existing generic support. If that doesn't work, could you post the output from There are a few questions that i have now:
The next step is to implement all features in a dedicated backend. |
I have added a new branch Currently implemented features (i will update this over time), any feedback is welcome:
|
In my previous experiments, running lsusb -vv output:
All 26(including scroll wheel) of them, except that there must be at least one left mouse click button somewhere.
The mouse includes a single programmable LED. https://redragon.ru/catalog/gaming-mice/legend-laser-24-buttons-16400-dpi https://redragon.ru/catalog/gaming-mice/legend-chroma-rgb-24000dpi-24-buttons I'm not quite sure what's the difference between them, but Chroma seems to have more LED's in it and also more lighting options. Here are the differences in GUI options side by side.
Yes
Also yes. Although, the software I'm using is somewhat broken. The UI implies that polling rate, pointer speed, acceleration and color schemes are different for each profile, but only the currently selected profile's settings are applied and they do not change when profile is switched. |
Thanks for the info, that really helped to get a general understanding of the features. Unfortunately i am now certain that this mouse uses a different data layout (not such a big deal) and different keycodes, led mode codes, etc. (bigger problem) than the other known mice. This makes it basically impossible to reverse engineer without capturing an amount of data and immediate experimentation that is only practical with access to the hardware. Therefore the situation is as follows:
I am sorry that i could not be of much help to you. Your contributions are welcome, and i will support you as best as i can if you decide to start working on this. |
Thank you so much! You are a life saver! I've been looking for this software for ages and I decide to look at this repository (and it's issues) one more time in a false hope that compatibility for this mouse would be added. Sadly, compatibility has not been added, but you are genuinely a life saver for uploading your copy of the software. Thank you again! |
Hey there. Been watching this project for a long time. Keep up the great work!
Unfortunately, though, the current build does not support my M990 Legend(PN70389) with any of the available profiles. And I've been too busy to capture the USB data... until now.
So, here it goes: https://github.com/rfxDarth/m990_capture_data
If there's anything else I can provide or help you with, please, let me know.
Note, though, that this is different from M990 Legend Chroma(PN 78345) as the software is incompatible. There might have been even been multiple revisions, as the software they offer for 70389 is broken too. So, for anyone who might stumble here from google, I've uploaded an older but working version to https://github.com/rfxDarth/m990_legend-software.
The text was updated successfully, but these errors were encountered: