| 1 |
.TH sane\-plustek_pp 5 "14 Jul 2008" "" "SANE Scanner Access Now Easy" |
| 2 |
.IX sane\-plustek_pp |
| 3 |
.SH NAME |
| 4 |
sane\-plustek_pp \- SANE backend for Plustek parallel port |
| 5 |
flatbed scanners |
| 6 |
.SH DESCRIPTION |
| 7 |
The |
| 8 |
.B sane\-plustek_pp |
| 9 |
library implements a SANE (Scanner Access Now Easy) backend that |
| 10 |
provides access to Plustek ASIC 9600[1/3] and P9800[1/3] based |
| 11 |
parallel port flatbed scanners. |
| 12 |
|
| 13 |
.SH "SUPPORTED DEVICES" |
| 14 |
|
| 15 |
At present, the following scanners should work with this backend: |
| 16 |
.PP |
| 17 |
.B "PLUSTEK SCANNERS" |
| 18 |
.PP |
| 19 |
.ft CR |
| 20 |
.nf |
| 21 |
Parallelport Model: ASIC: Properties: |
| 22 |
---------------------- ----- ------------------------ |
| 23 |
OpticPro PT12 98003 600x1200 dpi 36bit 512Kb |
| 24 |
OpticPro P12 98003 600x1200 dpi 36bit 512Kb |
| 25 |
OpticPro 9636T/12000T 98001 600x1200 dpi 36bit 512Kb |
| 26 |
OpticPro 12000P Turbo 98001 600x1200 dpi 36bit 512Kb |
| 27 |
OpticPro 9636P+/Turbo 98001 600x1200 dpi 36bit 512Kb |
| 28 |
OpticPro 9636P 96003 600x1200 dpi 36bit 128Kb |
| 29 |
OpticPro 12000P/96000P 96003 600x1200 dpi 36bit 128Kb |
| 30 |
OpticPro 1236P 96003 600x1200 dpi 30bit 128Kb |
| 31 |
OpticPro 9600P 96003 600x1200 dpi 30bit 128Kb |
| 32 |
OpticPro 9630P/FBIV 96003 600x1200 dpi 30bit 128Kb |
| 33 |
OpticPro 9630PL (14") 96003 600x1200 dpi 30bit 128Kb |
| 34 |
OpticPro A3I 96003 400x800 dpi 36bit 128Kb |
| 35 |
OpticPro 600P/6000P 96003 300x600 dpi 30bit 32Kb |
| 36 |
OpticPro 4831P 96003 300x600 dpi 30bit 32Kb |
| 37 |
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb |
| 38 |
OpticPro 4800P/FBII 96001 300x600 dpi 24bit 32Kb |
| 39 |
.fi |
| 40 |
.ft R |
| 41 |
.PP |
| 42 |
|
| 43 |
.B "PRIMAX SCANNERS" |
| 44 |
|
| 45 |
There are some scanners sold by Primax, but they are in fact |
| 46 |
Plustek devices. These scanners are also supported. |
| 47 |
The following table will show the relationship: |
| 48 |
.PP |
| 49 |
.ft CR |
| 50 |
.nf |
| 51 |
Model: Plustek Model: Remarks: |
| 52 |
--------------------------- -------------- ------------ |
| 53 |
Colorado 4800 OpticPro 4800 not tested |
| 54 |
Compact 4800 Direct OpticPro 600 mov=2 |
| 55 |
Compact 4800 Direct 30bit OpticPro 4830 mov=7 |
| 56 |
Compact 9600 Direct 30bit OpticPro 9630 works |
| 57 |
.fi |
| 58 |
.ft R |
| 59 |
.PP |
| 60 |
|
| 61 |
.B "GENIUS SCANNERS" |
| 62 |
|
| 63 |
The following devices are sold as Genius Scanners, but are in fact |
| 64 |
Plustek devices. |
| 65 |
The table will show the relationship: |
| 66 |
.PP |
| 67 |
.ft CR |
| 68 |
.nf |
| 69 |
Model: Remarks: |
| 70 |
--------------------------- ---------------------------- |
| 71 |
Colorpage Vivid III V2 Like P12 but has two buttons |
| 72 |
and Wolfson DAC |
| 73 |
.fi |
| 74 |
.ft R |
| 75 |
.PP |
| 76 |
|
| 77 |
.B "ARIES SCANNERS" |
| 78 |
|
| 79 |
There's one scanner sold as Aries Scanner, but is in fact a |
| 80 |
Plustek device. |
| 81 |
The following table will show the relationship: |
| 82 |
.PP |
| 83 |
.ft CR |
| 84 |
.nf |
| 85 |
Model: Plustek Model: Remarks: |
| 86 |
--------------------------- -------------- ------------ |
| 87 |
Scan-It 4800 OpticPro 600 mov=2 |
| 88 |
.fi |
| 89 |
.ft R |
| 90 |
.PP |
| 91 |
|
| 92 |
.B "BrightScan SCANNERS" |
| 93 |
|
| 94 |
There's one scanner sold as BrightScan OpticPro Scanner, this is also |
| 95 |
a rebadged Plustek device. |
| 96 |
The following table will show the relationship: |
| 97 |
.PP |
| 98 |
.ft CR |
| 99 |
.nf |
| 100 |
Model: Remarks: |
| 101 |
--------------------------- ---------------------------- |
| 102 |
BrightScan OpticPro OpticPro P12 |
| 103 |
.fi |
| 104 |
.ft R |
| 105 |
|
| 106 |
.SH "DEVICE NAMES" |
| 107 |
This backend's default device is: |
| 108 |
.PP |
| 109 |
.RS |
| 110 |
.I 0x378 |
| 111 |
.RE |
| 112 |
.PP |
| 113 |
This "default device" will be used if no configuration |
| 114 |
file can be found. It is the base address of the parallel port |
| 115 |
on i386 machines. |
| 116 |
.PP |
| 117 |
As the backend supports up to four devices, it is possible to |
| 118 |
specify them in the configuration file |
| 119 |
.PP |
| 120 |
.RS |
| 121 |
.I /etc/sane.d/plustek_pp.conf |
| 122 |
.RE |
| 123 |
.PP |
| 124 |
See this file for examples. |
| 125 |
.PP |
| 126 |
|
| 127 |
.SH "CONFIGURATION" |
| 128 |
.PP |
| 129 |
This section describes the backend's configuration file entries. |
| 130 |
The file is located at: |
| 131 |
.I /etc/sane.d/plustek_pp.conf |
| 132 |
.PP |
| 133 |
For a proper setup, you will need at least two entries: |
| 134 |
.RS |
| 135 |
.PP |
| 136 |
.I [direct] |
| 137 |
.br |
| 138 |
.I device 0x378 |
| 139 |
.RE |
| 140 |
.PP |
| 141 |
.I direct |
| 142 |
tells the backend, that the following devicename (here |
| 143 |
.IR 0x378 ) |
| 144 |
has to be interpreted as parallel port scanner device. In |
| 145 |
fact it is the address to use. Alternatively you can use |
| 146 |
.I /dev/parport0 |
| 147 |
if the backend has been compiled with libieee1284 support. |
| 148 |
.PP |
| 149 |
Further options: |
| 150 |
.PP |
| 151 |
option warmup t |
| 152 |
.RS |
| 153 |
.I t |
| 154 |
specifies the warmup period in seconds |
| 155 |
.RE |
| 156 |
.PP |
| 157 |
option lampOff t |
| 158 |
.RS |
| 159 |
.I t |
| 160 |
is the time in seconds for switching off the lamps in |
| 161 |
standby mode |
| 162 |
.RE |
| 163 |
.PP |
| 164 |
option lOffonEnd b |
| 165 |
.RS |
| 166 |
.I b |
| 167 |
specifies the behaviour when closing the backend, 1 --> switch |
| 168 |
lamps off, 0 --> do not change lamp status |
| 169 |
.RE |
| 170 |
.PP |
| 171 |
option mov m |
| 172 |
.RS |
| 173 |
.I m |
| 174 |
is the model override switch, which only works in direct mode. |
| 175 |
.TP |
| 176 |
.IR m " = 0" |
| 177 |
default: no override |
| 178 |
.TP |
| 179 |
.IR m " = 1" |
| 180 |
OpticPro 9630PL override (works if OP9630 |
| 181 |
has been detected) forces legal size (14") |
| 182 |
.TP |
| 183 |
.IR m " = 2" |
| 184 |
Primax 4800Direct override (works if OP600 |
| 185 |
has been detected) swaps red/green color |
| 186 |
.TP |
| 187 |
.IR m " = 3" |
| 188 |
OpticPro 9636 override (works if OP9636 has |
| 189 |
been detected) disables backends |
| 190 |
transparency/negative capabilities |
| 191 |
.TP |
| 192 |
.IR m " = 4" |
| 193 |
OpticPro 9636P override (works if OP9636 has |
| 194 |
been detected) disables backends |
| 195 |
transparency/negative capabilities |
| 196 |
.TP |
| 197 |
.IR m " = 5" |
| 198 |
OpticPro A3I override (works if OP12000 has |
| 199 |
been detected) enables A3 scanning |
| 200 |
.TP |
| 201 |
.IR m " = 6" |
| 202 |
OpticPro 4800P override (works if OP600 |
| 203 |
has been detected) swaps red/green color |
| 204 |
.TP |
| 205 |
.IR m " = 7" |
| 206 |
Primax 4800Direct 30bit override (works if |
| 207 |
OP4830 has been detected) |
| 208 |
.RE |
| 209 |
.PP |
| 210 |
See the |
| 211 |
.I plustek_pp.conf |
| 212 |
file for examples. |
| 213 |
.PP |
| 214 |
|
| 215 |
.SH "PARALLEL PORT MODES" |
| 216 |
.PP |
| 217 |
The current driver works best, when the parallel port |
| 218 |
has been set to EPP-mode. When detecting any other |
| 219 |
mode such as ECP or PS/2 the driver tries to set to a |
| 220 |
faster, supported mode. If this fails, it will use the |
| 221 |
SPP mode, as this mode should work with all Linux supported |
| 222 |
parallel ports. If in doubt, enter your BIOS and set it to |
| 223 |
any mode except ECP. |
| 224 |
.PP |
| 225 |
Former Plustek scanner models (4830, 9630) supplied a |
| 226 |
ISA parallel port adapter card. This card is |
| 227 |
.BR not |
| 228 |
supported by the driver. |
| 229 |
.PP |
| 230 |
The ASIC 96001/3 based models have sometimes trouble with |
| 231 |
high resolution modes. If you encounter sporadic corrupted |
| 232 |
images (parts duplicated or shifted horizontally) kill all |
| 233 |
other applications before scanning and (if sufficient |
| 234 |
memory available) disable swapping. |
| 235 |
.PP |
| 236 |
See the |
| 237 |
.I plustek_pp.conf |
| 238 |
file for examples. |
| 239 |
.PP |
| 240 |
|
| 241 |
.SH FILES |
| 242 |
.TP |
| 243 |
.I /etc/sane.d/plustek_pp.conf |
| 244 |
The backend configuration file |
| 245 |
.TP |
| 246 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-plustek_pp.a |
| 247 |
The static library implementing this backend. |
| 248 |
.TP |
| 249 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-plustek_pp.so |
| 250 |
The shared library implementing this backend (present on systems that |
| 251 |
support dynamic loading). |
| 252 |
|
| 253 |
.SH ENVIRONMENT |
| 254 |
.TP |
| 255 |
.B SANE_CONFIG_DIR |
| 256 |
This environment variable specifies the list of directories that may |
| 257 |
contain the configuration file. On *NIX systems, the directories are |
| 258 |
separated by a colon (`:'), under OS/2, they are separated by a |
| 259 |
semi-colon (`;'). If this variable is not set, the configuration file |
| 260 |
is searched in two default directories: first, the current working |
| 261 |
directory (".") and then in |
| 262 |
.IR /etc/sane.d . |
| 263 |
If the value of the |
| 264 |
environment variable ends with the directory separator character, then |
| 265 |
the default directories are searched after the explicitly specified |
| 266 |
directories. For example, setting |
| 267 |
.B SANE_CONFIG_DIR |
| 268 |
to "/tmp/config:" would result in directories |
| 269 |
.IR "tmp/config" , |
| 270 |
.IR "." , |
| 271 |
and |
| 272 |
.I "/etc/sane.d" |
| 273 |
being searched (in this order). |
| 274 |
.TP |
| 275 |
.B SANE_DEBUG_PLUSTEK_PP |
| 276 |
If the library was compiled with debug support enabled, this |
| 277 |
environment variable controls the debug level for this backend. Higher |
| 278 |
debug levels increase the verbosity of the output. |
| 279 |
|
| 280 |
Example: |
| 281 |
export SANE_DEBUG_PLUSTEK_PP=10 |
| 282 |
|
| 283 |
.SH "SEE ALSO" |
| 284 |
.BR sane (7), |
| 285 |
.BR xscanimage (1), |
| 286 |
.br |
| 287 |
.I /usr/share/doc/libsane/plustek/Plustek\-PARPORT.changes |
| 288 |
|
| 289 |
.SH "CONTACT AND BUG-REPORTS" |
| 290 |
Please send any information and bug-reports to: |
| 291 |
.br |
| 292 |
.B SANE Mailing List |
| 293 |
.PP |
| 294 |
Additional info and hints can be obtained from our mailing-List archive at: |
| 295 |
.IR http://www.sane\-project.org/mailing\-lists.html . |
| 296 |
.PP |
| 297 |
To obtain debug messages from the backend, please set the |
| 298 |
environment-variable |
| 299 |
.B SANE_DEBUG_PLUSTEK_PP |
| 300 |
before calling your favorite SANE frontend (e.g. |
| 301 |
.BR xscanimage (1)): |
| 302 |
.PP |
| 303 |
.I export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage |
| 304 |
.PP |
| 305 |
The value controls the verbosity of the output. |
| 306 |
.PP |
| 307 |
|
| 308 |
.SH "KNOWN BUGS & RESTRICTIONS" |
| 309 |
.PP |
| 310 |
* The Halftoning works, but the quality is poor |
| 311 |
.PP |
| 312 |
* Printers (especially HP models) will start to |
| 313 |
print during scanning. This in fact is a problem |
| 314 |
to other printers too, using bidirectional protocol |
| 315 |
(see www.plustek.com (TAIWAN) page for further details) |
| 316 |
.PP |
| 317 |
* The driver does not support these manic scalings up |
| 318 |
to 16 times the physical resolution. The only scaling |
| 319 |
is done on resolutions between the physical resolution |
| 320 |
of the CCD-sensor and the stepper motor i.e. you have a |
| 321 |
600x1200 dpi scanner and you are scanning using 800dpi, |
| 322 |
so scaling is necessary, because the sensor only delivers |
| 323 |
600dpi but the motor is capable to perform 800dpi steps. |
| 324 |
.PP |
| 325 |
* On some devices, the pictures seems bluish |
| 326 |
.PP |
| 327 |
.I ASIC 98001 based models: |
| 328 |
.PP |
| 329 |
* The 300dpi transparency and negative mode does not work |
| 330 |
correctly. |
| 331 |
.PP |
| 332 |
* There is currently no way to distinguish a model with |
| 333 |
and without transparency unit. |
| 334 |
.PP |
| 335 |
* The scanned images seem to be too dark (P9636T) |
| 336 |
.PP |
| 337 |
.I ASIC 96003/1 based models: |
| 338 |
.PP |
| 339 |
* 30bit mode is currently not supported. |
| 340 |
.PP |
| 341 |
* On low end systems under heavy system load the |
| 342 |
driver may lose data, which can result in picture |
| 343 |
corruption or cause the sensor to hit the scan bed. |
| 344 |
.PP |
| 345 |
* The scanning speed on 600x1200 dpi models is slow. |
| 346 |
.PP |
| 347 |
* The scanning quality of the A3I is poor. |