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

NAME

6       sane-umax_pp  - SANE backend for Umax Astra parallel port flatbed scan‐
7       ners
8

DESCRIPTION

10       The sane-umax_pp library implements a SANE (Scanner  Access  Now  Easy)
11       backend  that  provides  access to Umax parallel port flatbed scanners.
12       The following scanners work with this backend:
13
14              Model:
15              --------------------
16              Astra 610P
17              Astra 1220P
18              HP3200C
19              Astra 1600P
20              Astra 2000P
21
22       This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200  for
23       1220P/1600P/2000P  dpi  scan reslutions,and 75x75, 150x150, 300x300 and
24       300x600 for 610P. In color and gray levels, there is a software lineart
25       mode.
26
27       The new generation models share a newer version of the 610P ASIC embed‐
28       ded in an EPAT chip.  Only parts such as CCD and ADC change from one to
29       another.  They  even  all  reports being UMAX Astra 1220P via IEEE1284.
30       There isn't software way to recognize  them  properly.  Under  windows,
31       model is set by the driver installed, regardless of the hardware.
32
33       EPP/ECP MODES ONLY
34              The  current version of the backend uses only EPP or ECP mode to
35              communicate with the scanner. PS/2 mode isn't  implemented.  The
36              610P  only use SPP. It is recommended that you set your parallel
37              port to EPP in BIOS with the current version  of  this  backend.
38              You can leave it to ECP or ECP+EPP, but in this case you may not
39              use ppdev but only direct hardware access if  you  have  to  use
40              ECP.   ECPEPP will only work if you use a 2.4 or 2.6 kernel with
41              ppdev character device support.
42
43       This backend does support parport sharing only if  you  have  a  kernel
44       with ppdev support.
45
46       Note  that  if  you  don't  use the ppdev character device, the backend
47       needs to run as root. To allow user access to the scanner run the back‐
48       end  through  the  network interface (See saned(8) and sane-net(5)).  A
49       more relaxed solution (security wise) is to add suid bit to  the  fron‐
50       tend  (See  chmod(1)).  The backend drop root priviledges as soon as it
51       can, right after gaining direct access to IO ports, which lessen  risks
52       when being root.
53
54

DEVICE NAMES

56       This backend expects device names of the form:
57
58              port value
59
60       Where value is :
61
62
63              auto   autodetect all parallel ports and probe them for scanner
64
65              safe-auto
66                     autodetect all parallel ports and probe them for scanner,
67                     but does not try direct hardware access
68
69              /dev/ppi0
70                     uses *BSD ppi device, depending on the number  of  avail‐
71                     able parallel port, you have to use /dev/ppi1, /dev/ppi2,
72                     ...
73
74              /dev/parport0
75                     uses linux ppdev  device,  depending  on  the  number  of
76                     available  parallel  port, you have to use /dev/parport1,
77                     /dev/parport2, ...
78
79              0x378  does direct hardware access on the given  address.  Usual
80                     values  are 0x378, 0x278, 0x3BC In this case, you have to
81                     run the  scanner  as  root  (*BSD  and  linux),  or  with
82                     'IOPL=yes' on OS/2
83
84       NOTE:  in all cases, you must have sufficient priviledges to get access
85       to the chosen device or address. Depending on  the  security  settings,
86       devices may not be available for all users.  You have to change permis‐
87       sions on the dev/ppi* or /dev/parport* devices.
88
89       You can rename any device using the
90
91              name devname
92              model model
93              vendor vendor
94
95       options. These options apply to the last port option.
96
97

CONFIGURATION

