Scanners not supported by SANE

Manufacturer and model

Avision iVina FB1800
UMAX Astra 4700

Bus type

USB

Vendor ID

0x0638

Product ID

0x0a20

Chipset

Is reported to use a Genesys Logic GL660USB chip (USB 2.0 converter) and the Avision B2 (=GL646) chipset.

Main circuit board: AVISION B2 \ 163-54-001005 \ 0215E38B3
                    GL660USB   \ 0221MF3K7-32  \ 164-07-000660
                    tm TECH 0041 \ 100 MHz \ NA010MN T224162B-25J

Aux. circuit board: L6219DS \ 6992D0215 \ ST Malaysia
                    F P22SD \ 7 4VHCUO4
    

Comments

Will most probably work with the Genesys backend, when it's finished.

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

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1   
P:  Vendor=0638 ProdID=0a20 Rev= 3.01
S:  Manufacturer=UMAX
S:  Product=ASTRA 4700
S:  SerialNumber=1
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   1 Ivl=8ms

<device descriptor of 0x0638/0x0a20 at 004:004 (UMAX ASTRA 4700)>
bLength               18
bDescriptorType       1
bcdUSB                2.00
bDeviceClass          255
bDeviceSubClass       255
bDeviceProtocol       255
bMaxPacketSize0       64
idVendor              0x0638
idProduct             0x0A20
bcdDevice             3.01
iManufacturer         4 (UMAX)
iProduct              5 (ASTRA 4700)
iSerialNumber         1 (1)
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         39
 bNumInterfaces       1
 bConfigurationValue  1
 iConfiguration       0 ()
 bmAttributes         192 (Self-powered)
 MaxPower             10 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    0
   bInterfaceSubClass 0
   bInterfaceProtocol 0
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x81 (in 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    512
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x02 (out 0x02)
    bmAttributes      2 (bulk)
    wMaxPacketSize    512
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x83 (in 0x03)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    1
    bInterval         8 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 = 0x200)
    checking for GT-6816 ...
    this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 0)
    checking for GT-8911 ...
    this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 0)
    checking for MA-1017 ...
    this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 0)
    checking for MA-1015 ...
    this is not a MA-1015 (bcdUSB = 0x200)
    checking for MA-1509 ...
    this is not a MA-1509 (bcdUSB = 0x200)
    checking for LM983[1,2,3] ...
    this is not a LM983x (bDeviceClass = 255, bInterfaceClass = 0)
    checking for GL646 ...
    this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 0)
    checking for GL646_HP ...
    this is not a GL646_HP (bDeviceClass = 255, bInterfaceClass = 0)
    checking for GL660+GL646 ...
<This USB chip looks like a GL660+GL646>

found USB scanner (vendor=0x0638 [UMAX], product=0x0a20 [ASTRA 4700], chip=GL660+GL646) at libusb:004:004
    

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.


SANE homepage
Contact