Visioneer OneTouch Pro 8800 USB
Visioneer OneTouch Pro 8820 USB
USB
0x04a7
0x0410
Plustek ASIC P99002A
ALI Jpeg/USB M5615
Uses a winbond
microcontroller; there are separate RAM chips for the JPEG and controller,
and an external +socketed rom for the controller.
The 8820 is the same as the 8800 but has an additional transparency adapter.
8820:
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=04a7 ProdID=0410 Rev= 1.02
S: Manufacturer=Visioneer
S: Product=OneTouch Pro 8820 USB
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
8800:
bus-0/\\.\libusb0-0006--0x04a7-0x0410 04A7/0410
- Manufacturer : Visioneer
- Product : OneTouch Pro 8800 USB
wTotalLength: 32
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 40h
MaxPower: 25
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 2
bInterfaceClass: 255
bInterfaceSubClass: 255
bInterfaceProtocol: 255
iInterface: 0
bEndpointAddress: 81h
bmAttributes: 02h
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 02h
bmAttributes: 02h
wMaxPacketSize: 8
bInterval: 0
bRefresh: 0
bSynchAddress: 0
8820:
<device descriptor of 0x04a7/0x0410 at 002:008>
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 255
bDeviceSubClass 255
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x04A7
idProduct 0x0410
bcdDevice 1.02
iManufacturer 1 ((null))
iProduct 2 ((null))
iSerialNumber 0 ()
bNumConfigurations 1
<configuration 0>
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 64 (Self-powered)
MaxPower 50 mA
<interface 0>
<altsetting 0>
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()
<endpoint 0>
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 64
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<endpoint 1>
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 8
bInterval 0 ms
bRefresh 0
bSynchAddress 0
<trying to find out which USB chip is used>
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 GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
Couldn't set configuration: could not set config 1: Operation not permitted
checking for MA-1509 ...
this is not a MA-1509 (bcdUSB = 0x100)
checking for LM983[1,2,3] ...
this is not a LM983x (bDeviceSubClass = 0xff)
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 ...
this is not a ICM532B (check 2, bcdUSB = 0x100)
<Couldn't determine the type of the USB chip>
found USB scanner (vendor=0x04a7, product=0x0410) at libusb:002:008
If anything is wrong or missing on this page please file a bug report or use the the form for adding an unsupported device.
If you own an unsupported scanner, please send as much information as possible. Especially the output of sane-find-scanner -v -v and/or cat /proc/scsi/scsi (for SCSI scanners) or cat /proc/bus/usb/devices (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.
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 information for manufacturers.