Hello and questions about UVC 1.0

Jun 19, 2007 at 2:25 PM
Hi,
It's nice to see that this project found a new home.

Now questions:

I am trying to use the driver with a camera that is probably only UVC 1.0 compliant but I'm having problems. Is the driver suited to handle UVC 1.0 devices?
What are the main differences between UVC 1.0 and UVC 1.1 that may affect working with the driver?

One place where the driver fails for example is in the GetVendorTransfeLen which returns a STALL error. I suppose that means that the camera does not support this command?
Are there any assumptions that can be made on this length?

Thanks
Pini
Jun 20, 2007 at 6:43 AM
The different queries have different lengths. I was successful with the trial and error approach early in the development phase. Perhaps that'll work for you.

What camera are you looking at?

Doug
Jun 20, 2007 at 9:35 AM
I am trying to work with the Proscope HR. It is supposed to be UVC compliant and on their website they also refer to a UVC driver for Linux to support their camera.
https://linux-uvc.berlios.de/

I tried to look into this driver source code to compare it to the WinCE driver, however my understanding of linux coding is limited.

I try to use a length of 26 instead of GetVendorTransferLen. It works fine with some queries but not with others. However, I am not sure that the queries that do not work, fail because of the length. Most problems are in the probe/commit phase.

One strange issue for example is with frame intervals. When getting the supported formats I get the following data:

===>Video Streaming Uncompressed Frame Type Descriptor<===
bLength: 0x1E
bDescriptorType: 0x24
bDescriptorSubtype: 0x05
bFrameIndex: 0x01
bmCapabilities: 0x00
wWidth: 0x0280
wHeight: 0x01E0
dwMinBitRate: 0x0030C000
dwMaxBitRate: 0x0030C000
dwMaxVideoFrameBufferSize: 0x00096000
dwDefaultFrameInterval: 0x00EAC027
bFrameIntervalType: 0x01
===>Additional Discrete Frame Type Data
dwFrameInterval1: 0x00EAC027

===>Video Streaming Uncompressed Frame Type Descriptor<===
bLength: 0x1E
bDescriptorType: 0x24
bDescriptorSubtype: 0x05
bFrameIndex: 0x02
bmCapabilities: 0x00
wWidth: 0x0140
wHeight: 0x00F0
dwMinBitRate: 0x0041A000
dwMaxBitRate: 0x0041A000
dwMaxVideoFrameBufferSize: 0x00025800
dwDefaultFrameInterval: 0x002B98B6
bFrameIntervalType: 0x01
===>Additional Discrete Frame Type Data
dwFrameInterval1: 0x002B98B6


This data was actually aquierd using the MS uvc tool but I get the same data from the WinCE driver as well. The frame intervals seems strange to me.

I am trying to get help from the maker but didn't get it yet.

The Logitech Pro 5000 works fine on my WinCE 5.0 device.
Pini
Jun 22, 2007 at 2:42 AM
Each camera can define its own frame intervals. The interval you're listing doesn't look to strange.

Probe commit is a difficult area. Some cameras vary a bit from the spec. It also could be my code in that area that's wrong. I would continue to look at the vendor transfer length area to see if you can figure it out. Good luck.

Doug