1sane-genesys(5) SANE Scanner Access Now Easy sane-genesys(5)
2
6 sane-genesys - SANE backend for GL646, GL841, GL843, GL847 and GL124
7 based USB flatbed scanners
8
10 The sane-genesys library implements a SANE (Scanner Access Now Easy)
11 backend that provides access to USB flatbed scanners based on the
12 Genesys GL646, GL841, GL843, GL847 and GL124 chips. At present, the
13 following scanners are known to work with this backend:
14 Canon LiDE 35/40/50/60/100/110/200/210/700
16 Hewlett-Packard HP2300C/HP2400/HP3670/HP3690/G4010/G4050
17 Medion MD5345/MD6228/MD6274
18 Panasonic KV-SS080
19 Plustek OpticBook 3600
20 Pentax DSmobile 600
21 Syscan/Ambir DocketPORT 467/485/487/665/685
22 Visioneer OneTouch 7100/Strobe XP100 (rev3)/XP200/XP300/Roadwar‐
23 rior
24 Xerox Travel Scanner 100, OneTouch 2400
25 This is stable software for supported models. But if you test new or
28 untested scanners, keep your hand at the scanner's plug and unplug it,
29 if the head bumps at the end of the scan area.
30 If you own a scanner other than the ones listed above that works with
32 this backend, please let me know this by sending the scanner's exact
33 model name and the USB vendor and device ids (e.g. from
34 /proc/bus/usb/devices, sane-find-scanner or syslog) to the sane-devel
35 mailing list. Even if the scanner's name is only slightly different
36 from the models mentioned above, please let me know.
37 If you own a scanner that isn't detected by the genesys backend but has
39 a GL646, GL841, GL843, GL847 or GL124 chipset, you can try to add it to
40 the backend.
41
43 To give correct image quality, sheet fed scanners need to be calibrated
44 using the calibration sheet sold with the scanner. To do calibration,
45 you must insert this target in the feeder then start calibration either
46 by passing the --calibrate option to scanimage or by clicking on the
47 available 'calibrate' button in the 'advanced options' in a graphical
48 frontend. The result of the calibration is stored in a file in the home
49 directory of the user doing it. If you plug the scanner in another
50 machine or use it with another account, calibration will have to be
51 redone.
52
55 --lamp-off-time number
56 The lamp will be turned off after the given time (in
57 minutes). A value of 0 means that the lamp won't be turned off.
58 --threshold percent
60 0..100% (in steps of 1). Select minimum brightness to get a
61 white point. Pixels whith brightness below that value will be
62 scanned as black.
63 --brightness value
65 -100..100 (in steps of 1). Set the brightness enhancement.
66 0 for no enhancement, negative values to decrease brigthness,
67 and positive values to increase it.
68 --contrast value
70 -100..100 (in steps of 1). Set the contrast enhancement. 0
71 for no enhancement, negative values to decrease contrast, and
72 positive values to increase it.
73 --disable-interpolation yes|no
75 When using high resolutions where the horizontal resolu‐
76 tion is smaller than vertical resolution, data is expanded by
77 software to preserve picture geometry. This can be disabled by
78 this option to get real scanned data.
79 --disable-dynamic-lineart yes|no
81 Disable use of a software adaptive algorithm to generate
82 lineart and rely on hardware lineart.
83 --color-filter None|Red|Green|Blue
85 When using gray or lineart this option selects the used
86 color. Using a color filter will give a monochrome scan. CIS
87 based scanners can to true gray when no filter (None value) is
88 selected.
89 --lamp-off-scan
91 The lamp will be turned off during the scan. Calibration
92 is still done with lamp on.
93 --clear-calibration
95 Clear calibration cache data, triggering a new calibra‐
96 tion for the device when the next scan will happen.
97 --calibration-file
99 Specify the calibration file name to use. At least the
100 directory containing the file must exist, since it won't be cre‐
101 ated. This allow to handle the case of several identical devices
102 that would otherwise use the same calibration data. This option
103 is disabled if the backend is ran as root.
104 Additionally, several 'software' options are exposed by the backend.
107 These are reimplementations of features provided natively by larger
108 scanners, but running on the host computer. This enables smaller
109 machines to have similar capabilities. Please note that these features
110 are somewhat simplistic, and may not perform as well as the native
111 implementations. Note also that these features all require that the
112 driver cache the entire image in memory. This will almost certainly
113 result in a reduction of scanning speed.
114 --swcrop
116 Requests the driver to detect the extremities of the paper
117 within the larger image, and crop the empty edges.
118 --swdeskew
120 Requests the driver to detect the rotation of the paper
121 within the larger image, and counter the rotation.
122 --swdespeck --despeck X
124 Requests the driver to find and remove dots of X diameter
125 or smaller from the image, and fill the space with the average
126 surrounding color.
127 --swskip 0..100% (in steps of 1) [0]
129 Request driver to discard pages with low numbers of dark
130 pixels.
131 --swderotate[=(yes|no)] [no]
133 Request driver to detect and correct 90 degree image
134 rotation.
135
138 This backend needs libusb-0.1.6 or later installed, and hasn't tested
139 in other configuration than a linux kernel 2.6.9 or higher. However, it
140 should work any system with libusb where the SANE package can be com‐
141 piled. For setting permissions and general USB information look at
142 sane-usb(5).
143
147 The contents of the genesys.conf file is a list of usb lines containing
148 vendor and product ids that correspond to USB scanners. The file can
149 also contain option lines. Empty lines and lines starting with a hash
150 mark (#) are ignored. The scanners are autodetected by usb vendor_id
151 product_id statements which are already included into genesys.conf.
152 "vendor_id" and "product_id" are hexadecimal numbers that identify the
153 scanner.
154
156 /etc/sane.d/genesys.conf
157 The backend configuration file (see also description of
158 SANE_CONFIG_DIR below).
159 /usr/lib64/sane/libsane-genesys.a
161 The static library implementing this backend.
162 /usr/lib64/sane/libsane-genesys.so
164 The shared library implementing this backend (present on systems
165 that support dynamic loading).
166
168 SANE_CONFIG_DIR
169 This environment variable specifies the list of directories that
170 may contain the configuration file. Under UNIX, the directories
171 are separated by a colon (`:'), under OS/2, they are separated
172 by a semi-colon (`;'). If this variable is not set, the config‐
173 uration file is searched in two default directories: first, the
174 current working directory (".") and then in /etc/sane.d. If the
175 value of the environment variable ends with the directory sepa‐
176 rator character, then the default directories are searched after
177 the explicitly specified directories. For example, setting
178 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
179 "tmp/config", ".", and "/etc/sane.d" being searched (in this
180 order).
181 SANE_DEBUG_GENESYS
183 If the library was compiled with debug support enabled, this
184 environment variable controls the debug level for this backend.
185 Higher debug levels increase the verbosity of the output. If the
186 debug level is set to 1 or higher, some debug options become
187 available that are normally hidden. Handle them with care. This
188 will print messages related to core genesys functions.
189 SANE_DEBUG_GENESYS_LOW
191 This environment variable controls the debug level for low level
192 functions common to all genesys ASICs.
193 SANE_DEBUG_GENESYS_GL646
195 This environment variable controls the debug level for the spe‐
196 cific GL646 code part.
197 SANE_DEBUG_GENESYS_GL841
199 This environment variable controls the debug level for the spe‐
200 cific GL841 code part.
201 SANE_DEBUG_GENESYS_GL843
203 This environment variable controls the debug level for the spe‐
204 cific GL843 code part.
205 SANE_DEBUG_GENESYS_GL847
207 This environment variable controls the debug level for the spe‐
208 cific GL847 code part.
209 SANE_DEBUG_GENESYS_GL124
211 This environment variable controls the debug level for the spe‐
212 cific GL124 code part.
213 Example (full and highly verbose output for gl646):
216 export SANE_DEBUG_GENESYS=255
217 export SANE_DEBUG_GENESYS_LOW=255
218 export SANE_DEBUG_GENESYS_GL646=255
219
222 Jack McGill for donating several sheetfed and flatbed scanners, which
223 made possible to add support for them in the genesys backend:
224 Hewlett-Packard HP3670
225 Visioneer Strobe XP100 (rev3)/XP200/XP300/Roadwarrior
226 Canon LiDE 200
227 Pentax DSmobile 600
228 Syscan/Ambir DocketPORT 467/485/487/665/685
229 Xerox Travel Scanner 100, Onetouch 2400
230 cncsolutions (http://www.cncsolutions.com.br) sponsored and supported
232 the work on the Panasonic KV-SS080.
233 Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE
235 700F.
236
239 sane(7), sane-usb(5)
240
244 Oliver Rauch
245 Henning Meier-Geinitz <henning@meier-geinitz.de>
246 Gerhard Jaeger <gerhard@gjaeger.de>
247 Stéphane Voltz <stef.dev@free.fr>
248 Philipp Schmid <philipp8288@web.de>
249 Pierre Willenbrock <pierre@pirsoft.dnsalias.org>
250 Alexey Osipov <simba@lerlan.ru> for HP2400 final support
251
254 Powersaving isn't implemented for gl646 based scanner. Dynamic (emu‐
255 lated from gray data and with dithering) isn't enabled for gl646 scan‐
256 ners. Hardware lineart is limited up to 600 dpi for gl847 based scan‐
257 ners, due to the way image sensors are built.
258 This backend will be much slower if not using libusb-1.0. So be sure
260 that sane-backends is built with the --enable-libusb_1_0 option.
261
264 For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from
265 sensor. It seems the windows driver does some digital processing to
266 improve it, which is not implemented in the backend.
267 4 Jul 2012 sane-genesys(5)