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@lists.alioth.debian.org. 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 either the path-name for the special device that cor‐
34 responds to a SCSI scanner. For SCSI scanners, the special device name
35 must be a generic SCSI device or a symlink to such a device. Under
36 Linux, such a device name could be /dev/sga or /dev/sge, for example.
37 See sane-scsi(5) for details.
38
40 The contents of the st400.conf file is a list of device names that cor‐
41 respond to Siemens scanners. Empty lines and lines starting with a
42 hash mark (#) are ignored. A sample configuration file is shown below:
43 /dev/scanner
45 # this is a comment
46 /dev/sge
47 The default configuration file that is distributed with SANE looks like
49 this:
50 scsi SIEMENS "ST 400" Scanner * * 3 0
52 In this configuration, the driver can only access the ST400 model at
54 SCSI ID 3 LUN 0 (see section "BUGS" below for the reason). To use the
55 driver with other scanner models, add an appropriate line to the con‐
56 figuration file. For example, to use it with an ST800 at SCSI ID 3 LUN
57 0, add the line:
58 scsi SIEMENS "ST 800" Scanner * * 3 0
60
63 /etc/sane.d/st400.conf
64 The backend configuration file (see also description of
65 SANE_CONFIG_DIR below).
66 /usr/lib64/sane/libsane-st400.a
68 The static library implementing this backend.
69 /usr/lib64/sane/libsane-st400.so
71 The shared library implementing this backend (present on systems
72 that support dynamic loading).
73
75 SANE_CONFIG_DIR
76 This environment variable specifies the list of directories that
77 may contain the configuration file. Under UNIX, the directories
78 are separated by a colon (`:'), under OS/2, they are separated
79 by a semi-colon (`;'). If this variable is not set, the config‐
80 uration file is searched in two default directories: first, the
81 current working directory (".") and then in /etc/sane.d. If the
82 value of the environment variable ends with the directory sepa‐
83 rator character, then the default directories are searched after
84 the explicitly specified directories. For example, setting
85 SANE_CONFIG_DIR to "/tmp/config:" would result in directories
86 "tmp/config", ".", and "/etc/sane.d" being searched (in this
87 order).
88 SANE_DEBUG_ST400
90 If the library was compiled with debug support enabled, this
91 environment variable controls the debug level for this backend.
92 E.g., a value of 128 requests all debug output to be printed.
93 Smaller levels reduce verbosity.
94
97 Everything but the most basic stuff.
98
101 Currently, the backend does not check if the attached device really is
102 a ST400. It will happily accept everything that matches the configura‐
103 tion entries. This makes it easy to test the backend with other scan‐
104 ners: Just add an appropriate line to the configuration file. The con‐
105 figuration file as distributed (see above) only works with the ST400.
106 Be careful: If there is no config file at all, the backend defaults to
107 /dev/scanner.
108 The ST400 answers on all eight SCSI LUNs. Normally this is not a prob‐
110 lem, as LUN support is usually disabled in SCSI drivers, but if you are
111 seeing multiple instances of the scanner in a device list, either dis‐
112 able LUNs in your SCSI setup or change the entry in the configuration
113 file to match LUN 0 only.
114
117 If you encounter a bug please set the environment variable
118 SANE_DEBUG_ST400 to 128 and try to regenerate the problem. Then send me
119 a report with the log attached.
120 If you encounter a SCSI bus error or trimmed and/or displaced images
122 please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
123 before sending me the report.
124
127 sane(7), sane-scsi(5)
128 http://www.informatik.uni-oldenburg.de/~ingo/sane/
129
132 Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
133 14 Jul 2008 sane-st400(5)