1sane-avision(5) SANE Scanner Access Now Easy sane-avision(5)
2
3
4
6 sane-avision - SANE backend for original Avision and Avision OEM scan‐
7 ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film
8 scanners.
9
10
12 This file is a short description for the avision-backend shipped with
13 SANE.
14
15
17 The sane-avision library implements a SANE (Scanner Access Now Easy)
18 backend that provides access to various Avision scanners and the Avi‐
19 sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
20
21 It is fully big-endian aware and in every-day use on PowerPC and SPARC
22 systems.
23
24 I suggest you hold one hand on the power-button of the scanner while
25 you try the first scans - especially with film-scanners!
26
27
29 The configuration file for this backend resides in /etc/sane.d/avi‐
30 sion.conf.
31
32 Its contents is a list of device names that correspond to Avision and
33 Avision compatible scanners and backend-options. Empty lines and lines
34 starting with a hash mark (#) are ignored. A sample configuration file
35 is shown below:
36
37 # this is a comment
38
39 option force-a4
40 option force-a3
41 option skip-adf
42 option disable-gamma-table
43 option disable-calibration
44
45 #scsi Vendor Model Type Bus Channel ID LUN
46 scsi AVISION
47 scsi HP
48 scsi /dev/scanner
49 usb 0x03f0 0x0701
50
51
52 force-a4:
53 Forces the backend to overwrite the scanable area returned by
54 the scanner to ISO A4. Scanner that are known to return bogus
55 data are marked in the backend so if you need this option please
56 report this to the backend maintainer. USE WITH CARE!
57
58 force-a3:
59 Forces the backend to overwrite the scanable area returned by
60 the scanner to ISO A3. Scanner that are known to return bogus
61 data are marked in the backend so if you need this option please
62 report this to the backend maintainer. USE WITH CARE!
63
64 skip-adf:
65 Forces the backend to ignore an inconsistent ADF status returned
66 by the scanner (ADF not present, but ADF model number non-zero).
67 Without this option, the backend will make several attempts to
68 reset the ADF and retry the query in this situation, and will
69 fail with a "not supported" error if the ADF still doesn't
70 respond.
71
72 disable-gamma-table:
73 Disables the usage of the scanner's gamma-table. You might try
74 this if your scans hang or only produces random garbage.
75
76 disable-calibration:
77 Disables the scanner's color calibration. You might try this if
78 your scans hang or only produces random garbage.
79
80 Note: Any option above modifies the default code-flow for your scan‐
81 ner. The options should only be used when you encounter problems
82 with the default be- haviour of the backend. Please report the
83 need of options to the backend-author so the backend can be
84 fixed as soon as possible.
85
86
88 This backend expects device names of the form:
89
90 scsi scsi-spec
91
92 usb usb-spec
93
94 Where scsi-spec is the path-name to a special device or a device ID for
95 the device that corresponds to a SCSI scanner. The special device name
96 must be a generic SCSI device or a symlink to such a device, for exam‐
97 ple on Linux "/dev/sga" or "/dev/sg0". The device ID is the ID returned
98 by the scanner, for example "HP" or "AVISION". See sane-scsi(5) for
99 details.
100
101 Note: Since the backend now includes native USB access, it is no
102 longer needed - even considered obsolete - to access USB scanner
103 via the SCSI emulation (named hpusbscsi on Linux) for Avision
104 USB devices such as the HP 53xx, HP 74xx or Minolta film-scan‐
105 ners.
106
107 usb-spec is the USB device name, the vendor/product ID pair or the name
108 used by libusb corresponding to the USB scanner. For example "0x03f0
109 0x0701" or "libusb:002:003". See sane-usb(5) for details.
110
111 The program sane-find-scanner helps to find out the correct scsi or usb
112 device name.
113
114 A list with supported devices is built into the avision backend so nor‐
115 mally specifying an ID should not be necessary.
116
117
119 /etc/sane.d/avision.conf
120 The backend configuration file (see also description of
121 SANE_CONFIG_DIR below).
122
123 /usr/lib64/sane/libsane-avision.a
124 The static library implementing this backend.
125
126 /usr/lib64/sane/libsane-avision.so
127 The shared library implementing this backend (present on systems
128 that support dynamic loading).
129
130
132 SANE_CONFIG_DIR
133 This environment variable specifies the list of directories that
134 may contain the configuration file. Under UNIX, the directories
135 are separated by a colon (`:'), under OS/2, they are separated
136 by a semi-colon (`;'). If this variable is not set, the config‐
137 uration file is searched in two default directories: first, the
138 current working directory (".") and then in /etc/sane.d. If the
139 value of the environment variable ends with the directory sepa‐
140 rator character, then the default directories are searched after
141 the explicitly specified directories. For example, setting
142 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
143 "tmp/config", ".", and "/etc/sane.d" being searched (in this
144 order).
145
146 SANE_DEBUG_AVISION
147 If the library was compiled with debug support enabled, this
148 environment variable controls the debug level for this backend.
149 Higher debug levels increase the verbosity of the output. The
150 debug level 7 is the author's preferred value to debug backend
151 problems.
152
153 Example: export SANE_DEBUG_AVISION=7
154
155
157 sane(7), sane-scsi(5), sane-usb(5)
158 http://exactcode.com/site/open_source/saneavision/
159
160
162 René Rebe
163
165 René Rebe and Meino Christian Cramer
166
167
168
169 11 Jul 2008 sane-avision(5)