+ Syscan TravelScan 460/464
+ Ambir Visigo A4
+
+ USB +
++ 0x0a82 +
++ 0x4600 +
++ LM9832 +
++ Both scanners have the same ids. Some more details can be found in the sane-devel + archive. +
++ As these scanners use a LM9832 chipset, they might be supported by the + Plustek backend in future. Patches are welcome. +
++Ambir Visigio A4: ++ ++bLength 18 +bDescriptorType 1 +bcdUSB 1.00 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x0A82 +idProduct 0x4600 +bcdDevice 1.00 +iManufacturer 64 (SYSCAN) +iProduct 79 (TravelScan 460) +iSerialNumber 0 () +bNumConfigurations 1 + + bLength 9 + bDescriptorType 2 + wTotalLength 39 + bNumInterfaces 1 + bConfigurationValue 1 + iConfiguration 0 () + bmAttributes 160 (Remote Wakeup) + MaxPower 500 mA + + + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 3 + bInterfaceClass 255 + bInterfaceSubClass 0 + bInterfaceProtocol 255 + iInterface 0 () + + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x81 (in 0x01) + bmAttributes 3 (interrupt) + wMaxPacketSize 1 + bInterval 16 ms + bRefresh 0 + bSynchAddress 0 + + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x82 (in 0x02) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x03 (out 0x03) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + + + checking for GT-6801 ... + this is not a GT-6801 (bDeviceClass = 0) + checking for GT-6816 ... + this is not a GT-6816 (bcdUSB = 0x100) + checking for MA-1017 ... + this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) + checking for MA-1015 ... + this is not a MA-1015 (bDeviceClass = 0) + checking for MA-1509 ... + this is not a MA-1509 (bDeviceClass = 0) + checking for LM983[1,2,3] ... + + +found USB scanner (vendor=0x0a82 [SYSCAN], product=0x4600 [TravelScan 460], chip=LM9832/3) at libusb:003:002-0a82-4600-00-00 + +
+ 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. +
+ +
+ SANE homepage
+ Contact
+
+ $Date$ $Author$ +
+ + +