Wireless controller to Pc through Play and charge kit

[johnace]

I just wondered if any of you clever software types have figured out how to make the wireless controller work on pc through the play and charge kit?

I know this is just a software issue as i have checked the hardware side of things and it will work with the correct drivers...if someone was to make them that is But im more a hardware guy than a software one.

[wombat]

I was under the impression that the 'play & charge' kit only acts as a power source, so it doesn't really make your wireless gamepad 'wired'. So your kinda stuck on getting the wireless receiver.

[johnace]

I was under the impression that the 'play & charge' kit only acts as a power source, so it doesn't really make your wireless gamepad 'wired'. So your kinda stuck on getting the wireless receiver.

This is what alot of people have told me but its just false information from M$ to get people to spend more money.....the Play and charge kit has 7 pins on its connector (the same amount as a wired controller) also seeing as it showed up on my pc "xbox 360 controller via Play and charge" shows that it does send data too.

So as a test i "disabled" the wireless module on a junk 360 i have so it didnt pick up a controllers signal, then i plugged the controller into the 360 with the PnC kit and i could play games quite happily with it...so its 100% software locked out via the pc.

[CodeAsm]

you... removed the rf board, or realy disabled the RF board on your 360? i dint cheked the cable yet, and also dint checked the usb-view on a pc yet, but i dont think a plug and charge has d+ and d-. not sure tho

[johnace]

you... removed the rf board, or realy disabled the RF board on your 360? i dint cheked the cable yet, and also dint checked the usb-view on a pc yet, but i dont think a plug and charge has d+ and d-. not sure tho

I actually bypassed the Rf Reciever, if i had removed it or disabled the board any other way it wouldnt have booted.....oh and it does have the data lines btw.

Are you able to code a simple driver or "modify" the wired controller driver?....software is not my forte xD

[ddxcb]

You need the RF board on the pc, you can buy one or make one from a xbox 360 RF board.

The play and charge cable does send d- d+ but only to sync the controller to the RF board.

[johnace]

I was looking for a software approach rather than a "ghetto" rf reciever....plus the fact i use a laptop and dont really want to take a home made rf board with me xD, and the play and charge cable does actually send all the data the controller needs as i have played arkham city for 30 mins without a functional wireless board.

I think if i change something in the Xusb21.setup file i could get it to work maybe??


Edit: just opened up the setup file and i see this.....checkout the part where it states that it NULLS the play and charge kit from working.

;
; XUSB21.INF file
;
; Installs the XUSB21 device driver
;
; Supports the following devices
; Wired Common Controller USB\Vid_045E&Pid_028E
; Wireless Common Controller USB\Vid_045E&Pid_0719
; Wired CC Compatible USB\MS_COMP_XUSB10
; Wireless CC Compatible USB\MS_COMP_XUSB20
;
; Installs a NULL Service for the Play and Charge Cable
; Play and Charge Cable USB\Vid_045E&Pid_028F
;
; Uses Version 1.9 of the WDF Coninstaller
;[Version]
Signature="$WINDOWS NT$"
Class=XnaComposite
ClassGUID={D61CA365-5AF4-4486-998B-9DB4734C6CA3}
Provider=%MSFT%
CatalogFile=xusb21.cat
DriverVer=08/13/2009,2.1.0.1349
[ClassInstall32]
AddReg=XnaComposite_AddReg
[XnaComposite_AddReg]
HKR,,,,%XUSB21.ClassName%
HKR,,Icon,,-24

; Add source disk stuff to allow chkinf to work properly
[SourceDisksNames]
1=%XUSB21.DiskName%
; Add source disk stuff to allow chkinf to work properly
[SourceDisksFiles.x86]
xusb21.sys=1,x86
WdfCoInstaller01009.dll=1,x86

[SourceDisksFiles.amd64]
xusb21.sys=1,x64
WdfCoInstaller01009.dll=1,x64
[ControlFlags]
ExcludeFromSelect=*
[DestinationDirs]
DefaultDestDir=12
CC_Install_CoInstaller_CopyFiles=11
[Manufacturer]
%MSFT%=MSFT,NTx86,NTamd64,NTx86.6.0,NTamd64.6.0
[MSFT.NTx86.6.0]
%XUSB21.DeviceName.Wired%=CC_Install, USB\Vid_045E&Pid_028E
%XUSB21.DeviceName%=CC_Install, USB\Vid_045E&Pid_0719
%XUSB21.DeviceName.Wired%=CC_Install, USB\MS_COMP_XUSB10
%XUSB21.DeviceName%=CC_Install, USB\MS_COMP_XUSB20
%XUSB21.DeviceName.Jump%=CC_Install, USB\Vid_045E&Pid_028F
[MSFT.NTamd64.6.0]
%XUSB21.DeviceName.Wired%=CC_Install, USB\Vid_045E&Pid_028E
%XUSB21.DeviceName%=CC_Install, USB\Vid_045E&Pid_0719
%XUSB21.DeviceName.Wired%=CC_Install, USB\MS_COMP_XUSB10
%XUSB21.DeviceName%=CC_Install, USB\MS_COMP_XUSB20
%XUSB21.DeviceName.Jump%=CC_Install, USB\Vid_045E&Pid_028F
[MSFT.NTx86]
%XUSB21.DeviceName.Wired%=CC_Install, USB\Vid_045E&Pid_028E
%XUSB21.DeviceName%=CC_Install, USB\Vid_045E&Pid_0719
%XUSB21.DeviceName.Wired%=CC_Install, USB\MS_COMP_XUSB10
%XUSB21.DeviceName%=CC_Install, USB\MS_COMP_XUSB20
%XUSB21.DeviceName.Jump%=CC_Install, USB\Vid_045E&Pid_028F
[MSFT.NTamd64]
%XUSB21.DeviceName.Wired%=CC_Install, USB\Vid_045E&Pid_028E
%XUSB21.DeviceName%=CC_Install, USB\Vid_045E&Pid_0719
%XUSB21.DeviceName.Wired%=CC_Install, USB\MS_COMP_XUSB10
%XUSB21.DeviceName%=CC_Install, USB\MS_COMP_XUSB20
%XUSB21.DeviceName.Jump%=CC_Install, USB\Vid_045E&Pid_028F
[CC_Install]
CopyFiles=CC_Install.CopyFiles
AddReg=CC_Install.AddReg
[CC_Install.CopyFiles]
xusb21.sys
[CC_Install.AddReg]
HKR,,"AudioOutTerminalType" , 0x00010001, 0x00000306
;HKR,,"LiveCallButtonVidPid" , 0x045e0001, 0x00000306
;HKR,,"WheelUsage" , 0x00000004, 0x00000306
;HKR,,"SwapFFWirelessWheelVibration", 0x00000001, 0x00000306
[CC_Install.Services]
AddService=xusb21,0x00000002,CC_XUSB21_Service
[CC_Install.CoInstallers]
AddReg=CC_Install_CoInstaller_AddReg
CopyFiles=CC_Install_CoInstaller_CopyFiles
[CC_Install_CoInstaller_AddReg]
HKR,,CoInstallers32,0x00010000, "WdfCoInstaller01009.dll,WdfCoInstaller"
[CC_Install_CoInstaller_CopyFiles]
WdfCoInstaller01009.dll
[CC_Install.Wdf]
KmdfService = XUSB21, XUSB21_wdfsect
[XUSB21_wdfsect]
KmdfLibraryVersion = 1.9

[CC_XUSB21_Service]
DisplayName = %XUSB21.ServiceName%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 0 ; SERVICE_ERROR_IGNORE
ServiceBinary = %12%\xusb21.sys

