sane-mustek_usbSection: SANE Scanner Access Now Easy (5)
Updated: 09 Jan 2003
Return to Main Contents
NAMEsane-mustek_usb - SANE backend for Mustek USB flatbed scanners
DESCRIPTIONThe sane-mustek_usb library implements a SANE (Scanner Access Now Easy) backend that provides access to Mustek USB flatbed scanners (including a clone from Trust). At present, the following scanners are known to work more or less with this backend:
More details can be found on the Mustek USB backend homepage http://www.meier-geinitz.de/sane/mustek_usb-backend/.
This backend can only work with scanners that are already detected by the operating system. See sane-usb(5) for details.
If you own a Mustek (or Trust) 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 or syslog) to me.
DEVICE NAMESThis backend expects device names of the form:
Where special is a path-name for the special device that corresponds to a USB scanner. With Linux, such a device name could be /dev/usb/scanner0 or /dev/usbscanner1, for example.
For FreeBSD use /dev/uscanner0.
CONFIGURATIONThe contents of the mustek_usb.conf file is a list of options and device names that correspond to Mustek USB scanners. Empty lines and lines starting with a hash mark (#) are ignored. If a device name is placed in mustek_usb.conf, it must be followed by a line containing the keyword option and an option specifying the scanner type. The following options can be used: 600cu, 1200cu, 1200cu_plus, 1200ub. For the Trust Compact Scan USB 19200 use `option 1200ub'.
Instead of using the device name, the scanner can be autodetected by usb vendor_id product_id statements which are already included into mustek_usb.conf. This is only supported with Linux 2.4.8 and higher and all systems that support libsub. "vendor_id" and "product_id" are hexadecimal numbers that identfy the scanner. If this doesn't work, a device name and the option specifying the scanner type must be placed in mustek_usb.conf as described above.
The global option max_block_size can be used to limit the amount of data acquired in one turn from the USB system. It may be worth trying, if USB errors occur.
A sample configuration file is shown below:
The first line is ignored. The second line sets the buffer size to a maximum of 1024 bytes. The third line tries to autodetect a scanner with vendor id 0x055f and product id 0x0001 (Mustek 1200 CU). The fourth line tells the backend to attach to /dev/usb/scanner0 and the fifth line specifies that /dev/usb/scanner0 is a Mustek 600 CU.
SEE ALSOsane(7), sane-usb(5), sane-mustek(5), sane-mustek_pp(5), sane-plustek(5), sane-gt68xx(5)
AUTHORHenning Meier-Geinitz <firstname.lastname@example.org>
This backend is based on the Mustek 1200ub backend from Mustek, maintained by Tom Wang.
BUGSThese devices have a hardware bug: Once data is written to them, they can't be resetted (toggle = DATA0). That means, any operation that tries to reset the device will result in running into timeouts.
That means that this backend will fail when it is loaded the second time in some configurations: E.g. using libusb, (Free|Open|Net)BSD or with Linux if you unload and reload the scanner module. The only choice is to replug the scanner in this case.
More detailed bug information is available at the Mustek backend homepage http://www.meier-geinitz.de/sane/mustek_usb-backend/.
This document was created by man2html, using the manual pages.
Time: 02:05:40 GMT, May 20, 2013