| 1 |
.TH sane 7 "03 Jan 2020" "" "SANE Scanner Access Now Easy" |
| 2 |
.IX sane |
| 3 |
|
| 4 |
.SH NAME |
| 5 |
sane \- Scanner Access Now Easy: API for accessing scanners |
| 6 |
|
| 7 |
.SH DESCRIPTION |
| 8 |
.B SANE |
| 9 |
is an application programming interface (API) that provides standardized |
| 10 |
access to any raster image scanner hardware. The standardized interface makes |
| 11 |
it possible to write just one driver for each scanner device instead of one |
| 12 |
driver for each scanner and application. |
| 13 |
|
| 14 |
While |
| 15 |
.B SANE |
| 16 |
is primarily targeted at a UNIX environment, the standard has been carefully |
| 17 |
designed to make it possible to implement the API on virtually any hardware or |
| 18 |
operating system. |
| 19 |
.PP |
| 20 |
This manual page provides a summary of the information available about |
| 21 |
.BR SANE . |
| 22 |
.PP |
| 23 |
If you have trouble getting your scanner detected, read the PROBLEMS section. |
| 24 |
|
| 25 |
.SH TERMINOLOGY |
| 26 |
|
| 27 |
An application that uses the |
| 28 |
.B SANE |
| 29 |
interface is called a |
| 30 |
.B SANE frontend. |
| 31 |
A driver that implements the |
| 32 |
.B SANE |
| 33 |
interface is called a |
| 34 |
.B SANE backend. |
| 35 |
A |
| 36 |
.B meta backend |
| 37 |
provides some means to manage one or more other backends. |
| 38 |
|
| 39 |
|
| 40 |
.SH "SOFTWARE PACKAGES" |
| 41 |
The package |
| 42 |
.B sane\-backends |
| 43 |
contains backends, documentation, networking support, and the |
| 44 |
command line frontend |
| 45 |
.BR scanimage (1). |
| 46 |
The frontends |
| 47 |
.BR xscanimage (1), |
| 48 |
.BR xcam (1), |
| 49 |
and |
| 50 |
.BR scanadf (1) |
| 51 |
are included in the package |
| 52 |
.BR sane\-frontends . |
| 53 |
Both packages can be downloaded from the |
| 54 |
.B SANE |
| 55 |
homepage |
| 56 |
.RI ( http://www.sane\-project.org/ ). |
| 57 |
Information about other frontends and backends can also be found on the |
| 58 |
.B SANE |
| 59 |
homepage. |
| 60 |
|
| 61 |
.SH "GENERAL INFORMATION" |
| 62 |
The following sections provide short descriptions and links to more |
| 63 |
information about several aspects of |
| 64 |
.BR SANE . |
| 65 |
A name with a number in parenthesis (e.g. |
| 66 |
.BR sane\-dll (5)) |
| 67 |
points to a manual page. In this case |
| 68 |
.I man\ 5\ sane\-dll |
| 69 |
will display the page. Entries like |
| 70 |
.I /usr/share/doc/libsane/README |
| 71 |
are references to text files that were copied to the |
| 72 |
.B SANE |
| 73 |
documentation directory |
| 74 |
.RI ( /usr/share/doc/libsane/ ) |
| 75 |
during installation. Everything else is a URL to a resource on the web. |
| 76 |
|
| 77 |
.TP 2 |
| 78 |
.B SANE homepage |
| 79 |
Information on all aspects of SANE including a tutorial and a link to the SANE FAQ |
| 80 |
can be found on the SANE homepage: |
| 81 |
.IR http://www.sane\-project.org/ . |
| 82 |
.TP |
| 83 |
.B SANE device lists |
| 84 |
The |
| 85 |
.B SANE |
| 86 |
device lists contain information about the status of |
| 87 |
.B SANE |
| 88 |
support for a specific device. If your scanner is not listed there (either |
| 89 |
supported or unsupported), please contact us. See section HOW CAN YOU HELP |
| 90 |
SANE for details. There are lists for specific releases of SANE, for the |
| 91 |
current development version and a search engine: |
| 92 |
.IR http://www.sane\-project.org/sane\-supported\-devices.html . |
| 93 |
The lists are also installed on your system at |
| 94 |
.IR /usr/share/doc/libsane/ . |
| 95 |
.TP |
| 96 |
.B SANE mailing list |
| 97 |
There is a mailing list for the purpose of discussing the SANE standard and its |
| 98 |
implementations: sane\-devel. Despite its name, the list is not only intended |
| 99 |
for developers, but also for users. There are also some more lists for special |
| 100 |
topics. However, for users, sane\-devel is the right list. How to subscribe and |
| 101 |
unsubscribe: |
| 102 |
.IR http://www.sane\-project.org/mailing\-lists.html . |
| 103 |
.TP |
| 104 |
.B SANE IRC channel |
| 105 |
The IRC (Internet Relay Chat) channel #sane can be found on the Freenode |
| 106 |
network (irc.libera.chat). It's for discussing |
| 107 |
.B SANE |
| 108 |
problems, talking about development and general |
| 109 |
.B SANE |
| 110 |
related chatting. Before asking for help, please read the other documentation |
| 111 |
mentioned in this manual page. The channel's topic is also used for |
| 112 |
announcements of problems with SANE infrastructure (mailing lists, web server, |
| 113 |
etc.). |
| 114 |
.TP |
| 115 |
.B Compiling and installing SANE |
| 116 |
Look at |
| 117 |
.I /usr/share/doc/libsane/README |
| 118 |
and the os-dependent README files for information about compiling and |
| 119 |
installing |
| 120 |
.B SANE. |
| 121 |
.TP |
| 122 |
.B SCSI configuration |
| 123 |
For information about various systems and SCSI controllers see |
| 124 |
.BR sane\-scsi (5). |
| 125 |
.TP |
| 126 |
.B USB configuration |
| 127 |
For information about USB configuration see |
| 128 |
.BR sane\-usb (5). |
| 129 |
|
| 130 |
.SH "FRONTENDS AND MISCELLANEOUS PROGRAMS" |
| 131 |
.TP 2 |
| 132 |
.B scanimage |
| 133 |
Command-line frontend. See |
| 134 |
.BR scanimage (1). |
| 135 |
.TP |
| 136 |
.B saned |
| 137 |
.B SANE |
| 138 |
network daemon that allows remote clients to access image acquisition devices |
| 139 |
available on the local host. See |
| 140 |
.BR saned (8). |
| 141 |
.TP |
| 142 |
.B sane\-find\-scanner |
| 143 |
Command-line tool to find SCSI and USB scanners and determine their UNIX |
| 144 |
device files. See |
| 145 |
.BR sane\-find\-scanner (1). |
| 146 |
.PP |
| 147 |
Also, have a look at the |
| 148 |
.B sane\-frontends |
| 149 |
package (which includes |
| 150 |
.BR xscanimage (1), |
| 151 |
.BR xcam (1), |
| 152 |
and |
| 153 |
.BR scanadf (1)) |
| 154 |
and the frontend information page at |
| 155 |
.IR http://www.sane\-project.org/sane\-frontends.html . |
| 156 |
|
| 157 |
.SH "BACKENDS FOR SCANNERS" |
| 158 |
.TP 2 |
| 159 |
.B abaton |
| 160 |
Supports Abaton flatbed scanners such as the Scan 300/GS (8bit, |
| 161 |
256 levels of gray) and the Scan 300/S (black and white, untested). See |
| 162 |
.BR sane\-abaton (5) |
| 163 |
for details. |
| 164 |
.TP |
| 165 |
.B agfafocus |
| 166 |
Supports AGFA Focus scanners and the Siemens S9036 (untested). |
| 167 |
See |
| 168 |
.BR sane\-agfafocus (5) |
| 169 |
for details. |
| 170 |
.TP |
| 171 |
.B apple |
| 172 |
Supports Apple flatbed scanners including the following scanners: |
| 173 |
AppleScanner, OneScanner and ColorOneScanner. See |
| 174 |
.BR sane\-apple (5) |
| 175 |
for details. |
| 176 |
.TP |
| 177 |
.B artec |
| 178 |
Supports several Artec/Ultima SCSI flatbed scanners as |
| 179 |
well as the BlackWidow BW4800SP and the Plustek 19200S. See |
| 180 |
.BR sane\-artec (5) |
| 181 |
for details. |
| 182 |
.TP |
| 183 |
.B artec_eplus48u |
| 184 |
Supports the Artec E+ 48U scanner and re-badged |
| 185 |
models like Tevion MD 9693, Medion MD 9693, Medion MD 9705 and Trust Easy |
| 186 |
Webscan 19200. See |
| 187 |
.BR sane\-artec_eplus48u (5) |
| 188 |
for details. |
| 189 |
.TP |
| 190 |
.B as6e |
| 191 |
Supports the Artec AS6E parallel port interface scanner. See |
| 192 |
.BR sane\-as6e (5) |
| 193 |
for details. |
| 194 |
.TP |
| 195 |
.B avision |
| 196 |
Supports several Avision based scanners including the |
| 197 |
original Avision scanners (like AV 630, AV 620, ...) as well as the HP |
| 198 |
ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and |
| 199 |
Minolta film-scanners. |
| 200 |
See |
| 201 |
.BR sane\-avision (5) |
| 202 |
for details. |
| 203 |
.TP |
| 204 |
.B bh |
| 205 |
Supports Bell+Howell Copiscan II series document scanners. See |
| 206 |
.BR sane\-bh (5) |
| 207 |
for details. |
| 208 |
.TP |
| 209 |
.B canon |
| 210 |
Supports the CanoScan 300, CanoScan 600, and CanoScan |
| 211 |
2700F SCSI flatbed scanners. See |
| 212 |
.BR sane\-canon (5) |
| 213 |
for details. |
| 214 |
.TP |
| 215 |
.B canon630u |
| 216 |
Supports the CanoScan 630u and 636u USB scanners. See |
| 217 |
.BR sane\-canon630u (5) |
| 218 |
for details. |
| 219 |
.TP |
| 220 |
.B canon_dr |
| 221 |
Supports the Canon DR-Series ADF SCSI and USB scanners. See |
| 222 |
.BR sane\-canon_dr (5) |
| 223 |
for details. |
| 224 |
.TP |
| 225 |
.B canon_lide70 |
| 226 |
Supports the CanoScan LiDE 70 and 600 USB scanners. See |
| 227 |
.BR sane\-canon_lide70 (5) |
| 228 |
for details. |
| 229 |
.TP |
| 230 |
.B canon_pp |
| 231 |
Supports the CanoScan FB330P, FB630P, N340P and N640P parallel port |
| 232 |
scanners. See |
| 233 |
.BR sane\-canon_pp (5) |
| 234 |
for details. |
| 235 |
.TP |
| 236 |
.B cardscan |
| 237 |
Support for Corex Cardscan USB scanners. See |
| 238 |
.BR sane\-cardscan (5) |
| 239 |
for details. |
| 240 |
.TP |
| 241 |
.B coolscan coolscan2 coolscan3 |
| 242 |
Supports Nikon Coolscan film-scanners. See |
| 243 |
.BR sane\-coolscan (5), |
| 244 |
.BR sane\-coolscan2 (5) |
| 245 |
and |
| 246 |
.BR sane\-coolscan3 (5) |
| 247 |
for details. |
| 248 |
.TP |
| 249 |
.B epjitsu |
| 250 |
Supports Epson-based Fujitsu USB scanners. See |
| 251 |
.BR sane\-epjitsu (5) |
| 252 |
for details. |
| 253 |
.TP |
| 254 |
.B epson |
| 255 |
Old driver for Epson SCSI, parallel port and USB flatbed scanners. See |
| 256 |
.BR sane\-epson (5) |
| 257 |
for details but try |
| 258 |
.BR epson2 |
| 259 |
first. |
| 260 |
.TP |
| 261 |
.B epson2 |
| 262 |
Newer driver for Epson SCSI, parallel port, network and USB flatbed |
| 263 |
scanners (try this before |
| 264 |
.BR epson |
| 265 |
which is outdated). See |
| 266 |
.BR sane\-epson2 (5) |
| 267 |
for details. |
| 268 |
.TP |
| 269 |
.B escl |
| 270 |
Supports scanners through the eSCL protocol. See |
| 271 |
.BR sane\-escl (5) |
| 272 |
for details. |
| 273 |
.TP |
| 274 |
.B fujitsu |
| 275 |
Supports most Fujitsu SCSI and USB, flatbed and adf scanners. See |
| 276 |
.BR sane\-fujitsu (5) |
| 277 |
for details. |
| 278 |
.TP |
| 279 |
.B genesys |
| 280 |
Supports several scanners based on the Genesys Logic |
| 281 |
GL646, GL841, GL843, GL847 and GL124 chips like the |
| 282 |
Medion 6471 and Hewlett-Packard 2300c. |
| 283 |
See |
| 284 |
.BR sane\-genesys (5) |
| 285 |
for details. |
| 286 |
.TP |
| 287 |
.B gt68xx |
| 288 |
Supports scanners based on the Grandtech |
| 289 |
GT-6801 and GT-6816 chips like the Artec Ultima 2000 |
| 290 |
and several Mustek BearPaw CU and TA models. |
| 291 |
.br |
| 292 |
Some Genius, |
| 293 |
Lexmark, Medion, Packard Bell, Plustek, and Trust scanners |
| 294 |
are also supported. See |
| 295 |
.BR sane\-gt68xx (5) |
| 296 |
for details. |
| 297 |
.TP |
| 298 |
.B hp |
| 299 |
Supports Hewlett-Packard ScanJet scanners which |
| 300 |
utilize SCL (Scanner Control Language by HP). See |
| 301 |
.BR sane\-hp (5) |
| 302 |
for details. |
| 303 |
.TP |
| 304 |
.B hpsj5s |
| 305 |
Supports the Hewlett-Packard ScanJet 5S scanner. See |
| 306 |
.BR sane\-hpsj5s (5) |
| 307 |
for details. |
| 308 |
.TP |
| 309 |
.B hp3500 |
| 310 |
Supports the Hewlett-Packard ScanJet 3500 series. See |
| 311 |
.BR sane\-hp3500 (5) |
| 312 |
for details. |
| 313 |
.TP |
| 314 |
.B hp3900 |
| 315 |
Supports the Hewlett-Packard ScanJet 3900 series. See |
| 316 |
.BR sane\-hp3900 (5) |
| 317 |
for details. |
| 318 |
.TP |
| 319 |
.B hp4200 |
| 320 |
Supports the Hewlett-Packard ScanJet 4200 series. See |
| 321 |
.BR sane\-hp4200 (5) |
| 322 |
for details. |
| 323 |
.TP |
| 324 |
.B hp5400 |
| 325 |
Supports the Hewlett-Packard ScanJet 54XXC series. See |
| 326 |
.BR sane\-hp5400 (5) |
| 327 |
for details. |
| 328 |
.TP |
| 329 |
.B hpljm1005 |
| 330 |
Supports the Hewlett-Packard LaserJet M1005 scanner. See |
| 331 |
.BR sane\-hpljm1005 (5) |
| 332 |
for details. |
| 333 |
.TP |
| 334 |
.B hs2p |
| 335 |
Supports the Ricoh IS450 family of SCSI scanners. See |
| 336 |
.BR sane\-hs2p (5) |
| 337 |
for details. |
| 338 |
.TP |
| 339 |
.B ibm |
| 340 |
Supports some IBM and Ricoh SCSI scanners. See |
| 341 |
.BR sane\-ibm (5) |
| 342 |
for details. |
| 343 |
.TP |
| 344 |
.B kodak |
| 345 |
Supports some large Kodak scanners. See |
| 346 |
.BR sane\-kodak (5) |
| 347 |
for details. |
| 348 |
.TP |
| 349 |
.B kodakaio |
| 350 |
Supports Kodak AiO printer/scanners. See |
| 351 |
.BR sane\-kodakaio (5) |
| 352 |
for details. |
| 353 |
.TP |
| 354 |
.B kvs1025 |
| 355 |
Supports Panasonic KV-S102xC scanners. See |
| 356 |
.BR sane\-kvs1025 (5) |
| 357 |
for details. |
| 358 |
.TP |
| 359 |
.B leo |
| 360 |
Supports the LEO S3 and the Across FS-1130, which is a re-badged |
| 361 |
LEO FS-1130 scanner. See |
| 362 |
.BR sane\-leo (5) |
| 363 |
for details. |
| 364 |
.TP |
| 365 |
.B lexmark |
| 366 |
Supports the Lexmark X1100 series of USB scanners. See |
| 367 |
.BR sane\-lexmark (5) |
| 368 |
for details. |
| 369 |
.TP |
| 370 |
.B lexmark_x2600 |
| 371 |
Supports the Lexmark X2600 series of USB scanners. See |
| 372 |
.BR sane\-lexmark_x2600 (5) |
| 373 |
for details. |
| 374 |
.TP |
| 375 |
.B ma1509 |
| 376 |
Supports the Mustek BearPaw 1200F USB flatbed scanner. See |
| 377 |
.BR sane\-ma1509 (5) |
| 378 |
for details. |
| 379 |
.TP |
| 380 |
.B magicolor |
| 381 |
Supports the KONICA MINOLTA magicolor 1690MF multi-function printer/scanner/fax. See |
| 382 |
.BR sane\-magicolor (5) |
| 383 |
for details. |
| 384 |
.TP |
| 385 |
.B matsushita |
| 386 |
Supports some Panasonic KVSS high speed scanners. See |
| 387 |
.BR sane\-matsushita (5) |
| 388 |
for details. |
| 389 |
.TP |
| 390 |
.B microtek |
| 391 |
Supports "second generation" Microtek scanners with SCSI-1 command set. See |
| 392 |
.BR sane\-microtek (5) |
| 393 |
for details. |
| 394 |
.TP |
| 395 |
.B microtek2 |
| 396 |
Supports some Microtek scanners with a SCSI-2 command set. See |
| 397 |
.BR sane\-microtek2 (5) |
| 398 |
for details. |
| 399 |
.TP |
| 400 |
.B mustek |
| 401 |
Supports most Mustek SCSI flatbed scanners including the |
| 402 |
Paragon and ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some |
| 403 |
Trust scanners are also supported. See |
| 404 |
.BR sane\-mustek (5) |
| 405 |
for details. |
| 406 |
.TP |
| 407 |
.B mustek_pp |
| 408 |
Supports Mustek parallel port flatbed scanners. See |
| 409 |
.BR sane\-mustek_pp (5) |
| 410 |
for details. |
| 411 |
.TP |
| 412 |
.B mustek_usb |
| 413 |
Supports some Mustek ScanExpress USB flatbed scanners. See |
| 414 |
.BR sane\-mustek_usb (5) |
| 415 |
for details. |
| 416 |
.TP |
| 417 |
.B mustek_usb2 |
| 418 |
Supports scanners using the SQ113 chipset like the Mustek BearPaw 2448 TA Pro |
| 419 |
USB flatbed scanner. See |
| 420 |
.BR sane\-mustek_usb2 (5) |
| 421 |
for details. |
| 422 |
.TP |
| 423 |
.B nec |
| 424 |
Supports the NEC PC-IN500/4C SCSI scanner. See |
| 425 |
.BR sane\-nec (5) |
| 426 |
for details. |
| 427 |
.TP |
| 428 |
.B niash |
| 429 |
Supports the Agfa Snapscan Touch and the HP ScanJet 3300c, |
| 430 |
3400c, and 4300c USB flatbed scanners. See |
| 431 |
.BR sane\-niash (5) |
| 432 |
for details. |
| 433 |
.TP |
| 434 |
.B p5 |
| 435 |
Supports the Primax PagePartner. See |
| 436 |
.BR sane\-p5 (5) |
| 437 |
for details. |
| 438 |
.TP |
| 439 |
.B pie |
| 440 |
Supports Pacific Image Electronics (PIE) and Devcom |
| 441 |
SCSI flatbed scanners. See |
| 442 |
.BR sane\-pie (5) |
| 443 |
for details. |
| 444 |
.TP |
| 445 |
.B pixma |
| 446 |
Supports Canon PIXMA MP series (multi-function devices), |
| 447 |
Canon imageCLASS series (laser devices), Canon MAXIFY series and some Canon |
| 448 |
CanoScan series. See |
| 449 |
.BR sane\-pixma (5) |
| 450 |
for details. |
| 451 |
.TP |
| 452 |
.B plustek |
| 453 |
Supports USB flatbed scanners that use the National |
| 454 |
Semiconductor LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips |
| 455 |
include some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek, Umax, |
| 456 |
Epson, and Canon. See |
| 457 |
.BR sane\-plustek (5) |
| 458 |
for details. |
| 459 |
.TP |
| 460 |
.B plustek_pp |
| 461 |
Supports Plustek parallel port flatbed scanners using the Plustek ASIC P96001, |
| 462 |
P96003, P98001 and P98003, which includes some |
| 463 |
models from Plustek, KYE/Genius, Primax. See |
| 464 |
.BR sane\-plustek_pp (5) |
| 465 |
for details. |
| 466 |
.TP |
| 467 |
.B ricoh |
| 468 |
Supports the Ricoh flatbed scanners IS50 and IS60. See |
| 469 |
.BR sane\-ricoh (5) |
| 470 |
for details. |
| 471 |
.TP |
| 472 |
.B ricoh2 |
| 473 |
Supports the Ricoh flatbed scanners: SG-3100SNw, SP-100SU, and SP-111SU. See |
| 474 |
.BR sane\-ricoh2 (5) |
| 475 |
for details. |
| 476 |
.TP |
| 477 |
.B s9036 |
| 478 |
Supports Siemens 9036 flatbed scanners. See |
| 479 |
.BR sane\-s9036 (5) |
| 480 |
for details. |
| 481 |
.TP |
| 482 |
.B sceptre |
| 483 |
Supports the Sceptre S1200 flatbed scanner. See |
| 484 |
.BR sane\-sceptre (5) |
| 485 |
for details. |
| 486 |
.TP |
| 487 |
.B sharp |
| 488 |
Supports Sharp SCSI scanners. See |
| 489 |
.BR sane\-sharp (5) |
| 490 |
for details. |
| 491 |
.TP |
| 492 |
.B sm3600 |
| 493 |
Supports the Microtek ScanMaker 3600 USB scanner. See |
| 494 |
.BR sane\-sm3600 (5) |
| 495 |
for details. |
| 496 |
.TP |
| 497 |
.B sm3840 |
| 498 |
Supports the Microtek ScanMaker 3840 USB scanner. See |
| 499 |
.BR sane\-sm3840 (5) |
| 500 |
for details. |
| 501 |
.TP |
| 502 |
.B snapscan |
| 503 |
Supports AGFA SnapScan flatbed scanners including some which are |
| 504 |
rebadged to other brands. See |
| 505 |
.BR sane\-snapscan (5) |
| 506 |
for details. |
| 507 |
.TP |
| 508 |
.B sp15c |
| 509 |
Supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See |
| 510 |
.BR sane\-sp15c (5) |
| 511 |
for details. |
| 512 |
.TP |
| 513 |
.B st400 |
| 514 |
Supports the Siemens ST400 and ST800. See |
| 515 |
.BR sane\-st400 (5) |
| 516 |
for details. |
| 517 |
.TP |
| 518 |
.B tamarack |
| 519 |
Supports Tamarack Artiscan flatbed scanners. See |
| 520 |
.BR sane\-tamarack (5) |
| 521 |
for details. |
| 522 |
.TP |
| 523 |
.B teco1 teco2 teco3 |
| 524 |
Supports some TECO scanners, usually sold under the Relisys, Trust, |
| 525 |
Primax, Piotech, Dextra names. See |
| 526 |
.BR sane\-teco1 (5), |
| 527 |
.BR sane\-teco2 (5) |
| 528 |
and |
| 529 |
.BR sane\-teco3 (5) |
| 530 |
for details. |
| 531 |
.TP |
| 532 |
.B u12 |
| 533 |
Supports USB flatbed scanners based on Plustek's ASIC 98003 |
| 534 |
(parallel-port ASIC) and a GeneSys Logics' USB-parport bridge chip like the |
| 535 |
Plustek OpticPro U(T)12. See |
| 536 |
.BR sane\-u12 (5) |
| 537 |
for details. |
| 538 |
.TP |
| 539 |
.B umax |
| 540 |
Supports UMAX-SCSI-scanners and some Linotype Hell SCSI-scanners. See |
| 541 |
.BR sane\-umax (5) |
| 542 |
for details. |
| 543 |
.TP |
| 544 |
.B umax_pp |
| 545 |
Supports Umax parallel port flatbed scanners and the HP 3200C. See |
| 546 |
.BR sane\-umax_pp (5) |
| 547 |
for details. |
| 548 |
.TP |
| 549 |
.B umax1200u |
| 550 |
Supports the UMAX Astra 1220U (USB) flatbed scanner |
| 551 |
(and also the UMAX Astra 2000U, sort of). See |
| 552 |
.BR sane\-umax1220u (5) |
| 553 |
for details. |
| 554 |
.TP |
| 555 |
.B xerox_mfp |
| 556 |
Supports multiple Samsung-based Samsung, Xerox, and Dell |
| 557 |
scanners. See |
| 558 |
.BR sane\-xerox_mfp (5) |
| 559 |
for details. |
| 560 |
.PP |
| 561 |
Also, have a look at the backend information page at |
| 562 |
.I http://www.sane\-project.org/sane\-supported\-devices.html |
| 563 |
and the list of projects in |
| 564 |
.IR /usr/share/doc/libsane/PROJECTS . |
| 565 |
|
| 566 |
.SH "BACKENDS FOR DIGITAL CAMERAS" |
| 567 |
.TP 2 |
| 568 |
.B dc210 |
| 569 |
Supports the Kodak DC210 Digital Camera. See |
| 570 |
.BR sane\-dc210 (5). |
| 571 |
.TP |
| 572 |
.B dc240 |
| 573 |
Supports the Kodak DC240 Digital Camera. See |
| 574 |
.BR dc240 (5). |
| 575 |
.TP |
| 576 |
.B dc25 |
| 577 |
Supports Kodak DC20/DC25 Digital Cameras. See |
| 578 |
.BR dc25 (5). |
| 579 |
.TP |
| 580 |
.B dmc |
| 581 |
Supports the Polaroid Digital Microscope Camera. See |
| 582 |
.BR dmc (5). |
| 583 |
.TP |
| 584 |
.B gphoto2 |
| 585 |
Supports digital cameras supported by the gphoto2 library package. (See |
| 586 |
.I http://www.gphoto.org |
| 587 |
for more information and a list of supported cameras.) Gphoto2 supports over |
| 588 |
140 different camera models. However, please note that more development and |
| 589 |
testing is needed before all of these cameras will be supported by |
| 590 |
.B SANE |
| 591 |
backend. See |
| 592 |
.BR gphoto2 (5). |
| 593 |
.TP |
| 594 |
.B qcam |
| 595 |
Supports Connectix QuickCam cameras. See |
| 596 |
.BR qcam (5). |
| 597 |
.TP |
| 598 |
.B stv680 |
| 599 |
Supports webcams with a stv680 chip. See |
| 600 |
.BR stv680 (5) |
| 601 |
for details. |
| 602 |
.PP |
| 603 |
Also, have a look at the backend information page at |
| 604 |
.I http://www.sane\-project.org/sane\-supported\-devices.html |
| 605 |
and the list of projects in |
| 606 |
.IR /usr/share/doc/libsane/PROJECTS . |
| 607 |
|
| 608 |
.SH "MISCELLANEOUS BACKENDS" |
| 609 |
.TP 2 |
| 610 |
.B dll |
| 611 |
Implements a |
| 612 |
.B SANE |
| 613 |
backend that provides access to an arbitrary number of other |
| 614 |
.B SANE |
| 615 |
backends by dynamic loading. See |
| 616 |
.BR sane\-dll (5). |
| 617 |
.TP |
| 618 |
.B net |
| 619 |
The |
| 620 |
.B SANE |
| 621 |
network daemon |
| 622 |
.BR saned (8) |
| 623 |
provides access to scanners located on different |
| 624 |
computers in connection with the |
| 625 |
.BR sane\-net (5) |
| 626 |
backend. See |
| 627 |
.BR saned (8). |
| 628 |
.TP |
| 629 |
.B pnm |
| 630 |
PNM image reader pseudo-backend. The purpose of this backend is primarily to |
| 631 |
aid in debugging of |
| 632 |
.B SANE |
| 633 |
frontends. See |
| 634 |
.BR sane\-pnm (5). |
| 635 |
.TP |
| 636 |
.B pint |
| 637 |
Supports scanners that use the |
| 638 |
.B PINT |
| 639 |
(Pint Is Not Twain) device driver. The |
| 640 |
.B PINT |
| 641 |
driver is being actively developed on the OpenBSD platform, and has been |
| 642 |
ported to a few other *NIX-like operating systems. See |
| 643 |
.BR sane\-pint (5). |
| 644 |
.TP |
| 645 |
.B test |
| 646 |
Tests frontends and the |
| 647 |
.B SANE |
| 648 |
installation. It provides test pictures and various test options. See |
| 649 |
.BR sane\-test (5). |
| 650 |
.TP |
| 651 |
.B v4l |
| 652 |
Provides generic access to video cameras and similar equipment |
| 653 |
using the |
| 654 |
.B V4L |
| 655 |
(Video for Linux) API. See |
| 656 |
.BR sane\-v4l (5) . |
| 657 |
.PP |
| 658 |
Also, have a look at the backend information page at |
| 659 |
.I http://www.sane\-project.org/sane\-supported\-devices.html |
| 660 |
and the list of projects in |
| 661 |
.IR /usr/share/doc/libsane/PROJECTS . |
| 662 |
|
| 663 |
.SH "CHANGING THE TOP-LEVEL BACKEND" |
| 664 |
By default, all |
| 665 |
.B SANE |
| 666 |
backends (drivers) are loaded dynamically by the |
| 667 |
.B sane\-dll |
| 668 |
meta backend. If you have any questions about the dynamic loading, read |
| 669 |
.BR sane\-dll (5). |
| 670 |
.B SANE |
| 671 |
frontends can also be linked to other backends directly by copying or linking a |
| 672 |
backend to |
| 673 |
.B libsane.so |
| 674 |
in |
| 675 |
.IR /usr/lib/x86_64-linux-gnu/sane . |
| 676 |
.PP |
| 677 |
|
| 678 |
.SH "DEVELOPER'S DOCUMENTATION" |
| 679 |
It's not hard to write a |
| 680 |
.B SANE |
| 681 |
backend. It can take some time, however. You should have basic knowledge of C |
| 682 |
and enough patience to work through the documentation and find out how your |
| 683 |
scanner works. Appended is a list of some documents that help to write backends |
| 684 |
and frontends. |
| 685 |
.PP |
| 686 |
The |
| 687 |
.B SANE |
| 688 |
standard defines the application programming interface (API) that is used to |
| 689 |
communicate between frontends and backends. It can be found at |
| 690 |
.I http://sane\-project.gitlab.io/standard/ . |
| 691 |
.PP |
| 692 |
There is some more information for programmers in |
| 693 |
.IR /usr/share/doc/libsane/backend\-writing.txt . |
| 694 |
Most of the internal |
| 695 |
.B SANE |
| 696 |
routines |
| 697 |
.RB ( sanei ) |
| 698 |
are documented using doxygen: |
| 699 |
.IR http://www.sane\-project.org/sanei/ . |
| 700 |
Before a new backend or frontend project is started, have a look at |
| 701 |
.I /usr/share/doc/libsane/PROJECTS |
| 702 |
for projects that are planned or not yet included into the |
| 703 |
.B SANE |
| 704 |
distribution and at our bug-tracking system: |
| 705 |
.IR http://www.http://www.sane\-project.org/bugs.html . |
| 706 |
.PP |
| 707 |
There are some links on how to find out about the protocol of a scanner: |
| 708 |
.IR http://www.meier\-geinitz.de/sane/misc/develop.html . |
| 709 |
|
| 710 |
.PP |
| 711 |
If you start writing a backend or frontend or any other part of |
| 712 |
.BR SANE, |
| 713 |
please contact the sane\-devel mailing list for coordination so |
| 714 |
that work is not duplicated. |
| 715 |
|
| 716 |
.SH "FILES" |
| 717 |
.TP |
| 718 |
.I /etc/sane.d/*.conf |
| 719 |
The backend configuration files. |
| 720 |
.TP |
| 721 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-*.a |
| 722 |
The static libraries implementing the backends. |
| 723 |
.TP |
| 724 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-*.so |
| 725 |
The shared libraries implementing the backends (present on systems that |
| 726 |
support dynamic loading). |
| 727 |
.TP |
| 728 |
.I /usr/share/doc/libsane/* |
| 729 |
.B SANE |
| 730 |
documentation: The READMEs, text files for backends etc. |
| 731 |
|
| 732 |
.SH "PROBLEMS" |
| 733 |
If your device isn't found but you know that it is supported, make |
| 734 |
sure that it is detected by your operating system. For SCSI and USB scanners, |
| 735 |
use the |
| 736 |
.BR sane\-find\-scanner (1) |
| 737 |
utility. |
| 738 |
It prints one line for each scanner it has detected and some comments (#). |
| 739 |
If |
| 740 |
.BR sane\-find\-scanner (1) |
| 741 |
finds your scanner only as root but not as normal user, the permissions for |
| 742 |
the device files are not adjusted correctly. If the scanner isn't found at all, |
| 743 |
the operating system hasn't detected it and may need some help. Depending on |
| 744 |
the type of your scanner, read |
| 745 |
.BR sane\-usb (5) |
| 746 |
or |
| 747 |
.BR sane\-scsi (5). |
| 748 |
If your scanner (or other device) is not connected over the SCSI bus or USB, |
| 749 |
read the backend's manual page for details on how to set it up. |
| 750 |
.PP |
| 751 |
|
| 752 |
Is your scanner detected by the operating system but not by |
| 753 |
.BR SANE ? |
| 754 |
Try |
| 755 |
.IR "scanimage\ \-L" . |
| 756 |
If the scanner is not found, check that the backend's name is mentioned in |
| 757 |
.IR /etc/sane.d/dll.conf . |
| 758 |
Some backends are commented out by default. Remove the comment sign for your |
| 759 |
backend in this case. Also some backends aren't compiled at all if one of their |
| 760 |
prerequisites are missing. Examples include dc210, dc240, canon_pp, hpsj5s, |
| 761 |
gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you need one of these |
| 762 |
backends and it isn't available, read the build instructions in the |
| 763 |
.B README |
| 764 |
file and the individual manual pages of the backends. |
| 765 |
.PP |
| 766 |
|
| 767 |
Another reason for not being detected by |
| 768 |
.I scanimage\ \-L |
| 769 |
may be a missing or incorrect configuration in the backend's configuration |
| 770 |
file. While |
| 771 |
.B SANE |
| 772 |
tries to automatically find most scanners, some can't be setup correctly |
| 773 |
without the intervention of the administrator. Also on some operating systems |
| 774 |
auto-detection may not work. Check the backend's manual page for details. |
| 775 |
.PP |
| 776 |
If your scanner is still not found, try |
| 777 |
setting the various environment variables that are available to assist in |
| 778 |
debugging. The environment variables are documented in the |
| 779 |
relevant manual pages. For example, to get the maximum amount of debug |
| 780 |
information when testing a Mustek SCSI scanner, set environment variables |
| 781 |
.BR SANE_DEBUG_DLL ", " SANE_DEBUG_MUSTEK ", and " SANE_DEBUG_SANEI_SCSI |
| 782 |
to 128 and then invoke |
| 783 |
.IR scanimage\ \-L . |
| 784 |
The |
| 785 |
.B SANE_DEBUG_DLL |
| 786 |
messages tell if the |
| 787 |
.BR sane\-mustek (5) |
| 788 |
backend was found and loaded at all. The |
| 789 |
.B SANE_DEBUG_MUSTEK |
| 790 |
messages explain what the backend is |
| 791 |
doing while the |
| 792 |
.B SANE_DEBUG_SCSI |
| 793 |
debugging shows the low level handling. If you can't find |
| 794 |
out what's going on by checking the messages carefully, contact the sane\-devel |
| 795 |
mailing list for help (see REPORTING BUGS below). |
| 796 |
.PP |
| 797 |
Now that your scanner is found by |
| 798 |
.IR "scanimage\ \-L" , |
| 799 |
try to do a scan: |
| 800 |
.IR "scanimage\ >image.pnm" . |
| 801 |
This command starts a scan for the default scanner with default settings. All |
| 802 |
the available options are listed by running |
| 803 |
.IR "scanimage\ \-\-help" . |
| 804 |
If scanning aborts with an error message, turn on debugging as mentioned |
| 805 |
above. Maybe the configuration file needs some tuning, e.g. to setup the path |
| 806 |
to a firmware that is needed by some scanners. See the backend's manual page |
| 807 |
for details. If you can't find out what's wrong, contact sane\-devel. |
| 808 |
.PP |
| 809 |
To check that the |
| 810 |
.B SANE |
| 811 |
libraries are installed correctly you can use the test backend, even if you |
| 812 |
don't have a scanner or other |
| 813 |
.B SANE |
| 814 |
device: |
| 815 |
.IP |
| 816 |
scanimage \-d test \-T |
| 817 |
.PP |
| 818 |
You should get a list of PASSed tests. You can do the same with your backend |
| 819 |
by changing "test" to your backend's name. |
| 820 |
.PP |
| 821 |
So now scanning with |
| 822 |
.B scanimage (1) |
| 823 |
works and you want to use one of the graphical frontends like |
| 824 |
.BR xsane (1) , |
| 825 |
.BR xscanimage (1) ", or" |
| 826 |
.BR quiteinsane (1) |
| 827 |
but those frontends don't detect your scanner? One reason may be that you |
| 828 |
installed two versions of |
| 829 |
.BR SANE . |
| 830 |
E.g. the version that was installed by your distribution in |
| 831 |
.I /usr |
| 832 |
and one you installed from source in |
| 833 |
.IR /usr/local/ . |
| 834 |
Make sure that only one version is installed. Another possible reason is, that |
| 835 |
your system's dynamic loader can't find the |
| 836 |
.B SANE |
| 837 |
libraries. For Linux, make sure that |
| 838 |
.I /etc/ld.so.conf |
| 839 |
contains |
| 840 |
.I /usr/local/lib |
| 841 |
and does |
| 842 |
.B not |
| 843 |
contain |
| 844 |
.IR /usr/local/lib/sane . |
| 845 |
See also the documentation of the frontends. |
| 846 |
.PP |
| 847 |
|
| 848 |
.SH "HOW CAN YOU HELP SANE" |
| 849 |
We appreciate any help we can get. Please have a look at our web page about |
| 850 |
contributing to |
| 851 |
.BR SANE : |
| 852 |
.I http://www.sane\-project.org/contrib.html |
| 853 |
.PP |
| 854 |
|
| 855 |
.SH "CONTACT" |
| 856 |
For reporting bugs or requesting new features, please use our bug-tracking |
| 857 |
system: |
| 858 |
.IR http://www.sane\-project.org/bugs.html . |
| 859 |
You can also contact the author of your backend directly. Usually the email |
| 860 |
address can be found in the |
| 861 |
.I /usr/share/doc/libsane/AUTHORS |
| 862 |
file or the backend's manpage. For general discussion about SANE, please use |
| 863 |
the |
| 864 |
.B SANE |
| 865 |
mailing list sane\-devel (see |
| 866 |
.I http://www.sane\-project.org/mailing\-lists.html |
| 867 |
for details). |
| 868 |
.PP |
| 869 |
|
| 870 |
.SH "SEE ALSO" |
| 871 |
.BR saned (8), |
| 872 |
.BR sane\-find\-scanner (1), |
| 873 |
.BR scanimage (1), |
| 874 |
.BR sane\-abaton (5), |
| 875 |
.BR sane\-agfafocus (5), |
| 876 |
.BR sane\-apple (5), |
| 877 |
.BR sane\-artec (5), |
| 878 |
.BR sane\-artec_eplus48u (5), |
| 879 |
.BR sane\-as6e (5), |
| 880 |
.BR sane\-avision (5), |
| 881 |
.BR sane\-bh (5), |
| 882 |
.BR sane\-canon (5), |
| 883 |
.BR sane\-canon630u (5), |
| 884 |
.BR sane\-canon_dr (5), |
| 885 |
.BR sane\-canon_pp (5), |
| 886 |
.BR sane\-cardscan (5), |
| 887 |
.BR sane\-coolscan (5), |
| 888 |
.BR sane\-coolscan2 (5), |
| 889 |
.BR sane\-coolscan3 (5), |
| 890 |
.BR sane\-dc210 (5), |
| 891 |
.BR sane\-dc240 (5), |
| 892 |
.BR sane\-dc25 (5), |
| 893 |
.BR sane\-dll (5), |
| 894 |
.BR sane\-dmc (5), |
| 895 |
.BR sane\-epson (5), |
| 896 |
.BR sane\-epson2 (5), |
| 897 |
.BR sane\-escl (5), |
| 898 |
.BR sane\-fujitsu (5), |
| 899 |
.BR sane\-genesys (5), |
| 900 |
.BR sane\-gphoto2 (5), |
| 901 |
.BR sane\-gt68xx (5), |
| 902 |
.BR sane\-hp (5), |
| 903 |
.BR sane\-hpsj5s (5), |
| 904 |
.BR sane\-hp3500 (5), |
| 905 |
.BR sane\-hp3900 (5), |
| 906 |
.BR sane\-hp4200 (5), |
| 907 |
.BR sane\-hp5400 (5), |
| 908 |
.BR sane\-hpljm1005 (5), |
| 909 |
.BR sane\-ibm (5), |
| 910 |
.BR sane\-kodak (5), |
| 911 |
.BR sane\-leo (5), |
| 912 |
.BR sane\-lexmark (5), |
| 913 |
.BR sane\-lexmark_x2600 (5), |
| 914 |
.BR sane\-ma1509 (5), |
| 915 |
.BR sane\-matsushita (5), |
| 916 |
.BR sane\-microtek2 (5), |
| 917 |
.BR sane\-microtek (5), |
| 918 |
.BR sane\-mustek (5), |
| 919 |
.BR sane\-mustek_pp (5), |
| 920 |
.BR sane\-mustek_usb (5), |
| 921 |
.BR sane\-mustek_usb2 (5), |
| 922 |
.BR sane\-nec (5), |
| 923 |
.BR sane\-net (5), |
| 924 |
.BR sane\-niash (5), |
| 925 |
.BR sane\-pie (5), |
| 926 |
.BR sane\-pint (5), |
| 927 |
.BR sane\-plustek (5), |
| 928 |
.BR sane\-plustek_pp (5), |
| 929 |
.BR sane\-pnm (5), |
| 930 |
.BR sane\-qcam (5), |
| 931 |
.BR sane\-ricoh (5), |
| 932 |
.BR sane\-ricoh2 (5), |
| 933 |
.BR sane\-s9036 (5), |
| 934 |
.BR sane\-sceptre (5), |
| 935 |
.BR sane\-scsi (5), |
| 936 |
.BR sane\-sharp (5), |
| 937 |
.BR sane\-sm3600 (5), |
| 938 |
.BR sane\-sm3840 (5), |
| 939 |
.BR sane\-snapscan (5), |
| 940 |
.BR sane\-sp15c (5), |
| 941 |
.BR sane\-st400 (5), |
| 942 |
.BR sane\-stv680 (5), |
| 943 |
.BR sane\-tamarack (5), |
| 944 |
.BR sane\-teco1 (5), |
| 945 |
.BR sane\-teco2 (5), |
| 946 |
.BR sane\-teco3 (5), |
| 947 |
.BR sane\-test (5), |
| 948 |
.BR sane\-u12 (5), |
| 949 |
.BR sane\-umax1220u (5), |
| 950 |
.BR sane\-umax (5), |
| 951 |
.BR sane\-umax_pp (5), |
| 952 |
.BR sane\-usb (5), |
| 953 |
.BR sane\-v4l (5), |
| 954 |
.BR sane\-xerox_mfp (5) |
| 955 |
|
| 956 |
.SH AUTHOR |
| 957 |
David Mosberger-Tang and many many more (see |
| 958 |
.I /usr/share/doc/libsane/AUTHORS |
| 959 |
for details). This man page was written by Henning Meier-Geinitz. Quite a lot |
| 960 |
of text was taken from the |
| 961 |
.B SANE |
| 962 |
standard, several man pages, and README files. |