[sane-devel] CanoScan 5000F support?

[xy]

On 03/21/2010 03:39 AM, Gernot Hassenpflug wrote:
> On Sun, Mar 21, 2010 at 7:54 AM, xy<abi1789 at googlemail.com>  wrote:
>> I am trying to get my CanoScan 5000F working.
>>
>> My sane-find-devices output matches the one on the SANE device page:
>> http://www.sane-project.org/unsupported/canon-5000f.html
>>
>> I have access to a Windows XP machine, so I could sniff something. I also
>> noticed the "To owners of CanoScan 5600F: please volunteer for
>> testing"-thread; is there a chance my scanner uses the pixma protocol? How
>> could I check this?
>
> Hello Peter,
> I think the best you could do is download a CVS version of SANE,
> compile it, and run the sane-find-scanner -v -v command to detect a
> scanner: the CVS version of SANE includes much new code that will
> detect more of the Genesys chips. I do not think the scanner will use
> a pixma protocol if it uses one of those chips.
> Regards,
> Gernot Hassenpflug
sane-find-scanner from git HEAD (2010-03-16 06:40:12) just outputed this:

############
<device descriptor of 0x04a9/0x2212 at 001:004 (Canon CanoScan)>
bLength               18
bDescriptorType       1
bcdUSB                2.00
bDeviceClass          255
bDeviceSubClass       255
bDeviceProtocol       255
bMaxPacketSize0       64
idVendor              0x04A9
idProduct             0x2212
bcdDevice             3.03
iManufacturer         2 (Canon)
iProduct              3 (CanoScan)
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 is not a GL660+GL646 (reg 0x4e != reg 0x38)
      checking for GL84x ...
      this is not a GL84x (bDeviceClass = 255, bInterfaceClass = 0)
      checking for ICM532B ...
      this is not a ICM532B (check 1, bDeviceClass = 255, 
bInterfaceClass = 0)
      checking for PV8630/LM9830 ...
      this is not a PV8630/LM9830 (bDeviceClass = 255)
      checking for M011 ...
      this is not a M011 (bcdUSB = 0x200)
      checking for RTS8822 ...
      this is not a RTS8822 (bDeviceClass = 255)
      checking for rts8858c ...
      this is not a rts8858c (bDeviceClass = 255)
      checking for SQ113 ...
      this is not a SQ113 (bDeviceClass = 255)
      checking for HP4500C/4570C/5500C/5550C/5590/7650 chipset ...
      Couldn't send send USB-in-USB command (Connection timed out)
      checking for rts8801/rts8891 ...
      this is not a rts8801/rts8891 (bDeviceClass = 255)
<Couldn't determine the type of the USB chip (result from sane-backends 
1.0.21cvs)>

found USB scanner (vendor=0x04a9 [Canon], product=0x2212 [CanoScan]) at 
libusb:001:004
###############

so I opened the device and made some photos.

There is a "very big" chip with lots of pins on all four edges, which is 
labled with:
      Mercury 03
      A234-0604
      FFHWA-2

There is also a chip with pins on two edges, which is nearer to the 
usb-port and labled with:
      tm    (superscript) TE     (subscript) C      (obviously some 
company name)
      7S
      0212
      T431616A   EP0539X

I will also attach a photo of this.


PyroPeter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: canoscan5000f.jpg
Type: image/jpeg
Size: 57545 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100321/1ba88582/attachment-0001.jpg>