title: sane-dc240(5)

text:
# sane-dc240(5)

## NAME
sane-dc240 - SANE backend for Kodak DC240 Digital Camera

## DESCRIPTION
The sane-dc240 library implements a SANE (Scanner Access Now Easy) backend that provides access to the Kodak DC240 camera. THIS IS EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!

## DEVICE NAMES
The current version of the backend only allows one camera to be connected. The device name is always "0".

## CONFIGURATION
The contents of the dc240.conf specify the serial port and baud rate to use. The baud rate specifies the maximum rate to use while downloading pictures. (The camera is always initialized using 9600 baud, then switches to the higher rate). On a 450MHz Pentium, I usually have no problems downloading at 115200 baud, though the camera sometimes has to resend packets due to lost characters. Results are better when the "interrupt-unmask flag" is set in the IDE driver (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and 115200.

The dumpinquiry line causes some information about the camera to be printed.

cmdrespause specifies how many usec (1,000,000ths of a second) to wait between writing the command and reading the result. 125000 seems to be the lowest I could go reliably.

breakpause specifies how many usec (1,000,000ths of a second) between sending the "back to default" break and sending commands.

Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:

port=/dev/ttyS0

\# this is a comment

baud=115200

dumpinquiry

cmdrespause=125000

breakpause=1000000

## FILES
/etc/sane.d/dc240.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-dc240.a

The static library implementing this backend.

/usr/lib64/sane/libsane-dc240.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_DC240

If the library was compiled with debugging support enabled, this environment variable controls the debug level for this backend. A value of 128 requests maximally copious debug output; smaller levels reduce verbosity.

## SEE ALSO
sane(7)

## AUTHOR
Peter S. Fales

This backend borrows heavily from the sane-dc210(5) backend by Brian J. Murrell which is based somewhat on the sane-dc25(5) backend by Peter Fales.

The manpage was largely copied from the sane-dc210(5) manpage.

## BUGS
The major limitation that I know of is that the backend assumes the directory in the camera is 100dc240. Once the camera has taken more than 9999 pictures, the directory will increment to 101dc240. Not only should we check for the additional directory, but pictures may actually be found in multiple directories.

More general comments, suggestions, and inquiries about frontends or SANE should go to the SANE Developers mailing list (see http://www.sane-project.org/mailing-lists.html for details). You must be subscribed to the list, otherwise your mail won't be sent to the subscribers.


package: libsane

title: sane-dc25(5)

text:
# sane-dc25(5)

## NAME
sane-dc25 - SANE backend for Kodak DC20/DC25 Digital Cameras

## DESCRIPTION
The sane-dc25 library implements a SANE (Scanner Access Now Easy) backend that provides access to Kodak DC20 and DC25 cameras. At present, only the DC25 has been tested, but since the code is based on a DC20 interface program, it is likely to work for that model also.

## DEVICE NAMES
The current version of the backend only allows one camera to be connected. The device name is always "0".

## CONFIGURATION
The contents of the dc25.conf specify the serial port and baud rate to use. The baud rate specifies the maximum rate to use while downloading pictures. (The camera is always initialized using 9600 baud, then switches to the higher rate). On my 90MHz Pentium, I usually have no problems downloading at 115200 baud as long as the system is not excessively busy and the "interrupt-unmask flag" is set in the IDE driver (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and 115200.

The dumpinquiry line causes some information about the camera to be printed to stderr during startup. Note: This is not compatible with saned, so make sure you don't have any dumpinquiry lines if you are using saned (i.e. scanning on a remote machine using a network).

Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:

port=/dev/ttyS0

\# this is a comment

baud=115200

dumpinquiry

## FILES
/etc/sane.d/dc25.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-dc25.a

The static library implementing this backend.

/usr/lib64/sane/libsane-dc25.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_DC25

If the library was compiled with debugging support enabled, this environment variable controls the debug level for this backend. A value of 128 requests maximally copious debug output; smaller levels reduce verbosity.

## SEE ALSO
sane(7)

## AUTHOR
Peter Fales, dc25-devel@fales-lorenz.net.

## BUGS
Known bugs/limitations are:

I haven't figured out how to trigger an option reload following a "scan." This causes problems when a new picture is snapped for example, the slider that is used to select the picture from the camera may not be updated immediately.

More general comments, suggestions, and inquiries about frontends or SANE should go to the SANE Developers mailing list (see http://www.sane-project.org/mailing-lists.html for details). You must be subscribed to the list, otherwise your mail won't be sent to the subscribers.


sane-dll

title: sane-dll(5)

summary: SANE dynamic backend loader

text:
# sane-dll(5)

## NAME
sane-dll - SANE dynamic backend loader

## DESCRIPTION
The sane-dll library implements a SANE (Scanner Access Now Easy) backend that provides access to an arbitrary number of other SANE backends. These backends may either be pre-loaded at the time the sane-dll library is built or, on systems that support dynamic loading of shared libraries, the backends may be loaded at runtime. In the latter case, adding support for a new backend simply involves installing the relevant library in /usr/lib64/sane and adding an entry to the dll.conf configuration file. In other words, no applications need to be modified or recompiled to add support for new devices.

## DEVICE NAMES
This backend expects device names of the form:

backend:device

Where backend is the name of the backend and device is the name of the device in this backend that should be addressed. If the device name does not contain a colon (:), then the entire string is treated as the device string for the default backend. The default backend is the backend listed last in the configuration file (see below) or the first pre-loaded backend (if any).

## CONFIGURATION
The contents of the dll.conf file is a list of backend names that may be loaded dynamically upon demand. Empty lines are ignored, also everything after a hash mark (#). A sample configuration file is shown below:

net

\# this is a comment

pnm

mustek

It is also possible to add a file in /etc/sane.d/dll.d that contains the list of backends to be added. Backends mentioned in a file included in this directory will be added before any backends listed in dll.conf. Files in /etc/sane.d/dll.d can be freely named. They shall follow the format conventions as apply for dll.conf.

Note that backends that were pre-loaded when building this library do not have to be listed in this configuration file. That is, if a backend was preloaded, then that backend will always be present, regardless of whether it's listed in the configuration file or not.

The list of preloaded backends is determined by macro PRELOADABLE_BACKENDS in file backend/Makefile.in of the SANE source code distribution. After changing the value of this macro, it is necessary to reconfigure, rebuild, and reinstall SANE for the change to take effect.

Aliases are defined in the config file dll.aliases. It can contain entries of the form

alias SomeName SaneDeviceName

alias "Some Name" SaneDeviceName

hide SaneDeviceName

For example:

alias Epson net:somehost:epson:/dev/sgX

alias "Siemens ST400" st400:/dev/sgY

hide net:somehost:pnm:0

hide net:somehost:pnm:1

alias "Read from file" pnm:0

hide pnm:1

Aliased device names are automatically hidden.

The idea is that users don't have to deal with complicated device names (especially for networked devices), and to hide other exported devices which might confuse them. Note that a hidden device can still be accessed if the device name is known, it just doesn't appear on the list.

## FILES
/etc/sane.d/dll.aliases

The list of aliased or hidden backends.

/etc/sane.d/dll.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-dll.a

The static library implementing this backend.

/usr/lib64/sane/libsane-dll.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_DLL

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

```
Value  Description
0      print severe errors only
1      print normal errors and important messages
2      print normal messages
3      print debugging messages
4      print everything
```

Example: export SANE_DEBUG_DLL=3

## SEE ALSO
sane(7), scanimage(1), sane-"backendname"(5)

## AUTHOR
David Mosberger


sane-dmc

title: sane-dmc(5)

text:
# sane-dmc(5)

## NAME
sane-dmc - SANE backend for the Polaroid Digital Microscope Camera

## DESCRIPTION
The sane-dmc library implements a SANE (Scanner Access Now Easy) backend that provides access to the Polaroid Digital Microscope Camera.

## DEVICE NAMES
This backend expects device names of the form:

special

Where special is the UNIX path-name for the special device that corresponds to the scanner. The special device name must be a generic SCSI device or a symlink to such a device. Under Linux, such a device name could be /dev/sga or /dev/sge, for example.

## IMAGING MODES
The Polaroid DMC supports a number of imaging modes. This driver supports five of the imaging modes:

Full Frame

This mode corresponds to the 801-by-600 pixel full-color full-frame image.

Viewfinder

This mode corresponds to the 270-by-201 pixel grey-scale viewfinder image. This image is acquired very quickly.

Raw

This mode corresponds to the 1599-by-600 pixel "raw" image from the CCD. It is grey-scale, with pixels alternating horizontally between red, green and blue stripes. The pixels are twice as high as they are wide, so the image is distorted.

Thumbnail

This mode corresponds to the 80-by-60 pixel full-color thumbnail image.

Super Resolution

This image is a 1599-by-1200 pixel full-color image constructed by filtering and interpolating the "raw" image. The filtering and interpolation is done in software, so this mode is very slow. Also, this mode places restrictions on how the image is read which means that the "preview" mode of xscanimage(1) does not work in Super Resolution mode. (xcam(1) and the non-preview modes of scanimage(1) and xscanimage(1) work fine, however.)

## OTHER SETTINGS
ASA Setting

This setting adjusts the camera's sensitivity. You can choose one of 25, 50, or 100 "equivalent" ASA.

Shutter Speed

You can select a shutter speed from 8 to 1000 milliseconds. The shutter speed is quantized in units of 32 microseconds.

White Balance

You can choose one of "Daylight", "Incandescent" or "Fluorescent" white balances. This setting more-or-less corresponds to the "Color Temperature" settings on Polaroid's Windows and Mac software.

## CONFIGURATION
The contents of the dmc.conf file is a list of device names that correspond to DMC scanners. Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:

/dev/scanner

\# this is a comment

/dev/sge

## FILES
/etc/sane.d/dmc.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-dmc.a

The static library implementing this backend.

/usr/lib64/sane/libsane-dmc.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_DMC

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

## BUGS
In the "Full Frame" and "Raw" modes, images must be read in units of entire lines. The driver performs no buffering in these modes; if you ask sane_read to read a non-integral number of lines, it may read less than you ask for. If you ask sane_read to read less than a single line, it returns SANE_STATUS_INVAL.

In the "Super Resolution" mode, images must be read in units of two lines (3198 pixels or 9594 bytes). If you try to read less than two lines, you get SANE_STATUS_INVAL. The Super Resolution mode is very slow.

In the "Viewfinder" and "Thumbnail" modes, the entire image must be read in one SCSI transfer. In this case, the driver performs buffering and you can read the image in as small an increment as you like.

## SEE ALSO
sane(7), sane-scsi(5)

## AUTHOR
Dianne Skoll <dianne@skoll.ca>

The backend is derived from sane-hp(5) by David Mosberger.


sane-epjitsu

title: sane-epjitsu(5)

text:
# sane-epjitsu(5)

## NAME
sane-epjitsu - SANE backend for Epson-based Fujitsu USB scanners

## DESCRIPTION
The sane-epjitsu library implements a SANE (Scanner Access Now Easy) backend which provides basic access the Fujitsu fi-60F/fi-65F and ScanSnap S300/S1300(i)/S1100(i) scanners.

## HARDWARE SUPPORT
These scanners are fairly limited, only supporting a couple of modes and resolutions, and always scanning full width. The backend supports missing modes (binary, grayscale) and intermediate resolutions in software, but provides only minimal scan area controls. See KNOWN ISSUES.

This backend may support other scanners. If physical inspection reveals an Epson chipset, please contact the author for instructions on collecting a USB trace under Windows to verify.

## OPTIONS
A limited effort has been made to expose the standard options to the API. This allows a frontend to set resolution, color mode, and choose the ADF setting. The sane-epjitsu backend supports the following basic options for most scanners:

source s

Selects the source for the scan. Options may include "Flatbed", "ADF Front", "ADF Back", "ADF Duplex".

mode m

Selects the mode for the scan. Options may include "Lineart", "Gray", "Color".

resolution, y-resolution

Controls scan resolution. Setting --resolution also sets --y-resolution, though this behavior is overridden by some frontends.

Other options will be available based on the capabilities of the scanner. Use 'scanimage --help' to get a list. Be aware that some options may appear only when another option has been set, and that advanced options may be hidden by the frontend.

## CONFIGURATION FILE
The configuration file /etc/sane.d/epjitsu.conf is used to tell the backend how to look for scanners, and provide options controlling the operation of the backend. This file is read each time the frontend asks the backend for a list of scanners, generally only when the frontend starts. If the configuration file is missing, the backend will not work.

Scanners can be specified in the configuration file in two ways:

"usb 0x04c5 0x10c7" (or other vendor/product ids)

Requests backend to search all usb buses in the system for a device which uses that vendor and product id. The device will then be queried to determine if it is a supported scanner.

"usb /dev/usb/scanner0" (or other device file)

Some systems use a kernel driver to access usb scanners. This method is untested.

The only configuration option supported is "firmware /PATH/TO/FILE", allowing you to set the location of the firmware file you have extracted from the Windows driver.

Note: This firmware is a copyrighted work of Fujitsu, so cannot be provided by the backend or the author. Please do not ask.

Note: These scanners REQUIRE a firmware file to function. See the supplied configuration file for more detail.

Note: This option may appear multiple times in the configuration file. It only applies to scanners discovered by 'usb' lines that follow this option.

## ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_EPJITSU, which enables debugging output to stderr. Valid values are:

5 Errors

10 Function trace

15 Function detail

20 Option commands

25 USB trace

30 USB detail

35 Useless noise

## KNOWN ISSUES
Only limited scan area options are exposed.

fi-60F and fi-65F hardware grayscale mode is not used, because the calibration code is not finished.

## CREDITS
S300 support funded by Microdea, Inc. and Archivista, GmbH.

fi-60F support funded by TrueCheck, Inc.

Improved calibration code provided by Richard Goedeken.

## SEE ALSO
sane(7), sane-usb(5) scanimage(1)

## AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>


sane-epson

title: sane-epson(5)

summary: SANE backend for EPSON scanners

text:
# sane-epson(5)

## NAME
sane-epson - SANE backend for EPSON scanners

## DESCRIPTION
The sane-epson library implements a SANE (Scanner Access Now Easy) backend that provides access to Epson flatbed scanners. Some functions of this backend should be considered beta-quality software! Most functions have been stable for a long time, but of course new development can not and often will not function properly from the very first day. Please report any strange behavior to the maintainer of the backend.

At present, the following scanners are known to work with this backend:

```
Model:                       Connection Type
---------------------------  -------------------
GT-5000                      SCSI, parallel
GT-6000                      parallel
GT-6500                      SCSI (use only the line "scsi" in epson.conf)
ActionScanner II             SCSI, parallel
GT-7000                      SCSI
Perfection 636               SCSI
Perfection 636U              USB
Perfection 610               USB
Perfection 640               USB
Perfection 1200S             SCSI
Perfection 1200U             USB
Perfection 1240              USB, SCSI
Perfection 1640              USB, SCSI
Perfection 1650              USB
Perfection 1660              USB
Perfection 2400              USB
Perfection 2450              USB, IEEE-1394
Expression 636 / GT-9500     SCSI
Expression 1600              USB, SCSI, IEEE-1394
Expression 1680              USB, SCSI, IEEE-1394
CX-3200                      USB
CX-5200                      USB
```

and many more. The official list is on the Sane web site.

For other scanners the software may or may not work. Please send mail to the backend author (khk@khk.net) to report success with scanners not on the list or problems with scanners that are listed.

## OPTIONS
The options the backend supports can either be selected through command line options to programs like scanimage(1) or through GUI elements in programs like xscanimage(1) or xsane(1).

Valid command line options and their syntax can be listed by using:

scanimage --help -d epson

Not all devices support all options.

Scan Mode

The --mode switch selects the basic mode of operation of the scanner. Valid choices are Binary, Gray and Color. The Binary mode is black and white only, Gray will produce 256 levels of gray or more depending on the scanner and Color means 24 bit color mode or more depending on the scanner. Some scanners will internally use 36 bit color, their external interface however may only support 24 bits. The --depth option selects the bit depth the scanner is using. This option is only available for scanners that support more than one bit depth. Older scanners will always transfer the image in 8bit mode. Newer scanners allow one to select either 8 bits, 12 or 14 bits per color channel. For a color scan this means an effective color depth of 36 or 42 bits over all three channels. The valid choices depend on the scanner model.

The --halftoning switch selects the mode that is used in Binary mode. Valid options are "None", "Halftone A (Hard Tone)", "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Download pattern A", and "Download pattern B".

The --dropout switch selects the so called dropout color. Valid options are None, Red, Green and Blue. The default is None. The dropout color is used for monochrome scanning and selects the color that is not scanned. This can be used to e.g. scan an original with a colored background.

The --brightness switch controls the brightness of the scan. Valid options are integer values from -3 to 3. The default is 0. The larger the brightness value, the brighter the image gets. If a user defined table for the gamma correction is selected, the brightness parameter is not available.

The --sharpness switch sets the sharpness of the image data. Valid options are integer values from -2 to 2, with -2 meaning "Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen slightly" and 2 "Sharpen".

The --gamma-correction switch controls the scanner's internal gamma correction. Valid options are "Default", "User defined", "High density printing" "Low density printing" and "High contrast printing".

The --color-correction switch controls the scanner's internal color correction function. Valid options are "No Correction", "Impact-dot printers", "Thermal printers", "Ink-jet printers" and "CRT monitors". The default is "CRT monitors".

The --resolution switch selects the resolution for a scan. Some EPSON scanners will scan in any resolution between the lowest and highest possible value. The list reported by the scanner can be displayed using the "--help -d epson" parameters to scanimage(1).

The --mirror option controls the way the image is scanned. By reading the image data from right to left the image is mirrored. Valid options are "yes" and "no". The default is "no".

The --speed option can improve the scan speed in monochrome mode. Valid options are "yes" or "no", the "yes" option will speed up the scan if this option is supported.

The --auto-area-segmentation switch activates the automatic area segmentation for monochrome scans. The scanner will try to determine which areas are text and which contain images. The image areas will be halftoned, and the text will be improved. Valid options are "yes" and "no". The default is "yes".

The --gamma-table parameter can be used to download a user defined gamma table. The option takes 256 values from the range 0-255. In color mode this option equally affects the red, green, and blue channel.

The --red-gamma-table parameter can be used to download a user defined gamma table for the red channel. The valid options are the same as for --gamma-table.

The --green-gamma-table parameter can be used to download a user defined gamma table for the green channel. The valid options are the same as for --gamma-table.

The --blue-gamma-table parameter can be used to download a user defined gamma table for the blue channel. The valid options are the same as for --gamma-table.

The color correction coefficients --cct-1 --cct-2 --cct-3 ... --cct-9 will install color correction coefficients for the user defined color correction. Values are specified as integers in the range -127..127.

The --preview option requests a preview scan. The frontend software automatically selects a low resolution. Valid options are "yes" and "no". The default is "no".

The --preview-speed options will increase the scan speed if this is supported by the scanner. Valid options are "yes" and "no", the default is "no".

The geometry options -l -t -x -y control the scan area: -l sets the top left x coordinate, -t the top left y coordinate, -x selects the width and -y the height of the scan area. All parameters are specified in millimeters.

The --quick-format option lets the user select a scan area with predefined sizes. Valid parameters are "CD", "A5 portrait", "A5 landscape", "Letter", "A4" and "max". The default is "max", which selects the largest possible area.

The --source option selects the scan source. Valid options depend on the installed options. The default is "Flatbed".

The --auto-eject option will eject a page after scanning from the document feeder.

The --film-type option will select the film type for scans with the transparency unit. This option is only activated if the TPU is selected as scan source. Valid options are "Negative Film" and "Positive Film".

The --focus-position option selects the focus position for all scans. Valid options are "Focus 2.5mm above glass" and "Focus on glass". The focus on the 2.5mm point above the glass is necessary for scans with the transparency unit, so that the scanner can focus on the film if one of the film holders is used. This option is only functional for selected scanners, all other scanners will ignore this option.

## CONFIGURATION FILE
The configuration file /etc/sane.d/epson.conf specifies the device(s) that the backend will use. Possible connection types are:

SCSI

This is the default, and if nothing else is specified the backend software will open a given path as SCSI device. More information about valid syntax for SCSI devices can be found in sane-scsi(5).

Usually SCSI scanners are configured with a line "scsi EPSON" in this file. In some cases it may be necessary to only use the string "scsi" (e.g. for the GT-6500).

PIO - Parallel Interface

The parallel interface can be configured in two ways: An integer value starting at the beginning of a line will be interpreted as the IO address of the parallel port. To make it clearer that a configured IO address is a parallel port the port address can be preceded by the string "PIO". The PIO connection does not use a special device file in the /dev directory. The IO address can be specified in hex mode (prefixed with "0x").

USB

A device file that is preceded by the string "USB" is treated as a scanner connected via the Universal Serial Bus. The correct special device file has to be created prior to using it with Sane. See the USB documentation for more information about how to set up the USB subsystem and the required device files.

## FILES
/usr/lib64/sane/libsane-epson.a

The static library implementing this backend.

/usr/lib64/sane/libsane-epson.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_DEBUG_EPSON

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

SANE_DEBUG_EPSON_SCSI

If the library was compiled with debug support enabled, this environment variable controls the SCSI related debug level for this backend. Only a value of 2 is supported.

SANE_EPSON_CMD_LVL

This allows one to override the function or command level that the backend uses to communicate with the scanner. The function level a scanner supports is determined during the initialization of the device. If the backend does not recognize the function level reported by the scanner it will default to function level B3. Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6, B7, B8, D1 and F5. Use this feature only if you know what you are doing!

## SEE ALSO
sane-scsi(5), scanimage(1), xscanimage(1), xsane(1)

## BUGS
None :-) At least none are currently known.

## UNSUPPORTED DEVICES
The backend may be used with Epson scanners that are not yet listed under the list of supported devices. A scanner that is not recognized may default to the function level B3, which means that not all functions that the scanner may be capable of are accessible.

If the scanner is not even recognized as an Epson scanner this is probably because the device name reported by the scanner is not in the correct format. Please send this information to the backend maintainer (email address is in the AUTHOR section of this man page or in the AUTHORS file of the SANE distribution).

The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and Perfection 1260 are not supported by this backend.

## AUTHOR
The package is actively maintained by Karl Heinz Kremer (khk@khk.net). The software is based on work by Christian Bucher and Kazuhiro Sasayama.


title: sane-epson2(5)

summary: SANE backend for EPSON scanners

text:
# sane-epson2(5)

## NAME
sane-epson2 - SANE backend for EPSON scanners

## DESCRIPTION
The sane-epson2 library implements a SANE (Scanner Access Now Easy) backend that provides access to Epson flatbed scanners. This library supports a similar set of scanners as the sane-epson driver but was developed to support a wider range of connections to the scanner; include network access.

Because sane-epson and sane-epson2 drivers support many of the same devices, if one driver gives you problems you may try disabling it to try the other. This can be done by removing the driver name from the dll.conf or perhaps by commenting out the options in epson.conf or epson2.conf.

At present, the following scanners are known to work with this backend:

```
Model:                       Connection Type
---------------------------  -------------------
ActionScanner II             SCSI, parallel
AcuLaser CX11 Series         USB, Network
AcuLaser CX21 Series         USB, Network
CX-3200                      USB
CX-3600                      USB
CX-3650                      USB
CX-4050                      USB
CX-4600                      USB
CX-4800                      USB
CX-5000                      USB
CX-5200                      USB
CX-5400                      USB
CX-6300                      USB
CX-6400                      USB
CX-6500                      USB
CX-6600                      USB
DX-3800                      USB
DX-5000                      USB
DX-5050                      USB
DX-6000                      USB
DX-7400                      USB
ES-300C                      SCSI, parallel
ES-300GS                     SCSI
ES-600C                      parallel
ES-1200C                     parallel
Expression 636               SCSI
Expression 800               SCSI
Expression 1600              USB, SCSI, IEEE-1394
Expression 1680              USB, SCSI, IEEE-1394
FilmScan 200                 SCSI
GT-5000                      SCSI, parallel
GT-5500                      SCSI
GT-6000                      parallel
GT-6500                      parallel
GT-7000                      SCSI
GT-8000                      SCSI
GT-8500                      SCSI
Perfection 610               USB
Perfection 636S              SCSI
Perfection 636U              USB
Perfection 640               USB
Perfection 1200S             SCSI
Perfection 1200U             USB
Perfection 1240              USB, SCSI
Perfection 1640              USB, SCSI
Perfection 1650              USB
Perfection 1660              USB
Perfection 2400              USB
Perfection 2450              USB, IEEE-1394
Perfection 3200              USB
Perfection 4870              USB
Perfection 4990              USB
RX-425                       USB
RX-500                       USB
RX-600                       USB
RX-700                       USB
V700                         USB, IEEE-1394
V750                         USB, IEEE-1394
```

and many more. The official list is on the Sane web site.

For other scanners the software may or may not work. Please send mail to the sane-backend mailing list to report success with scanners not on the list or problems with scanners that are listed.

## OPTIONS
The options the backend supports can either be selected through command line options to programs like scanimage(1) or through GUI elements in programs like xscanimage(1) or xsane(1).

Valid command line options and their syntax can be listed by using

scanimage --help -d epson2

Not all devices support all options.

Scan Mode

The --mode switch selects the basic mode of operation of the scanner. Valid choices are Binary, Gray and Color. The Binary mode is black and white only, Gray will produce 256 levels of gray or more depending on the scanner and Color means 24 bit color mode or more depending on the scanner. Some scanners will internally use 36 bit color, their external interface however may only support 24 bits. The --depth option selects the bit depth the scanner is using. This option is only available for scanners that support more than one bit depth. Older scanners will always transfer the image in 8bit mode. Newer scanners allow one to select either 8 bits, 12 or 14 bits per color channel. For a color scan this means an effective color depth of 36 or 42 bits over all three channels. The valid choices depend on the scanner model.

The --halftoning switch selects the mode that is used in Binary mode. Valid options are "None", "Halftone A (Hard Tone)", "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Download pattern A", and "Download pattern B".

The --dropout switch selects the so called dropout color. Valid options are None, Red, Green and Blue. The default is None. The dropout color is used for monochrome scanning and selects the color that is not scanned. This can be used to e.g. scan an original with a colored background.

The --brightness switch controls the brightness of the scan. Valid options are integer values from -3 to 3. The default is 0. The larger the brightness value, the brighter the image gets. If a user defined table for the gamma correction is selected, the brightness parameter is not available.

The --sharpness switch sets the sharpness of the image data. Valid options are integer values from -2 to 2, with -2 meaning "Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen slightly" and 2 "Sharpen".

The --gamma-correction switch controls the scanner's internal gamma correction. Valid options are "Default", "User defined", "High density printing" "Low density printing" and "High contrast printing".

The --color-correction switch controls the scanner's internal color correction function. Valid options are "No Correction", "Impact-dot printers", "Thermal printers", "Ink-jet printers" and "CRT monitors". The default is "CRT monitors".

The --resolution switch selects the resolution for a scan. Some EPSON scanners will scan in any resolution between the lowest and highest possible value. The list reported by the scanner can be displayed using the "--help -d epson" parameters to scanimage(1).

The --threshold switch selects the minimum brightness to get a white point.

The --mirror option controls the way the image is scanned. By reading the image data from right to left the image is mirrored. Valid options are "yes" and "no". The default is "no".

The --auto-area-segmentation switch activates the automatic area segmentation for monochrome scans. The scanner will try to determine which areas are text and which contain images. The image areas will be halftoned, and the text will be improved. Valid options are "yes" and "no". The default is "yes".

The --red-gamma-table parameter can be used to download a user defined gamma table for the red channel. The valid options are the same as for --gamma-table.

The --green-gamma-table parameter can be used to download a user defined gamma table for the green channel. The valid options are the same as for --gamma-table.

The --blue-gamma-table parameter can be used to download a user defined gamma table for the blue channel. The valid options are the same as for --gamma-table.

The --wait-for-button parameter can be used to wait until the button on the scanner is pressed to actually start the scan process.

The color correction coefficients --cct-1 --cct-2 --cct-3 ... --cct-9 will install color correction coefficients for the user defined color correction. Values are specified as integers in the range -127..127.

The --preview option requests a preview scan. The frontend software automatically selects a low resolution. Valid options are "yes" and "no". The default is "no".

The geometry options -l -t -x -y control the scan area: -l sets the top left x coordinate, -t the top left y coordinate, -x selects the width and -y the height of the scan area. All parameters are specified in millimeters.

The --source option selects the scan source. Valid options depend on the installed options. The default is "Flatbed".

The --auto-eject option will eject a page after scanning from the document feeder.

The --film-type option will select the film type for scans with the transparency unit. This option is only activated if the TPU is selected as scan source. Valid options are "Negative Film" and "Positive Film".

The --focus-position option selects the focus position for all scans. Valid options are "Focus 2.5mm above glass" and "Focus on glass". The focus on the 2.5mm point above the glass is necessary for scans with the transparency unit, so that the scanner can focus on the film if one of the film holders is used. This option is only functional for selected scanners, all other scanners will ignore this option.

The --bay option selects which bay to scan.

The --eject option ejects the sheet in the ADF.

The --adf-mode option select the ADF mode (simplex/duplex).

## CONFIGURATION FILE
The configuration file /etc/sane.d/epson2.conf specifies the device(s) that the backend will use. Possible connection types are:

SCSI

This is the default, and if nothing else is specified the backend software will open a given path as SCSI device. More information about valid syntax for SCSI devices can be found in sane-scsi(5).

Usually SCSI scanners are configured with a line "scsi EPSON" in this file. In some cases it may be necessary to only use the string "scsi" (e.g. for the GT-6500).

PIO - Parallel Interface

The parallel interface can be configured in two ways: An integer value starting at the beginning of a line will be interpreted as the IO address of the parallel port. To make it clearer that a configured IO address is a parallel port the port address can be preceded by the string "PIO". The PIO connection does not use a special device file in the /dev directory. The IO address can be specified in hex mode (prefixed with "0x").

USB

For USB scanners not automatically detect, their VENDOR and PRODUCT ID can be specified manually in the config file. More information about valid syntax for USB devices can be found in sane-usb(5).

Network

Network scanners can be auto-discovered if autodiscovery is specified after net keyword. An IP address to connect to can also be used.

## FILES
/usr/lib64/sane/libsane-epson2.a

The static library implementing this backend.

/usr/lib64/sane/libsane-epson2.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_DEBUG_EPSON2

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

SANE_DEBUG_EPSON2_SCSI

If the library was compiled with debug support enabled, this environment variable controls the SCSI related debug level for this backend. Only a value of 2 is supported.

SANE_DEBUG_EPSON2_NET

If the library was compiled with debug support enabled, this environment variable controls the network related debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

SANE_EPSON2_CMD_LVL

This allows one to override the function or command level that the backend uses to communicate with the scanner. The function level a scanner supports is determined during the initialization of the device. If the backend does not recognize the function level reported by the scanner it will default to function level B3. Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6, B7, B8, D1 and F5. Use this feature only if you know what you are doing!

## SEE ALSO
sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)

## BUGS
None :-) At least none are currently known.

## UNSUPPORTED DEVICES
The backend may be used with Epson scanners that are not yet listed under the list of supported devices. A scanner that is not recognized may default to the function level B3, which means that not all functions that the scanner may be capable of are accessible.

If the scanner is not even recognized as an Epson scanner this is probably because the device name reported by the scanner is not in the correct format. Please send this information to the backend maintainer (email address is in the AUTHOR section of this man page or in the AUTHORS file of the SANE distribution).

## AUTHOR
The package is written by Alessandro Zummo and is based on previous work done by Karl Hienz Kremer in the epson package as well as based on work by Christian Bucher and Kazuhiro Sasayama.


sane-epsonds

title: sane-epsonds(5)

summary: SANE backend for EPSON ESC/I-2 scanners

text:
# sane-epsonds(5)

## NAME
sane-epsonds - SANE backend for EPSON ESC/I-2 scanners

## DESCRIPTION
The sane-epsonds library implements a SANE (Scanner Access Now Easy) backend that provides access to Epson ESC/I-2 scanners.

Valid command line options and their syntax can be listed by using

scanimage --help -d epsonds

Not all devices support all options.

Scan Mode

The --mode switch selects the basic mode of operation of the scanner. Valid choices are Lineart, Gray and Color. The Lineart mode is black and white only, Gray will produce 256 levels of gray or more depending on the scanner and Color means 24 bit color mode or more depending on the scanner. Some scanners will internally use 36 bit color, their external interface however may only support 24 bits. The --depth option selects the bit depth the scanner is using. This option is only available for scanners that support more than one bit depth. Older scanners will always transfer the image in 8bit mode. Newer scanners allow one to select either 8 bits, 12 or 14 bits per color channel. For a color scan this means an effective color depth of 36 or 42 bits over all three channels. The valid choices depend on the scanner model.

The --resolution switch selects the resolution for a scan. Some EPSON scanners will scan in any resolution between the lowest and highest possible value. The list reported by the scanner can be displayed using the "--help -d epson" parameters to scanimage(1).

The geometry options -l -t -x -y control the scan area: -l sets the top left x coordinate, -t the top left y coordinate, -x selects the width and -y the height of the scan area. All parameters are specified in millimeters.

The --source option selects the scan source. Valid options depend on the installed options. The default is "Flatbed".

The --eject option ejects the sheet in the ADF.

The --adf-mode option select the ADF mode (simplex/duplex).

## CONFIGURATION FILE
The configuration file /etc/sane.d/epsonds.conf specifies the device(s) that the backend will use. Possible connection types are:

USB

For not automatically detected USB scanners, their VENDOR and PRODUCT ID can be specified manually in the config file. More information about valid syntax for USB devices can be found in sane-usb(5).

Network (not yet supported)

Network scanners can be auto-discovered if autodiscovery is specified after net keyword. An IP address to connect to can also be used.

## FILES
/usr/lib64/sane/libsane-epsonds.a

The static library implementing this backend.

/usr/lib64/sane/libsane-epsonds.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_DEBUG_EPSONDS

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity. Values around 11-16 will usually be enough for a bug report.

## SEE ALSO
sane-usb(5), scanimage(1), xscanimage(1), xsane(1)

## AUTHOR
The backend is written by Alessandro Zummo.


sane-fujitsu

title: sane-fujitsu(5)

text:
# sane-fujitsu(5)

## NAME
sane-fujitsu - SANE backend for Fujitsu and Ricoh fi series scanners

## DESCRIPTION
The sane-fujitsu library implements a SANE (Scanner Access Now Easy) backend which provides access to most Fujitsu flatbed and ADF scanners, and the subsequent Ricoh models.

This document describes backend version 140.

## SUPPORTED HARDWARE
This version supports every known model which speaks the Fujitsu SCSI and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x series, the SCSI fi-series, and most of the USB fi-, ScanSnap, & iX series scanners are supported. Please see the list at http://www.sane-project.org/sane-supported-devices.html for details.

This backend may support other Fujitsu or newer Ricoh scanners. The best way to determine level of support is to test the scanner directly, or to collect a trace of the windows driver in action. Please contact the author for help or with test results.

## UNSUPPORTED HARDWARE
The following scanners are known NOT to work with this backend, either because they have an unsupported chipset, or an unsupported interface type. Some of these scanners may be supported by another backend.

```
--------------------------------------
SCSI:        SERIAL:      USB:
------------ ------------ ------------
ScanStation  M3093E/DE/EX fi-4110EOX/2
ScanPartner  M3096EX      fi-4010CU
SP-Jr        M3097E+/DE   S300/S300M
SP-10/10C    M3099A/EH/EX S1300/S1100
SP-15C/300C               fi-60F/65F
SP-600C/620C              fi-5015C

                          SP-2x/3x
```

## OPTIONS
Effort has been made to expose all hardware options, including:

source s

Selects the source for the scan. Options may include "Flatbed", "ADF Front", "ADF Back", "ADF Duplex", "Card Front", "Card Back", "Card Duplex".

mode m

Selects the mode for the scan. Options may include "Lineart", "Halftone", "Gray", and "Color".

resolution, y-resolution

Controls scan resolution. Setting --resolution also sets --y-resolution, though this behavior is overridden by some frontends.

tl-x, tl-y, br-x, br-y

Sets scan area upper left and lower right coordinates. These are renamed t, l, x, y by some frontends.

page-width, page-height

Sets paper size. Used by scanner to determine centering of scan coordinates when using the ADF (Automatic Document Feeder) and to detect double feed errors.

Other options will be available based on the capabilities of the scanner: machines with IPC or DTC will have additional enhancement options, those with CMP will have compression options, those with a printer will have a group of endorser options.

Additionally, several 'software' options are exposed by the backend. These are reimplementations of features provided natively by larger scanners, but running on the host computer. This enables smaller machines to have similar capabilities. Please note that these features are somewhat simplistic, and may not perform as well as the native implementations. Note also that these features all require that the driver cache the entire image in memory. This will almost certainly result in a reduction of scanning speed.

swcrop

Requests the driver to detect the extremities of the paper within the larger image, and crop the empty edges.

swdeskew

Requests the driver to detect the rotation of the paper within the larger image, and counter the rotation.

swdespeck X

Requests the driver to find and remove dots of X diameter or smaller from the image, and fill the space with the average surrounding color.

Use 'scanimage --help' to get a list, but be aware that some options may be settable only when another option has been set, and that advanced options may be hidden by some frontend programs.

## CONFIGURATION FILE
The configuration file fujitsu.conf is used to tell the backend how to look for scanners, and provide options controlling the operation of the backend. This file is read each time the frontend asks the backend for a list of scanners, generally only when the frontend starts. If the configuration file is missing, the backend will be unable to locate any scanners.

Scanners can be specified in the configuration file in 4 ways:

"scsi FUJITSU"

Requests backend to search all scsi buses in the system for a device which reports itself to be a scanner made by 'FUJITSU'.

"scsi /dev/sg0" (or other scsi device file)

Requests backend to open the named scsi device. Only useful if you have multiple compatible scanners connected to your system, and need to specify one. Probably should not be used with the other "scsi" line above.

"usb 0x04c5 0x1042" (or other vendor/product ids)

Requests backend to search all usb buses in the system for a device which uses that vendor and product id. The device will then be queried to determine if it is a supported scanner.

"usb /dev/usb/scanner0" (or other device file)

Some systems use a kernel driver to access usb scanners. This method is untested.

The only configuration option supported is "buffer-size=xxx", allowing you to set the number of bytes in the data buffer to something other than the compiled-in default, 65536 (64K). Some users report that their scanner will "hang" mid-page, or fail to transmit the image if the buffer is not large enough.

Note: This option may appear multiple times in the configuration file. It only applies to scanners discovered by 'scsi/usb' lines that follow this option.

Note: The backend does not place an upper bound on this value, as some users required it to be quite large. Values above the default are not recommended, and may crash your OS or lockup your scsi card driver. You have been warned.

## ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_FUJITSU, which enables debugging output to stderr. Valid values are:

5 Errors

10 Function trace

15 Function detail

20 Option commands

25 SCSI/USB trace

30 SCSI/USB writes

31 SCSI/USB reads

35 Useless noise

## KNOWN ISSUES
Flatbed units may fail to scan at maximum area, particularly at high resolution.

Any model that does not support VPD during inquiry will not function until an override is added to the backend.

CCITT Fax compression used by older scanners is not supported.

JPEG output is supported by the backend, but not by the SANE protocol, so is disabled in this release. It can be enabled if you rebuild from source.

Network interfaces are not supported on any scanner model.

## CREDITS
m3091 backend: Frederik Ramm <frederik a t remote d o t org>

m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>

(with credit to the unnamed author of the coolscan driver)

fujitsu backend, m3093, fi-4340C, ipc, cmp, long-time maintainer:

Oliver Schirrmeister <oschirr a t abm d o t de>

m3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc-chemnitz dot de>

fi-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>

fi-4120, fi-series color, backend re-write, jpeg, current maintainer:

m. allan noah: <kitno455 a t gmail d o t com>

JPEG output and low memory usage support funded by:

Archivista GmbH www.archivista.ch

Endorser support funded by:

O A S Oilfield Accounting Service Ltd

1500, 840 - 7th Avenue S.W.

Calgary, Alberta

T2P 3G2 Canada

1-403-263-2600 www.oas.ca

Automatic length detection support funded by:

Martin G. Miller mgmiller at optonline.net

Hardware donated, software image enhancement and fi-6/7xxx support funded by:

PFU America, Inc. fujitsuscanners.com

iX500 support funded by:

Prefix Computer Services www.prefixservice.com

## SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), sane-sp15c(5), sane-avision(5), sane-epjitsu(5)

## AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>


sane-genesys

title: sane-genesys(5)

text:
# sane-genesys(5)

## NAME
sane-genesys - SANE backend for GL646, GL841, GL843, GL847 and GL124 based USB flatbed scanners

## DESCRIPTION
The sane-genesys library implements a SANE (Scanner Access Now Easy) backend that provides access to USB flatbed scanners based on the Genesys GL646, GL841, GL843, GL847 and GL124 chips. At present, the following scanners are known to work with this backend:

Canon LiDE 35/40/50/60/100/110/120/200/210/220/700

Hewlett-Packard HP2300C/HP2400/HP3670/HP3690/G4010/G4050

Medion MD5345/MD6228/MD6274

Panasonic KV-SS080

Plustek OpticBook 3600

Pentax DSmobile 600

Syscan/Ambir DocketPORT 467/485/487/665/685

Visioneer OneTouch 7100/Strobe XP100 (rev3)/XP200/XP300/Roadwarrior

Xerox Travel Scanner 100, OneTouch 2400

This is stable software for supported models. But if you test new or untested scanners, keep your hand at the scanner's plug and unplug it, if the head bumps at the end of the scan area.

If you own a scanner other than the ones listed above that works with this backend, please let me know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner or syslog) to the sane-devel mailing list. Even if the scanner's name is only slightly different from the models mentioned above, please let me know.

If you own a scanner that isn't detected by the genesys backend but has a GL646, GL841, GL843, GL847 or GL124 chipset, you can try to add it to the backend.

## CALIBRATION
To give correct image quality, sheet fed scanners need to be calibrated using the calibration sheet sold with the scanner. To do calibration, you must insert this target in the feeder then start calibration either by passing the --calibrate option to scanimage(1) or by clicking on the available 'calibrate' button in the 'advanced options' in a graphical frontend. The result of the calibration is stored in a file in the home directory of the user doing it. If you plug the scanner in another machine or use it with another account, calibration will have to be redone, unless you use the --calibration-file option. If no home directory is defined, USERAPPPROFILE will be used, then TMPDIR or TMP. If none of these directories exist, the backend will try to write in the current working directory. Flatbed scanners also make use of the calibration file as a cache to avoid calibration before each scan. Calibration file name is the name of the scanner model if only one scanner is detected. In the case of several identical model, the file name will be the name of the logical USB device name. The expiration time manages the time a calibration is valid in cache. A value of -1 means forever, 0 means no cache.

## EXTRAS SCAN OPTIONS
--lamp-off-time number

The lamp will be turned off after the given time (in minutes). A value of 0 means that the lamp won't be turned off.

--threshold percent

0..100% (in steps of 1). Select minimum brightness to get a white point. Pixels with brightness below that value will be scanned as black.

--brightness value

-100..100 (in steps of 1). Set the brightness enhancement. 0 for no enhancement, negative values to decrease brightness, and positive values to increase it.

--contrast value

-100..100 (in steps of 1). Set the contrast enhancement. 0 for no enhancement, negative values to decrease contrast, and positive values to increase it.

--disable-interpolation yes|no

When using high resolutions where the horizontal resolution is smaller than vertical resolution, data is expanded by software to preserve picture geometry. This can be disabled by this option to get real scanned data.

--disable-dynamic-lineart yes|no

Disable use of a software adaptive algorithm to generate lineart and rely on hardware lineart.

--color-filter None|Red|Green|Blue

When using gray or lineart this option selects the used color. Using a color filter will give a monochrome scan. CIS based scanners can do true gray when no filter (None value) is selected.

--lamp-off-scan

The lamp will be turned off during the scan. Calibration is still done with lamp on.

--clear-calibration

Clear calibration cache data, triggering a new calibration for the device when the next scan will happen.

--calibration-file

Specify the calibration file name to use. At least the directory containing the file must exist, since it won't be created. This option is disabled if the backend is run as root. It maybe used in case of sheet-fed scanners to share a calibration file for several users.

--expiration-time

Specify the time (in minutes) a cached calibration is considered valid. If older than the given value, a new calibration is done. A value of -1 means no expiration and cached value are kept forever unless cleared by user with the calibration clear option. A value of 0 means cache is disabled.

Additionally, several 'software' options are exposed by the backend. These are reimplementations of features provided natively by larger scanners, but running on the host computer. This enables smaller machines to have similar capabilities. Please note that these features are somewhat simplistic, and may not perform as well as the native implementations. Note also that these features all require that the driver cache the entire image in memory. This will almost certainly result in a reduction of scanning speed.

--swcrop

Requests the driver to detect the extremities of the paper within the larger image, and crop the empty edges.

--swdeskew

Requests the driver to detect the rotation of the paper within the larger image, and counter the rotation.

--swdespeck --despeck X

Requests the driver to find and remove dots of X diameter or smaller from the image, and fill the space with the average surrounding color.

--swskip 0..100% (in steps of 1) [0]

Request driver to discard pages with low numbers of dark pixels.

--swderotate[=(yes|no)] [no]

Request driver to detect and correct 90 degree image rotation.

## SYSTEM ISSUES
This backend needs libusb-0.1.6 or later installed, and hasn't tested in other configuration than a linux kernel 2.6.9 or higher. However, it should work any system with libusb where the SANE package can be compiled. For setting permissions and general USB information look at sane-usb(5).

## CONFIGURATION
The contents of the genesys.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. The file can also contain option lines. Empty lines and lines starting with a hash mark (#) are ignored. The scanners are autodetected by usb vendor_id product_id statements which are already included into genesys.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner.

## FILES
/etc/sane.d/genesys.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-genesys.a

The static library implementing this backend.

/usr/lib64/sane/libsane-genesys.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_GENESYS

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. If the debug level is set to 1 or higher, some debug options become available that are normally hidden. Handle them with care. This will print messages related to core genesys functions.

SANE_DEBUG_GENESYS_IMAGE

If the library was compiled with debug support enabled, this environment variable enables logging of intermediate image data. To enable this mode, set the environmental variable to 1.

Example (full and highly verbose output for gl646):

export SANE_DEBUG_GENESYS=255

## CREDITS
Jack McGill for donating several sheetfed and flatbed scanners, which made possible to add support for them in the genesys backend:

Hewlett-Packard HP3670

Visioneer Strobe XP100 (rev3)/XP200/XP300/Roadwarrior

Canon LiDE 200

Pentax DSmobile 600

Syscan/Ambir DocketPORT 467/485/487/665/685

Xerox Travel Scanner 100, Onetouch 2400

cncsolutions sponsored and supported the work on the Panasonic KV-SS080.

Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE 700F.

Dany Qumsiyeh for donating a Canoscan LiDE 210 and a LiDE 220.

Luc Verhaegen for donating a Canoscan LiDE 120.

## SEE ALSO
sane(7), sane-usb(5)

## AUTHOR
Oliver Rauch

Henning Meier-Geinitz <henning@meier-geinitz.de>

Gerhard Jaeger <gerhard@gjaeger.de>

Stéphane Voltz <stef.dev@free.fr>

Philipp Schmid <philipp8288@web.de>

Pierre Willenbrock <pierre@pirsoft.dnsalias.org>

Alexey Osipov <simba@lerlan.ru> for HP2400 final support

## LIMITATIONS
Powersaving isn't implemented for gl646 based scanner. Dynamic (emulated from gray data and with dithering) isn't enabled for gl646 scanners. Hardware lineart is limited up to 600 dpi for gl847 based scanners, due to the way image sensors are built.

This backend will be much slower if not using libusb-1.0. So be sure that sane-backends is built with the --enable-libusb_1_0 option.

## BUGS
For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from sensor. It seems the windows driver does some digital processing to improve it, which is not implemented in the backend.


title: sane-gphoto2(5)

text:
# sane-gphoto2(5)

## NAME
sane-gphoto2 - SANE backend for gphoto2 supported cameras

## DESCRIPTION
The sane-gphoto2 library implements a SANE (Scanner Access Now Easy) backend that provides access to the digital cameras supported by gphoto2. This backend has only been tested with a handful of cameras so far. Patches to support other models are welcome.

Because of the limited testing of this backend, it is commented out in /etc/sane.d/dll.conf by default. Either the comment character must be removed or the backend must be called explicitly. E.g. scanimage -d gphoto2 or xscanimage gphoto2.

## DEVICE NAMES
The current version of the backend only allows one camera to be connected. The device name is always "0".

## CONFIGURATION
The contents of the gphoto2.conf specify the characteristics of the camera to be used. Resolutions (high resolution, low resolution, and thumbnail size) are required since they are needed by the sane frontends, but can't be obtained through the gphoto2 interface. Valid ports and cameras can be obtained by gphoto2 --list-cameras and gphoto2 --list-ports.

The dumpinquiry line causes some information about the camera to be printed.

Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:

The topfolder line specifies the "fixed" part of the file path. For example, on the Kodak DC-240, files are stored in the directory /DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will change and must be read from the camera. In this case, the line would read "topfolder=/DCIM"

Some cameras don't implement a file structure and store all pictures in the / directory. This is indicated by setting "subdirs=0" with "topfolder=/"

port=usb:

camera=Kodak DC240

\# this is a comment

high_resolution=1280x960

low_resolution=640x480

thumb_resolution=160x120

dumpinquiry

## FILES
/etc/sane.d/gphoto2.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-gphoto2.a

The static library implementing this backend.

/usr/lib64/sane/libsane-gphoto2.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_GPHOTO2

If the library was compiled with debugging support enabled, this environment variable controls the debug level for this backend. A value of 128 requests maximally copious debug output; smaller levels reduce verbosity.

GP_DEBUG

Set to 1, 2, or 3, to enable various levels of debugging within the gphoto2 libraries.

## SEE ALSO
sane(7), scanimage(1), xscanimage(1), libgphoto2(3)

## AUTHOR
Peter S. Fales

The manpage was largely copied from the sane-dc210(5) manpage.

## BUGS
Many, no doubt.

More general comments, suggestions, and inquiries about frontends or SANE should go to the SANE Developers mailing list (see http://www.sane-project.org/mailing-lists.html for details). You must be subscribed to the list, otherwise your mail won't be sent to the subscribers.


title: sane-gt68xx(5)

text:
# sane-gt68xx(5)

## NAME
sane-gt68xx - SANE backend for GT-68XX based USB flatbed scanners

## DESCRIPTION
The sane-gt68xx library implements a SANE (Scanner Access Now Easy) backend that provides access to USB flatbed scanners based on the Grandtech GT-6801 and GT-6816 chips. A list of supported scanners can be found on the gt68xx backend homepage: http://www.meier-geinitz.de/sane/gt68xx-backend/.

This is BETA software. Especially if you test new or untested scanners, keep your hand at the scanner's plug and unplug it, if the head bumps at the end of the scan area.

If you own a scanner other than the ones listed on the gt68xx homepage that works with this backend, please let me know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from sane-find-scanner(1) or syslog) to me. Even if the scanner's name is only slightly different from the models already listed as supported, please let me know.

If you own a scanner that isn't detected by the gt68xx backend but has a GT-6801 or GT-6816 chipset, you can try to add it to the backend. Have a look at the following web page: http://www.meier-geinitz.de/sane/gt68xx-backend/adding.html

## LIBUSB ISSUES
Please use libusb-0.1.8 or later. Without libusb or with older libusb versions all kinds of trouble can be expected. The scanner should be found by sane-find-scanner(1) without further actions. For setting permissions and general USB information, look at sane-usb(5).

## FIRMWARE FILE
You need a firmware file for your scanner. That's a small file containing software that will be uploaded to the scanner's memory. It's usually named *.usb, e.g. PS1fw.usb. It comes on the installation CD that was provided by the manufacturer, but it may be packaged together with the installation program in an .exe file. For Mustek scanners, the file can be downloaded from the gt68xx backend homepage. For other scanners, check the CD for .usb files. If you only find *.cab files, try cabextract(1) to unpack. If everything else fails, you must install the Windows driver and get the firmware from there (usually in the windows/system or system32 directories). Put that firmware file into /usr/share/sane/gt68xx/. Make sure that it's readable by everyone.

## CONFIGURATION
The contents of the gt68xx.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. The file can also contain option lines. Empty lines and lines starting with a hash mark (#) are ignored. The scanners are autodetected by usb vendor_id product_id statements which are already included into gt68xx.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner.

The override, firmware, vendor, model, and afe options must be placed after the usb line they refer to.

Option override is used to override the default model parameters. That's necessary for some scanners that use the same vendor/product ids but are different. For these scanners there are already commented out override lines in the configuration file. override mustek-scanexpress-1200-ub-plus is necessary for the Mustek Scanexpress 1200 UB Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB 19200. override artec-ultima-2000 is used for the Artec Ultima 2000, the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458, and the Trust Flat Scan USB 19200. override mustek-bearpaw-2400-cu is necessary for the Mustek BearPaw 2400 CU and the Fujitsu 1200CUS. The override option must be the first one after the usb line.

Option firmware selects the name and path of the firmware file. It's only necessary if the default (or override) doesn't work. The default firmware directory is /usr/share/sane/gt68xx/. You may need to create this directory. If you want to place the firmware files at a different path, use a firmware line.

The vendor and model options are not absolutely necessary but for convenience. Quite a lot of scanners from different manufacturers share the same vendor/product ids so you can set the "correct" name here.

The afe option allows one to set custom offset and gain values for the Analog FrontEnd of the scanner. This option can be either used to select the AFE values if automatic coarse calibration is disabled, or to make automatic coarse calibration faster. For the latter usage, enable debug level 3 (see below), scan an image and look for debug line string with "afe". Copy this line to gt68xx.conf. The option has six parameters: red offset, red gain, green offset, green gain, blue offset, and blue gain.

A sample configuration file is shown below:

usb 0x05d8 0x4002

override "mustek-scanexpress-1200-ub-plus"

firmware "/opt/gt68xx/SBfw.usb"

vendor "Trust"

model "Compact Scan USB 19200"

afe 0x20 0x02 0x22 0x03 0x1f 0x04

## FILES
/etc/sane.d/gt68xx.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-gt68xx.a

The static library implementing this backend.

/usr/lib64/sane/libsane-gt68xx.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_GT68XX

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. If the debug level is set to 1 or higher, some debug options become available that are normally hidden. Handle them with care. Example: export SANE_DEBUG_GT68XX=4

## SEE ALSO
sane(7), sane-usb(5), sane-artec_eplus48u(5) sane-plustek(5), sane-ma1509(5), sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5), cabextract(1)

/usr/share/doc/sane-backends/gt68xx/gt68xx.CHANGES

http://www.meier-geinitz.de/sane/gt68xx

## AUTHOR
Henning Meier-Geinitz <henning@meier-geinitz.de>

The original gt68xx driver was written by Sergey Vlasov, Andreas Nowack, and David Stevenson. Thanks for sending patches and answering questions to them and all the other contributors.

## BUGS
The first few lines of the image are garbage for the 2400 TA Plus.

Interpolation should be used instead of just copying data, when the X- and Y-resolution differ.

Support for buttons is missing.

More detailed bug information is available at the gt68xx backend homepage http://www.meier-geinitz.de/sane/gt68xx-backend/.

Please contact us if you find a bug or missing feature: <sane-devel@alioth-lists.debian.net>.

Please send a debug log if your scanner isn't detected correctly (see SANE_DEBUG_GT68XX above).


sane-hp

title: sane-hp(5)

summary: SANE backend for HP ScanJet scanners

text:
# sane-hp(5)

## NAME
sane-hp - SANE backend for HP ScanJet scanners

## DESCRIPTION
The sane-hp library implements a SANE (Scanner Access Now Easy) backend that provides access to HP ScanJet scanners which support SCL (Scanner Control Language by HP). The following scanners are known positively to work with this backend:

```
Model:         Product id:     Interface:
----------     -----------     ----------
ScanJet Plus   C9195A          HP Parallel Interface Card
ScanJet IIc    C1750A 3226     SCSI
ScanJet IIcx   C2500A 3332     SCSI
ScanJet IIp    C1790A          SCSI
ScanJet 3C     C2520A 3503     SCSI
ScanJet 3P     C2570A 3406     SCSI
ScanJet 4C     C2520A          SCSI
ScanJet 4P     C1130A 3540     SCSI
ScanJet 4100C  C6290A          USB
ScanJet 5P     C5110A          SCSI
ScanJet 5100C  C5190A          parallel port
ScanJet 5200C  C7190A 3846     parallel port/USB
ScanJet 6100C  C2520A 3644     SCSI
ScanJet 6200C  C6270A 3828     SCSI/USB
ScanJet 6250C  C6270A 3828     SCSI/USB
ScanJet 6300C  C7670A          SCSI/USB
ScanJet 6350C  C7670A          SCSI/USB
ScanJet 6390C  C7670A          SCSI/USB
PhotoSmart     C5100A R029,R030,R032    SCSI
```

Support for models 5100C/5200C connected to the parallel port requires the ppSCSI driver available at http://cyberelk.net/tim/parport/ppscsi.html and http://penguin-breeder.org/kernel/download/.

Support for models 5200C/62X0C/63X0C connected to USB requires libusb. See sane-usb(5) for more details.

The sane-hp backend no longer supports OfficeJet multi-function peripherals. For these devices use the external "hplip" packages available at: https://developers.hp.com/hp-linux-imaging-and-printing/. For information about the previous hpoj driver, see: http://hpoj.sourceforge.net/.

Because Hewlett-Packard does no longer produce scanners that support SCL (beside the OfficeJets), the above list of supported scanners is complete. Other HP scanners are not supported by the sane-hp backend, but might be supported by another one. See http://www.sane-project.org/. You can also watch the sane-devel mailing list at http://www.sane-project.org/mailing-lists.html.

More details about the hp backend can be found on its homepage http://web.archive.org/web/20070206115546/http://www.kirchgessner.net/sane.html.

## DEVICE NAMES
This backend expects device names of the form:

special

Where special is the UNIX path-name for the special device that corresponds to the scanner. For SCSI scanners the special device name must be a generic SCSI device or a symlink to such a device. Under Linux, such a device name could be /dev/sga or /dev/sg2, for example. If the special device name contains "usb", "uscanner" or "ugen", it is assumed that the scanner is connected by USB. For the HP ScanJet Plus the special device name must be the device that corresponds to the parallel interface card that was shipped with the scanner. That is /dev/hpscan. A special driver is required for this card. See ftp://rvs.ctrl-c.liu.se/pub/wingel/hpscan for details. If the link does not work, try ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.

## CONFIGURATION
The contents of the hp.conf file is a list of options and device names that correspond to HP ScanJet scanners. Empty lines and lines starting with a hash mark (#) are ignored. See sane-scsi(5) and sane-usb(5) on details of what constitutes a valid device name.

Options specified in front of the first line that contains a device name are defaults for all devices. Options specified below a line that contains a device name apply just to the most recently mentioned device.

Supported options are connect-scsi, connect-device, enable-image-buffering, and dumb-read.

Option connect-scsi specifies that the scanner is connected to the system by SCSI. Input/output is performed using SCSI-commands. This is the default. But if your SCSI device name contains "usb", "uscanner" or "ugen", option connect-scsi must be specified. Otherwise it is assumed that the scanner is connected by USB.

Option connect-device specifies that the scanner is connected to the system by a special device. Input/output is performed by read()/write()-operations on the device. This option must be used for HP ScanJet Plus or scanners connected to USB which are accessed through a named device (e.g. /dev/usb/scanner0). For device names that contain "usb", "uscanner" or "ugen", it is not necessary to specify option connect-device.

Option enable-image-buffering stores the scanned image in memory before passing it to the frontend. Could be used in case of forward/backward moving scanner lamp.

Option dumb-read can be used to work around problems with "Error during device I/O". These problems may occur with certain SCSI-to-USB converters or Buslogic SCSI cards. The option should not be used for SCSI devices which are working correctly. Otherwise startup of frontends and changing parameters might be slower.

A sample configuration file is shown below:

```
/dev/scanner
# this is a comment
/dev/hpscan
option connect-device
```

/dev/scanner is typically a symlink to the actual SCSI scanner device.

## FILES
/etc/sane.d/hp.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-hp.a

The static library implementing this backend.

/usr/lib64/sane/libsane-hp.so

The shared library implementing this backend (present on systems that support dynamic loading).

$HOME/.sane/calib-hp:<device>.dat

Calibration data for HP PhotoSmart PhotoScanner that is retrieved from the scanner after calibration. The data is uploaded to the scanner at start of the backend if it is in media mode 'print media' or if the media mode is changed to 'print media'.

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_HP

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.

SANE_HOME_HP

Only used for OS/2 and along with use of HP PhotoSmart PhotoScanner. Must be set to the directory where the directory .sane is located. Is used to save and read the calibration file.

SANE_HP_KEEPOPEN_SCSI

SANE_HP_KEEPOPEN_USB

SANE_HP_KEEPOPEN_DEVICE

For each type of connection (connect-scsi, connect-usb, connect-device) it can be specified if the connection to the device should be kept open ("1") or not ("0"). Usually the connections are closed after an operation is performed. Keeping connection open to SCSI-devices can result in errors during device IO when the scanner has not been used for some time. By default, USB-connections are kept open. Other connections are closed.

SANE_HP_RDREDO

Specifies number of retries for read operation before returning an EOF error. Only supported for non-SCSI devices. Default: 1 retry. Time between retries is 0.1 seconds.

## BUGS
HP PhotoSmart PhotoScanner

In media mode 'slide' and 'negative', scan resolutions are rounded to multiple of 300 dpi. The scanner does not scale the data correctly on other resolutions. Some newer models (firmware code R030 and later) do not support adjustment of contrast/intensity level and tone map. The backend will simulate this by software, but only for gray and 24 bit color.

Automatic Document Feeder (ADF)

For use of the ADF with xscanimage(1), first place paper in the ADF and then change option scan source to 'ADF'. Press 'change document' to load a sheet. Then press 'scan' to start a scan. Maybe it is sufficient to press 'scan' without 'change document' for repeated scans. The use of the preview window is not recommended when working with the ADF. Setting a window to scan from ADF is not supported with xscanimage(1). Try xsane(1).

Immediate actions

Some actions in xscanimage(1) (i.e. unload, select media, calibrate) have an immediate effect on the scanner without starting a scan. These options can not be used with scanimage(1).

## TODO
HP PhotoSmart PhotoScanner

PhotoScanners with firmware release R030 and up have no firmware support for contrast/brightness/gamma table. In the current backend this is simulated by software on 24 bits data. Simulation on 30 bits should give better results.

Data widths greater than 8 bits

Custom gamma table does not work.

Parallel scanner support

Beside the ScanJet Plus which came with its own parallel interface card, currently only the HP ScanJet 5100C/5200C are supported. These scanners are using an internal parallel-to-SCSI converter which is supported by the ppSCSI-driver (see above).

## SEE ALSO
sane(7), sane-scsi(5), sane-usb(5) scanimage(1), xscanimage(1), scanimage(1)

## AUTHOR
The sane-hp backend was written by Geoffrey T. Dairiki.

HP PhotoSmart PhotoScanner support by Peter Kirchgessner.


title: sane-hp3500(5)

text:
# sane-hp3500(5)

## NAME
sane-hp3500 - SANE backend for Hewlett-Packard ScanJet 3500 series scanners

## DESCRIPTION
The sane-hp3500 library implements a SANE (Scanner Access Now Easy) backend that provides access to the following Hewlett-Packard USB flatbed scanners:

ScanJet 3500C

ScanJet 3530C

ScanJet 3570C

If you own a scanner other than the ones listed above that works with this backend, please let us know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner (1) or syslog) to us. Even if the scanner's name is only slightly different from the models mentioned above, please let us know.

## CONFIGURATION
None required.

## FILES
/usr/lib64/sane/libsane-hp3500.a

The static library implementing this backend.

/usr/lib64/sane/libsane-hp3500.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_DEBUG_HP3500 If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output.

Example: export SANE_DEBUG_HP3500=4

## SEE ALSO
sane(7), sane-usb(5),

http://projects.troy.rollo.name/rt-scanners/

## AUTHOR
Troy Rollo <sane@troy.rollo.name>


title: sane-hp3900(5)

text:
# sane-hp3900(5)

## NAME
sane-hp3900 - SANE backend for RTS8822 chipset based scanners

## DESCRIPTION
The sane-hp3900 library implements a SANE (Scanner Access Now Easy) backend that provides access at least to the following USB flatbed scanners:

```
Model:                     Chipset:
------                     --------
HP ScanJet 3800            RTS8822BL-03A
HP ScanJet 3970            RTS8822L-01H
HP ScanJet 4070 Photosmart RTS8822L-01H
HP ScanJet 4370            RTS8822L-02A
HP ScanJet G2710           RTS8822BL-03A
HP ScanJet G3010           RTS8822L-02A
HP ScanJet G3110           RTS8822L-02A
UMAX Astra 4900/4950       RTS8822L-01H *
BenQ 5550                  RTS8823L-01E *
```

More details can be found on the sane-hp3900(5) backend homepage http://sourceforge.net/projects/hp3900-series/.

This is ALPHA software. Keep your hand at the scanner's plug and unplug it, if scanner does not start to scan. See also the BUGS section.

If you own a scanner other than the ones listed above that works with this backend, please let us know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if the scanner's name is only slightly different from the models mentioned above, please let us know.

## CONFIGURATION
The contents of the hp3900.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. The file can also contain the names of device files that correspond to an HP 39XX scanner. Empty lines and lines starting with a hash mark (#) are ignored. The scanners are autodetected by usb vendor_id product_id statements which are already included into hp3900.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner. If autodetection does not work, add the device name of your scanner to the configuration file,

## FILES
/etc/sane.d/hp3900.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-hp3900.a

The static library implementing this backend.

/usr/lib64/sane/libsane-hp3900.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_HP3900

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. Example: export SANE_DEBUG_HP3900=4

## SEE ALSO
sane(7), sane-usb(5), sane-find-scanner(1),

http://sourceforge.net/projects/hp3900-series/

http://jkdsoftware.dyndns.org/drupal/?q=es/books/151

## AUTHOR
Jonathan Bravo Lopez <jkdsoft@gmail.com>

## BUGS
Scanning is only tested with Linux/ix86/gcc. Be careful when testing on other operating systems and especially on big-endian platforms. The scanner may get wrong data.


title: sane-hp4200(5)

text:
# sane-hp4200(5)

## NAME
sane-hp4200 - SANE backend for Hewlett-Packard 4200 scanners

## DESCRIPTION
The sane-hp4200 library implements a SANE (Scanner Access Now Easy) backend that provides access to the following Hewlett-Packard USB flatbed scanners:

ScanJet 4200 C

ScanJet 4200 Cxi

ScanJet 4200 Cse

More details can be found on the hp4200 backend homepage http://hp4200-backend.sourceforge.net/.

This is BETA software. Keep your hand at the scanner's plug and unplug it, if the head bumps at the end of the scan area.

If you own a scanner other than the ones listed above that works with this backend, please let us know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if the scanner's name is only slightly different from the models mentioned above, please let us know.

## CONFIGURATION
The contents of the hp4200.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. The file can also contain the names of device files that correspond to an HP 4200 scanner. Empty lines and lines starting with a hash mark (#) are ignored. The scanners are autodetected by usb vendor_id product_id statements which are already included into hp4200.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner. If autodetection does not work, add the device name of your scanner to the configuration file, e.g. /dev/usb/scanner0.

## FILES
/etc/sane.d/hp4200.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-hp4200.a

The static library implementing this backend.

/usr/lib64/sane/libsane-hp4200.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_HP4200

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. Example: export SANE_DEBUG_HP4200=4

## SEE ALSO
sane(7), sane-usb(5), sane-find-scanner(1),

http://hp4200-backend.sourceforge.net/

## AUTHOR
Adrian Perez Jorge, Andrew John Lewis, Arnar Mar Hrafnkelsson, Frank Zago, Henning Meier-Geinitz. Current maintainer: Henning Meier-Geinitz <henning@meier-geinitz.de>.

## BUGS
Tested only with Linux.

Only 8 bit color mode works.

Scanning is slow due to backtracking.

Send bug reports to the sane-devel mailing list: sane-devel@alioth-lists.debian.net.


title: sane-hp5400(5)

text:
# sane-hp5400(5)

## NAME
sane-hp5400 - SANE backend for Hewlett-Packard 54XX scanners

## DESCRIPTION
The sane-hp5400 library implements a SANE (Scanner Access Now Easy) backend that provides access to the following Hewlett-Packard USB flatbed scanners:

ScanJet 5400C

ScanJet 5470C

ScanJet 5490C

More details can be found on the hp5400 backend homepage http://hp5400backend.sourceforge.net/.

This is ALPHA software. Keep your hand at the scanner's plug and unplug it, if the head bumps at the end of the scan area. See also the BUGS section.

If you own a scanner other than the ones listed above that works with this backend, please let us know this by sending the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if the scanner's name is only slightly different from the models mentioned above, please let us know.

## CONFIGURATION
The contents of the hp5400.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. The file can also contain the names of device files that correspond to an HP 54XX scanner. Empty lines and lines starting with a hash mark (#) are ignored. The scanners are autodetected by usb vendor_id product_id statements which are already included into hp5400.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner. If autodetection does not work, add the device name of your scanner to the configuration file, e.g. /dev/usb/scanner0.

## FILES
/etc/sane.d/hp5400.conf

The backend configuration file (see also description of SANE_CONFIG_DIR below).

/usr/lib64/sane/libsane-hp5400.a

The static library implementing this backend.

/usr/lib64/sane/libsane-hp5400.so

The shared library implementing this backend (present on systems that support dynamic loading).

## ENVIRONMENT
SANE_CONFIG_DIR

This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order).

SANE_DEBUG_HP5400

If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. Example: export SANE_DEBUG_HP5400=4

## SEE ALSO
sane(7), sane-usb(5), sane-find-scanner(1),

http://hp5400backend.sourceforge.net/

## AUTHOR
Martijn van Oosterhout <kleptog@svana.org>, Thomas Soumarmon <soumarmt@nerim.net>. Manpage by Henning Meier-Geinitz <henning@meier-geinitz.de>.

## BUGS
Scanning is only tested with Linux/ix86/gcc. Be careful when testing on other operating systems and especially on big-endian platforms. The scanner may get wrong data.