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

NAME

6       sane-microtek2 - SANE backend for Microtek scanners with SCSI-2 command
7       set
8

DESCRIPTION

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
16       There exists a different backend for Microtek scanners with SCSI-1 com‐
17       mand set.  Refer to sane-microtek(5) for details.
18
19       And   there   is   work  in  progress  for  the  ScanMaker  3600.   See
20       http://sourceforge.net/projects/sm3600.
21
22       At present, the following scanners are known positively  to  work  with
23       this backend:
24
25       Vendor     Product id        Remark
26       --------------------------------------------------------------------
27       Microtek   E3+               Parport and SCSI
28       Microtek   X6                SCSI
29       Microtek   X6EL              SCSI
30       Microtek   X6USB             USB
31       Microtek   ScanMaker V300    Parport and SCSI
32       Microtek   ScanMaker V310    Parport and SCSI
33       Microtek   ScanMaker V600    Parport and SCSI
34       Microtek   ScanMaker 330     SCSI
35       Microtek   ScanMaker 630     SCSI
36       Microtek   ScanMaker 636     SCSI
37       Microtek   ScanMaker 9600XL  SCSI; only flatbed mode?
38       Microtek   Phantom 330CX     Parport
39       Microtek   SlimScan C3       Parport
40       Microtek   SlimScan C6       USB
41       Microtek   Phantom 636       SCSI
42       Microtek   Phantom 636CX     Parport
43       Microtek   V6USL             SCSI and USB
44       Microtek   V6UPL             USB; not stable
45       Microtek   X12USL            SCSI; only 8bit color, work in progress
46       Vobis      HighScan          SCSI (E3+ based models)
47       Scanport   SQ300             Parport?
48       Scanport   SQ4836            SCSI
49       Scanpaq    SQ2030            Parport
50
51       Additional information can be found at http://www.sane-project.org/.
52
53       If  you own a Microtek scanner other than the ones listed above, it may
54       or may not work with SANE! Because equal scanners are sold  under  dif‐
55       ferent names in different countries your model may be equivalent to one
56       of the above.
57
58       The parport scanners work with the ppscsi + onscsi kernel modules.  See
59       http://cyberelk.net/tim/parport/ppscsi.html     and     http://penguin-
60       breeder.org/kernel/download/.
61
62
63       The USB scanners work with the microtek kernel module. You may have  to
64       add  the vendor and model codes to microtek.c if they aren't yet listed
65       there.
66
67       Both parport and USB scanners need the generic SCSI support,  so  check
68       if you have loaded the scsi_mod and sg modules!
69
70       If  you  try  your  scanner for the first time keep an eye on it. If it
71       gets commands that it doesn't understand the scanhead may go beyond the
72       scan area.  The scanner then makes strange noises. In this case immedi‐
73       ately switch off the scanner or disconnect its power cable  to  prevent
74       damages!
75
76       If  your scanner is a different one than the models mentioned above and
77       it is working please tell the author about it. It would be nice if  you
78       add a logfile to this information (creation of the logfile: see below).
79
80       If  your  scanner is not working properly you also should create a log‐
81       file and send it to the author. He will use the information to  improve
82       the backend and possibly make your scanner work.
83
84       How to create the logfile?
85
86       - put the line
87              "option  dump  2"  into  your  microtek2.conf file or change the
88              existing "option dump" to "2"
89
90       - in a terminal (bash) type
91              "export SANE_DEBUG_MICROTEK2=30" and then
92              "scanimage -l0 -t0 -x100 -y20 2>scan.log >sout.pnm"
93              You get two files: scan.log contains the  logfile  and  sout.pnm
94              the  scanned  image  (if  there was scanned something). Zip them
95              before sending.
96
97

FRONTEND OPTIONS

99       This backend dynamically enables the options for the frontend, that are
100       supported  by  the scanner in dependence of the scanning-mode and other
101       options.  Not supported options are disabled.
102
103       The following options are supported by the sane-microtek2 driver:
104
105       Color, grayscale, halftone and lineart scans.
106
107       Highlight, midtone, shadow, contrast, brightness,  exposure  time  con‐
108       trol,  gamma  correction, threshold (dependent of the scan mode and the
109       scanner capabilities)
110
111       Transparency media adapter, automatic document feeder
112
113       Additional options can be enabled or  disabled  in  the  microtek2.conf
114       file. See the configuration section of this manpage.
115
116

DEVICE NAMES

118       This backend expects device names of the form:
119
120              special
121
122       Where  special is the UNIX path-name for the special device that corre‐
123       sponds to the scanner.  The special device name must be a generic  SCSI
124       device  or a symlink to such a device.  Under Linux, such a device name
125       could be /dev/sga or /dev/sge for example.
126

CONFIGURATION

