sane

This page provides some scanner drivers for SANE (which work under Linux, *BSD and most unices).

Note: Most of it is old stuff, already integrated into SANE.

Umax Sceptre Matsushita Relisys Leo HP Windows

UMAX 2200 USB

Patch to support the UMAX 2200 USB scanner. The scanner has both connectors.
The SCSI version is already supported by the umax backend. This patch adds the USB support.

For SANE 1.0.6:

apply that patch (umax2200usb-2.diff.gz) to the sources. Build and install.

For SANE 1.0.7:

Apply that patch (sane-umaxusb-1.0.7-1.diff.gz ) to the sources. Build and install.

For SANE 1.0.8:

Nothing special to do. The patch has been integrated in SANE 1.0.8.

For SANE 1.0.9:

Some changes were made to SANE to support libusb. Unfortunatly I didn't fully use the SANE's usb API and this broke the support for that scanner. This patch (umax-usb-1.0.9-fix1.diff) is necessary to make it work again.

Miscellaneous:

Under Linux, if the scanner module doesn't show up automatically, you may have to use the following command (run as root):

	modprobe scanner vendor=0x1606 product=0x0230

The kernels until 2.4.14 (?) doesn't have the full support for what the UMAX scanner requires. Either upgrade the USB scanner driver or upgrade the kernel.
The kernel 2.2.20 does not have the support either. To make it work, replace the scanner_ioctl() function in drivers/usr/scanner.c with the one from 2.4.18.

And disable the "quality calibration" else you would be able to preview but not to scan. The calibration is done anyway on that scanner, so that does not hurt.

Since some backend are sending some commands to the scanner that make it crash, always specify which backend you want to use. For instance:
xscanimage umax
scanimage -d umax

