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