Help help.. the USB port does not appear to work for data

mzm · April 17, 2018, 5:00am

Hi Guys,

Got the PIXY board in and am finally able to work with it.
Short cable plugged into my windows 7 system and the system does not appear to attempt to load the USB driver.
Nada - zip…

The board does work and I can do the light pipe etc. Just can’t seem to see the images because the USB never gets recognized.

Anyone else have this issue?

When I use the USBView tool in the windows DDK i don’t see a device showing up when I plug in.

Thanks!

mzm · April 17, 2018, 5:00am

power only cable… I found another - one I use for my PIC emulator - that worked!
so now I can see the pixy show up in device manager.

But the app still does not work…

Is there a diagnostic mode to see if it is trying to talk to the device?

mzm · April 17, 2018, 5:00am

Got it.

Seems like it did not appreciate USB 3.0 for some reason. I connected to the 2.0 port and it started to work…

Up and running!

Thanks!

srobins1 · April 17, 2018, 5:00am

Glad you were able to resolve the issues, Matt. I’m not entirely familiar with USB 3.0 yet, but I believe its not fully backwards compatible with 2.0 (mostly hardware compatibility issues, I think). As you’ve found out, we recommend you use USB 2.0.

Thanks!

Scott

rmsanchez · April 17, 2018, 5:00am

Hi Matt,
So on your computer, you have a 2.0 port (usually black) and a 3.0 port (blue). The 3.0 port doesn’t work and the 2.0 port works? (Pixy fails to enumerate on the 3.0 port, isn’t detected, etc) Is this repeatable?

What kind of computer do you have?

thanks!
–rich

mzm · April 17, 2018, 5:00am

Hi rich,

Its a sony vaio laptop - vintage is last year - core i7 gen 2. The 3.0 ports don’t appear to work, however there is a 2.0 port that does.

I am using a USB cable from my PICKIT3 emulator (little red thing). It can also source power to a target.
In all cases the 3.0 port do provide power to the pixy and I can do lite pipe mode etc.

Its real repeatable as I have not been able to get the 3.0 ports working with the application and they also do not enumerate thru usbview.
The 30 ports work reliably with other devices like printers and mouses and pickit 3 emulators…

If you have any diagnostics you want to run I can do that for you here. It just didn’t enumerate on the 3.0 ports…

rmsanchez · April 17, 2018, 5:00am

Thanks Matt, that’s good info. I need to do some more investigation. I have 2 machines with 3.0 ports and they work fine. I’m guessing it has something to do with libusb (our USB driver) and/or the USB controller. See the attached image-- if you can bring up the Device Manager and report what you see for the USB controller, that would be great.

thanks!

mzm · April 17, 2018, 5:00am

Here is the USBView text from the USB 2.0 - working -port

Intel 6 series hub

DriverKey: {36fc9e60-c465-11cf-8056-444553540000}\0000
VendorID: 8086
DeviceID: 1C26
SubSysID: 9089104D
Revision: 04

root hub

Root Hub: USB#ROOT_HUB20#4&39cbb5f2&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Hub Power: Self Power
Number of Ports: 2
Power switching: Ganged
Compound device: No
Over-current Protection: Global

Extended Hub Capability Flags: 0x000013
High speed Capable: Yes
High speed: Yes
Mulit-transaction Capable: No
Mulit-transaction ON: No
Root hub: Yes
Armed for wake on connect: No
Reserved (26 bits): 000000

port 1

External Hub: USB#VID_8087&PID_0024#5&196794a3&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Hub Power: Self Power
Number of Ports: 6
Power switching: Individual
Compound device: No
Over-current Protection: Individual

Extended Hub Capability Flags: 0x000003
High speed Capable: Yes
High speed: Yes
Mulit-transaction Capable: No
Mulit-transaction ON: No
Root hub: No
Armed for wake on connect: No
Reserved (26 bits): 000000

Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x09
bDeviceSubClass: 0x00
bDeviceProtocol: 0x01
bMaxPacketSize0: 0x40 (64)
idVendor: 0x8087
idProduct: 0x0024
bcdDevice: 0x0000
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x01
Open Pipes: 1

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0001 (1)
bInterval: 0x0C

Configuration Descriptor:
wTotalLength: 0x0019
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xE0 (Bus Powered Self Powered Remote Wakeup)
MaxPower: 0x00 (0 mA)

Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x09 (Hub)
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0001 (1)
bInterval: 0x0C

Pixy CMUcam5 plugged into port 2

Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0xFF
bDeviceSubClass: 0x01
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 (64)
idVendor: 0xB1AC
idProduct: 0xF000
bcdDevice: 0x0100
iManufacturer: 0x01
0x0409: “Charmed Labs”
iProduct: 0x02
0x0409: “Pixy”
iSerialNumber: 0x03
0x0409: “DEMO 0.0”
bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x02
Open Pipes: 3

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x02

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Configuration Descriptor:
wTotalLength: 0x0030
bNumInterfaces: 0x02
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 (Bus Powered )
MaxPower: 0x32 (100 mA)

Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x00
iInterface: 0x04
0x0409: “Camera”
0x0409: “Camera”

Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x02

Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x00
iInterface: 0x04
0x0409: “Camera”
0x0409: “Camera”

Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

mzm · April 17, 2018, 5:00am

This is in a USB 3.0 port

Renesas Electronics USM 3.0 Host Controller

DriverKey: {36fc9e60-c465-11cf-8056-444553540000}\0008
VendorID: 1033
DeviceID: 0194
SubSysID: 9089104D
Revision: 04

Root Hub: NUSB3#ROOT_HUB30#5&2c347bfb&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Hub Power: Self Power
Number of Ports: 4
Power switching: Individual
Compound device: No
Over-current Protection: Individual

Extended Hub Capability Flags: 0x000011
High speed Capable: Yes
High speed: No
Mulit-transaction Capable: No
Mulit-transaction ON: No
Root hub: Yes
Armed for wake on connect: No
Reserved (26 bits): 000000

The pixy