QuickCam Team Forums

I'm attempting to use the QuickCam Pro 9000 in an embedded commercial application using Linux running on a microcontroller which only supports USB 1.1. The reduced list of available resolutions is okay except MJPG format returns no data. YUYV format works fine but doesn't support sufficient resolution (I need 640 x 480).

To verify that it's not me, I set it up on a PC motherboard via a USB 1.1 hub to ensure that the camera would only function as if connected to a USB 1.1 host. The same reduced list of resolutions is reported (using luvcview), which is good. However, luvcview also hangs when attempting to use MJPG format. So, it seems as though it's not me. In both applications (the embedded version and the PC version) and at all supported resolutions YUYV format works fine while MJPG returns no data.

The USB BCD of the camera I'm developing with is 0x0007, which apparently makes it 2nd generation. Was this a known problem with this version of this camera? Has it been/will it be corrected in the 4th generation? Should I be using a different camera for this host (Linux, USB 1.1)? Would the Orbit AF be expected to behave any better? Any advice would be appreciated.

Sorry for the long delay, it's a very busy time ...

I ran a few tests with different QuickCam Pro 9000 cameras, including the one with BCD 0x0007, and I saw some similar things. My test was to plug them into a normal PC that doesn't have the ehci_hcd module loaded, which effectively disables USB 2.0.

Sometimes the streaming was fine (MJPEG, all resolutions), but sometimes the camera would just hang, in a way similar to the one described here. Using USB 1.1 seems to make the problem more likely.

The 4th generation probably won't fix that but I will forward the problem to the engineers in question to fix it for future cameras.