1sane-fujitsu(5) SANE Scanner Access Now Easy sane-fujitsu(5)
2
3
4
6 sane-fujitsu - SANE backend for Fujitsu flatbed and ADF scanners
7
8
10 The sane-fujitsu library implements a SANE (Scanner Access Now Easy)
11 backend which provides access to most Fujitsu flatbed and ADF scanners.
12
13 This document describes the rewritten backend versions 1.0.21 and
14 greater.
15
16 The backend supports lineart, halftone, grayscale, and color scanning
17 for most USB and SCSI scanners, depending on hardware capabilities.
18 Most simple scanning related features are exposed. This version fea‐
19 tures at least basic support for many more models. See KNOWN ISSUES.
20
21
23 The following scanners are thought to have at least basic scanning
24 capability, either because they have been tested with a prior version,
25 or because documentation indicates they are compatible with a tested
26 model.
27
28 WORKGROUP SIZED SCANNERS:
29 --------------------------------------
30 SCSI: SCSI/USB: USB:
31 ------------ ------------ ------------
32 M3091DC fi-4120C fi-5110C
33 M3092DC fi-4220C fi-5110EOX
34 SP-93GX fi-4120C2
35 fi-4220C2
36 fi-5120C
37 fi-5220C
38
39 DEPARTMENTAL SIZED SCANNERS:
40 --------------------------------------
41 SCSI: SCSI/USB:
42 ------------ ------------
43 M3093GX/DG fi-4340C
44 M3096G/GX fi-4530C
45 M3097G+/DG fi-5530C
46 fi-4640S
47 fi-4750C
48
49 PRODUCTION SIZED SCANNERS:
50 --------------------------------------
51 SCSI: SCSI/USB:
52 ------------ ------------
53 M3099G/GH/GX fi-5650C
54 M4097D fi-5750C
55 fi-4750L fi-5900C
56 fi-4860C
57 M4099D
58
59 The following scanners are known NOT to work with this backend, either
60 because they have a non-fujitsu chipset, or an unsupported interface
61 type. Some of these scanners may be supported by another backend.
62
63 UNSUPPORTED SCANNERS:
64 --------------------------------------
65 SCSI: SERIAL: USB:
66 ------------ ------------ ------------
67 ScanStation M3093E/DE/EX fi-4110EOX2
68 ScanPartner M3096EX fi-4010CU
69 SP-Jr M3097E+/DE
70 SP-10/10C M3099A/EH/EX
71 SP-15C/300C
72 SP-600C/620C
73
74 This backend may support scanners not listed here. The best way to
75 determine level of support is to test the scanner directly. Fujitsu
76 equipment has historically been good enough to not be damaged by incor‐
77 rect commands if the scanner is incompatible. Please contact the
78 author with test results, positive or negative.
79
80
82 A modest effort has been made to expose the standard options to the
83 API. This allows a frontend to set scanning region, resolution, bit-
84 depth, color mode, and enable the automatic document feeder. The
85 fujitsu backend supports the following basic options for most scanners:
86
87 source s
88 Selects the source for the scan. Options may include "Flatbed",
89 "ADF Front", "ADF Back", "ADF Duplex".
90
91 mode m
92 Selects the mode for the scan. Options may include "Lineart",
93 "Halftone", "Gray", and "Color".
94
95 resolution, y-resolution
96 Controls scan resolution. Setting --resolution also sets --y-
97 resolution but not vice versa. This behavior is overridden by
98 some frontends.
99
100 tlx, tly, brx, bry
101 Sets scan area upper left and lower right coordinates. Often
102 converted to t, l, x, y by frontend code.
103
104 pagewidth, pageheight
105 Sets paper size. Used by scanner to determine centering of scan
106 coordinates when using ADF.
107
108 Other options will be available based on the capabilities of the scan‐
109 ner. Use 'scanimage --help' to get a list. Be aware that some options
110 may appear only when another option has been set.
111
113 The configuration file "fujitsu.conf" is used to tell the backend how
114 to look for scanners, and provide options controlling the operation of
115 the backend. This file is read each time the frontend asks the backend
116 for a list of scanners, generally only when the frontend starts. If the
117 configuration file is missing, the backend will use a set of compiled
118 defaults, which are identical to the default configuration file shipped
119 with SANE.
120
121 Scanners can be specified in the configuration file in 4 ways:
122
123 "scsi FUJITSU"
124 Requests backend to search all scsi busses in the system for a
125 device which reports itself to be a scanner made by 'FUJITSU'.
126
127 "scsi /dev/sg0" (or other scsi device file)
128 Requests backend to open the named scsi device. Only useful if
129 you have multiple compatible scanners connected to your system,
130 and need to specify one. Probably should not be used with the
131 other "scsi" line above.
132
133 "usb 0x04c5 0x1042" (or other vendor/product ids)
134 Requests backend to search all usb busses in the system for a
135 device which uses that vendor and product id. The device will
136 then be queried to determine if it is a Fujitsu scanner.
137
138 "usb /dev/usb/scanner0" (or other device file)
139 Some systems use a kernel driver to access usb scanners. This
140 method is untested.
141
142 The only configuration option supported is "buffer-size=xxx", allowing
143 you to set the number of bytes in the data buffer to something other
144 than the compiled-in default, 65536 (64K). Some users report that their
145 scanner will "hang" mid-page, or fail to transmit the image if the buf‐
146 fer is not large enough.
147
148 Note: This option may appear multiple times in the configuration file.
149 It only applies to scanners discovered by 'scsi/usb' lines that follow
150 this option.
151
152 Note: The backend does not place an upper bound on this value, as some
153 users required it to be quite large. Values above the default are not
154 recommended, and may crash your OS or lockup your scsi card driver. You
155 have been warned.
156
158 The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
159 which enables debugging output to stderr. Valid values are:
160
161 5 Errors
162 10 Function trace
163 15 Function detail
164 20 Option commands
165 25 SCSI/USB trace
166 30 SCSI/USB detail
167
168
170 Backend versions prior to this were numbered with a two part version,
171 or with no version number at all. At the time this version was written,
172 all older versions were retroactively renumbered, 1.0.2 - 1.0.20.
173
174 The current backend may have lost support for some feature you were
175 using. The last of the "old" backends, 1.0.20, is still available as
176 source from:
177
178 http://www2.pfeiffer.edu/~anoah/fujitsu/
179
180 If you find that you need to use the older version, please contact the
181 author, to try and get those features restored to a later version.
182
183
185 All IPC, imprinter, and compression options are disabled.
186 Most scanner specific 'quirks' are not accounted for, making it
187 possible to set some options in ways that the scanner does not
188 support.
189 Some flatbed options are affected by adf settings.
190 Any model that does not support VPD during inquiry will not
191 function.
192
193
195 m3091 backend: Frederik Ramm <frederik a t remote d o t org>
196 m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>
197 (with credit to the unnamed author of the coolscan driver)
198 fujitsu backend, 3093, fi-4340C, ipc, cmp, long-time maintainer:
199 Oliver Schirrmeister <oschirr a t abm d o t de>
200 3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc-chemnitz d o t de>
201 fi-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>
202 fi-4120, fi-series color support, backend re-write, current maintainer:
203 M. Allan Noah: <anoah a t pfeiffer d o t edu>
204
205
207 sane(7), sane-scsi(5), sane-usb(5), sane-sp15c(5), sane-avision(5)
208
209
211 M. Allan Noah: <anoah a t pfeiffer d o t edu>
212
213
214
215
216sane-backends 1.0.18 2006-06-06 sane-fujitsu(5)