99       Please make sure to edit umax_pp.conf before you use the backend.
100
101       The contents of the umax_pp.conf file is a list of options  and  device
102       names that correspond to Umax scanners.  Empty lines and lines starting
103       with a hash mark (#) are ignored.
104
105       The height options supported are red-gain, green-gain, blue-gain,  red-
106       offset, green-offset, blue-offset, astra, and buffer.
107
108       Options  red-gain  ,  green-gain  and blue-gain allow you to adjust the
109       sensitivy of your scanner for the given  color.  Values  range  from  0
110       (lowest  gain)  to  15  (highest).  If the advanced option "Gain" isn't
111       checked in the frontend, the backend does automatic  gain  calibration,
112       and do not use user provided values.
113
114
115       Options  red-offset  , green-offset and blue-offset allow you to adjust
116       the offset of your scanner for the given color.  Values  range  from  0
117       (lowest offset) to 15 (highest).
118
119       Option  astra  allows  you to change the model of your scanner. Current
120       auto detection is based on side effects on scanning  when  using  1220P
121       command set on other models, so it may fail on unkown hardware combina‐
122       tion. Valid values are 610, 1220, 1600 and 2000.  It  is  usefull  only
123       when autodetection fails to detect properly your scanner model. If your
124       scanner work properly but is reported wrongly, let it be that way.  The
125       only  valid  case  to  change  the  model is when your scanner produces
126       'black' or prevent scanner model autodetection.
127
128       Option buffer allows you to change the size of  the  scan  buffer.  The
129       size  must  be  specified  in  bytes. The default value is 2 megabytes.
130       Decreasing this value will improve the smoothness of  progress  bar  in
131       the frontend, but will stall the scan more often.
132
133

FILES

135       /etc/sane.d/umax_pp.conf
136              The   backend   configuration  file  (see  also  description  of
137              SANE_CONFIG_DIR below).
138
139       /usr/lib*/sane/libsane-umax_pp.a
140              The static library implementing this backend.
141
142       /usr/lib*/sane/libsane-umax_pp.so
143              The shared library implementing this backend (present on systems
144              that support dynamic loading).
145
146

ENVIRONMENT

148       SANE_CONFIG_DIR
149              This environment variable specifies the list of directories that
150              may contain the configuration file.  Under UNIX, the directories
151              are  separated  by a colon (`:'), under OS/2, they are separated
152              by a semi-colon (`;').  If this variable is not set, the config‐
153              uration  file is searched in two default directories: first, the
154              current working directory (".") and then in /etc/sane.d.  If the
155              value  of the environment variable ends with the directory sepa‐
156              rator character, then the default directories are searched after
157              the  explicitly  specified  directories.   For  example, setting
158              SANE_CONFIG_DIR to "/tmp/config:" would  result  in  directories
159              "tmp/config",  ".",  and  "/etc/sane.d"  being searched (in this
160              order).
161
162       SANE_DEBUG_UMAX_PP
163              If the library was compiled with  debug  support  enabled,  this
164              environment  variable controls the debug level for this backend.
165              E.g., a value of 128 requests all debug output  to  be  printed.
166              Smaller levels reduce verbosity.
167
168
169              level   debug output
170              ------- ------------------------------
171               0       nothing
172               1       errors
173               2       warnings & minor errors
174               3       additional information
175               4       debug information
176               5       code flow (not supported yet)
177               6       special debug information
178
179       SANE_DEBUG_UMAX_PP_LOW
180              This  variable  sets  the debug level for the SANE interface for
181              the Umax ASIC. Note that enabling this will spam  your  terminal
182              with some million lines of debug output.
183
184
185              level   debug output
186              ------- -------------------------------
187               0       nothing
188               1       errors
189               8       command blocks
190               16      detailed code flow
191               32      dump datafiles
192               255     everything
193

SEE ALSO

195       sane(7), sane-net(5), saned(8)
196
197
198       For latest bug fixes and information see
199              http://umax1220p.sourceforge.net/
200
201

AUTHOR

203       Stéphane VOLTZ <svoltz@wanadoo.fr>
204
205

CREDITS

207       Support  for the 610P has been made possible thank to an hardware dona‐
208       tion by William Stuart.
209
210

BUG REPORTS

212       If something doesn't work, please contact me. But I need some  informa‐
213       tion about your scanner to be able to help you...
214
215
216       SANE version
217              run "scanimage -V" to determine this
218
219       the backend version and your scanner hardware
220              run  "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log" as root. If you
221              don't get any output from the umax_pp backend, make sure a  line
222              "umax_pp"  is  included into your /etc/sane.d/dll.conf.  If your
223              scanner isn't detected, make sure you've defined the right  port
224              address, or the correct device in your umax_pp.conf.
225
226       the name of your scanner/vendor
227              also a worthy information. Please also include the optical reso‐
228              lution and lamp type of your scanner, both can be found  in  the
229              manual of your scanner.
230
231       any further comments
232              if you have comments about the documentation (what could be done
233              better), or you think I should know  something,  please  include
234              it.
235
236
237
238sane-backends 1.0.18            23 August 2004                 sane-umax_pp(5)
Impressum