The Wireless Receiver, needed to use the Wireless controllers, as they don't speak standard Bluetooth, act as normal non-HID USB device and provides support for up to four controller at once. Its USB layout looks like this:
Originally Posted by GAFBlizzard
Endpoint 1(in/out): Controller 1
Endpoint 2(in/out): Headset 1
Endpoint 3(in/out): Controller 2
Endpoint 4(in/out): Headset 2
Endpoint 5(in/out): Controller 3
Endpoint 6(in/out): Headset 3
Endpoint 7(in/out): Controller 4
Endpoint 8(in/out): Headset 4
The troublesome part is that this is noticeably different then from the wired controllers, which look something like this:
Endpoint 1(in): Controller events
Endpoint 2(out): Messages to the controller
Endpoint 3(in): Headset mic
Endpoint 4(out): Headset phone
Endpoint 5(in): Headset status information
Endpoint 5(out): Headset configuration information
Endpoint 6(in): Chatpad
So knowledge gained on the wired one doesn't really translate to the wireless one, similarities exist of course, but USB packages have different length and such.
I don't really have an idea of how one could event start development on the wireless controller chatpad support, as there is no easy way to intercept the messages passed between Xbox360 and the controller, and even if there would be, that still might not provide enough information for reproduction with the wireless receiver.
Some more Xbox360 controller info is available at:
I don't have a physical Jumi Joystick. That was a red herring from an iPhone app I had played with that lets you remotely control a PC from your phone. Those are all the devices you get with the wireless receiver.
Good info as always, Grumbel. It looks like one should be able to figure the protocol out by analyzing USB logs in Windows (and presumably there are already other drivers that support it...maybe even your driver. I can't remember at the moment. :sorry:), but to get the chatpad to work, one would have to be lucky. It could be impossible! It could be easy! Ah, the world of reverse engineering.
Thanks, Microsoft, as always. :P
hey blizzard have you seen this?
it's from the author of the mac os driver I can remotely test with a wireless receiver
I might have seen it while looking through his site, but I probably didn't look through it in detail since I don't have a wireless controller. It's more good info. Figuring out how (if it's even possible) to enable the chatpad seems like it would be the tricky part, unless the chatpad data actually comes through. At any rate, the first step would be using a USB trace utility to monitor it under Windows for a startup/button press/chatpad keypress sequence, if anyone is bored. :P
Originally Posted by jeduars
I posted some work in an attached archive on the wireless controller with Windows XP a while back:
I clarified that it wasn't actually the "driver" on the next page (that was totally my bad on the mis-naming of the downloadable Zip):
As it is right now you could maybe think of it more as a very basic wireless 360 controller signal "harness" (for testing) written in C#. Not sure if it'll be a ton of help with the chatpad, though. The reason is because I've been following this thread for close to 3 years now, and the majority of the work appears to be in the realm of low-level code harnessing to "awaken" the chatpad from the wired controller, rather than the ".NET Framework Windows USB/HID stack/keyboard stack" direction I was aiming towards through sending/receiving byte signals for the wireless one. My initial hope was to enable the ability for someone to possibly find the magic "byte" sequence to first wake up the chatpad and then have a byte conversation with it. But, if memory serves from reading this thread throughout the years off and on, it seems that you can't just wake it up once for an entire session; you still have to continually wake it up as each command is sent by wrapping the command in the "wakeup" command bytes. Does that sound familiar to anyone?
Good Luck! :)
Lady Ada has posted a rather lengthy treatise on how they reverse engineered the Kinect - it's posted here. Perhaps this can be of some use in this process.
That's a very nice guide...the people here had to work all that out for themselves. We did benefit from replaying packets and using a Mac and a USB analyzer (or more than one) to dump data, though!
Originally Posted by Penzance
I wonder if this knockoff will work better than M$ jacked up version?
Chatpad Super Driver
Hey just thought I'd let you guys know that someone has created a chatpad driver for the PC. It currently only works with wired controllers and is in the Alpha testing phase right now so if you want to try to help the project out go ahead and install it and leave some feedback.
Here's the link: Chatpad Super Driver
Thanks to everyone, hope you have a nice day! :)