128       The    configuration    file    for    this    backend    resides    in
129       /etc/sane.d/microtek2.conf.
130
131       Its  contents  is  a  list  of device names that correspond to Microtek
132       scanners with SCSI-2 interface. Empty lines and lines starting  with  a
133       hash mark (#) are ignored.
134
135       The  configuration  file  may also contain options. Global options that
136       are valid for all devices are placed above the  device  names.  Device-
137       specific  options  are  placed under the device name. Note that, except
138       for option dump <n> and option  strip-height  <n>,  the  entry  in  the
139       microtek2.conf  file  only  enables  the corresponding option for being
140       showed in the frontend. There, in the  frontend,  you  can  switch  the
141       options on and off.  Currently the following options are supported:
142
143              option dump <n>
144              option strip-height <n>
145              option no-backtrack-option <on/off>
146              option lightlid-35 <on/off>
147              option toggle-lamp <on/off>
148              option lineart-autoadjust <on/off>
149              option backend-calibration <on/off>
150              option colorbalance-adjust <on/off>
151
152       option  dump  <n>  enables printing of additional information about the
153       SCSI commands that are sent to the scanner to stderr.  This  option  is
154       primarily  useful for debugging purpose. This option has to be a global
155       option and is best placed at the top of the microtek2.conf file.
156
157       If n=1 the contents of the command  blocks  and  the  results  for  the
158       INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
159
160       If  n=2  the contents of the command blocks for all other SCSI commands
161       are printed to stderr, too. If n=3 the contents of the gamma  table  is
162       printed, too. If n=4 all scan data is additionally printed to stderr.
163
164       The default is n=1.
165
166       option  strip-height <n> , where <n> is a floating point number, limits
167       the amount of data that is read from the scanner with one read command.
168       The  unit is inch and <n> defaults to 1.0, if this option is not set in
169       the configuration file. If less than <n> inch of data fit into the SCSI
170       buffer, then the smaller value is used and this option has no effect.
171
172       If  your  system  has a big SCSI buffer and you want to make use of the
173       whole buffer, increase the value for <n>. For example, if <n> is set to
174       14.0,  no  restrictions  apply  for scanners with a letter, legal or A4
175       sized scan area.
176
177       The following options enable or disable additional frontend options. If
178       an option is set to <on> an appropriate option will appear in the fron‐
179       tend.
180
181       option no-backtrack-option <on/off> prevents the scanner head from mov‐
182       ing  backwards between the read commands.  This speeds up scanning. Try
183       it.
184
185       option lightlid-35 <on/off> If you  use  the  LightLid-35  transparency
186       adapter  you get an advanced option which switches off the flatbed lamp
187       during the scan.
188
189       option toggle-lamp <on/off> You get a button in the frontend where  you
190       can switch on and off the flatbed lamp.
191
192       option  lineart-autoadjust  <on/off> You can tell the backend to try to
193       determine a good value for the lineart threshold.
194
195       option backend-calibration <on/off> Some scanners (e.g.  Phantom  330CX
196       and  636CX)  need  to have calibrated the data by the backend. Try this
197       option if you see vertical stripes in your pictures.
198
199       option colorbalance-adjust <on/off> Some scanners (e.g.  Phantom  330CX
200       and  636CX) need to have corrected the color balance. If this option is
201       enabled you get advanced options where you can balance the colors.  And
202       you will have a button to use the values that the firmware of the scan‐
203       ner provides.
204
205       A sample configuration file is shown below:
206
207              option dump 1
208              option strip-height 1.0
209              /dev/scanner
210              option no-backtrack-option on
211              # this is a comment
212              /dev/sge
213              option lightlid-35 on
214
215       This backend also supports the  new  configuration  file  format  which
216       makes  it  easier  to detect scanners under Linux. If you have only one
217       scanner it would be best to use the following  configuration  file  for
218       this backend:
219
220              option dump 1
221              option strip-height 14.0
222              option no-backtrack-option on
223              option backend-calibration on
224              option lightlid-35 on
225              option toggle-lamp on
226              option lineart-autoadjust on
227              option colorbalance-adjust off
228              scsi * * Scanner
229
230       In this case all SCSI-Scanners should be detected automatically because
231       of the
232
233       scsi * * Scanner
234
235       line.
236
237

FILES

239       /etc/sane.d/microtek2.conf
240              The backend configuration file.
241
242       /usr/lib64/sane/libsane-microtek2.a
243              The static library implementing this backend.
244
245       /usr/lib64/sane/libsane-microtek2.so
246              The shared library implementing this backend (present on systems
247              that support dynamic loading).
248

ENVIRONMENT

250       SANE_DEBUG_MICROTEK2
251              If  the  library  was  compiled with debug support enabled, this
252              environment variable controls the debug level for this  backend.
253              E.g.,  a  value  of 255 requests all debug output to be printed.
254              Smaller levels reduce verbosity. To see error messages on stderr
255              set  SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev‐
256              els should be better revised).
257              E.g. just say:
258              export SANE_DEBUG_MICROTEK2=128
259
260

SEE ALSO

262       sane-scsi(5), sane(7)
263
264

AUTHORS

266       Bernd Schroeder (not active anymore)
267       Karsten Festag <karsten.festag@gmx.de>.
268
269
270
271                                  13 Jul 2008                sane-microtek2(5)
Impressum