diff --git a/unsupported/visioneer-strobe-xp-100.html b/unsupported/visioneer-strobe-xp-100.html new file mode 100644 index 00000000..bb59fc68 --- /dev/null +++ b/unsupported/visioneer-strobe-xp-100.html @@ -0,0 +1,174 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

+ Visioneer Strobe XP 100 +

+

Bus type

+

+ USB +

+

Vendor ID

+

+ 0x04a7 +

+

Product ID

+

+ 0x0427 +

+

Chipset

+

+ sane-find-scanner says that it's a NS LM9832/3. +

+

Comments

+

+ Sheetfed scanner. Maybe it can be supported by the plustek backend? +

+

Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv

+
+<device descriptor of 0x04a7/0x0427 at 003:002-04a7-0427-00-00 (Visioneer Inc. Strobe XP 100)>
+bLength               18
+bDescriptorType       1
+bcdUSB                1.00
+bDeviceClass          0
+bDeviceSubClass       0
+bDeviceProtocol       0
+bMaxPacketSize0       8
+idVendor              0x04A7
+idProduct             0x0427
+bcdDevice             1.00
+iManufacturer         64 (Visioneer Inc.)
+iProduct              95 (Strobe XP 100)
+iSerialNumber         0 ()
+bNumConfigurations    1
+ <configuration 0>
+ bLength              9
+ bDescriptorType      2
+ wTotalLength         39
+ bNumInterfaces       1
+ bConfigurationValue  1
+ iConfiguration       0 ()
+ bmAttributes         160 (Remote Wakeup)
+ MaxPower             500 mA
+  <interface 0>
+   <altsetting 0>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   0
+   bAlternateSetting  0
+   bNumEndpoints      3
+   bInterfaceClass    255
+   bInterfaceSubClass 0
+   bInterfaceProtocol 255
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x81 (in 0x01)
+    bmAttributes      3 (interrupt)
+    wMaxPacketSize    1
+    bInterval         16 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x82 (in 0x02)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 2>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x03 (out 0x03)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    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 (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] ...
+<This USB chip looks like a LM9832/3>
+
+found USB scanner (vendor=0x04a7 [Visioneer Inc.], product=0x0427 [Strobe XP 100], chip=LM9832/3) at libusb:003:002-04a7-0427-00-00
+
+    
+ +

Want to add or correct information?

+

+ 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. +

+ +

Information for Manufacturers

+

+ 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. +

+ +

Links

+ + +
+ +

+ SANE homepage
+ Contact +

+

+ $Date$ $Author$ +

+ + +