1sane-st400(5) SANE Scanner Access Now Easy sane-st400(5)
2
6 sane-st400 - SANE backend for Siemens ST/Highscan flatbed scanners
7
9 The sane-st400 library implements a SANE (Scanner Access Now Easy)
10 backend that provides access to Siemens ST400 flatbed scanners and com‐
11 patibles. At present, the following scanners are supported by this
12 backend:
13 Siemens ST400 (6 bit gray scale)
15 Siemens ST800 (6 bit gray scale)
16 The driver supports line art and gray scans up to 8bpp.
18 The Siemens ST/Highscan series includes several more models, e.g. the
20 ST300 and ST600. If you own one of these scanners, or a scanner other
21 than the ones listed above that works with this backend, please let us
22 know by sending the scanner's model name, SCSI ID, and firmware revi‐
23 sion to sane-devel@alioth-lists.debian.net. Have a look at
24 http://www.sane-project.org/mailing-lists.html concerning subscription
25 to sane-devel.
26
29 This backend expects device names of the form:
30 special
32 Where special is the path-name for the special device that corresponds
34 to a SCSI scanner. For SCSI scanners, the special device name must be a
35 generic SCSI device or a symlink to such a device. Under Linux, such a
36 device name could be /dev/sga or /dev/sge, for example. See
37 sane-scsi(5) for details.
38
41 The contents of the st400.conf file is a list of device names that cor‐
42 respond to Siemens scanners. Empty lines and lines starting with a
43 hash mark (#) are ignored. A sample configuration file is shown below:
44 /dev/scanner
46 # this is a comment
47 /dev/sge
48 The default configuration file that is distributed with SANE looks like
50 this:
51 scsi SIEMENS "ST 400" Scanner * * 3 0
53 In this configuration, the driver can only access the ST400 model at
55 SCSI ID 3 LUN 0 (see section BUGS below for the reason). To use the
56 driver with other scanner models, add an appropriate line to the con‐
57 figuration file. For example, to use it with an ST800 at SCSI ID 3 LUN
58 0, add the line:
59 scsi SIEMENS "ST 800" Scanner * * 3 0
61
64 /etc/sane.d/st400.conf
65 The backend configuration file (see also description of
66 SANE_CONFIG_DIR below).
67 /usr/lib64/sane/libsane-st400.a
69 The static library implementing this backend.
70 /usr/lib64/sane/libsane-st400.so
72 The shared library implementing this backend (present on systems
73 that support dynamic loading).
74
76 SANE_CONFIG_DIR
77 This environment variable specifies the list of directories that
78 may contain the configuration file. On *NIX systems, the direc‐
79 tories are separated by a colon (`:'), under OS/2, they are sep‐
80 arated by a semi-colon (`;'). If this variable is not set, the
81 configuration file is searched in two default directories:
82 first, the current working directory (".") and then in
83 /etc/sane.d. If the value of the environment variable ends with
84 the directory separator character, then the default directories
85 are searched after the explicitly specified directories. For
86 example, setting SANE_CONFIG_DIR to "/tmp/config:" would result
87 in directories tmp/config, ., and /etc/sane.d being searched (in
88 this order).
89 SANE_DEBUG_ST400
91 If the library was compiled with debug support enabled, this en‐
92 vironment variable controls the debug level for this backend.
93 E.g., a value of 128 requests all debug output to be printed.
94 Smaller levels reduce verbosity.
95
98 Everything but the most basic stuff.
99
102 Currently, the backend does not check if the attached device really is
103 a ST400. It will happily accept everything that matches the configura‐
104 tion entries. This makes it easy to test the backend with other scan‐
105 ners: Just add an appropriate line to the configuration file. The con‐
106 figuration file as distributed (see above) only works with the ST400.
107 Be careful: If there is no config file at all, the backend defaults to
108 /dev/scanner.
109 The ST400 answers on all eight SCSI LUNs. Normally this is not a prob‐
111 lem, as LUN support is usually disabled in SCSI drivers, but if you are
112 seeing multiple instances of the scanner in a device list, either dis‐
113 able LUNs in your SCSI setup or change the entry in the configuration
114 file to match LUN 0 only.
115
118 If you encounter a bug please set the environment variable SANE_DE‐
119 BUG_ST400 to 128 and try to regenerate the problem. Then send me a re‐
120 port with the log attached.
121 If you encounter a SCSI bus error or trimmed and/or displaced images
123 please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
124 before sending me the report.
125
128 sane(7), sane-scsi(5)
129 http://www.informatik.uni-oldenburg.de/~ingo/sane/
130
133 Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
134 14 Jul 2008 sane-st400(5)