1sane-avision(5)          SANE Scanner Access Now Easy          sane-avision(5)
2
3
4

NAME

6       sane-avision  -  SANE  backend for Avision branded and Avision OEM (HP,
7       Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners.
8
9

DESCRIPTION

11       The sane-avision library implements a SANE (Scanner  Access  Now  Easy)
12       backend  that  provides access to various Avision scanners and the Avi‐
13       sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
14
15       It is fully big-endian aware and in everyday use on PowerPC  and  SPARC
16       systems.
17
18       I  suggest  you  hold one hand on the power-button of the scanner while
19       you try the first scans - especially with film-scanners!
20
21

CONFIGURATION

23       The configuration file for this  backend  resides  in  /etc/sane.d/avi‐
24       sion.conf.
25
26       Its  contents  is a list of device names that correspond to Avision and
27       Avision compatible scanners and backend-options. Empty lines and  lines
28       starting  with a hash mark (#) are ignored. A sample configuration file
29       is shown below:
30
31        # this is a comment
32        option force-a4
33        option force-a3
34        option skip-adf
35        option disable-gamma-table
36        option disable-calibration
37        #scsi Vendor Model Type Bus Channel ID LUN
38        scsi AVISION
39        scsi HP
40        scsi /dev/scanner
41        usb 0x03f0 0x0701
42
43
44       force-a4:
45              Forces the backend to overwrite the scanable  area  returned  by
46              the  scanner  to  ISO A4. Scanner that are known to return bogus
47              data are marked in the backend so if you need this option please
48              report this to the backend maintainer. USE WITH CARE!
49
50       force-a3:
51              Forces  the  backend  to overwrite the scanable area returned by
52              the scanner to ISO A3. 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       skip-adf:
57              Forces the backend to ignore an inconsistent ADF status returned
58              by the scanner (ADF not present, but ADF model number non-zero).
59              Without this option, the backend will make several  attempts  to
60              reset  the  ADF  and retry the query in this situation, and will
61              fail with a "not supported" error if the ADF still  doesn't  re‐
62              spond.
63
64       disable-gamma-table:
65              Disables  the  usage of the scanner's gamma-table. You might try
66              this if your scans hang or only produce random garbage.
67
68       disable-calibration:
69              Disables the scanner's color calibration. You might try this  if
70              your scans hang or only produce random garbage.
71
72       Note:  Any  option  above modifies the default code-flow for your scan‐
73              ner. The options should only be used when you encounter problems
74              with the default behavior of the backend. Please report the need
75              of options to the backend-author so the backend can be fixed  as
76              soon as possible.
77
78

DEVICE NAMES

80       This backend expects device names of the form:
81
82              scsi scsi-spec
83
84              usb usb-spec
85
86       Where scsi-spec is the path-name to a special device or a device ID for
87       the device that corresponds to a SCSI scanner. The special device  name
88       must  be a generic SCSI device or a symlink to such a device, for exam‐
89       ple on Linux /dev/sga or /dev/sg0.  The device ID is the ID returned by
90       the  scanner,  for  example "HP" or "AVISION". See sane-scsi(5) for de‐
91       tails.
92
93       Note:  Since the backend now includes  native  USB  access,  it  is  no
94              longer needed - even considered obsolete - to access USB scanner
95              via the SCSI emulation (named hpusbscsi on  Linux)  for  Avision
96              USB  devices  such as the HP 53xx, HP 74xx or Minolta film-scan‐
97              ners.
98
99       usb-spec is the USB device name, the vendor/product ID pair or the name
100       used  by  libusb  corresponding to the USB scanner. For example "0x03f0
101       0x0701" or "libusb:002:003". See sane-usb(5) for details.
102
103       The program sane-find-scanner(1) helps to find out the correct scsi  or
104       usb device name.
105
106       A list with supported devices is built into the avision backend so nor‐
107       mally specifying an ID should not be necessary.
108
109

FILES

111       /etc/sane.d/avision.conf
112              The  backend  configuration  file  (see  also   description   of
113              SANE_CONFIG_DIR below).
114
115       /usr/lib64/sane/libsane-avision.a
116              The static library implementing this backend.
117
118       /usr/lib64/sane/libsane-avision.so
119              The shared library implementing this backend (present on systems
120              that support dynamic loading).
121
122

ENVIRONMENT

124       SANE_CONFIG_DIR
125              This environment variable specifies the list of directories that
126              may contain the configuration file.  On *NIX systems, the direc‐
127              tories are separated by a colon (`:'), under OS/2, they are sep‐
128              arated  by a semi-colon (`;').  If this variable is not set, the
129              configuration file  is  searched  in  two  default  directories:
130              first,   the   current  working  directory  (".")  and  then  in
131              /etc/sane.d.  If the value of the environment variable ends with
132              the  directory separator character, then the default directories
133              are searched after the explicitly  specified  directories.   For
134              example,  setting SANE_CONFIG_DIR to "/tmp/config:" would result
135              in directories tmp/config, ., and /etc/sane.d being searched (in
136              this order).
137
138       SANE_DEBUG_AVISION
139              If the library was compiled with debug support enabled, this en‐
140              vironment variable controls the debug level  for  this  backend.
141              Higher  debug  levels  increase the verbosity of the output. The
142              debug level 7 is the author's preferred value to  debug  backend
143              problems.
144
145              Example: export SANE_DEBUG_AVISION=7
146
147

SEE ALSO

149       sane(7), sane-scsi(5), sane-usb(5)
150       http://exactcode.com/site/open_source/saneavision
151
152

MAINTAINER

154       René Rebe
155
156

AUTHOR

158       René Rebe and Meino Christian Cramer
159
160
161
162                                  11 Jul 2008                  sane-avision(5)
Impressum