NAME<\/a> sane\u2212canon630u \u2212 SANE backend for the Canon 630u USB flatbed scanner<\/p>\n The sane\u2212canon630u<\/b> library implements a SANE (Scanner Access Now Easy) backend that provides access to the following Canon flatbed scanners:<\/p>\n CanoScan 630u Color scanning is supported at 75, 150, 300, and 600 dpi, and gamma and analog gain are adjustable.<\/p>\n TESTERS ARE WELCOME. Send your bug reports and comments to Nathan Rutman The contents of the canon630u.conf<\/i> file is a list of device names that correspond to Canon USB scanners. Empty lines and lines starting with a hash mark (#) are ignored. Only one device name can be listed in canon630u.conf<\/i>. The program sane\u2212find\u2212scanner<\/b>(1) helps to find out the correct device. Under Linux, such a device name could be \/dev\/usb\/scanner0<\/i> for example. See sane\u2212usb<\/b>(5) for details.<\/p>\n This product-specific scanner driver uses the lower-level kernel USB driver “scanner”. Check for “Driver=usbscanner” under \/proc\/bus\/usb\/devices<\/i>. If “Driver=(none)”, try forcing it with insmod scanner vendor=0x04a9 product=0x2204<\/i><\/p>\n Due to Canon\u2019s unwillingness to provide scanner documentation, this software was developed by analyzing the USB traffic of the Windows 2000 driver. So things like the calibration procedure I kind of made up; it seems to work for my scanner. If you have complaints, let me know.<\/p>\n This driver requires the ability to send USB Control Messages, available in kernel 2.4.12 or later.<\/p>\n Some users have reported that this driver doesn\u2019t work at all. This seems to be a hardware specific issue, although I dsane\u2212uson\u2019t know what exactly the problem is. If you are having problems, please send me the info in \/proc\/bus\/usb\/devices<\/i>, \/proc\/pci<\/i>, the kernel scanner.c<\/i> driver version from \/var\/log\/messages<\/i>, and the output from SANE_DEBUG_CANON630U=12 scanimage > \/dev\/null<\/i><\/p>\n \/etc\/sane.d\/canon630u.conf<\/i><\/p>\n The backend configuration file (see also description of SANE_CONFIG_DIR<\/b> below).<\/p>\n \/usr\/lib64\/sane\/libsane\u2212canon630u.a<\/i><\/p>\n The static library implementing this backend.<\/p>\n \/usr\/lib64\/sane\/libsane\u2212canon630u.so<\/i><\/p>\n The shared library implementing this backend (present on systems that support dynamic loading).<\/p>\n \/tmp\/canon.cal<\/i><\/p>\n The calibration file used to normalize pixel brightness. This is calculated every time the scanner is first used after it has lost power. Deleting this file will force recalibration.<\/p>\n SANE_CONFIG_DIR<\/b><\/p>\n This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (\u2018:\u2019), under OS\/2, they are separated by a semi-colon (\u2018;\u2019). 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<\/i>. 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<\/b> to “\/tmp\/config:” would result in directories tmp\/config<\/i>, .<\/i>, and \/etc\/sane.d<\/i> being searched (in this order).<\/p>\n SANE_DEBUG_CANON630U<\/b><\/p>\n 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.<\/p>\n Example:
DESCRIPTION<\/a>
CONFIGURATION<\/a>
NOTES<\/a>
FILES<\/a>
ENVIRONMENT<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
CanoScan 636u<\/p>\nCONFIGURATION <\/a> <\/h2>\n
NOTES <\/a> <\/h2>\n
FILES <\/a> <\/h2>\n
ENVIRONMENT <\/a> <\/h2>\n
SANE_DEBUG_CANON630U=12 scanimage > \/dev\/null<\/p>\nSEE ALSO <\/a> <\/h2>\n