Support for x52 (non pro)

Question

Support for x52 (non pro)

winiciuscota opened this issue 8 years ago · 14 comments

Hi, Does this driver work on the x52 (non pro)?

I just need a way to turn off those annoying leds

Answer 1 · 2016-12-22T16:45:37.000Z

I only have the pro. It works very well and is easy to use. Some one with the x52 (non pro) might comment, but I would suggest that you consider running a test and posting your results for others.

I think it's a good question and am interested. Personally I would expect for most of the common functions between the two to actually work.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

Answer 2 · 2016-12-22T17:20:41.000Z

I have a check during initialization for the product code that is specific to the X52 Pro. Since I don't have the non-Pro version, I have no clue about the functionality. It should be fairly straightforward to add a case for the non-Pro model here - https://github.com/nirenjan/x52pro-linux/blob/master/libx52/x52_core.c#L30

I'd suggest along similar lines as @apollothethird to pull the source code, modify it to accept the non-pro version and run your tests.

Answer 3 · 2016-12-23T11:18:15.000Z

Thanks for the instructions. I have little experience on c but I'll definitely try that when I have more time

Answer 4 · 2017-01-11T06:19:00.000Z

@winiciuscota, I've added support for the X52, but as the commit message states, you cannot update the LEDs individually. I'd need to know the control messages for those in order to update the library. However, you should be able to reduce the brightness down to zero for the LEDs, assuming that the control messages are the same between the pro and non-pro models.

Answer 5 · 2017-03-07T22:34:01.000Z

@nirenjan Sorry for taking this long to test it. That worked perfectly!

Answer 6 · 2017-03-07T22:54:32.000Z

Could you try to verify if the other commands work? My assumption is that apart from setting the LED states, everything else should work as is.

Answer 7 · 2017-03-08T00:19:40.000Z

All the commands are working(except for led and I didn't tested raw). Attempting to use led gives this message: Error: Operation not supported. The mfd command is awesome, I didn't even know it was possible to change the mfd text on the x52 non pro

Answer 8 · 2017-03-08T00:56:11.000Z

That's awesome! I'd still like to identify the LED commands, so let me know if you're ready to try some raw commands to try and turn on or off the LEDs.

Answer 9 · 2017-03-08T02:29:36.000Z

I can do that as long as there is no risk of destroying my device

Answer 10 · 2017-03-10T06:35:15.000Z

Seems like the API is more or less the same between the X52 and X52 Pro. The only info I have though is that the LEDs are probably single color blue LEDs on the X52, while they are red/green LED pairs on the Pro.

The risk is minimal, IMHO.

Answer 11 · 2017-03-10T06:50:26.000Z

Can you describe what LEDs are glowing on the X52 when you first plug it in?

Answer 12 · 2017-03-28T14:53:41.000Z

The easiest way to add support for the LEDs would be to snoop the USB messages from a Windows instance which has the Saitek drivers installed. The manual is no help - it simply states that you can control the LED brightness, but doesn't say anything about the individual LEDs.

Answer 13 · 2017-03-28T20:54:03.000Z

Use WireShark, select the USB device for capturing packets, while only capturing when changing the color. I started doing this myself, but have been quite busy.

If I'm not mistaken, the bytes you need to look at are marked something like "extra data". The initial bytes are usually USB protocol stuff, and already labelled by WireShark. Sparse data on the web with replaying packets using C, etc.. (Please correct me if I'm wrong.)

Answer 14 · 2020-05-06T22:27:50.000Z

Well, according to this website, the LEDs cannot be individually controlled on the X52 (non-pro). Given that the library already supports everything else, I'm going to close this issue.