Logitech G Pro X Superlight 2 support #2207
Labels
Comments
|
Solaar is reporting the polling rate that the mouse is reporting via the normal methods. It may be that the mouse uses onboard profiles for polling rate instead. Please provide the output of Solaar doesn't currently support onboard profiles but you are welcome to work on supporting this feature. It is a complex feature, perhaps with several variations. You will probably have to sign an NDA with Logitech to get enough information on the feature. Let me know if you want to proceed. |
Who do you think I am? I'm not a Logitech employee or anything, just letting you know. 😅 Anyway, the output of |
|
Thanks. It does look as if most of the device programmability uses onboard profiles, which Solaar does not support. But there are some other features that Solaar does not even have a name for, and might be useful. I've asked my contact at Logitech for information on these features. As far as the onboard profiles feature goes, it is possible to get information about it from Logitech but you have to sign a simple NDA saying that you won't distribute the information further. You are allowed to implement support for the feature in Solaar though. Some of the settings in Solaar have been implemented this way. |
|
Could I get some further information on this? I'd be interested. |
|
Contact me directly at pfpschneider@gmail.com |
|
I have information on a couple of the new features of the mouse - polling rate and adjustable dpi. It should be fairly easy to have Solaar have correct polling rate for the mouse. |
|
I'm not sure what toggling the hybrid switches would involve. Can you tell me more about this part of the mouse? |
|
PR #2229 adds support for the report rate for this mouse. Please give it a try - there is considerable untested code in the PR, so expect bugs. Run To clone and use Solar from its GitHub repository Run Solaar as bin/solaar from this directory. To run PR #2229, first clone Solaar if you have not already done so and cd to the clone directory. The first time you download the pull request, fetch it into a new branch and checkout that branch, as in: To download a new version of the pull request, fetch it and then set your pull branch to the new fetch, as in: |
|
hello, i am testing this out as i just picked up the mouse. i do not see any option to change dpi or report rate
The following is whats in my config.yaml and the following is the output from running with -ddd |
|
@kaneyumin Please provide output of |
|
first run of after after removing config.yaml |
|
@kaneyumin Thanks. Please run |
|
@kaneyumin By the way, the errors in your first run of |
|
here is the output of |
|
@kaneyumin Thanks. There are a couple of bugs. Please download the new version of the PR and try |
|
This mouse uses Onboard Profiles, which is a very complex feature and is not supported by Solaar (yet). So there are things that can be done to the mouse but that can't be done using Solaar. All that Solaar can do with Onboard Profiles is to turn it off so that, for example, the Polling Frequency can be adjusted. |
|
By the way, there are public descriptions of some of the features of the device in https://drive.google.com/drive/folders/0BxbRzx7vEV7eWmgwazJ3NUFfQ28 The feature numbers output by |
pfps
changed the title
|
The other feature for this mouse that can be implemented in Solaar is an extended adjustable DPI. Documentation on this feature is available at https://drive.google.com/drive/folders/0BxbRzx7vEV7eWmgwazJ3NUFfQ28?resourcekey=0-dQ-Lx1FORQl0KAdOHQaE1A It's a moderately complex feature and implementation will take some back-and-forth. The first thing to do is to get some information on the feature on the mouse by probing it using hidconsole - a tool to send HID++ messages to a device. This tool is in the tools directory of the Solaar repository so to use it you can go to where you downloaded Solaar and run HID++ messages can be of several lengths but probaby the best way to go here is to use one length that is likely to work for all messages. The messages start with four one-byte fields - a length code, a device index, a feature offset, and a feature message ID. These four fields are echoed in responses to valid messages. The messages then contain fields specific to the feature and message. The first thing to do is to see how many sensors the mouse has. This can be done by sending 11 01 090F 00000000000000000000000000000000 (the blanks are ignored and only serve as formatting). The response should look something like 11 01 090F 02000000000000000000000000000000 showing two sensors. I'm not sure whether this mouse has more than one sensor and it may be that Solaar will only ever support one sensor. The next step is to probe each sensor using 11 01 091F NN000000000000000000000000000000 for NN less than the number of sensors. This returns information about the sensor in the form 11 01 091F NNXXBB00000000000000000000000000 Then probe each sensor to find out the resolutions in both X and Y directions using 11 01 092F NN000000000000000000000000000000 Finally, probe for the current and default resolutions using 11 01 095F NN000000000000000000000000000000 |
|
Here is the output: It seems I still do not have an option to change the polling rate
|
|
Yes, a stupid bug. Please try again. You may have to remove ~/.config/solaar/config.yaml before Solaar attempts to try to add the setting. |
|
Okay, it seems to work great.
Will there be a way to change the DPI as well? |
|
Hopefully, but I need information on how the feature is implemented on this mouse. See my message above. |
|
@kaneyumin @DexterHaxxor I need help to implement adjustable DPI as described about five comments above. |
|
@kaneyumin @DexterHaxxor Most of the fancy features of this mouse use Onboard Profiles, which is a complex feature not currently implemented in Solaar. Support for this feature may not be coming for quite some time. |
|
With PR #2237 you should see a DPI setting. If you have downloaded and are running this PR and you don't see the setting, run Solaar as Modifying the Onboard Profiles is done via |
|
Here is the log: |
|
Yes, a silly bug, just fixed. Please download the PR and try again. |
|
The exception is now gone, but it is still not working |
|
I forgot to tell you to edit Solaar tries to optimize communication with devices and one of the ways it does this is to remember settings that caused errors or otherwise didn't work. |
|
I removed the entry in the config and also the config itself, but still nothing :( |
|
OK, something is going wrong. Stay tuned. |
|
happy to help too :) |
|
There is a new version of PR #2237 that should work better, but there are aspects of the device that are not covered in the spec so there still could easily be errors. Anyway, give it a try and if it doesn't work post the output of |
|
With current #2237 it seems to not show up here...
|
Same with me, no mouse |
|
Oops, an infinite loop trying to set up the extended dpi setting. |
|
Hopefully fixed now. However, it is unclear exactly what devices will do when the DPI settings are changed the way that Solaar will do. When you get to that point make sure to see whether anything unusual happens. |
|
@CuteSC2 Some of the things you ask for are not something that the mice I have access to support so I don't know what they might correspond to in terms of the features of the PRO X 2. Please try out the current version of PR #2237 and see what it supports and what it doesn't. There are things that Solaar cannot do that Logitech software can. Solaar is not a device driver so it does not process regular messages from the mouse, only special messages that the mouse normally sends or has been set up to send. |
|
Hi @pfps I also have this mouse and would love to see DPI adjustment supported. Anything I can do to help? |
|
You should clone this repository, download the PR (see #2207 (comment) above), and run Solaar as |
No problem. Can I ask, is there a risk of damaging the hardware by running this patch? |
|
The DPI changes are only retained in the device until it goes into a power-saving mode, so if there are changes that you don't like and can't undo all you need to do is to stop running Solaar and turn the device off and on. Most changes that Solaar makes are like this. One major exception is pairing. Another is profiles. That said, any change to any device, particularly devices that have complex firmware, has risk. About the only way around this risk is to only use very simple devices. |
|
Running your PR I can see the following: The X, Y, and LOD options are available. X and Y were set to 800 by default. I tried changing X to 1200 but nothing changed. After playing around with it for a while and quitting out a few times, I tried opening Solaar and setting X to 1000, then quitting with verbose logging enabled (I disconnected the second USB receiver for the PRO X beforehand). Here's a log of that process: It's possible that I may have missed a dependency when installing the various packages through pip. |
|
@deadmeu I expect that you have an active Onboard Profile. This prevents changes to the DPI settings. So to make changes using this setting you first need to disable Onboard Profiles. |
This does not appear to be possible. peter |
|
I have no idea how what you did or if it worked for you, but I am unable to change my DPI or report rate, it appears to work in the UI but has no effect on the mouse and resets when Solaar is restarted. |
|
To have changes to DPI and Report Rate be effective you have to have Onboard Profiles set to Disabled. Please run Solaar as |
|
Closing due to no response. |
|
@pfps Oh, it just started working after a few days somehow and I forgot to respond. You can keep this closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue doesn't really need too many details, but I'd like to get involved with adding support for the Superlight 2 mouse, which I've recently purchased. It's showing up like this:
Wired:
Lightspeed receiver:
Solaar is actually lying in the second screenshot, the polling rate reported by
evhzis 1000 Hz, which isn't the full potential of the mouse but is also perfectly usable for gaming.The mouse doesn't have many features, but 2000 Hz report rate on Linux and being able to toggle their hybrid switches would be great.
The text was updated successfully, but these errors were encountered: