Timeouts sending to controller

[ErekoseTCE]

Hi,
I noticed that while my setup worked, the 360 controller's ring light never got set except for this one time. It also seems a bit sluggish to respond. So I started looking into the code to try and understand. After adding some debugging and getting to know libusb some (I am still new to it) I noticed that the first read from the adapter (DIY adapter) got sent to the 360 controller (usb_callback gets a success), but all the other reads from the adapter that are sent to the controller time out.

I think I got "lucky" in the one of the successes changed the light once, but am not sure. So the questions are:
* getting these timeouts is unexpected and indicate something is wrong, correct?
* if not, is there something I am missing here? I am new to this and so I may miss things you veterans take for granted.
* I changed the X360_USB_INTERRUPT_ENDPOINT_OUT from 2 to 1 and that made the timeouts go away, but not sure if that was the right thing

my pc is an Intel I7 3.2Ghz, 32Gb Mem, running Ubuntu 14.04 LTS.
the adapter is a DYI, using the Teensy 2.0 and the CP2102 as recommended (and works)
firmware is 5.4, latest GIMX code base from git
Console: xbox 360, controller: genuine xbox 360 wired (mostly works)
config is a simple "pass through" where all the buttons and axis from the 360 controller are mapped 1 to 1 to the adapter (i.e. no other devices)

Any suggestions or tips would be appreciated. The next thing I think I would have to do is to dig into the controller protocol to understand what is supposed to go where, but I haven't jumped in that deep yet.
-Erik


p.s. I did find that libusb had a real problems when I plugged the controller into the USB3.0 port, but I have since switch to the USB2.0 which works much better (drivers I suppose)

[Matlo]

Hi,

I think you are right, the endpoint number looks wrong.

[Matlo]

It turns out the endpoint number was right.
What's happening here is that GIMX does not resend the led status if it fails.