Scanners not supported by SANE

Manufacturer and model

Hewlett-Packard ScanJet 3670c

Bus type

USB

Vendor ID

0x03f0

Product ID

0x1405

Chipset

GL646_HP

Written on the chipset:

 26-00204-00A
 0310FGGSH-10
    

Also there is an Elite MT RAM chip:

EliteMT (100MHz)
M1B416256A
DZC1HF2GJ
    

Comments

Te Genesys backend may support that scanner when it's finished.

Same scanner as 3690?

Several people want to write a backend. See this thread on sane-devel for details.

Some Snoopy logs are available.

The Windows .inf file says, that it's the same driver for 3600 series and 2400 series?

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

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs=  1
P:  Vendor=03f0 ProdID=1405 Rev= 1.00
S:  Manufacturer=Hewlett-Packard
S:  Product=HP Scanjet Scanner
S:  SerialNumber=CN39AS2QW0
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 48mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff 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 0x03f0/0x1405 at 001:004 (Hewlett-Packard HP Scanjet Scanner)>
bLength               18
bDescriptorType       1
bcdUSB                1.10
bDeviceClass          255
bDeviceSubClass       255
bDeviceProtocol       255
bMaxPacketSize0       8
idVendor              0x03F0
idProduct             0x1405
bcdDevice             1.00
iManufacturer         1 (Hewlett-Packard)
iProduct              2 (HP Scanjet Scanner)
iSerialNumber         12 (CN39AS2QW0)
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         39
 bNumInterfaces       1
 bConfigurationValue  1
 iConfiguration       0 ()
 bmAttributes         192 (Self-powered)
 MaxPower             48 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   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    64
    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 (bNumEndpoints = 3)
    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 ...
    this is not a MA-1015 (bcdUSB = 0x110)
    checking for MA-1509 ...
    this is not a MA-1509 (bEndpointAddress = 0x2, bmAttributes = 0x2, wMaxPacketSize = 0x40)
    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 USB chip looks like a GL646_HP>

found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1405 [HP Scanjet Scanner], chip=GL646_HP) at libusb:001: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.

Links


SANE homepage
Contact

$Date$ $Author$