1sane-plustek(5) SANE Scanner Access Now Easy sane-plustek(5)
2
6 sane-plustek - SANE backend for LM983[1/2/3] based USB flatbed scanners
7
9 The sane-plustek library implements a SANE (Scanner Access Now Easy)
10 backend that provides access to USB flatbed scanners based on National
11 Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're look‐
12 ing for parallel-port support for Plustek scanner please refer to the
13 sane-plustek_pp backend.
14
17 The Backend is able to support USB scanner based on the National Semi‐
18 conductor chipsets LM9831, LM9832 and LM9833. The following tables show
19 various devices which are currently reported to work. If your Plustek
20 scanner has another Product ID, then the device is NOT supported by
21 this backend.
22 Vendor Plustek - ID: 0x07B3
24 ----------------------------------------------------------
25 USB Model: ASIC: Properties: Prod-ID
26 ----------------------------------------------------------
27 OpticPro U12 LM9831 600x1200dpi 42bit 512Kb 0x0010
28 OpticPro UT12 LM9831 600x1200dpi 42bit 512Kb 0x0013
29 OpticPro UT12 LM9832 600x1200dpi 42bit 512Kb 0x0017
30 OpticPro UT16 LM9832 600x1200dpi 42bit 512Kb 0x0017
31 OpticPro U24 LM9831 1200x2400dpi 42bit 2Mb 0x0011
32 OpticPro U24 LM9832 1200x2400dpi 42bit 2Mb 0x0015
33 OpticPro UT24 LM9832 1200x2400dpi 42bit 2Mb 0x0017
34 Vendor KYE/Genius - ID: 0x0458
36 ----------------------------------------------------------
37 USB Model: ASIC: Properties: Prod-ID
38 ----------------------------------------------------------
39 Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2007
40 Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2008
41 Colorpage HR6A LM9832 600x1200dpi 42bit 512Kb 0x2009
42 Colorpage HR7 LM9832 600x1200dpi 42bit 512Kb 0x2013
43 Colorpage HR7LE LM9832 600x1200dpi 42bit 512Kb 0x2015
44 Colorpage HR6X LM9832 600x1200dpi 42bit 512Kb 0x2016
45 Vendor Hewlett-Packard - ID: 0x03F0
47 ----------------------------------------------------------
48 USB Model: ASIC: Properties: Prod-ID
49 ----------------------------------------------------------
50 ScanJet 2100C LM9831 600x1200dpi 42bit 512Kb 0x0505
51 ScanJet 2200C LM9832 600x1200dpi 42bit 512Kb 0x0605
52 Vendor Mustek - ID: 0x0400
54 ----------------------------------------------------------
55 USB Model: ASIC: Properties: Prod-ID
56 ----------------------------------------------------------
57 BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
58 BearPaw 1200 LM9832 600x1200dpi 42bit 512Kb 0x1001*
59 BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
60 * see also description for model override switch below!
61 Vendor UMAX - ID: 0x1606
63 ----------------------------------------------------------
64 USB Model: ASIC: Properties: Prod-ID
65 ----------------------------------------------------------
66 UMAX 3400 LM9832 600x1200dpi 42bit 512Kb 0x0050
67 UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
68 UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
69 Vendor COMPAQ - ID: 0x049F
71 ----------------------------------------------------------
72 USB Model: ASIC: Properties: Prod-ID
73 ----------------------------------------------------------
74 S4-100 LM9832 600x1200dpi 42bit 512Kb 0x001A
75 Vendor Epson - ID: 0x04B8
77 ----------------------------------------------------------
78 USB Model: ASIC: Properties: Prod-ID
79 ----------------------------------------------------------
80 Perfection 1250 LM9832 1200x2400dpi 42bit 512Kb 0x010F
81 Perfection 1260 LM9832 1200x2400dpi 42bit 512Kb 0x011D
82 Vendor CANON - ID: 0x04A9
84 ----------------------------------------------------------
85 USB Model: ASIC: Properties: Prod-ID
86 ----------------------------------------------------------
87 CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
88 CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
89 CanoScan D660U LM9832 600x1200dpi 42bit 512Kb 0x2208
90 CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
91 CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
92 CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
93 CanoScan LIDE25 LM9833 1200x2400dpi 48bit 512Kb 0x2220
94 CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
95 Vendor Syscan - ID: 0x0A82
97 ----------------------------------------------------------
98 USB Model: ASIC: Properties: Prod-ID
99 ----------------------------------------------------------
100 Travelscan 662 LM9833 600x1200dpi 48bit 512Kb 0x6620
101 Travelscan 464 LM9833 600x1200dpi 48bit 512Kb 0x4600
102 Vendor Portable Peripheral Co., Ltd. - ID: 0x0A53
104 ----------------------------------------------------------
105 USB Model: ASIC: Properties: Prod-ID
106 ----------------------------------------------------------
107 Q-Scan USB001 LM9832 300x600dpi 42bit 512Kb 0x1000
108 Q-Scan USB201 LM9832 300x600dpi 42bit 512Kb 0x2000
109 Vendor Visioneer - ID: 0x04A7
111 ----------------------------------------------------------
112 USB Model: ASIC: Properties: Prod-ID
113 ----------------------------------------------------------
114 Strobe XP100 LM9833 600x1200dpi 48bit 512Kb 0x0427
115
117 For parallelport device support see the plustek_pp backend.
118 The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
119 is supported by the Artec backend.
120 Only the National Semiconductor LM983[1/2/] based devices of Plustek
121 are supported by this backend. Older versions of the U12, the UT12, the
122 U1212 and U1248 (GrandTech chipset) are not supported.
123 Model Chipset backend
125 ------------------------------------
126 U1248 GrandTech gt68xx
127 UT16B GrandTech gt68xx
128 OpticSlim 1200 GrandTech gt68xx
129 OpticSlim 2400 GrandTech gt68xx
130 U12 P98003 u12
131 UT12 P98003 u12
132 1212U P98003 u12
133 For a more complete and up to date list see:
134 http://www.sane-project.org/sane-supported-devices.html
135
138 To use your scanner with this backend, you need at least two entries in
139 the configuration file /etc/sane.d/plustek.conf
140 [usb] vendor-id product-id
141 device /dev/usbscanner
142 [usb] tells the backend, that the following devicename (here /dev/usb‐
144 scanner) has to be interpreted as USB scanner device. If vendor- and
145 product-id has not been specified, the backend tries to detect this by
146 its own. If device is set to auto then the next matching device is
147 used.
148 The following options can be used for a default setup of your device.
149 Most of them are also available through the frontend.
150 The Options:
152 option warmup t
154 t specifies the warmup period in seconds, if set to -1, the
155 automatic warmup function will be used
156 option lampOff t
158 t is the time in seconds for switching off the lamps in standby
159 mode
160 option lOffonEnd b
162 b specifies the behaviour when closing the backend, 1 --> switch
163 lamps off, 0 --> do not change lamp status
164 option mov m
166 m is the model override switch. It works only with Mustek
167 BearPaw devices.
168 m/PID | 0x1000 | 0x1001
169 ------+--------------+--------------
170 0 | BearPaw 1200 | BearPaw 2400
171 1 | no function | BearPaw 1200
172 option invertNegatives b
174 b 0 --> do not invert the picture during negativ scans,
175 1 --> invert picture
176 option cacheCalData b
178 b 0 --> do not save calibration results,
179 1 --> save results of calibration in ~/.sane/ directory
180 option altCalibration b
182 b 0 --> use standard calibration routines,
183 1 --> use alternate calibration (only non Plustek devices, stan‐
184 dard for CIS devices)
185 option skipFine b
187 b 0 --> perform fine calibration,
188 1 --> skip fine calibration (only non Plustek devices)
189 option skipFineWhite b
191 b 0 --> perform white fine calibration,
192 1 --> skip white fine calibration (only non Plustek devices)
193 option skipDarkStrip b
195 b 0 --> perform dark calibration, with enabled lamp using the
196 dark calibration strip of the scanner. If the scanner does not
197 have such a strip, the alternative way is to switch off the lamp
198 during this step.
199 1 --> always switch off the lamp for dark calibration, even a
200 black strip is available
201 option skipCalibration b
203 b 0 --> perform calibration,
204 1 --> skip calibration (only non Plustek devices)
205 option enableTPA b
207 b 0 --> default behaviour, specified by the internal tables,
208 1 --> override internal tables and allow TPA mode (EPSON/UMAX
209 only)
210 option posOffX x
213 option posOffY y
214 option tpaOffX x
215 option tpaOffY y
216 option negOffX x
217 option negOffY y
218 x y By using this settings, the user can adjust the given image
219 positions. Please note, that there's no internal range checking
220 for this feature.
221 option posShadingY p
223 option tpaShadingY p
224 option negShadingY p
225 p overrides the internal shading position. The values are in
226 steps. Please note, that there's no internal range checking for
227 this feature.
228 option redGamma r
230 option greenGamma g
231 option blueGamma b
232 option grayGamma gr
233 r g b gr
234 By using these values, the internal linear gamma table (r,g,b,gr = 1.0)
235 can be adjusted.
236 option red_gain r
238 option red_offset ro
239 option green_gain g
240 option green_offset go
241 option blue_gain b
242 option blue_offset bo
243 r g b ro go bo These values can be used to set the gain and off‐
244 set values of the AFE for each channel. The range is between 0
245 and 63. -1 means autocalibration.
246 See the plustek.conf file for examples.
249 Note:
251 You have to make sure, that the USB subsystem is loaded correctly and
252 you have access to the device-node. For more details see sane-usb (5)
253 manpage. You might use sane-find-scanner to check that you have access
254 to your device.
255 Note:
257 If there's no configuration file, the backend defaults to device auto
258
261 /etc/sane.d/plustek.conf
262 The backend configuration file
263 /usr/lib64/sane/libsane-plustek.a
265 The static library implementing this backend.
266 /usr/lib64/sane/libsane-plustek.so
268 The shared library implementing this backend (present on systems
269 that support dynamic loading).
270
273 SANE_CONFIG_DIR
274 This environment variable specifies the list of directories that
275 may contain the configuration file. Under UNIX, the directories
276 are separated by a colon (`:'), under OS/2, they are separated
277 by a semi-colon (`;'). If this variable is not set, the config‐
278 uration file is searched in two default directories: first, the
279 current working directory (".") and then in /etc/sane.d. If the
280 value of the environment variable ends with the directory sepa‐
281 rator character, then the default directories are searched after
282 the explicitly specified directories. For example, setting
283 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
284 "tmp/config", ".", and "/etc/sane.d" being searched (in this
285 order).
286 SANE_DEBUG_PLUSTEK
288 If the library was compiled with debug support enabled, this
289 environment variable controls the debug level for this backend.
290 Higher debug levels increase the verbosity of the output.
291 Example: export SANE_DEBUG_PLUSTEK=10
293
296 sane(7), sane-usb(5), sane-u12(5), sane-gt68xx(5),
297 /usr/share/doc/sane-backends/plustek/Plustek-USB.changes
298
301 Please send any information and bug-reports to:
302 SANE Mailing List
303 Additional info and hints can be obtained from our
305 Mailing-List archive at:
306 http://www.sane-project.org/mailing-lists.html
307 To obtain debug messages from the backend, please set the environment-
309 variable SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
310 (i.e. scanimage).
311 i.e.: export SANE_DEBUG_PLUSTEK=20 ; scanimage
312 The value controls the verbosity of the backend. Please note, that val‐
314 ues greater than 24 force the backend to output raw data files, which
315 could be rather large. The ending of these files is ".raw". For prob‐
316 lem reports it should be enough the set the verbosity to 13.
317
320 * The driver does not support these manic scalings up to 16 times the
321 physical resolution. The only scaling is done on resolutions between
322 the physical resolution of the CCD-/CIS-sensor and the stepper motor
323 i.e. you have a 600x1200 dpi scanner and you are scanning using 800dpi,
324 so scaling is necessary, because the sensor only delivers 600dpi but
325 the motor is capable to perform 1200dpi steps.
326 * Plusteks' model policy is somewhat inconsistent. They sell techni‐
328 cally different devices under the same product name. Therefore it is
329 possible that some devices like the UT12 or U12 won't work - please
330 check the model list above and compare the product-id to the one your
331 device has.
332 * Negative/Slide scanning quality is poor.
334 03 Nov 2017 sane-plustek(5)