Need Xbox 360 Chatpad driver

Question

Hi,

one year ago i buy a Xbox 360 Controller Made by Microsoft Corporation and a Chatpad for it. on the box was info about use for Windows-based PCs but until now no driver... so i am here to ask for some help. For now i can turn the backlight on sending

ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)

ctrl 0x41 0x0 0x8 0x02 # capslock

ctrl 0x41 0x0 0x9 0x02 # square

ctrl 0x41 0x0 0xa 0x02 # circle

ctrl 0x41 0x0 0xb 0x02 # people

ctrl 0x41 0x0 0xc 0x02 # backlight

ctrl 0x41 0x0 0x11 0x02 # capslock

ctrl 0x41 0x0 0x12 0x02 # square

ctrl 0x41 0x0 0x13 0x02 # square and capslock

ctrl 0x41 0x0 0x14 0x02 # circle

ctrl 0x41 0x0 0x15 0x02 # capslock and circle

ctrl 0x41 0x0 0x16 0x02 # circle, square

ctrl 0x41 0x0 0x17 0x02 # circle, square, capslock

ctrl 0x41 0x0 0x1b 0x02 # makes led go on on keypress

ctrl 0x41 0x0 0x1e 0x02 # Init2 >>> Ep6: [5] { 0xf0, 0x03, 0x00, 0x01, 0x01 }

ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)

i also have acess to USB protocol analyzer (but it is not mine... sorry) to have the info that travell between the controller and the Xbox

also we can recive one key press but after it is dead.... and i dont know why... a lot of people are working on it but microsoft made it so at leas you can help us to try make a driver...

2nd byte flags:

shift/capslock = 0x01

square = 0x02

circle = 0x04

people = 0x08

3rd byte keycodes:

1 = 0x17

2 = 0x16

3 = 0x15

4 = 0x14

5 = 0x13

6 = 0x12

7 = 0x11

8 = 0x67

9 = 0x66

0 = 0x65

q = 0x27

w = 0x26

e = 0x25

r = 0x24

t = 0x23

y = 0x22

u = 0x21

i = 0x76

o = 0x75

p = 0x64

...

...

...

Answer 1

@JohnD

  You're right about the discussion being about an Xbox 360 accessory, but the discussion is also about making said accessory work within Windows making it still relevant within this forum. If we had had this exact same discussion in the forum you suggested they would have told us to come here.

@Mattetch

  It seems Microsoft seems to refuse to acknowledge that the first chatpads released had packaging that said Works with Windows Live Messenger. Instead of saying something along the lines of, chat with friends on Windows Live Messenger via the Xbox 360 Live Messenger interface. They later changed the packaging to correct this oversight. Also if you can get window to recognize the device, you can use third party software to emulate key functions for just about any game out there. This software works by intercepting the keystroke on the game pad or chat pad in this case and telling the game that it came from the key board.

lastly there is a video on youtube of a programmer using the XNA studio to send information from his chatpad to the 360, and then from the 360 to his PC. Crude, but effective. There is however a notable delay which would be an issue with gamers. For those who don't know the XNA studio is a programming environment for the 360 on windows that allows you to program and run games designed for the xbox on your pc. It has an annual subscription fee. But its the same platform used to make the "Community Games" that you see in the marketplace.

I've concluded that it's not that Microsoft Can't make the chatpad work within Windows, but rather Microsoft doesn't want to make it work, and is refusing to tell us why.

Answer 2

You know an XBOX Chatpad would be useful on PC. Here is a few reasons why someone would buy an XBOX 360 chatpad for their PC and how they would use it:

1. Home Theater PC (HTPC); a person would use the joysticks for the mouse, and use the Chatpad as a keyboard to control there HTPC from the couch INSTEAD of having a keyboard, mouse, and a table for the mouse and keyboard to rest on.
2. Couch Gaming; a person wants to PC Game on there couch, and doesnt want to have a table, mouse, and keyboard in there living room, and uses it to type in text on a game.
3. Gaming Hotkeys; a person prefers using a controller INSTEAD of mouse and keyboard, AND likes the open ecosystem of PC Gaming. The person would use the Joysticks, D-Pad, ABXY keys, Triggers, and Bumpers for doing regular stuff, AND they would use the Chatpad for EXTRA features like mods, console commands/cheat codes (if the game supports it), and chatting.
4. Extra Weight/Mass; a person thinks their XBOX Controller is too light, and they buy a chatpad just to add a few more ounces/grams, and since that person bought it, they should be able to use it.

Answer 3

I really wish that Microsoft would release the PC drivers for the Chat pad, at least just for the corded controller, I would pay $20 for it.  There is no logical reason for keeping this driver from coming out, I wish that someone would leak it from MS, I bet a couple of their Programmers made some just for fun.

Answer 4

so wait, what is that supposed to mean? i like many of the other people that bought the chat pad add on would like a actual driver to use the device within windows; from the above post there seems to be some effort to make this work as it was supposed to, yet to this day microsoft still hasn't released the necessary driver.

is nothing going to come from this? i dont see the logic in releasing a device that says on the box "works with windows" when clearly it doesn't.

Sincerely,

Matt

Etchells

Answer 5

"also we can recive one key press but after it is dead.... "

As you know, the 360 chatpad isn't on all the time.  The Xbox OS activates it when it needs input.  I wonder if the Xbox OS sends the packet you have found that allows for one following key as a "keep it alive packet."  Flow chart example:

OS needs input --->  OS sends "keep alive packet" --->  Keypad lights up --->  Press key on pad ---> OS receives input ---> Notes that it is still in input mode --->  Sends "Keep alive packet" --->  chatpad stays on can send another key.

Once you close the input diag on the 360 the chatpad wont receive a packet from the xbox os and is then off and non responsive.

This is just a theory, and I am making assumptions, but its worth considering.