Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sane-cardscan(5) [centos man page]

sane-cardscan(5)					   SANE Scanner Access Now Easy 					  sane-cardscan(5)

NAME
sane-cardscan - SANE backend for Corex CardScan usb scanners DESCRIPTION
The sane-cardscan library implements a SANE (Scanner Access Now Easy) backend which provides access to the Corex CardScan 800c & 600c small-format scanners. The backend supports only grayscale and color modes and media of (theoretically) infinite length. This backend may support other scanners. The best way to determine level of support is to get a trace of the windows driver in action, and send it to the author. OPTIONS
The cardscan backend supports the following options: mode m Selects the mode for the scan. Options are "Gray" and "Color". CONFIGURATION FILE
The configuration file "cardscan.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 use a set of compiled defaults, which are identical to the default configuration file shipped with SANE. Scanners can be specified in the configuration file in 2 ways: "usb 0x04c5 0x1042" (or other vendor/product ids) Requests backend to search all usb busses 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 cardscan scanner. "usb /dev/usb/scanner0" (or other device file) Some systems use a kernel driver to access usb scanners. This method is untested. Additionally, there are two configuration options that control the protocol used by the backend: "lines_per_block 16" (or other number from 1 to 32) Controls the number of lines of image data which will be aquired in each pass. Older scanners will require this number set lower, often 1. "has_cal_buffer 1" (1 or 0) Causes the backend to get calibration data from scanner during initialization. Older scanners do not support this request, and must be set to 0. ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_CARDSCAN, 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 detail 35 Useless noise KNOWN ISSUES
The scanner does not seem to have much control possible, so the backend cannot set x/y coordinate values, resolutions, etc. These things could be simulated in the backend, but there are plenty of command line tools. The backend also does not send all the commands that the windows driver does, so it may not function the same. The backend does not have the calibration or ejection options of the windows driver. CREDITS
The hardware to build this driver was provided to the author by: Jeff Kowalczyk <jtk a t yahoo d o t com> SEE ALSO
sane(7), sane-usb(5) AUTHOR
m. allan noah: <kitno455 a t gmail d o t com> 10 Feb 2010 sane-cardscan(5)

Check Out this Related Man Page

sane-mustek_usb2(5)					   SANE Scanner Access Now Easy 				       sane-mustek_usb2(5)

NAME
sane-mustek_usb2 - SANE backend for SQ113 based USB flatbed scanners DESCRIPTION
The sane-mustek_usb2 library implements a SANE (Scanner Access Now Easy) backend that provides access to USB flatbed scanners based on the Service & Quality SQ113 chipset. At the moment, only the Mustek BearPaw 2448 TA Pro is supported. It's planned to add support for other scanners that are based on the SQ113 and maybe SQ11 chip. For more details, see the mustek_usb2 backend homepage: http://www.meier-geinitz.de/sane/mustek_usb2-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 mustek_usb2 homepage that works with this backend, please let me know this by send- ing the scanner's exact model name and the USB vendor and device ids (e.g. from sane-find-scanner 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. 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 without further actions. For setting permissions and general USB information looks at sane-usb(5). FILES
/usr/lib64/sane/libsane-mustek_usb2.a The static library implementing this backend. /usr/lib64/sane/libsane-mustek_usb2.so The shared library implementing this backend (present on systems that support dynamic loading). ENVIRONMENT
SANE_DEBUG_MUSTEK_USB2 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_MUSTEK_USB2=4 SEE ALSO
sane(7), sane-usb(5), sane-plustek(5), sane-ma1509(5), sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5) /usr/share/doc/sane-backends-1.0.24/mustek_usb2/mustek_usb2.CHANGES http://www.meier-geinitz.de/sane/mustek_usb2-backend/ AUTHOR
The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from Mustek. Adjustments to SANE by Henning Meier-Geinitz. BUGS
Please contact me if you find a bug or missing feature: <henning@meier-geinitz.de>. Please send a debug log if your scanner isn't detected correctly (see SANE_DEBUG_MUSTEK_USB2 above). 13 Jul 2008 sane-mustek_usb2(5)
Man Page