1sane-microtek2(5) SANE Scanner Access Now Easy sane-microtek2(5)
2
6 sane-microtek2 - SANE backend for Microtek scanners with SCSI-2 command
7 set
8
10 The sane-microtek2 library implements a SANE (Scanner Access Now Easy)
11 backend that provides access to Microtek scanners with a SCSI-2 command
12 set. This backend can be considered alpha to beta. Some scanner models
13 are reported to work well, others not. New development versions of this
14 backend can be obtained from http://karstenfestag.gmxhome.de
15 There exists a different backend for Microtek scanners with SCSI-1 com‐
17 mand set. Refer to sane-microtek(5) for details.
18 And there is work in progress for the ScanMaker 3600. See
20 http://sourceforge.net/projects/sm3600
21 At present, the following scanners are known positively to work with
23 this backend:
24 ┌──────────────────────────────────────────────────────────────────────┐
26 │Vendor Product id Remark │
27 ├──────────────────────────────────────────────────────────────────────┤
28 │Microtek E3+ Parport and SCSI │
29 │Microtek X6 SCSI │
30 │Microtek X6EL SCSI │
31 │Microtek X6USB USB │
32 │Microtek ScanMaker V300 Parport and SCSI │
33 │Microtek ScanMaker V310 Parport and SCSI │
34 │Microtek ScanMaker V600 Parport and SCSI │
35 │Microtek ScanMaker 330 SCSI │
36 │Microtek ScanMaker 630 SCSI │
37 │Microtek ScanMaker 636 SCSI │
38 │Microtek ScanMaker 9600XL SCSI; only flatbed mode? │
39 │Microtek Phantom 330CX Parport │
40 │Microtek SlimScan C3 Parport │
41 │Microtek SlimScan C6 USB │
42 │Microtek Phantom 636 SCSI │
43 │Microtek Phantom 636CX Parport │
44 │Microtek V6USL SCSI and USB │
45 │Microtek V6UPL USB; not stable │
46 │Microtek X12USL SCSI; only 8bit color, work in progress │
47 │Vobis HighScan SCSI (E3+ based models) │
48 │Scanport SQ300 Parport? │
49 │Scanport SQ4836 SCSI │
50 │Scanpaq SQ2030 Parport │
51 └──────────────────────────────────────────────────────────────────────┘
52 Additional information can be found at http://www.sane-project.org/.
53 If you own a Microtek scanner other than the ones listed above, it may
55 or may not work with SANE! Because equal scanners are sold under dif‐
56 ferent names in different countries your model may be equivalent to one
57 of the above.
58 The parport scanners work with the ppscsi + onscsi kernel modules. See
60 http://cyberelk.net/tim/parport/ppscsi.html and http://penguin-
61 breeder.org/kernel/download/.
62 The USB scanners work with the microtek kernel module. You may have to
65 add the vendor and model codes to microtek.c if they aren't yet listed
66 there.
67 Both parport and USB scanners need the generic SCSI support, so check
69 if you have loaded the scsi_mod and sg modules!
70 If you try your scanner for the first time keep an eye on it. If it
72 gets commands that it doesn't understand the scanhead may go beyond the
73 scan area. The scanner then makes strange noises. In this case immedi‐
74 ately switch off the scanner or disconnect its power cable to prevent
75 damages!
76 If your scanner is a different one than the models mentioned above and
78 it is working please tell the author about it. It would be nice if you
79 add a logfile to this information (creation of the logfile: see below).
80 If your scanner is not working properly you also should create a log‐
82 file and send it to the author. He will use the information to improve
83 the backend and possibly make your scanner work.
84 How to create the logfile?
86 - put the line
88 "option dump 2" into your microtek2.conf file or change the
89 existing "option dump" to "2"
90 - in a terminal (bash) type
92 "export SANE_DEBUG_MICROTEK2=30" and then
93 "scanimage -l0 -t0 -x100 -y20 2>scan.log >sout.pnm"
94 You get two files: scan.log contains the logfile and sout.pnm
95 the scanned image (if there was scanned something). Zip them
96 before sending.
97
100 This backend dynamically enables the options for the frontend, that are
101 supported by the scanner in dependence of the scanning-mode and other
102 options. Not supported options are disabled.
103 The following options are supported by the Microtek2-driver:
105 Color, grayscale, halftone and lineart scans.
107 Highlight, midtone, shadow, contrast, brightness, exposure time con‐
109 trol, gamma correction, threshold (dependent of the scan mode and the
110 scanner capabilities)
111 Transparency media adapter, automatic document feeder
113 Additional options can be enabled or disabled in the microtek2.conf
115 file. See the configuration section of this manpage.
116
119 This backend expects device names of the form:
120 special
122 Where special is the UNIX path-name for the special device that corre‐
124 sponds to the scanner. The special device name must be a generic SCSI
125 device or a symlink to such a device. Under Linux, such a device name
126 could be /dev/sga or /dev/sge for example.
127
129 The configuration file for this backend resides in
130 /etc/sane.d/microtek2.conf.
131 Its contents is a list of device names that correspond to Microtek
133 scanners with SCSI-2 interface. Empty lines and lines starting with a
134 hash mark (#) are ignored.
135 The configuration file may also contain options. Global options that
137 are valid for all devices are placed above the device names. Device-
138 specific options are placed under the device name. Note that, except
139 for option dump <n> and option strip-height <n>, the entry in the
140 microtek2.conf file only enables the corresponding option for being
141 showed in the frontend. There, in the frontend, you can switch the
142 options on and off. Currently the following options are supported:
143 option dump <n>
145 option strip-height <n>
146 option no-backtrack-option <on/off>
147 option lightlid-35 <on/off>
148 option toggle-lamp <on/off>
149 option lineart-autoadjust <on/off>
150 option backend-calibration <on/off>
151 option colorbalance-adjust <on/off>
152 option dump <n> enables printing of additional information about the
154 SCSI commands that are sent to the scanner to stderr. This option is
155 primarily useful for debugging purpose. This option has to be a global
156 option and is best placed at the top of the microtek2.conf file.
157 If n=1 the contents of the command blocks and the results for the
159 INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
160 If n=2 the contents of the command blocks for all other SCSI commands
162 are printed to stderr, too. If n=3 the contents of the gamma table is
163 printed, too. If n=4 all scan data is additionally printed to stderr.
164 The default is n=1.
166 option strip-height <n> , where <n> is a floating point number, limits
168 the amount of data that is read from the scanner with one read command.
169 The unit is inch and <n> defaults to 1.0, if this option is not set in
170 the configuration file. If less than <n> inch of data fit into the SCSI
171 buffer, then the smaller value is used and this option has no effect.
172 If your system has a big SCSI buffer and you want to make use of the
174 whole buffer, increase the value for <n>. For example, if <n> is set to
175 14.0, no restrictions apply for scanners with a letter, legal or A4
176 sized scan area.
177 The following options enable or disable additional frontend options. If
179 an option is set to <on> an appropriate option will appear in the fron‐
180 tend.
181 option no-backtrack-option <on/off> prevents the scanner head from mov‐
183 ing backwards between the read commands. This speeds up scanning. Try
184 it.
185 option lightlid-35 <on/off> If you use the LightLid-35 transparency
187 adapter you get an advanced option which switches off the flatbed lamp
188 during the scan.
189 option toggle-lamp <on/off> You get a button in the frontend where you
191 can switch on and off the flatbed lamp.
192 option lineart-autoadjust <on/off> You can tell the backend to try to
194 determine a good value for the lineart threshold.
195 option backend-calibration <on/off> Some scanners (e.g. Phantom 330CX
197 and 636CX) need to have calibrated the data by the backend. Try this
198 option if you see vertical stripes in your pictures.
199 option colorbalance-adjust <on/off> Some scanners (e.g. Phantom 330CX
201 and 636CX) need to have corrected the color balance. If this option is
202 enabled you get advanced options where you can balance the colors. And
203 you will have a button to use the values that the firmware of the scan‐
204 ner provides.
205 A sample configuration file is shown below:
207 option dump 1
209 option strip-height 1.0
210 /dev/scanner
211 option no-backtrack-option on
212 # this is a comment
213 /dev/sge
214 option lightlid-35 on
215 This backend also supports the new configuration file format which
217 makes it easier to detect scanners under Linux. If you have only one
218 scanner it would be best to use the following configuration file for
219 this backend:
220 option dump 1
222 option strip-height 14.0
223 option no-backtrack-option on
224 option backend-calibration on
225 option lightlid-35 on
226 option toggle-lamp on
227 option lineart-autoadjust on
228 option colorbalance-adjust off
229 scsi * * Scanner
230 In this case all SCSI-Scanners should be detected automatically because
232 of the
233 scsi * * Scanner
235 line.
237
240 /etc/sane.d/microtek2.conf
241 The backend configuration file.
242 /usr/lib*/sane/libsane-microtek2.a
244 The static library implementing this backend.
245 /usr/lib*/sane/libsane-microtek2.so
247 The shared library implementing this backend (present on systems
248 that support dynamic loading).
249
251 SANE_DEBUG_MICROTEK2
252 If the library was compiled with debug support enabled, this
253 environment variable controls the debug level for this backend.
254 E.g., a value of 255 requests all debug output to be printed.
255 Smaller levels reduce verbosity. To see error messages on stderr
256 set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev‐
257 els should be better revised).
258 E.g. just say:
259 export SANE_DEBUG_MICROTEK2=128
260
262 sane-scsi(5), sane(7)
263
265 Bernd Schroeder (not active anymore)
266 Karsten Festag karsten.festag@gmx.de
267sane-backends 1.0.18 28 Jan 2002 sane-microtek2(5)