Skip to content
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

How can I check if my mouse is compatible ? #72

Closed
waterreedshimmer opened this issue Dec 18, 2018 · 8 comments
Closed

How can I check if my mouse is compatible ? #72

waterreedshimmer opened this issue Dec 18, 2018 · 8 comments

Comments

@waterreedshimmer
Copy link

waterreedshimmer commented Dec 18, 2018

Hello, my gamer mouse uses: Steelseries Engine pilot. It's an Acer Predator Gaming Mouse - product: PMW510 - but it's build by the same company then Rival. Steelseries says they don't support its pilot but I think it is same pilot, as any past and future version of this pilot works well on Windows, and as Acer uses the pilot from their website - this download address was written on the box, I no more have -, so I usually use the latest.

sudo apt-get install build-essential python-dev libusb-1.0-0-dev libudev-dev
sudo apt install python-pip
pip install rivalcfg
→ Installing collected packages: setuptools, hidapi, rivalcfg
→ Successfully installed hidapi-0.7.99.post21 rivalcfg-3.1.0 setuptools-40.6.3
rivalcfg --version
3.1.0

Actual Steelseries engine version is: Download Engine 3.13.3

How can I test to know if your pilot works on my mouse ?

You may need to know I was on Windows 10 before, so inside the mouse already has its configuration and works well. But now I am on Ubuntu Studio 18.04. For its shape it has 2 left buttons, one roll on top, plus one click button I never knew use. And forward the left and right click buttons. So it's 6 features plus the light that is OK in red and the rolling with light on horizontal plastic material that should have fine pixels.

@flozz
Copy link
Owner

flozz commented Dec 18, 2018

Hello,

I looked at some photos of your mouse, it seems to be a Rival 300 (rebranded for Acer), so it should be compatible with rivalcfg... once we know its product id.

Can you give me the result of th efollowing command:

lsusb | grep 1038:

:)

@flozz
Copy link
Owner

flozz commented Dec 18, 2018

Also, can you confirm it is this one : https://www.ldlc.com/fiche/PB00199792.html ?

@waterreedshimmer
Copy link
Author

waterreedshimmer commented Dec 18, 2018

Hello, here it is:
dracchingan@earendil-light:~$ lsusb | grep 1038: Bus 003 Device 005: ID 1038:1714 SteelSeries ApS
Yes it's the same. I bought mine a few years ago, maybe 3years ago, but I don't think they changed it.

@flozz
Copy link
Owner

flozz commented Dec 18, 2018

Ok,

so can you try the following command (as root):

RIVALCFG_PROFILE=1038:1710 RIVALCFG_DEVICE=1038:1714  rivalcfg -c red

The light of your mouse should become red

If this work, it will be easy to add support for this mouse :)

@waterreedshimmer
Copy link
Author

waterreedshimmer commented Dec 20, 2018

Hello, my USB does loop, and the inner pilot must have a few differences with the Rival 300 although I used to use same engine to change colour. I'll also post some information that may help you:
`dracchingan@earendil-light:~$ RIVALCFG_PROFILE=1038:1710 RIVALCFG_DEVICE=1038:1714 rivalcfg -c red
[DEBUG] Rivalcfg 3.1.0
[DEBUG] Python version: 2.7.15rc1
[DEBUG] OS: Linux
[DEBUG] Linux distribution: Ubuntu 18.04 bionic
[DEBUG] Forced profile: 1038:1710
[DEBUG] Targeted device: 1038:1714
W: The following mouse was found but rivalcfg was not able to open it:

  • mouse: SteelSeries Rival 300 (1038:1710)
  • error: Unable to find the requested device: 1038:1710:00

Please check that no other application is controlling this mouse and try to:

  • unplug the mouse from the USB port,
  • wait few seconds,
  • and plug the mouse to the USB port again.

[DEBUG] Selected mouse: None
Usage: rivalcfg [options]

rivalcfg: error: no such option: -c

dracchingan@earendil-light:~$ lsusb -v | grep -A117 1038:
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Bus 002 Device 003: ID 1038:1714 SteelSeries ApS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1038 SteelSeries ApS
idProduct 0x1714
bcdDevice 0.68
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 200mA
Interface Descriptor:
Couldn't open device, some information will be missing
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 37
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 74
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 76
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1

Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
dracchingan@earendil-light:~$
`
There is no pilot download option in the Acer website, there was Steelseries Engine in the box that works for anything that has to do with customization. And plus, this might be a website that took something different then what the Rival website proposes. https://drivers.softpedia.com/get/KEYBOARD-and-MOUSE/Steelseries/SteelSeries-Predator-Gaming-Mouse-Driver-2320-64-bit.shtml

But anyway, my mouse works, it's not this the problem. I just wanted to know how far compatibility was =)

@flozz
Copy link
Owner

flozz commented Dec 21, 2018

Hello, it seems there is a small bug in one of the debug functions... Anyway, I implemented the support of your mouse too let you try if it work...

Please run the following commands to test:

# Install git if you do not already have it
sudo apt install git 

# Clone the rivalcfg repository and go in its directory
git clone https://github.com/flozz/rivalcfg.git
cd rivalcfg

# Switch to the branch where I implemented support for your mouse
git checkout acer-predator-gaming-mouse
git pull

# Try if it work (this must be run as root as udev permission are not yet properly configured)
sudo python -m rivalcfg -c red

@waterreedshimmer
Copy link
Author

waterreedshimmer commented Dec 22, 2018

Hello,

Thank you very much for this fantastic work, your driver is now perfectly configured for the Acer Predator Gaming Mouse - NP.MCE11.005 - 6500 dpi, a mouse deeply inspired on the Steelseries Rival 300 mouse as the configuration tissue is the same, the light can change colour =)

First I did:
pip uninstall rivalcfg
Then I did follow your commands to install it again =)
It said in french that the branch 'acer-predator-gaming-mouse' has the parameter of following the far away branch 'acer-predator-gaming-mouse' starting from 'origin'.
Then it said that pull is already up to date.

sudo python -m rivalcfg -c red
sudo python -m rivalcfg -c yellow
sudo python -m rivalcfg -c blue
sudo python -m rivalcfg -c green
sudo python -m rivalcfg -c orange (orange doesn't exist)
Usage: rivalcfg [options]
__main__.py: error: option -c: invalid color: 'orange'
sudo python -m rivalcfg -c white
sudo python -m rivalcfg -c black (black is lights off)
sudo python -m rivalcfg -c red

I have 2 entrances in 'souris et pavé tactile' (mouse and touchpad) in Ubuntu Studio 18.04, but I think it's due to the fact that I can plugin the mouse in 2 different USB ports. I did put both acceleration and sensibility at max. It's just my mouse carpet that is not perfect. But I think I feel everything all right =)

Testing sensibility:

sudo python -m rivalcfg -s 6500
(that gives ballet feeling, it is too many pixels)

sudo python -m rivalcfg -s 3500
(that is fast but it's good)

Testing polling rate:

sudo python -m rivalcfg -p 250
(does angular curves on GIMP)

sudo python -m rivalcfg -p 1000
(makes soft curves on GIMP)

So all works =) =) =) Thank you very much =) =) =) =) =) =) =) =) =)

Should I close issue ?

@flozz
Copy link
Owner

flozz commented Dec 23, 2018

Thank you very much for your issue and your feedbacks. The support of the Acer Predator Gamin Mouse is now released in rivalcfg 3.3.0 :)

Should I close issue ?

I prefer closing it myself once everything is done (so now as I released the new rivalcfg version) ;)

@flozz flozz closed this as completed Dec 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants