Kodi Community Forum
REMOTEXBMC1.6 - remote+joystick XBMC - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59)
+---- Thread: REMOTEXBMC1.6 - remote+joystick XBMC (/showthread.php?tid=34425)

Pages: 1 2 3


- mace - 2008-07-05

There are a lot of china copies that has incorrect USB IDConfused.
They present themselfs with the same USB ID as the xbox handcontroller. Had to hack the lirc driver to get this to work for Linux earlier. Could be the same issue here


- MoDe2006 - 2008-07-05

DAM0, please can you use the software USBVIEW and connect your IRDA XBOX not working on the USB port. Then give me with USBVIEW the VendorID = & H? and ProductID = & H? for your hardware microsoft xbox remote control. ThanK Big Grin


- MoDe2006 - 2008-07-05

Jag hade inte väntat att detta scenario


- MoDe2006 - 2008-07-05

I hope that the bits on the remote are the same as the original controler microsoft


- hgumus - 2008-07-05

Thanks for your work Mode2006,

I try using my Pelican Xbox Eclipse II Wireless Controller with the drivers provided with your setup, but i get the error "This device cannot start. (Code 10)".Confused

Here are the idVendor and idProduct

idVendor: 0x0E6F
idProduct: 0x0005

It is working with XBCD 1.07 drivers, but i'm not sure this is compatible with remotexbmc 1.6.Huh

Any help will be appreciated.Big Grin


- MoDe2006 - 2008-07-06

Hi hgumus,
i'm sorry i don't have the Eclipse II Wireless for confIgure with remotexbmc.


- Dam0 - 2008-07-06

Mode2006,

heres product id + vendor id for you, seems the same values for each...

Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 (64)
idVendor: 0xFFFF
idProduct: 0xFFFF
bcdDevice: 0x0001

hope this helps,
Dam0


- MoDe2006 - 2008-07-06

Thank Dam0.
Apparently your material is really a copy made in china (idVendor: 0xFFFF- idProduct: 0xFFFF) or the driver is improperly installed.


- mace - 2008-07-06

It's a china copy alright Smile
my one just happends to have the same IDConfused


- MoDe2006 - 2008-07-06

it would be interesting to modify it. ini software to see if it works :VendorID=&HFFFF
ProductID=&HFFFF


- Dam0 - 2008-07-07

Mode2006,

i have tried to alter the profile embedded in the .ini file, but im afraid that the remote icon in task bar still shows "not connected"

i have taken a closer look at the data shown in the usbview app, and it seem all the inso is the same for both remotes except for ;

idproduct,idvendor and bcddevice.

this is what the chinese dongle data is...

idVendor: 0xFFFF
idProduct: 0xFFFF
bcdDevice: 0x0001.

whereas the bcddevice for MS dongle is valued at "bcdDevice: 0x000A"

i hope this helps,
Dam0


- Dam0 - 2008-07-07

just tried something else with weird results....

the dongles and remotes are interchangeable on xbox, however the chinese xmiter wont control MS dongle with xbmc...weird.

Dam0


- MoDe2006 - 2008-07-07

I corrected the problem


- Dam0 - 2008-07-08

MOde2006,

i uninstalled the drivers, and app.

re downloaded remoteclient.1.6 from first post here.and installed

changed the 2 x ids in .ini file

but still shows "not connected"

Dam0


- MoDe2006 - 2008-07-08

Dam0 Wrote:Mode2006,

heres product id + vendor id for you, seems the same values for each...

Device Descriptor:
bcdUSB: 0x0110
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 (64)
idVendor: 0xFFFF
idProduct: 0xFFFF
bcdDevice: 0x0001

hope this helps,
Dam0


Dam0
I may have a solution, open the remotexbmc.inf and insert a new line after:
[DeviceList]
"XBCD XBox Remote Control"=Install, USB\CLASS_58&SUBCLASS_42
"XBCD XBox Remote Control"=Install, USB\Vid_045e&Pid_0284&MI_00
"XBCD XBox Remote Control"=Install, USB\Vid_FFFF&Pid_FFFF&MI_00

and re install the driver, called me if it works Wink