I plug USB IR Toy in my Desktop (
windows 7 x64).
Driver installation fails :
USBIRtoy (CDC-232) - No Driver found
I start USB-view and get the following information.
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x04D8 (Microchip Technology Inc.)
idProduct: 0xFD08
bcdDevice: 0x0100
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x00
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Full
Device Address: 0x03
Open Pipes: 0
On Microchip site, it is said that the driver corresponding to the 18F2550 is included in the OS distribution.
OK, solution found...
I just forget to get .inf file from http://dangerous-prototypes-open-hardware.googlecode.com/files/USBIRtoy.source.v1.zip (http://http://dangerous-prototypes-open-hardware.googlecode.com/files/USBIRtoy.source.v1.zip)
Then, update the (nonexisting) device driver, using the released .inf
Driver is now OK
And USB view says :
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x04D8 (Microchip Technology Inc.)
idProduct: 0xFD08
bcdDevice: 0x0100
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x00
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: Full
Device Address: 0x03
Open Pipes: 3
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x02
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0040 (64)
bInterval: 0x00
LINUX :I've connected to my Laptop (Linux, last Debian).
Seems OK, but I want to work in Windows :(
dmesg
...
[ 409.172048] usb 2-2: new full speed USB device using uhci_hcd and address 3
[ 409.364133] usb 2-2: configuration #1 chosen from 1 choice
[ 409.375668] usb 2-2: New USB device found, idVendor=04d8, idProduct=fd08
[ 409.375677] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 409.375681] usb 2-2: Product: USBIRtoy (CDC-232)
[ 409.375685] usb 2-2: Manufacturer: DangerousPrototypes.com
[ 409.607277] cdc_acm: This device cannot do calls on its own. It is no modem.
[ 409.607426] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[ 409.611057] usbcore: registered new interface driver cdc_acm
[ 409.611066] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Hi cuagn - thanks for the update. It looks like you got everything working (?). If not, please let me know and I'll see how I can help.
It is pretty annoying that Windows needs a .inf to tell it to use the proper driver, the USB descriptor alone should be enough to do that. I believe Linux has no such problem. There's probably a good reason for it, but in my experience it just makes it less user friendly and 'plug and play'. Too bad there's no HID class virtual serial port (I wonder why not).
I fully agree.
However, as a .inf file is distributed, I was not finaly surprised.
May be (that's all we can say with a complex black box like Windows) it's due to the X64 version ... Or something else...
Could be fine to know if it's "contextual" to my system, or if the problem recurs in any (X64 or not) Windows 7 installation.
Anyway, the device is working fine.
Regards
Marc