Add more mice IDs

[MayeulC]

There are a lot of various R.A.T mice out there. From what I could gather, it seems that the protocol they are using is more or less the same.

I think we should add as much IDs as possible (preferably, after checking they are working). Feel free to post yours here if it's not present (it can be found with lsusb, and will probably begin with 06a3:, thus lsusb |grep 06a3 might be easier to read).

[alphaphee]

Mine is:

Bus 001 Device 006: ID 0738:1709 Mad Catz, Inc.

[MayeulC]

Thanks ! Could you specify the mouse model as well?

[alphaphee]

@MayeulC It's a regural R.A.T 9
xinput list output

Mad Catz Mad Catz R.A.T.9 Wireless Mouse    

[MayeulC]

Please try the https://github.com/MayeulC/Saitek/tree/new_VID branch. I added in your vendor ID. I would like to make sure this doesn't cause any regressions (and that ti works, btw) before merging.

I quickly checked the .inf files of the windows driver. It seems that with your mouse, we covered every R.A.T.9 mouse. Now, there's only the 3/5/MMO missing.

[alphaphee]

I switched to new_VID branch and get the following notice:
Could not acquire device handle. Please ensure that it is correctly plugged in and that you have the appropriate rights.
Could it be an issue with the ID?

[MayeulC]

Strange, it should have worked. I added this warning today. As far as I know, it only shows up if the device is not plugged in (it cannot find the vendorID/productID combo), or if you didn't run it with the appropriate permissions (the easiest way is of course with sudo).
You could try adding this debug line after line 57 (just before except, under the try. Be sure to respect the indentation) :

print("trying " + hex(vendor[0]) + ":" + hex(productID))

This would allow you to check that your device is tried, at least. If yours doesn't show up, this could also be because of an exception.
Or, you could also try like you did before, by replacing the vendor and product ID from the master branch with yours.
Let me know how it went.

[alphaphee]

Just to be sure we are in the same page. I am in the new_VID branch and this piece is above line 57.

for product in products:
                try:
                    self.handle = self.context.openByVendorIDAndProductID(
                        0x06a3, product)
                    print("trying " + hex(vendor[0]) + ":" + hex(productID))
                except:
                    pass

                if self.handle:
                    self.hasHandle = 1
                    break

and after compiling it successfully it still prints the same message. Same thing with sudo.

[MayeulC]

Without sudo, that's normal. With it, not so much.
Yep, you inserted it at the correct place. What is the console output after you added this line? Do you see your mouse vendor and product id?
If not, change the above code to :

for product in products:
                try:
                    self.handle = self.context.openByVendorIDAndProductID(
                        0x06a3, product)
                    print("trying " + hex(vendor[0]) + ":" + hex(productID))
                except:
                except Exception as e:
                    print(e)
                    pass

                if self.handle:
                    self.hasHandle = 1
                    break

This should print the error as returned from the operating system. This is probably an enhancement that will make it to mainline too.
(I hope I will not answer until tomorrow, its 00:30 here [GMT+1], but I have some exams tomorrow that need some work).

[alphaphee]

@MayeulC I believe the first except: is copy-paste leftover. Without it, it compiles fine and the output is:

name 'vendor' is not defined
name 'vendor' is not defined
Could not acquire device handle. Please ensure that it is correctly plugged in and that you have the appropriate rights. 

(btw, i am on GMT+2 and a student as well so we're in sync, don't worry.)

[MayeulC]

Strange, could it be that the array is not well defined ?
The whole code is at http://codepad.org/WQD1Og6P
Also try http://codepad.org/qnyG9T6u (which is less complicated).
I hope it will work, but I don't really see why it didn't already.

[rkruk]

If you are still interested with some other R.A.T.9 IDs - here is mine:
Bus 009 Device 002: ID 06a3:0cfa Saitek PLC
and the mouse is: Saitek Cyborg R.A.T.9 Wireless Mouse. That mouse is a very first series of RAT9 (grandpa), but all internal hardware are still the same like with later RATs9 as far as I'm concern.

[MayeulC]

Hello,
Thanks a lot, but this ID is already part of the driver (in fact, I have the very same mouse)
List of supported R.A.T 9 IDs : https://github.com/MayeulC/Saitek/wiki/R.A.T-9-USB-Documentation#usb-protocol

From what I could gather from the windows driver .inf files, there is only these three IDs for the 9 series. Then, of course, there's the other series, but it needs some adjustments to the driver I don't have time to make right now (maybe later this year).

[rkruk]

Cool. Thanks for the link - I'll read it for sure.