sane-project-website/unsupported/teco-vm6509.html

196 wiersze
6.0 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>
TECO VM6509<br>
GUILLEMOT SCAN@HOME 48 USB<br>
HERCULES SCAN@HOME 48 USB
</p>
<h2>Bus type</h2>
<p>
USB
</p>
<h2>Vendor ID</h2>
<p>
0x080d
</p>
<h2>Product ID</h2>
<p>
0x0102
</p>
<h2>Chipset</h2>
<p>
</p>
<h2>Comments</h2>
<p>Seems that the scanners from this manufactuer TECO are placed by VIC Hi-Tech
see http://www.vic-corp.com/ download section.
</p>
<h2>Output of /proc/bus/usb/devices or sane-find-scanner -v -v</h2>
<pre>
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=080d ProdID=0102 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
&lt;device descriptor of 0x080d/0x0102 at 002:002&gt;
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 255
bDeviceSubClass 0
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x080D
idProduct 0x0102
bcdDevice 1.00
iManufacturer 0 ()
iProduct 0 ()
iSerialNumber 0 ()
bNumConfigurations 1
&lt;configuration 0&gt;
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 64 (Self-powered)
MaxPower 100 mA
&lt;interface 0&gt;
&lt;altsetting 0&gt;
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()
&lt;endpoint 0&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 (out 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 8
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 1&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 (in 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 8
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;endpoint 2&gt;
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 (in 0x03)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
&lt;trying to find out which USB chip is used&gt;
checking for GT-6801 ...
this is not a GT-6801 (bcdUSB = 0x100)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
this is not a MA-1015 (bDeviceSubClass = 0x0)
checking for MA-1509 ...
this is not a MA-1509 (bcdUSB = 0x100)
checking for LM983[1,2,3] ...
this is not a LM983x (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x8, bInterval = 0x0)
checking for GL646 ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL646_HP ...
this is not a GL646_HP (bcdUSB = 0x100)
checking for GL660+GL646 ...
this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL841 ...
this is not a GL841 (bcdUSB = 0x100)
checking for ICM532B ...
check 2, this is not a ICM532B (bcdUSB = 0x100)
&lt;Couldn't determine the type of the USB chip&gt;
found USB scanner (vendor=0x080d, product=0x0102) at libusb:002:002
</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>