1sane-mustek(5) SANE Scanner Access Now Easy sane-mustek(5)
2
6 sane-mustek - SANE backend for Mustek SCSI flatbed scanners (and some
7 other devices)
8
10 The sane-mustek library implements a SANE (Scanner Access Now Easy)
11 backend that provides access to Mustek (and some relabeled Trust and
12 Primax) SCSI and parport flatbed scanners. At present, the following
13 scanners are known to work more or less with this backend:
14 Paragon MFS-6000CX
16 Paragon MFS-12000CX
17 Paragon MFC-600S, 600 II CD, ScanMagic 600 II SP
18 Paragon MFC-800S, 800 II SP
19 Paragon MFS-6000SP
20 Paragon MFS-8000SP
21 Paragon MFS-1200SP, MFS-12000SP
22 ScanExpress 6000SP
23 ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan‐
24 Magic 9636S, 9636S Plus
25 Paragon 1200 LS
26 ScanExpress A3 SP
27 Paragon 1200 SP Pro
28 Paragon 1200 A3 Pro
29 Paragon 600 II EP
30 Paragon 600 II N
31 Trust Imagery 1200
32 Trust Imagery 1200 SP
33 Trust Imagery 4800 SP
34 Trust SCSI Connect 19200
35 Primax Compact 4800 SCSI
36 More details can be found on the Mustek SCSI backend homepage
38 http://www.meier-geinitz.de/sane/mustek-backend/.
39 Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com‐
41 pletely different. Check the exact model name!
42 Note that most of the above scanners come with a SCSI interface. The
44 only non-SCSI scanners that have some support at this point is the 600
45 II N and 600 II EP scanners. The former one comes with its own parallel
46 port adapter (i.e., it does not attach to the printer port). Both scan‐
47 ners use the SCSI protocol internally, too. More info on how to use
48 these parallel port scanners can be found below in section PARALLEL
49 PORT SCANNERS. Other parallel port scanners are not supported by this
50 backend but you may be successful using the Mustek parallel port back‐
51 end mustek_pp, see sane-mustek_pp(5). USB scanners are also not sup‐
52 ported by this backend but the ma1509, mustek_usb, gt68xx, and plustek
53 backends include support for some of them, see sane-ma1509(5),
54 sane-mustek_usb(5), sane-gt68xx(5), and sane-plustek(5).
55 Mustek scanners have no protection against exceeding the physical scan
57 area height. That is, if a scan is attempted with a height that
58 exceeds the height of the scan surface, the scanner begins making loud
59 noises and the scan mechanism may be damaged. Thus, if you hear such a
60 noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
61 scanner is in the list of known scanners. There is more information in
62 the /usr/share/doc/sane-backends-1.0.22/PROBLEMS file.
63 If you own a Mustek (or Trust) scanner other than the ones listed above
65 that works with this backend, please let us know by sending the scan‐
66 ner's exact model name (look at the front and back of the scanner) and
67 a debug output to sane-devel@lists.alioth.debian.org. You can get the
68 debug output by setting the environment variable SANE_DEBUG_MUSTEK to 5
69 and showing the list of available scanners with scanimage -L. Please
70 send all of it to the mailing list. You must be subscribed to
71 sane-devel before you can send mail to the list. See
72 http://www.sane-project.org/mailing-lists.html for details.
73
76 This backend expects device names of the form:
77 special
79 Where special is either the path-name for the special device that cor‐
81 responds to a SCSI scanner or the port number at which the parallel
82 port scanners can be found (see section PARALLEL PORT SCANNERS below).
83 For SCSI scanners, the special device name must be a generic SCSI
84 device or a symlink to such a device. The program sane-find-scanner
85 helps to find out the correct device. Under Linux, such a device name
86 could be /dev/sg0 or /dev/sg3, for example. See sane-scsi(5) for
87 details.
88
90 The contents of the mustek.conf file is a list of options and device
91 names that correspond to Mustek scanners. Empty lines and lines start‐
92 ing with a hash mark (#) are ignored. See sane-scsi(5) on details of
93 what constitutes a valid device name.
94 The supported options are linedistance-fix, lineart-fix, legal-size,
96 buffersize, blocksize, strip-height, disable-double-buffering, dis‐
97 able-backtracking, and force-wait.
98 Options come in two flavors: global and positional ones. Global
100 options apply to all devices managed by the backend whereas positional
101 options apply just to the most recently mentioned device. Note that
102 this means that the order in which the options appear matters!
103 Option linedistance-fix is positional and works around a problem that
105 occurs with some SCSI controllers (notably the ncr810 controller under
106 Linux). If color scans have horizontal stripes and/or the colors are
107 off, then it's likely that your controller suffers from this problem.
108 Turning on this option usually fixes the problem.
109 Option lineart-fix is positional and works around a timing problem that
111 seems to exist with certain MFS-12000SP scanners. The problem mani‐
112 fests itself in dropped lines when scanning in lineart mode. Turning
113 on this option should fix the problem but may slow down scanning a bit.
114 Option legal-size is positional and sets the size of the scan area to
116 Legal format. Set this option if you own a Paragon 12000 LS. It can't
117 be distinguished by software from a ScanExpress 12000 SP (ISO A4 for‐
118 mat).
119 Option buffersize is a positional option that overrides the default
121 value set for the size of the SCSI buffer. The buffer size is specified
122 in kilobytes. The default value is 128. Because of double buffering the
123 buffer actually sent to the scanner is half the size of this value. Try
124 to increase this value to achieve higher scan speeds. Note that some
125 ScanExpress scanners don't like buffer sizes above 64 kb (buffersize =
126 128). If your sg driver can't set SCSI buffer sizes at runtime you may
127 have to change that value, too. See sane-scsi(5) for details.
128 Option blocksize is a positional option that overrides the default
130 value set for the maximum amount of data scanned in one block. The buf‐
131 fer size is specified in kilobytes. Some scanners freeze if this value
132 is bigger than 2048. The default value is 1 GB (so effectively no
133 limit) for most scanners. Don't change this value if you don't know
134 exactly what you do.
135 Option strip-height is a global option that limits the maximum height
137 of the strip scanned with a single SCSI read command. The height is
138 specified in inches and may contain a fractional part (e.g., 1.5).
139 Setting the strip-height to a small value (one inch, for example)
140 reduces the likelihood of encountering problems with SCSI driver time‐
141 outs and/or timeouts with other devices on the same SCSI bus. Unfortu‐
142 nately, it also increases scan times. With current SCSI adapters and
143 drivers this option shouldn't be needed any more.
144 Option disable-double-buffering is a global option. If set, the backend
146 will only send one buffer at a time to the scanner. Try this option if
147 you have trouble while scanning, e.g. SCSI errors, freezes, or the
148 first few cm are repeated over and over again in your image.
149 Option disable-backtracking is a positional option. If set, the scanner
151 will not move back its slider after each SCSI buffer is filled (`back‐
152 tracking'). Setting this option will lead to faster scans but may also
153 produce horizontal stripes. This option doesn't work with every scanner
154 (only some of the paragon models can modify backtracking).
155 Finally, force-wait is a global option. If set, the backend will wait
157 until the device is ready before sending the inquiry command. Further
158 more the backend will force the scan slider to return to its starting
159 position (not implemented for all scanners). This option may be neces‐
160 sary with the 600 II N or when scanimage is used multiple times (e.g.
161 in scripts). The default is off (not set).
162 A sample configuration file is shown below:
164 # limit strip height of all scanners to 1.5 inches:
166 option strip-height 1.5
167 /dev/scanner # first Mustek scanner
168 # 1 MB buffer for /dev/scanner:
169 option buffersize 1024
170 /dev/sge # second Mustek scanner
171 # turn on fixes for /dev/sge:
172 option lineart-fix
173 option linedistance-fix
174
177 You need a SCSI adapter for the SCSI scanners. Even if the connector is
178 the same as that of parallel port scanners, connecting it to the com‐
179 puters parallel port will NOT work.
180 Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
182 Unfortunately, that adapter is not worth much since it is not interrupt
183 driven. It is (sometimes) possible to get the supplied card to work,
184 but without interrupt line, scanning will be very slow and put so much
185 load on the system, that it becomes almost unusable for other tasks.
186 If you already have a working SCSI controller in your system, you
188 should consider that Mustek scanners do not support the SCSI-2 discon‐
189 nect/reconnect protocol and hence tie up the SCSI bus while a scan is
190 in progress. This means that no other SCSI device on the same bus can
191 be accessed while a scan is in progress.
192 Because the Mustek-supplied adapter is not worth much and because
194 Mustek scanners do not support the SCSI-2 disconnect/reconnect proto‐
195 col, it is recommended to install a separate (cheap) SCSI controller
196 for Mustek scanners. For example, ncr810 based cards are known to work
197 fine and cost as little as fifty US dollars.
198 For Mustek scanners, it is typically necessary to configure the low-
200 level SCSI driver to disable synchronous transfers (sync negotiation),
201 tagged command queuing, and target disconnects. See sane-scsi(5) for
202 driver- and platform-specific information.
203 The ScanExpress models have sometimes trouble with high resolution
205 color mode. If you encounter sporadic corrupted images (parts dupli‐
206 cated or shifted horizontally) kill all other applications before scan‐
207 ning and (if sufficient memory is available) disable swapping.
208 Details on how to get the Mustek SCSI adapters and other cards running
210 can be found at http://www.meier-geinitz.de/sane/mustek-backend/#SCSI.
211
214 This backend has support for the Paragon 600 II EP and Paragon 600 II N
215 parallel port scanners. Note that the latter scanner comes with its
216 own ISA card that implements a funky parallel port (in other words, the
217 scanner does not connected to the printer parallel port).
218 These scanners can be configured by listing the port number of the
220 adapter or the parallel port in the mustek.conf file. Valid port num‐
221 bers for the 600 II N are 0x26b, 0x2ab, 0x2eb, 0x22b, 0x32b, 0x36b,
222 0x3ab, 0x3eb. For the 600 II EP use one of these: parport0, parport1,
223 parport2, 0x378, 0x278, 0x3bc. Pick one that doesn't conflict with the
224 other hardware in your computer. Put only one number on a single line.
225 Example:
226 0x3eb
228 Note that for these scanners usually root privileges are required to
230 access the I/O ports. Thus, either make frontends such as scanimage(1)
231 and xscanimage(1) setuid root (generally not recommended for safety
232 reasons) or, alternatively, access this backend through the network
233 daemon saned(8).
234 If the Mustek backend blocks while sending the inquiry command to the
236 scanner, add the option force-wait to mustek.conf.
237 Also note that after a while of no activity, some scanners themselves
239 (not the SANE backend) turns off their CCFL lamps. This shutdown is not
240 always perfect with the result that the lamp sometimes continues to
241 glow dimly at one end. This doesn't appear to be dangerous since as
242 soon as you use the scanner again, the lamp turns back on to the normal
243 high brightness. However, the first image scanned after such a shutdown
244 may have stripes and appear to be over-exposed. When this happens,
245 just take another scan, and the image will be fine.
246
248 /etc/sane.d/mustek.conf
249 The backend configuration file (see also description of
250 SANE_CONFIG_DIR below).
251 /usr/lib64/sane/libsane-mustek.a
253 The static library implementing this backend.
254 /usr/lib64/sane/libsane-mustek.so
256 The shared library implementing this backend (present on systems
257 that support dynamic loading).
258
260 SANE_CONFIG_DIR
261 This environment variable specifies the list of directories that
262 may contain the configuration file. Under UNIX, the directories
263 are separated by a colon (`:'), under OS/2, they are separated
264 by a semi-colon (`;'). If this variable is not set, the config‐
265 uration file is searched in two default directories: first, the
266 current working directory (".") and then in /etc/sane.d. If the
267 value of the environment variable ends with the directory sepa‐
268 rator character, then the default directories are searched after
269 the explicitly specified directories. For example, setting
270 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
271 "tmp/config", ".", and "/etc/sane.d" being searched (in this
272 order).
273 SANE_DEBUG_MUSTEK
275 If the library was compiled with debug support enabled, this
276 environment variable controls the debug level for this backend.
277 Higher debug levels increase the verbosity of the output.
278 Value Description
280 0 no output
281 1 print fatal errors
282 2 print important messages
283 3 print non-fatal errors and less important messages
284 4 print all but debugging messages
285 5 print everything
286 Example: export SANE_DEBUG_MUSTEK=4
288
291 sane(7), sane-find-scanner(1), sane-scsi(5), sane-mustek_usb(5),
292 sane-gt68xx(5), sane-plustek(5), sane-mustek_pp(5)
293 /usr/share/doc/sane-backends-1.0.22/mustek/mustek.CHANGES
294 http://www.meier-geinitz.de/sane/mustek-backend/
295
298 David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
299 Henning Meier-Geinitz, James Perry (600 II EP).
300
303 Scanning with the SCSI adapters supplied by Mustek is very slow at high
304 resolutions and wide scan areas.
305 Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
307 The gamma table supports only 256 colors, even if some scanners can do
309 more.
310 More detailed bug information is available at the Mustek backend home‐
312 page: http://www.meier-geinitz.de/sane/mustek-backend/.
313 13 Jul 2008 sane-mustek(5)