# Re: Mustek 1200SP/12000SP Firmware-1.05

Dr. Andreas Bolsch (Andreas.Bolsch@maths.nott.ac.uk)
Thu, 15 Apr 1999 10:20:33 +0100

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Russell W. Behne: "Mustek 600 CP"
- Previous message: Tim Waugh: "Re: xscanimage spins when scan cancelled"
- Maybe in reply to: Oliver Rauch: "Mustek 1200SP/12000SP Firmware-1.05"
- Next in thread: Bjoern Buerger: "Re: Mustek 1200SP/12000SP Firmware-1.05"

As I haven't got an MFS-12000SP I can give only some vague advice.
First thing would be to check the line distance values returned
by the scanner via
export SANE_DEBUG_MUSTEK=128
scanimage --mode color --resolution 150 -x50mm -y50mm >/dev/null
There would be something like 'line_distance: (0/2/4)'
For 300dpi and 600dpi this should read (0/4/8),(0/8/16).
The actual values might be slightly different. To get some idea
how that might look like I've appended some debug output from
my scanner.

If you get reasonable values a closer look at the initialization
code would be a good idea, i.e. where the model is checked and
some variables are initialized. Look for the strncmp( ... MFS-12000
...). As far as I recall right know (sorry, my box is at home) there
are two different line distance correction algorithms for the MFS
models, depending on the firmware revision, so trying the other
variant might help.

If this fails, too: Change the code for sending the gamma table
such that red gets all zeros, green all ones, blue all twos,
and add some code to output_data so that the data is dumped in
hex format, too. Then ist's possible to verufy the color sequence
precisely. But mind that there are two functions for sending the
gamma tables. gamma_send_se is *only* for the SE models.

Regarding the slow scanning: Check that the transfer size is close
two 128 kByte (reader: about to read ??? bytes).
If it's much smaller SG_BIG_BUFF is not set to a reasonable value
and should be increased to 127 * 1024 (/usr/include/scsi/sg.h).
Kernel and SANE would have to be recompiled then.
Note that in my debug output it's only 64 kByte, but that's specific
to the SE.

export SANE_DEBUG_MUSTEK=128
scanimage --mode color --resolution 75 -x50mm -y50mm >/dev/null
[sanei_init_debug]: Setting debug level of mustek to 128.
[mustek] attach: opening /dev/scanner as scsi device
[mustek] attach: sending INQUIRY
[mustek] scsi_wait_ready: sending TEST_UNIT_READY
[mustek] attach: firmware revision 1.01
[mustek] attach: found Mustek scanner model C06 S12IDW (flatbed
scanner), 1-pass, SE
[mustek] scsi_wait_ready: sending TEST_UNIT_READY
[mustek] do_inquiry: sending INQUIRY
[mustek] get_window: calib_bytes=15900, calib_lines=16
[mustek] get_window: bytes_per_line=888, lines=300
[mustek] get_window: gamma length=4096
[mustek] line_distance: got res=150, (r/g/b)=(0/2/4)
[mustek] get_window: bytes_per_line=444, lines=148, pixels=444
[mustek] send_gamma_se: sending table for color 1
[mustek] send_gamma_se: sending table for color 2
[mustek] send_gamma_se: sending table for color 3
[mustek] lines_per_buffer=73, bytes_per_line=888
[mustek] reader: about to read 64824 bytes
[mustek] buffer_bank: 0

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Russell W. Behne: "Mustek 600 CP"
- Previous message: Tim Waugh: "Re: xscanimage spins when scan cancelled"
- Maybe in reply to: Oliver Rauch: "Mustek 1200SP/12000SP Firmware-1.05"
- Next in thread: Bjoern Buerger: "Re: Mustek 1200SP/12000SP Firmware-1.05"