EasySMX D10 Dongle Support

[RayJW]

I have the EasySMX D10 controller, which seems to work fine with xone as long as I use it with Bluetooth. However, I would like to use it with the 2.4 GHz dongle for obvious reasons. But, when I switch the mode, the controller connects fine to the dongle and the seems to be recognized as a controller, but it doesn't show up in any applications.

With the dongle plugged in and connected:

❯ ls -lah /dev/input/by-id/
Permissions Size User Date Modified Name
lrwxrwxrwx     - root 16 Okt 11:13  usb-_Xbox_360_Controller_for_Windows_5F0EE2D8-event-if01 -> ../event27
lrwxrwxrwx     - root 16 Okt 11:13  usb-_Xbox_360_Controller_for_Windows_5F0EE2D8-if01-event-kbd -> ../event25
lrwxrwxrwx     - root 16 Okt 11:13  usb-_Xbox_360_Controller_for_Windows_5F0EE2D8-if01-event-mouse -> ../event26
lrwxrwxrwx     - root 16 Okt 11:13  usb-_Xbox_360_Controller_for_Windows_5F0EE2D8-if01-hidraw -> ../../hidraw13
lrwxrwxrwx     - root 16 Okt 11:13  usb-_Xbox_360_Controller_for_Windows_5F0EE2D8-if01-mouse -> ../mouse1

Since it shows up as an Xbox 360 controller, I also tried with xpad-noone and xpadneo, but since xone has support for EasySMX as third-party controllers, I thought this might be the best place to start getting this resolved.

[Lawstorant]

If it shows up as an xbox controller then it doesn't need explicit support. Thing is, you say xone already has support for EasySMX but you didn't check the VID:PID. It seem that this controller is using a different PID.

Could you post lsusb -v so I can add the proper PID to the wired list and we could test it? It could be added to the upstream xpad as well, so there would be ootb support in upstream linux.

[RayJW]

If it shows up as an xbox controller then it doesn't need explicit support. Thing is, you say xone already has support for EasySMX but you didn't check the VID:PID. It seem that this controller is using a different PID.

Sorry, I assumed as much since everything seems to work fine with Bluetooth.

Could you post lsusb -v so I can add the proper PID to the wired list and we could test it? It could be added to the upstream xpad as well, so there would be ootb support in upstream linux.

Thanks for walking me through this, I think this should be what you're looking for?

Bus 001 Device 007: ID 2345:e062   Xbox 360 Controller for Windows
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2345  
  idProduct          0xe062 Xbox 360 Controller for Windows
  bcdDevice            1.10
  iManufacturer           1  
  iProduct                2 Xbox 360 Controller for Windows
  iSerial                 3 5F0EE2D8
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0050
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     93 [unknown]
      bInterfaceProtocol      1 
      iInterface              0 
      ** UNRECOGNIZED:  10 21 10 01 01 24 81 14 03 00 03 13 02 00 03 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               8
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      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 (null)
          wDescriptorLength     220
          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     0x0040  1x 64 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              32
Device Status:     0x0000
  (Bus Powered)

[Lawstorant]

@RayJW could you test the driver from the easy-smx branch? You can just sudo make test and then plug in the dongle.

[RayJW]

@RayJW could you test the driver from the easy-smx branch? You can just sudo make test and then plug in the dongle.

Hmmm, still doesn't seem to work. I tried it with the LTS and the latest kernel and the dongle still behaves the same, it shows up and connects, but the controller doesn't work.

[Lawstorant]

@RayJW Looking at your first post, the controller doesn't actually show up as a controller/joystick. The controller is in the name, but if you look closely, it's showing up as a keyboard and a mouse.

Does it need special drivers on windows? Any sort of software? If so, I think this might be out of scope for xone and even xpad

[RayJW]

Looking at your first post, the controller doesn't actually show up as a controller/joystick. The controller is in the name, but if you look closely, it's showing up as a keyboard and a mouse.

I see, that makes sense.

Does it need special drivers on windows? Any sort of software?

Nope, not really. On Windows, it's just plug-and-play and for Linux it works fine if I connect with Bluetooth, but not with the dongle. So something must already provide a compatible driver, no? With all these controller related drivers and tools, I'm just unsure what exactly makes it work when connected with Bluetooth.

[Lawstorant]

Generic HID BT controller. I still think this should probably be supported by xpad then, just with an ID change. I guess a HID descriptor dump would help

[RayJW]

Generic HID BT controller. I still think this should probably be supported by xpad then, just with an ID change. I guess a HID descriptor dump would help

I ran sudo usbhid-dump twice and checked the diff, this seems to be the relevant entry:

001:007:001:DESCRIPTOR         1761917139.293262
 05 01 09 06 A1 01 85 01 75 01 95 08 05 07 19 E0
 29 E7 15 00 25 01 81 02 95 01 75 08 81 03 95 05
 75 01 05 08 19 01 29 05 91 02 95 01 75 03 91 03
 95 06 75 08 15 00 26 FF 00 05 07 19 00 2A FF 00
 81 00 C0 05 01 09 02 A1 01 85 02 09 01 A1 00 05
 09 19 01 29 05 15 00 25 01 95 05 75 01 81 02 95
 01 75 03 81 01 05 01 09 30 09 31 16 01 F8 26 FF
 07 75 0C 95 02 81 06 09 38 15 81 25 7F 75 08 95
 01 81 06 95 01 81 03 C0 C0 05 0C 09 01 A1 01 85
 03 15 00 25 01 75 01 95 08 09 E2 09 EA 09 E9 09
 11 09 CD 09 B6 09 B7 09 B5 81 02 95 08 81 01 C0
 06 A0 FF 09 01 A1 01 09 03 85 06 15 80 25 7F 35
 00 45 FF 75 08 95 3F 81 02 09 05 85 07 15 80 25
 7F 35 00 45 FF 75 08 95 1F 91 02 C0

[Lawstorant]

Thanks, I'll decode it later and compare to my xbox controllers

[Lawstorant]

Nope, this is out of scope for xone unfortunately. It could be supported by xpad maybe with proper ids. This controller doesn't have official Xbox compatibility so probably shows up as X360 controller, not a GIP controller