1sane-mustek_usb(5)       SANE Scanner Access Now Easy       sane-mustek_usb(5)
2
3
4

NAME

6       sane-mustek_usb - SANE backend for Mustek USB flatbed scanners
7

DESCRIPTION

9       The sane-mustek_usb library implements a SANE (Scanner Access Now Easy)
10       backend that provides access to Mustek USB flatbed scanners  (including
11       a  clone  from Trust).  At present, the following scanners are known to
12       work more or less with this backend:
13
14              Mustek 600 CU
15              Mustek 1200 UB
16              Mustek 1200 CU
17              Mustek 1200 CU Plus
18              Trust Compact Scan USB 19200
19
20       More  details  can  be  found  on  the  Mustek  USB  backend   homepage
21       http://www.meier-geinitz.de/sane/mustek_usb-backend/.
22
23       The  Mustek BearPaw 1200 and 2400 scanners are supported by the plustek
24       backend. See sane-plustek(5) for details. The Mustek BearPaw  1200F  is
25       supported by the MA-1509 backend. See sane-ma1509(5) for details. Other
26       Mustek  USB  scanners  are  supported  by  the  gt68xx   backend,   see
27       sane-gt68xx(5).
28
29       This  backend  can only work with scanners that are already detected by
30       the operating system. See sane-usb(5) for details.
31
32       If you own a Mustek (or Trust) scanner other than the ones listed above
33       that  works  with  this backend, please let me know this by sending the
34       scanner's exact model name and the USB vendor and device ids (e.g. from
35       /proc/bus/usb/devices or syslog) to me.
36
37

DEVICE NAMES

39       This backend expects device names of the form:
40
41              special
42
43       Where special is a path-name for the special device that corresponds to
44       a USB scanner.  With Linux, such a device name could be  /dev/usb/scan‐
45       ner0 or /dev/usbscanner1, for example.
46
47       For FreeBSD use /dev/uscanner0.
48
49

CONFIGURATION

51       The  contents  of  the  mustek_usb.conf  file  is a list of options and
52       device names that correspond to Mustek USB scanners.  Empty  lines  and
53       lines  starting  with  a hash mark (#) are ignored. If a device name is
54       placed in mustek_usb.conf, it must be followed by a line containing the
55       keyword option and an option specifying the scanner type. The following
56       options can be used: 600cu, 1200cu, 1200cu_plus, 1200ub.  For the Trust
57       Compact Scan USB 19200 use `option 1200ub'.
58
59       Instead  of  using  the device name, the scanner can be autodetected by
60       usb vendor_id product_id statements which  are  already  included  into
61       mustek_usb.conf.   This  is  only supported with Linux 2.4.8 and higher
62       and all systems that support libsub. "vendor_id" and  "product_id"  are
63       hexadecimal  numbers that identify the scanner. If this doesn't work, a
64       device name and the option specifying the scanner type must  be  placed
65       in mustek_usb.conf as described above.
66
67       The  global  option  max_block_size  can be used to limit the amount of
68       data acquired in one turn from the USB system. It may be worth  trying,
69       if USB errors occur.
70
71       A sample configuration file is shown below:
72
73              # Comment
74              option max_block_size 1024
75              usb 0x055f 0x0001
76              /dev/usb/scanner0
77              option 600cu
78
79       The  first  line  is ignored. The second line sets the buffer size to a
80       maximum of 1024 bytes.  The third line tries to  autodetect  a  scanner
81       with  vendor  id  0x055f  and  product  id 0x0001 (Mustek 1200 CU). The
82       fourth line tells the backend to attach to  /dev/usb/scanner0  and  the
83       fifth line specifies that /dev/usb/scanner0 is a Mustek 600 CU.
84

FILES

86       /etc/sane.d/mustek_usb.conf
87              The   backend   configuration  file  (see  also  description  of
88              SANE_CONFIG_DIR below).
89
90       /usr/lib64/sane/libsane-mustek_usb.a
91              The static library implementing this backend.
92
93       /usr/lib64/sane/libsane-mustek_usb.so
94              The shared library implementing this backend (present on systems
95              that support dynamic loading).
96

ENVIRONMENT

98       SANE_CONFIG_DIR
99              This environment variable specifies the list of directories that
100              may contain the configuration file.  Under UNIX, the directories
101              are  separated  by a colon (`:'), under OS/2, they are separated
102              by a semi-colon (`;').  If this variable is not set, the config‐
103              uration  file is searched in two default directories: first, the
104              current working directory (".") and then in /etc/sane.d.  If the
105              value  of the environment variable ends with the directory sepa‐
106              rator character, then the default directories are searched after
107              the  explicitly  specified  directories.   For  example, setting
108              SANE_CONFIG_DIR to "/tmp/config:" would  result  in  directories
109              "tmp/config",  ".",  and  "/etc/sane.d"  being searched (in this
110              order).
111
112       SANE_DEBUG_MUSTEK_USB
113              If the library was compiled with  debug  support  enabled,  this
114              environment  variable controls the debug level for this backend.
115              Higher debug levels increase the verbosity of the output.
116
117              Value  Description
118              0      no output
119              1      print fatal errors
120              2      print important messages
121              3      print non-fatal errors and less important messages
122              4      print all but debugging messages
123              5      print high level debugging messages
124              6      print medium level debugging messages
125              7      print low level debugging messages
126
127              Example: export SANE_DEBUG_MUSTEK_USB=4
128
129

SEE ALSO

131       sane(7),  sane-usb(5),  sane-mustek(5),  sane-mustek_pp(5),  sane-plus‐
132       tek(5), sane-gt68xx(5), sane-ma1509(5)
133       /usr/share/doc/sane-backends/mustek_usb/mustek_usb.CHANGES,
134       /usr/share/doc/sane-backends/mustek_usb/mustek_usb.TODO
135       http://www.meier-geinitz.de/sane/mustek_usb-backend/
136
137

AUTHOR

139       Henning Meier-Geinitz <henning@meier-geinitz.de>
140       This  backend  is based on the Mustek 1200ub backend from Mustek, main‐
141       tained by Tom Wang.
142
143

BUGS

145       These devices have a hardware bug: Once data is written to  them,  they
146       can't  be  reset (toggle = DATA0). That means, any operation that tries
147       to reset the device will result in running into timeouts.
148
149       In earlier versions this backend failed when it was loaded  the  second
150       time  in some configurations. The only choice was to replug the scanner
151       in this case. The backend uses a workaround for that bug now  but  it's
152       only  tested on Linux. Reports for other operating systems are appreci‐
153       ated.
154
155
156       More detailed bug information is available at the Mustek backend  home‐
157       page http://www.meier-geinitz.de/sane/mustek_usb-backend/.
158
159
160
161                                  13 Jul 2008               sane-mustek_usb(5)
Impressum