-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Request: Support for Steelseries Prime Wireless #172
Comments
Thank you for all the detail. If someone is able to reverse engineer the device, I can help to implement it in Rivalcfg :) |
What do you need? I can probably do some USB packet traces from a Windows 10 QEMU VM. Do you have a sepcific test schema/plan I could work with? |
Yes I need some packet capture. While capturing packets, you have to change one setting at time in the SSE3 and match the changed setting with captured packets. I wrote articles about that on my blog (they are in French but Google Translate should help):
Here is an example of of the work done for the Aerox 3 Wireless:
As it is a Wireless mouse, the work must be done twice:
(ProductID and commands are a bit different in wired and wireless modes) :) |
So, I finally found the time to look into this. This is what I got so far: https://gist.github.com/haemka/45f135661090438518fbd97a64dde52f But I'm having a really hard time, finding any hint at battery levels. I was able to reproduce your reverse engineering process of battery levels for my Arctis 7 but that does not seem to help with this mouse. The protocol seems to communicate battery levels in another way. Maybe you (@flozz) or @gort818 could give me some pointers, where to look for this last missing piece? Edit: Unknown but maybe interesting captured packets are listed, here: https://gist.github.com/haemka/45f135661090438518fbd97a64dde52f#otherunknown-packets |
Hello ! I started working on the Prime Wireless. Currently I implemented DPI, Polling Rate and Color in wired mode:
Can someone test it works? The work is in the |
Update:
:) |
Thanks for your work! So far everything listed above seems to work. Only shortcoming (not sure if that's intended) I realized is, that I can't use the dpi-Button to cycle through sensitivity. The button seems to only switch to the next higher level until the highest level is reached. From there on a reset of sensitivity levels or full settings reset is needed, which will also re-select the lowest level from where "upwards selection" is possible again. |
@haemka for the dpi button, its behavior is implemented by the mouse firmware so I cannot do anything for this :/ I get some info about reading the battery level so I added it:
can someone test this too? :) |
;) |
I added Sleep Timer and Dim Timer:
If someone can confirm it works before I merge this to Note: I will not implement brightness setting (as it is already possible to do this using a darker color). I will not implement smart mode neither for now. |
Sleep timer seems to work. At least when testing with 1 minute ( Dim timer seems to behave somewhat strange. But I'm pretty sure this is the default for this device as I haven't seen any other behavior since I got it. Regardless of the setting the LED will light up bright for about half a second when the mouse is moved and dims afterwards. If movement persists the LED keeps turned off. I recorded a short video of the behavior: https://youtu.be/Iane0guFExI |
Hum The timing is probably wrong too, I forget a byte ... Can you also try with "command": [0x23, 0x0F, 0x01, 0x01, 0x00], and "command": [0x23, 0x0F, 0x01, 0x00, 0x00], |
Stops turning off the LED on movement. But does not change any timings
Turns the LED off on movement and dims immediately after stopping (same behavior as before).
Lights up on movement and dims after the specified amount of seconds. This seems right. But that "accidental implementation" of smart mode (which I had probably always enabled and didn't remember) was also nice. :) |
Thank you, I fixed the implementation :) |
This mouse is now supported by Rivalcfg v4.6.0 :) |
Function wise very similar to the normal Prime mouse, which was added through PR #169, but wireless.
Webpage: https://steelseries.com/gaming-mice/prime-wireless
Wireless mode (1038:1840)
(Wired mode is below)
kern.log:
lsusb:
Wired mode (1038:1842)
kern.log:
lsusb:
Logs generated on:
The text was updated successfully, but these errors were encountered: