[sane-devel] CANOSCAN 8400F

Wed Jun 4 10:22:24 UTC 2014

Dear Stef,

thanks a lot for your suggestions and scripts. The more I dig into the source code, the more
questions I have. Here they are:

1) file genesys_devices.c, definition of  Genesys_Model canon_8400f_model (line 1691). I realized that the dpi list does not correspond to the model (CS8400F has maximum resolution of 3200dpi).
- Shell I change the array with values available in the windows driver of the scanner? Is the length of the array fixed?

- Are the other values extracted from some logs, or shell I disassemble unit to measure all constants (position of white strip)?
- I have performed test scan with resolution of 100dpi of size 10x10 cm (specified with -x -y option). The resulting image had proper number of lines/rows (393), proper aspect ratio. However, the scan are was about 15x15 cm. I assume this has something to do with wrong array with dpi setting...

2) genesys_gl843.h, There is definition of the Sensor_Profile sensors. For the CS8400F there is defined array (line 666). I logged several scans with different dpi settings using usbsnoop. After processing logs with your script I found that there are different possible values reported for the sensor_profile and motor_profile. This profiles do not coincide with the one in the genesys_gl843.h. Here are ones, extracted from the logs:

sensor_profile { sensor_id, dpi, 7200, 0xe3f, 0x0, 0x1b6db, 5168, 0,0xffffffffffffffff,
0xfffffffffffffeff, 0xfffffffffffffeff, 0xfffffffffffffeff, 0xffffffffffffffff, 0x01, 0x02, 0xffffffffffffffff, 0xffffffffffffffff,
{0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0x33, 0x0c, 0x13, 0xffffffffffffffff, 0x30, 0xffffffffffffffff, 0x00, 0x84, },
{0x0d,0x10,0x01,0x04,0x07,0x0a,0x6b,0xffffffffffffffff,0x40,0x00,0x00,0xffffffffffffffff,0x85,},
}
sensor_profile { sensor_id, dpi, 7200, 0xe3f, 0x0, 0x1b6db, 5168, 0,0xffffffffffffffff,
0xfffffffffffffeff, 0xfffffffffffffeff, 0xfffffffffffffeff, 0xffffffffffffffff, 0x01, 0x02, 0xffffffffffffffff, 0xffffffffffffffff,
{0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0xffffffffffffffff, 0x33, 0x0c, 0x13, 0xffffffffffffffff, 0x30, 0xffffffffffffffff, 0x00, 0x84, },
{0x0d,0x10,0x01,0x04,0x07,0x0a,0x6b,0xffffffffffffffff,0x40,0x00,0x00,0xffffffffffffffff,0x88,},
},
sensor_profile { sensor_id, dpi, 22000, 0x0, 0xff, 0x0, 5168, 0,0x2a,
0x 0, 0x 0, 0x 0, 0xffffffffffffffff, 0x07, 0x08, 0xffffffffffffffff, 0xffffffffffffffff,
{0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x3b, 0x0c, 0x10, 0x2a, 0x30, 0x00, 0x00, 0x9a, },
{0x01,0x04,0x07,0x0a,0x0d,0x10,0x1b,0x00,0x40,0x00,0x00,0xffffffffffffffff,0x88,},
},
sensor_profile { sensor_id, dpi, 10800, 0xe3f, 0x0, 0x1b6db, 5168, 0,0x2a,
0x 0, 0x 0, 0x 0, 0xffffffffffffffff, 0x01, 0x02, 0xffffffffffffffff, 0xffffffffffffffff,
{0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33, 0x0c, 0x13, 0x2a, 0x30, 0x00, 0x00, 0x84, },
{0x0d,0x10,0x01,0x04,0x07,0x0a,0x6b,0x00,0x40,0x00,0x00,0xffffffffffffffff,0x88,},
},
sensor_profile { sensor_id, dpi, 14400, 0x1ff, 0x0, 0x24924, 5168, 0,0x2a,
0x 0, 0x 0, 0x 0, 0xffffffffffffffff, 0x00, 0x01, 0xffffffffffffffff, 0xffffffffffffffff,
{0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33, 0x0c, 0x11, 0x2a, 0x30, 0x00, 0x00, 0x84, },
{0x0b,0x0e,0x11,0x02,0x05,0x08,0x63,0x00,0x40,0x00,0x00,0xffffffffffffffff,0x88,},
},
sensor_profile { sensor_id, dpi, 7200, 0xe3f, 0x0, 0x1b6db, 5168, 0,0x2a,
0x 0, 0x 0, 0x 0, 0xffffffffffffffff, 0x01, 0x02, 0xffffffffffffffff, 0xffffffffffffffff,
{0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33, 0x0c, 0x13, 0x2a, 0x30, 0x00, 0x00, 0x84, },
{0x0d,0x10,0x01,0x04,0x07,0x0a,0x6b,0x00,0x40,0x00,0x00,0xffffffffffffffff,0x85,},
}

They are all different. Do you have any suggestions what to do with this? For each sensor_profile there is a motor_profile. They have the following structure:
motor_profile={id,7200,2, {0, 0, ......} all skipped numbers are zeros (in contrast to one in the genesys_gl843.h, line 677). The second number coincides with the first number reported in the sensor_profile.

I would appreciate you suggestions for further implementation.
Thank you in advance,
Best regards,
Myroslav

On Monday, June 2, 2014 9:39 PM, Stef <stef.dev at free.fr> wrote:

On 01/06/2014 14:19, Myroslav Kavatsyuk wrote:

Dear Stef,
>
>Finally I managed to test the CS8400F. In the git version of
          SANE there is
>some implementation of the scanner. After adding proper line
          to genesys.conf
>I managed to make first scan with the CS8400F. Scanning was
          invoked using
>scanimage. Here are my observations:
>* If I do not specify size of a document to scan (no -x and -y
          options), the scanner
>  head bumps into movement limiter (goes too far)
>* Scanner does not perform calibration and does not warm-up
          the lamp.
>   It starts scanning immediately after the scanimage command.
          Once I limited
>   scanning region with -x and -y options, I got image with
          vertical stripes (luck
>   of CCD gain calibration?)
>
>I am ready to work on the backend to make it usable. However,
          I need your help.
>In the SANE digest (vol 74, issue 19) you wrote: "Adding
          support for the Canoscan
>8400F will be a matter of tuning the settings structures in
          genesys_devices.c and
>genesys_gl843.h. Then maybe adapt the code in genesys_gl843.c
          to support the
>possible differences for this model."
>Can you give me more specific hints, where should I add
          calibration, warming up?
>I have running WindowsXP in the virtualbox with the usbsnoop,
          so I can get any
>required usb logs.
>
>
>Thank you in advance,
>Best regards,
>Myroslav
>
>
>
>
    Hello,

    calibration is currently desactived because of the
    GENESYS_FLAG_NO_CALIBRATION . Remove it to activate calibration.
    Since there are already 2 CCD scanners supported (KV-SS080 and HP
    G4050), you'll have to setup entries in data tables held in
    genesys_gl843:
    - Sensor_Profile sensors[]
    - Motor_Profile gl843_motors[]
    - slope table such a uint32_t kvss080[]

Data will have to be extracted from usb logs.  The dev cycle is run
    the backend with your changes, compare with usb logs, change code
    again to fix differences .... until it works.

Sometimes you'll may have to add specific behavior for your scanner
    in genesys_gl843.c see the use of CCD_G4050, CCD_KVSS080, etc...

    running 'doxygen genesys-doxygen.conf' in the doc/ sub dir will
    generate doxygen info for all the backend.

Regards,
    Stef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140604/78d6cd51/attachment.html>