If you have a big endian machine (eg PPC or Risc, but not Intel) you will need at least a kernel 2.4.20, or you can patch the kernel scanner driver with that patch (http://marc.theaimsgroup.com/?l=linux-usb-devel&m=102908250427293&w=2) or that patch (http://marc.theaimsgroup.com/?l=linux-usb-devel&m=103154732732619&w=2).

The frontend should be able to autodetect the scanner.

SCEPTRE

S1200 / S120

This backend has been integrated in SANE 1.0.8.

Sane 1.07 patch to support the Sceptre S1200 scanner.
This is a beta version. All scan modes are working (Black and white, Halftone, Grayscale, Color).
The resolutions goes from 50 to 1200 dpi, but only a number of these are available.
The backend has all the functionnalities of the windows driver.
This scanner seems to be a rebranded KINPO scanner. So KINPO scanners might also work.
This scanner was also sold under the name Komodo.

    the most recent version is in the CVS tree.

Previous versions:
    sanecvs-sceptre-20020220-2.diff.gz (for SANE CVS of that day - added to the CVS tree, 1.0.7+)
sanecvs-sceptre-20020220.diff.gz (for SANE CVS of that day)
    sane-sceptre-20020214.diff.gz (for SANE 1.0.7)
    sane-sceptre-20020210.diff.gz (for SANE 1.0.7)
    sane-sceptre-20020209.diff.gz (for SANE 1.0.7)
sane-sceptre-20020202.diff.gz (for SANE 1.0.6)

MATSUSHITA / PANASONIC

This backend has been integrated in SANE 1.0.8.

This backend supports the Panasonic KV-SS25 and KV-SS25A scanners. It should also support the following scanners with some customization:
KV-SS850 and KV-SS855.

The KV-SS50, KV-SS55, KV-SS50EX, KV-SS55EX have a "video" connection to the hosts. I don't think there is any drivers for these on Linux. If there was they should work with that backend.

It is probable that more Panasonic scanners can be supported.

The backend is the beta stage:
    - all resolution are working.
- all scan modes are working (B&W, Halftone, Gray 4 bits and Gray 8 bits)
    - duplex is working (tested with scanadf)
    - multi-pages scan is working (tested with scanadf)
    - all enhancement options are implemented and should work.
    - the sub-areas are not implemented, probably will never be (by me).
    - it is not possible to select different options for each side (eg. scan area).
    - download of halftone pattern and gamma is not possible.
    - scan speed (letter format, with scanadf):
       * B&W, 150 dpi, simplex : 28 ppm
        * B&W, 300 dpi, simplex : 14 ppm
        * B&W, 150 dpi, duplex: 25ppm
        * Gray 4 bits, 150 dpi, simplex: 26 ppm
        * Gray 8 bits, 150 dpi, simplex: 24 ppm

    the most recent version is in the CVS tree.

Previous versions:
    sane-matsushita-20020304.diff.gz (for SANE 1.0.7)
    sane-matsushita-20020303.diff.gz (for SANE 1.0.7)
    sane-matsushita-20020226.diff.gz (for SANE 1.0.7)
    sane-matsushita-20020223.diff.gz (for SANE 1.0.7)
    sane-matsushita-20020221.diff.gz (for SANE 1.0.7)

HOW TO DETECT A TECO SCANNER MODEL

Under SANE 1.0.8 (or more), as root, use the command
    sane-find-scanner -v Under SANE 1.0.10 (or more), as root, use the command
    sane-find-scanner -v -v

If in the inquiry strings you see the letters "TECO VM" followed by three or four numbers, then it is a TECO scanner. For instance:

   000: 06 00 02 02 43 00 00 10 41 61 73 68 69 6d 61 20    ....C...Aashima    016: 49 4d 41 47 45 52 59 20 34 38 30 30 53 50 20 2b    IMAGERY 4800SP +    032: 35 2e 30 38 35 2e 30 38 03 02 54 45 43 4f 20 56    5.085.08..TECO V    048: 4d 33 35 35 32 20 00 01 01 2c 00 01 04 b0 09 f6    M3552 ...,......    064: 10 68 01 2c 00 00 00 00                            .h.,....

TECO / RELISYS

The teco1 backend supports the following scanners:

Relisys RELI 2412	VM3530+	Works. (inquiry model VM353A.)
Relisys AVEC 2412	VM3520+	Untested. Should work with little modifications.
Relisys RELI 4830	VM4542	Works.
Relisys AVEC 2400	VM3520	Works.
Relisys AVEC 4800	VM4530	Untested. Should work with little modifications.
Relisys AVEC 4816	VM4530+	Untested. Should work with little modifications.
Relisys RELI DS6	VM3420	Untested. Should work with little modifications.
Relisys RELI DS15	VM3440	Untested. Should work with little modifications.
Relisys RELI 2400	VM3530	Untested. Should work with little modifications.
Relisys RELI 2412	VM3530+	Untested. Should work with little modifications.
Relisys RELI 4816	VM4540	Untested. Should work with little modifications.
Relisys RELI 9600	VM6530	Untested. Should work with little modifications.
Relisys RELI 9612	VM6530*	Untested. Should work with little modifications.
Relisys RELI 9624	VM6530+	Untested. Should work with little modifications.
Relisys RELI 9630	VM6540	Untested. Should work with little modifications.
Dextra DF-600P	VM3510	Works.
Dextra DF-4830T	VM4542	Untested. (same as Relisys RELI 4830.)
Dextra DF-1200T+	VM3530+	Untested. (same as Relisys RELI 2412.)
Dextra DF-9624	VM6530+	Untested. (same as Relisys RELI 9624.)

The backend status is:
- all modes working (B&W, Grayscale, Color)
- all resolutions working
- no ADF or transparency support
    - the image are stretched above 300dpi (the scanner doesnot interpolate if X and Y resolutions differ)
- some scanners respond to all luns. Use lun 0 ONLY, or the scanner won't work (this is be taken care of by the configuration file).

    the backend is now in SANE 1.0.8

These files are a replacement that adds support for the VM4542: teco1.c teco1.conf teco1.h
The support for VM4542 will be in SANE 1.0.9.

The mailing list for TECO scanners is http://groups.yahoo.com/group/teco-sane-devel/

Previous versions:
    sane-teco1-cvs20020407.diff.gz (for SANE CVS of 2002/04/07)
    sane-teco-20020326.diff.gz (for SANE 1.0.7)
    sane-teco-20020318.diff.gz (for SANE 1.0.7)
sane-teco-20020312.diff.gz (for SANE 1.0.7)

TECO / RELISYS

This backend has been integrated into SANE 1.0.9.
Gerard Klaver is the current maintainer of that backend. See http://gkall.hobby.nl/notes2.html

The teco2 backend supports the following scanners:

Relisys AVEC II S3	VM3564	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported) - SANE 1.0.12
Primax Jewel 4800	VM356A	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported) - SANE 1.0.12
Relisys APOLLO Express 3	VM356A	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported) - SANE 1.0.12
Relisys AVEC Super 3	VM3575	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported)
Relisys SCORPIO Super 3	VM3575	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported)
Relisys APOLLO Express 6	VM6565	All modes working fine. (inquiry model VM656A)
Relisys APOLLO Express 12	?	untested. Probaly a variant of the Express 6
Relisys SCORPIO Pro-S	VM6586	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported)
Primax Profi 19200	VM6586	B&W and Grayscale OK. Color is problematic (only a few resolutions are supported)
Relisys SCORPIO Pro	VM6575	All modes working fine.
Primax Profi 9600	VM6575	All modes working fine.

