sane-project-website/unsupported/biolux-654.html

288 wiersze
10 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Scanner information</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, backend, driver, scanner, unsupported">
<link href="mailto:henning@meier-geinitz.de" rev="made">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
</head>
<body>
<h1>Scanners not supported by SANE</h1>
<h2>Manufacturer and model</h2>
<p>
Biolux 654 MicrOcular (microscope with digital camera)<br>
Ezonics EZCam USB II webcam (UVT8532 label, inside icm532b not a CPIA or OV511)<br>
Ezonics EZCam USB III webcam<br>
TerraCam USB webcam (inside icm532b not a CPIA or OV511)<br>
Data Plus Supplies Ltd, Minicam on flexible stick designed for laptops<br>
iConcepts Desktop, Mini desktop webcam<br>
Tucan PenCam<br>
</p>
<h2>Bus type</h2>
<p>
USB
</p>
<h2>Vendor ID</h2>
<p>
0x0923
</p>
<h2>Product ID</h2>
<p>
0x010f
</p>
<h2>Chipset</h2>
<p>
icm532B chip from IC MEDIA CORP (SIIG MOBILECAM). See <a
href="http://www.ic-media.com/">datasheet with
technical info</a> on website.
</p>
<h2>Comments</h2>
<p>
More information can be found <a href="http://gkall.hobby.nl/notes5.html">on this
page</a>. Maybe once there will be SANE support for this device?
</p>
<p>
In this product from Meade-Bresser the chip is used in a MicrOculair for the Biolux microscope.
The other products are normal designed webcams.
</p>
<h2>Output of /proc/bus/usb/devices or sane-find-scanner -v -v</h2>
<pre>
Bus 002 Device 003: ID 0923:010f IC Media Corp. SIIG MobileCam
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 8
idVendor 0x0923 IC Media Corp.
idProduct 0x010f SIIG MobileCam
bcdDevice 0.01
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 137
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 256
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 384
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 512
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 640
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 768
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 896
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 1023
bInterval 1
Language IDs: (length=4)
0409 English(US)
</pre>
<h1>Want to add or correct information?</h1>
<p>
If anything is wrong or missing on this page please <a href="/bugs.html">file a bug report</a>
or use the <a href="http://www.meier-geinitz.de:80/tinc?key=rDoQ7lrj&#38;formname=adddev" target="_top">the
form for adding an unsupported device</a>.
</p>
<p>
If you own an unsupported scanner, please send as much information as
possible. Especially the output of <em>sane-find-scanner -v -v</em>
and/or <em>cat /proc/scsi/scsi</em> (for SCSI scanners) or <em>cat
/proc/bus/usb/devices</em> (for USB scanners) can help. If you dare to
open the scanner, have a look at the text that's printed on the
chips. That may help to identify the chipset. If you know that the
scanner is similar to another one (e.g. supported by the same Windows
driver), please also mention this fact.
</p>
<h1><a href="/manufacturers.html">Information for Manufacturers</a></h1>
<p>
Are you a manufacturer or vendor of scanners and one of your scanners is
not supported by SANE yet? In this case please have a look at our <a
href="/manufacturers.html">information for manufacturers</a>.
</p>
<h1>Links</h1>
<ul>
<li>
General information on how to <a href="/contrib.html">contribute to SANE</a>, e.g. by writing
backends
</li>
<li>
<a
href="/cgi-bin/driver.pl">Scanner
search engine</a>
</li>
<li>
<a href="http://www.sane-project.org/">SANE homepage</a>
</li>
</ul>
<hr>
<p>
<a href="/">SANE homepage</a><br>
<a href="/imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>