Xpadder works great for the wireless 360 controller as a mouse and 16 buttons to add keyboard/mouse style mapping but does not take the I/0 info from the chatpad. So basically the chatpad is still useless for any PC aspect. Just bought and returned mine today after searching several hours all I came up with is a contest that still hasn't produced a working wireless option and lots of complaining which has been going on since at least 2008, good luck to all who have been working towards a solution. Crazy how it seems that a simple input/output interpretation must be so complicated that not even third party developers came up with a solution, my guess is a security issue is stopping them.
Need Xbox 360 Chatpad driver
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
...
...
...
Windows for home | Previous Windows versions | Gaming
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
81 answers
Sort by: Most helpful
-
Anonymous
2011-08-01T21:18:12+00:00 -
Anonymous
2011-07-30T22:43:57+00:00 I also want drivers for this product and am very frustrated with MS for not rising to the task.
Can I ask the folks here...how effective would something like Xpadder be for this? Would it allow all keykoard functions to be assigned to the chatpad?
-
Anonymous
2011-07-11T15:55:59+00:00 I am also waiting for the day when people actually read the full post and take in all of what it says. Using only part of my post doesn't really make your point. Now, go back, reread my original post again, and comprehend it this time.
-
Anonymous
2011-06-01T04:56:58+00:00 actually for those of use who play wow or other games that require many keys from the key pad it does make it more sense since i wouldnt have to sacrifice keys for being able to sit away from my desk and i can just hit numbers on the chatpad for spells and abilities. So as you can see my logic makes sense. Yours not so much....
-
Anonymous
2011-05-27T17:56:18+00:00 Very True! I Hope You Don't Mind,But I Would Love To Send This To Xbox And Microsoft.
Is It Fine With You If I E-mail It To Xbox And Microsoft?