The backend should be considered beta version. Progress is slow since I have none of these scanners.
Some work is being done by Gerard Klaver on the PRIMAX Jewel 4800 (VM3564), which appear to be a clone or a close cousin of the Relisys Apollo Express 3 scanner (VM 3565).

The mailing list for TECO scanners is http://groups.yahoo.com/group/teco-sane-devel/

teco2

TECO / RELISYS

This backend has been integrated into SANE 1.0.9.

The teco3 backend supports the following scanners:

Relisys Scorpio	VM3552	Works.
Relisys Taurus/Infinity	VM3552	Untested, but should work as is.
Relisys Taurus/Infinity	VM4552	Untested. Probably a variant of VM3552.
Relisys Taurus/Infinity	VM6552	Untested. Probably a variant of VM3552.
Piotech Splendeur 3024	VM3552	Works.
Plustek OpticPro 2400SP	VM3552	Untested, but should work as is.
Trust Imagery 2400SP	VM3552	Works.
Trust Imagery 4800 SP+	VM3552	Works.
Trust Imagery 9600SP	?	Untested. Probably a VM3552 or a variant.

It is possible to extend the memory of a VM3552 (at least on the PIOTECH) by adding a RAM module. This is recommended, else the scanner crawls at high resolutions. Check here.
The mailing list for TECO scanners is http://groups.yahoo.com/group/teco-sane-devel/

    The backend status is:
- all modes working (B&W, Grayscale, Color)
- all resolutions working (as long as the memory extension is installed, else only a few color resolution are ok (100, 150 and 300)).
- no ADF or transparency support
    - the image are stretched above 300dpi (the scanner does not interpolate if X and Y resolutions differ)

    The backend has been integrated into the CVS tree. It will be in SANE 1.0.9.

    sane-teco3-20020724.diff.gz (for SANE CVS of 2002-07-24)

    sane-teco3-20020531.diff.gz (for SANE 1.0.8)
    sane-teco3-20020504.diff.gz (for SANE 1.0.7)

apply the patch above and then copy teco3.c teco3.h into backend/

LEO

This backend has been integrated in SANE 1.0.8.

This backend supports the Across Technologies FS1130. It is a rebadged LEO FS1130. If you have such a scanner or a scanner where the FCC ID starts with "LUZ", drop me an email.

Status:
    - black&white, gray, color ok
    - halftone supported
    - gamma supported
    - all resolutions supported (1 to 300 dpi)

    sane-leo-20020417.diff.gz (for SANE 1.0.7)

Previous versions:
    sane-leo-20020415.diff.gz (for SANE 1.0.7)
    sane-leo-20020412.diff.gz (for SANE 1.0.7)

HP4200

This is a cleaned-up version of the original hp4200 backend. It also adds the preview mode. Not very well tested. This version is for SANE CVS 2003/01/14
    hp4200-makefile.diff
    hp4200-backend-2.tar.gz (new release with all files)

Makefile / Configure cleanups
Use:
- in sane-backends, type "gunzip -c configure-cleanups-2.diff | patch -p0"
    - "rm configure aclocal.m4"
- "aclocal && autoconf"
- build as usual
Changes:
    - do not link every library to every backend (eg libusb and libjpeg)
    - do not link scanimage with libjpeg/libusb/...
    - add specific libraries with ADDLIB-<backend name> rule
    - tested under linux 2.4

    configure-cleanups-3.diff.gz

Old versions:
    configure-cleanups-2.diff.gz
    configure-cleanups-1.diff.gz

Translation (.po files) to French
saneopts (added to the CVS tree, 1.0.7+)
umax backend (added to the CVS tree, 1.0.7+)

Testsuite

This frontend has been integrated in SANE 1.0.8, in the sane-backends package.

This is a testsuite for backends. It tries to test the options and do some scans.

usage:
tstbackend [-d backendname] [-l level] [-r recursion_level]
level can be 0 (default),1 or 2. The higher the level, the more tests.
    0 - basic SANE interface tests
    1 - 0 + option tests
    2 - 1 + relatively short scans
3 - 2 + longer scans (12 scans per scan mode, so it can take some time)

Template

This is template to create a SANE backend. It's scsi oriented, but should work for USB or PP. I've used it to create my backends. If you have some scsi docs of your scanner or some good traces, it allows you to quickly create a backend. My third backend (teco) has done the first scan in about 6 hours using this template. Read template.txt and follows the instructions.

sane-template-2.tar.gz (2002/03/21)
sane-template-1.tar.gz

Windows

SANE on windows

Back

Frank Zago - sane at zago dot net
Speaking French and English.