Available USB to UART adapters:
0: /dev/ttyUSB0
Select the USB to UART adapter number: 0
Selected: /dev/ttyUSB0
Overwrite /home/user/serialusb-0.5/build/serialusb-0.5/capture.pcap? [y/n] y
Available USB devices:
0 VID 0x10c4 (Cygnal Integrated Products, Inc.) PID 0xea60 (CP210x UART Bridge / myAVR mySmartUSB light) PATH 01:01:05
1 VID 0x045e (Microsoft Corp.) PID 0x0289 (Xbox Controller S) PATH 01:01:04:01
2 VID 0x045e (Microsoft Corp.) PID 0x0288 (Xbox Controller S Hub) PATH 01:01:04
3 VID 0x045e (Microsoft Corp.) PID 0x0745 (Nano Transceiver v1.0 for Bluetooth) PATH 01:01:02
4 VID 0x0424 (Standard Microsystems Corp.) PID 0xec00 (SMSC9512/9514 Fast Ethernet Adapter) PATH 01:01:01
5 VID 0x0424 (Standard Microsystems Corp.) PID 0x9514 (SMC9514 Hub) PATH 01:01
6 VID 0x1d6b (Linux Foundation) PID 0x0002 (2.0 root hub) PATH 01
Select the USB device number: 1
lib/gasync/src/usb/gusb.c:793 get_lang_id_0: libusb_control_transfer failed with error: Pipe error
Opened device: VID 0x045e PID 0x0289 PATH 01:01:04:01
configuration: 1
interface: 0:0
endpoint: IN INTERRUPT 1
endpoint: OUT INTERRUPT 2
Proxy started successfully. Press ctrl+c to stop it.
When I selected "2 VID 0x045e (Microsoft Corp.) PID 0x0288 (Xbox Controller S Hub) PATH 01:01:04" noting happened but when "1 VID 0x045e (Microsoft Corp.) PID 0x0289 (Xbox Controller S) PATH 01:01:04:01" was selected controller started working on XBOX.
Matlo wrote: ↑Thu Jul 06, 2017 8:59 pm
I think there may be some kind of authentication involved.
Make sure to have your Xbox Controller S plugged to your Pi before starting GIMX.
Please make a log file with adapter debug messages enabled, and let me know the result.
Hi,
Still no reaction on console either with DS4 or Xbox Controller S but maybe the log can tell more -> https://pastebin.com/nGedRU4H - the pass-through device (XCS) was recognized. Both controllers were connected before starting GIMX.
I can capture more with SerialUSB if you want to be sure there is some additional authentication between the controller and XBOX.