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