Information about unsupported UMAX Astra 4600

[MP-14]

I manage to have UMAX Astra 4600, that happen to be one of unsupported
models. I noticed that there is no info on
http://www.sane-project.org/sane-mfgs.html about this model, so I hope
this will be useful.

It is USB scanner, vendor id 0x06dc, product id 0x0012, from lsusb:

Bus 005 Device 002: ID 06dc:0012 Foxlink Image Technology Co., Ltd
Scan 1200c Scanner

There are two bigger chips inside, marked as:

REALTEK RTS8801C2-6
and
GLT44016-35J4

Relevant info from "sane-find-scanner -v -v":

<device descriptor of 0x06dc/0x0012 at 005:002>
bLength               18
bDescriptorType       1
bcdUSB                1.10
bDeviceClass          0
bDeviceSubClass       0
bDeviceProtocol       0
bMaxPacketSize0       8
idVendor              0x06DC
idProduct             0x0012
bcdDevice             1.00
iManufacturer         1 ()
iProduct              2 ()
iSerialNumber         8 ()
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         39
 bNumInterfaces       1
 bConfigurationValue  1
 iConfiguration       6 ()
 bmAttributes         224 (Self-poweredRemote Wakeup)
 MaxPower             0 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    255
   bInterfaceSubClass 0
   bInterfaceProtocol 255
   iInterface         7 ()
    <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    8
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x83 (in 0x03)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    1
    bInterval         250 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 (bNumEndpoints = 3)
    checking for GT-8911 ...
    this is not a GT-8911 (check 5, bNumEndpoints = 3)
    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 is not a LM983x (bEndpointAddress = 0x81, bmAttributes = 0x2,
wMaxPacketSize = 0x40, bInterval = 0x0)
    checking for GL646 ...
    this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for GL646_HP ...
    this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255)
    checking for GL660+GL646 ...
    this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for GL84x ...
    this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 255)
    checking for ICM532B ...
    this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 255)
    checking for PV8630/LM9830 ...
    this is not a PV8630/LM9830 (bcdUSB = 0x110)
    checking for M011 ...
    this is not a M011 (bDeviceClass = 0)
    checking for RTS8822 ...
    this is not a RTS8822 (bEndpointAddress = 0x81, bmAttributes =
0x2, wMaxPacketSize = 0x40, bInterval = 0x0)
    checking for rts8858c ...
    Unexpected result from register reading (0xff/0x0)
    checking for SQ113 ...
    this is not a SQ113 (bcdUSB = 0x110)
    checking for HP5550/5590/7650 chipset ...
    this is not a HP5550/5590/7650 chipset (bDeviceClass = 0)
    checking for rts8801/rts8891 ...
    Unexpected result from register reading (0x12/0x0)
<Couldn't determine the type of the USB chip (result from sane-backends 1.0.20)>

found USB scanner (vendor=0x06dc, product=0x0012) at libusb:005:002

Hope that helps. If you think some further information/testing would
help, tell me.

Martin Petricek

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

[stef-22]

Le lundi 2 novembre 2009 21:48:11 MP, vous avez écrit :

> I manage to have UMAX Astra 4600, that happen to be one of unsupported
> models. I noticed that there is no info on
> http://www.sane-project.org/sane-mfgs.html about this model, so I hope
> this will be useful.
>
> It is USB scanner, vendor id 0x06dc, product id 0x0012, from lsusb:
>
> Bus 005 Device 002: ID 06dc:0012 Foxlink Image Technology Co., Ltd
> Scan 1200c Scanner
>
> There are two bigger chips inside, marked as:
>
> REALTEK RTS8801C2-6
> and
> GLT44016-35J4
>
> Relevant info from "sane-find-scanner -v -v":
>
> <device descriptor of 0x06dc/0x0012 at 005:002>
> bLength               18
> bDescriptorType       1
> bcdUSB                1.10
> bDeviceClass          0
> bDeviceSubClass       0
> bDeviceProtocol       0
> bMaxPacketSize0       8
> idVendor              0x06DC
> idProduct             0x0012
> bcdDevice             1.00
> iManufacturer         1 ()

...

>     this is not a SQ113 (bcdUSB = 0x110)
>     checking for HP5550/5590/7650 chipset ...
>     this is not a HP5550/5590/7650 chipset (bDeviceClass = 0)
>     checking for rts8801/rts8891 ...
>     Unexpected result from register reading (0x12/0x0)
> <Couldn't determine the type of the USB chip (result from sane-backends
>  1.0.20)>
>
> found USB scanner (vendor=0x06dc, product=0x0012) at libusb:005:002
>
> Hope that helps. If you think some further information/testing would
> help, tell me.
>
> Martin Petricek
>

        Hello,

        from the chip's label, support for you scanner belongs to the rts8891
backend, even though sane-find-scanner doesn't detect it properly. Do you have
a windows box where you can run your scanner ? If so I'd be interested by an
Usbsnoop (http://www.pcausa.com/Utilities/UsbSnoop/) log of a 75 dpi color
scan. I'd be able to tell for sure how close it is from supported models. If
needed I can provide some explanations on how doing it.
        From the known information, your scanner doesn't seem to be far from the
Astra 4400 which isn't yet supported. Bringing support for these 2 scanners is
a matter of how different they are from supported models. If close, by
exchanging logs and test code we'd be able to have them working. But if they
are too different, support wouldn't be possible with access for a developer to
the real hardware.
        If you feel like it you could add your scanner to rts8891.conf.in and  
rts8891_devices.c source files (cloning the HP4470 entry), and have a try. Be
aware that when experimenting with partially supported hardware, you can't
exclude it could be damaged.

Regards,
        Stef


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

[MP-14]

>         from the chip's label, support for you scanner belongs to the rts8891
>  backend, even though sane-find-scanner doesn't detect it properly. Do you have
>  a windows box where you can run your scanner ? If so I'd be interested by an

I have only windows instalation inside virtualbox, but as vbox does
support bridging USB devices inside virtual machines, I was able to
scan a 75 dpi color page from the scanner, while capturing
communication using UsbSnoop.

Since the log file is 3.6Mb even after bzipping, I uploaded it to
http://wtx.wz.cz/UsbSnoop.log.bz2
In the log, actual scanning (when the scanner started warming up)
starts about 97000 ms

>  Usbsnoop (http://www.pcausa.com/Utilities/UsbSnoop/) log of a 75 dpi color
>  scan. I'd be able to tell for sure how close it is from supported models. If
>  needed I can provide some explanations on how doing it.
>         From the known information, your scanner doesn't seem to be far from the
>  Astra 4400 which isn't yet supported. Bringing support for these 2 scanners is
>  a matter of how different they are from supported models. If close, by
>  exchanging logs and test code we'd be able to have them working. But if they
>  are too different, support wouldn't be possible with access for a developer to
>  the real hardware.

What about some form of remote access?

>         If you feel like it you could add your scanner to rts8891.conf.in and
>  rts8891_devices.c source files (cloning the HP4470 entry), and have a try. Be
>  aware that when experimenting with partially supported hardware, you can't
>  exclude it could be damaged.

What type of damage can I expect from that?  Something like the
scanner lamp driving off the rails, which could be maybe fixed just by
using a screwdriver or some parts irreversibly burning out?

Martin Petricek

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

[stef-22]

Le mardi 3 novembre 2009 13:38:44 MP, vous avez écrit :

> >         from the chip's label, support for you scanner belongs to the
> > rts8891 backend, even though sane-find-scanner doesn't detect it
> > properly. Do you have a windows box where you can run your scanner ? If
> > so I'd be interested by an
>
> I have only windows instalation inside virtualbox, but as vbox does
> support bridging USB devices inside virtual machines, I was able to
> scan a 75 dpi color page from the scanner, while capturing
> communication using UsbSnoop.
>
> Since the log file is 3.6Mb even after bzipping, I uploaded it to
> http://wtx.wz.cz/UsbSnoop.log.bz2
> In the log, actual scanning (when the scanner started warming up)
> starts about 97000 ms
>
> >  Usbsnoop (http://www.pcausa.com/Utilities/UsbSnoop/) log of a 75 dpi
> > color scan. I'd be able to tell for sure how close it is from supported
> > models. If needed I can provide some explanations on how doing it.
> >         From the known information, your scanner doesn't seem to be far
> > from the Astra 4400 which isn't yet supported. Bringing support for these
> > 2 scanners is a matter of how different they are from supported models.
> > If close, by exchanging logs and test code we'd be able to have them
> > working. But if they are too different, support wouldn't be possible with
> > access for a developer to the real hardware.
>
> What about some form of remote access?
>
> >         If you feel like it you could add your scanner to rts8891.conf.in
> > and rts8891_devices.c source files (cloning the HP4470 entry), and have a
> > try. Be aware that when experimenting with partially supported hardware,
> > you can't exclude it could be damaged.
>
> What type of damage can I expect from that?  Something like the
> scanner lamp driving off the rails, which could be maybe fixed just by
> using a screwdriver or some parts irreversibly burning out?
>
> Martin Petricek
>

        Hello,

        I have downloaded and decoded the log. I can confirm that your scanner will
work with the rts8891. The calibration (offset, gain and shading) uses the
same algorithm than the one coded in the backend. Also it looks close to the
Astra 4400 log I already have.

        But there are some differences that may make support for it difficult. First
the data in log looks like noise, I'd be inclined to think that it is
compressed. Did you scanned a white area ? Then it seems the scan is done at
200 or 100 dpi even if 75 was required. This resolution isn't supported at
all. So there will be some significant changes. While remote access to the
scanner would help, I think the best solution is that you start hacking the
backend. I will provide help for that. Another solution is that I can have the
same hardware.

        Based on the backend I worked on, here are the risks I see when adding
support for new hardware:
        - send wrong commands to motor, having them doing some strange noises and
          maybe shortening their lifespan
        - moving scanning head 'past end of device', having it banging on physical
          boundaries
        - send wrong command to scanner's lamp so it make it physically fails
        - wipe out EEPROM, firmware

        On the 10+ scanners I toyed with, I only have my HP4470 damaged. I wiped
EEPROM. Now it reports itself to be a Astra 4400. The offending code is
commented out and it shouldn't happen again with the rts8891 backend. None of
my scanners had a physical failure. If you stand close to the scanner, you can
unplug it when it is doing some strange noises.

Regards,
        Stef
       

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...