[strings]
;localized strings
MSFT = "Microsoft"
StdMfg = "(Standard system devices)"
XUSB21.ClassName = "XBOX 360 Peripherals"
XUSB21.DeviceName = "Xbox 360 Wireless Receiver for Windows"
XUSB21.DeviceName.Wired = "Xbox 360 Controller for Windows"
XUSB21.DeviceName.Jump = "Xbox 360 Wireless Controller via Play & Charge Kit"
XUSB21.ServiceName = "Xbox 360 Wireless Receiver Driver Service 21"
XUSB21.DiskName = "Xbox 360 Wireless Receiver for Windows Install Disk"

[Zetrox2k]

AFAIK, as others have suggested, the Play and Charge kit simply acts as a power source... havent looked at this myself, but assuming the data lines are there you could rig the mainboard of the controller, and completely bypass RF. Not much you can do without some soldering I'm afraid.... better off grabbing an adapter, I managed to get one for $2 from a local pawn shop.

[iamcheese]

i swear it was possible for a while after launch, i remember using it to play some emus on my pc... seems ms chaned some stuff when they started marketing the adapter for the pc to force you to buy it, when i did do it i played with no battery pack installed so it worked for both the data and power...

driver hack anyone?

[Zetrox2k]

definetely not possible. i remember trying it myself at launch with some custom drivers, then gutted it and worked out why.

[Bad_Ad84]

USB spec states the device needs to negotiate with the host for high power mode. Pretty sure the data that is sent is only to allow this so the batteries would actually charge.

This circuity is probably in the charge kit, rather than the actual pad itself.

Also, your comment about the driver inf is wrong, it doesnt state its nulling it. It states its installing a null service - probably a dummy service as theres no data coming from the pad.

[johnace]

AFAIK, as others have suggested, the Play and Charge kit simply acts as a power source... havent looked at this myself, but assuming the data lines are there you could rig the mainboard of the controller, and completely bypass RF. Not much you can do without some soldering I'm afraid.... better off grabbing an adapter, I managed to get one for $2 from a local pawn shop.

You don't need to modify the controller at all

i swear it was possible for a while after launch, i remember using it to play some emus on my pc... seems ms chaned some stuff when they started marketing the adapter for the pc to force you to buy it, when i did do it i played with no battery pack installed so it worked for both the data and power...

driver hack anyone?

That's what I'm hoping someone can do, as you can see from the above file I posted Microsoft INTENTIONALLY nulls/disables the play and charge kit from sending the required data for the controller to work properly.

definetely not possible. i remember trying it myself at launch with some custom drivers, then gutted it and worked out why.

So in your opinion why won't it work?

[CodeAsm]

In my play and charge cable the D+ and D- are directly connected to the controller, so im checking this link
So maybe its posible if the IC (mcu) supports it. Will take a look tonight when back home with USBView

EDIT: Its right after I got home i now check usbview and this is what USBview says abaout my (Off) controller:
also when it is searching its only this and the normal app dous not see it. maybe the driver, but im scared it can also be in the Controllers mcu be a diffrent Firmware.

Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0xFF
bDeviceSubClass: 0xFF
bDeviceProtocol: 0xFF
bMaxPacketSize0: 0x08 (8)
idVendor: 0x045E (Microsoft Corporation)
idProduct: 0x028F
bcdDevice: 0x0106
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Full
Device Address: 0x01
Open Pipes: 0

Configuration Descriptor:
wTotalLength: 0x0012
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xA0 (Bus Powered Remote Wakeup)
MaxPower: 0x32 (100 Ma)

Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x00
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x5D
bInterfaceProtocol: 0xFF
iInterface: 0x00

Also:

1. 0x045e | 0x028e | Microsoft Xbox 360 Controller
   
2. 0x045e | 0x028f | Microsoft Xbox 360 Play&Charge Kit
   

from here : Linky

[johnace]

I've ended up making a "ghetto" reciever lol, just untill I crack this bitch xD

[l_oliveira]

P&C Is not just a power source.

The XBOX360 (And PC software if host is a PC with Windows) will connect to the controller through the USB link to program the controller with the RF board mac address.

It's made that way because the kit covers the SYNC button on the controller.