Debian Codegraph @

upstream/debian-unstable/man5/sane-u12.5

raw
1 .TH sane\-u12 5 "14 Jul 2008" "" "SANE Scanner Access Now Easy"
2 .IX sane\-u12
3 .SH NAME
4 sane\-u12 \- SANE backend for Plustek USB flatbed scanners,
5 based on older parport designs
6 .SH DESCRIPTION
7 The
8 .B sane\-u12
9 library implements a SANE (Scanner Access Now Easy) backend that
10 provides access to USB flatbed scanners based on Plusteks' ASIC
11 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
12 bridge chip.
13
14 .SH "SUPPORTED DEVICES"
15 The backend is able to support some early Plustek USB scanners that based
16 their old parport design around the ASIC 98003 and other rebadged
17 Plustek devices. The following tables will give you a short overview.
18
19 If your Plustek scanner has another Product ID, then the device is
20 .B NOT
21 supported by this backend.
22 .br
23
24 Vendor Plustek \- ID: 0x07B3
25 .br
26 .ft CR
27 .nf
28 ----------------------------------------------------------
29 Model: Vendor-ID: Product-ID:
30 ----------------------------------------------------------
31 OpticPro U12 0x07B3 0x0001
32 OpticPro U1212 0x07B3 0x0001
33 OpticPro UT12 0x07B3 0x0001
34 .fi
35 .ft R
36 .PP
37
38 Vendor KYE/Genius
39 .br
40 .ft CR
41 .nf
42 --------------------------------------------------------
43 USB Model: Vendor-ID: Product-ID:
44 --------------------------------------------------------
45 ColorPage Vivid III USB 0x07B3 0x0001
46 ColorPage HR6 V1 0x0458 0x2004
47 .fi
48 .ft R
49 .PP
50
51 .SH "CONFIGURATION"
52 To use your scanner with this backend, you need at least two
53 entries in the configuration file
54 .I /etc/sane.d/u12.conf
55
56 .RS
57 .I [usb] vendor-id product-id
58 .br
59 .I device /dev/usbscanner
60 .RE
61 .PP
62 .I [usb]
63 tells the backend, that the following devicename (here
64 .IR /dev/usbscanner )
65 has to be interpreted as USB scanner device. If vendor- and
66 product-id has not been specified, the backend tries to
67 detect this by its own. If device is set to
68 .I auto
69 then the next matching device is used.
70 .PP
71 .B
72 The Options:
73 .PP
74 option warmup t
75 .RS
76 .I t
77 specifies the warmup period in seconds
78 .RE
79 .PP
80 option lampOff t
81 .RS
82 .I t
83 is the time in seconds for switching off the lamps in
84 standby mode
85 .RE
86 .PP
87 option lOffonEnd b
88 .RS
89 .I b
90 specifies the behaviour when closing the backend, 1 --> switch
91 lamps off, 0 --> do not change lamp status
92 .RE
93
94 .PP
95 See the
96 .I u12.conf
97 file for examples.
98 .PP
99 .B Note:
100 You have to make sure, that the USB subsystem is loaded
101 correctly and you have access to the device-node. For
102 more details see
103 .BR sane\-usb (5)
104 manpage. You might use
105 .BR sane\-find\-scanner (1)
106 to check that you have access to your device.
107 .PP
108 .B Note:
109 .br
110 If there's no configuration file, the backend defaults to
111 .B device auto
112
113 .SH FILES
114 .TP
115 .I /etc/sane.d/u12.conf
116 The backend configuration file
117 .TP
118 .I /usr/lib/x86_64-linux-gnu/sane/libsane\-u12.a
119 The static library implementing this backend.
120 .TP
121 .I /usr/lib/x86_64-linux-gnu/sane/libsane\-u12.so
122 The shared library implementing this backend (present on systems that
123 support dynamic loading).
124
125 .SH ENVIRONMENT
126 .TP
127 .B SANE_CONFIG_DIR
128 This environment variable specifies the list of directories that may
129 contain the configuration file. On *NIX systems, the directories are
130 separated by a colon (`:'), under OS/2, they are separated by a
131 semi-colon (`;'). If this variable is not set, the configuration file
132 is searched in two default directories: first, the current working
133 directory (".") and then in
134 .IR /etc/sane.d .
135 If the value of the
136 environment variable ends with the directory separator character, then
137 the default directories are searched after the explicitly specified
138 directories. For example, setting
139 .B SANE_CONFIG_DIR
140 to "/tmp/config:" would result in directories
141 .IR tmp/config ,
142 .IR . ,
143 and
144 .I /etc/sane.d
145 being searched (in this order).
146 .TP
147 .B SANE_DEBUG_U12
148 If the library was compiled with debug support enabled, this
149 environment variable controls the debug level for this backend. Higher
150 debug levels increase the verbosity of the output.
151
152 Example:
153 export SANE_DEBUG_U12=10
154
155 .SH "SEE ALSO"
156 .BR sane (7),
157 .BR sane\-usb (5),
158 .BR sane\-plustek (5),
159 .BR sane\-find\-scanner (1),
160 .BR xscanimage (1),
161 .BR scanimage (1)
162 .br
163 .I /usr/share/doc/libsane/u12/U12.changes
164
165 .SH "CONTACT AND BUG-REPORTS"
166 Please send any information and bug-reports to:
167 .br
168 .B SANE Mailing List
169 .PP
170 Additional info and hints can be obtained from our mailing-List archive at:
171 .IR http://www.sane\-project.org/mailing\-lists.html .
172 .PP
173 To obtain debug messages from the backend, please set the
174 environment-variable
175 .B SANE_DEBUG_U12
176 before calling your favorite SANE frontend (e.g.
177 .BR xscanimage (1)):
178 .PP
179 .I export SANE_DEBUG_U12=20 ; xscanimage
180 .PP
181 The value controls the verbosity of the backend.
182
183 .SH "KNOWN BUGS & RESTRICTIONS"
184 * The driver is in alpha state, so please don't expect too much!!!
185 .PP
186 * When using libusb, it might be, that the backend hangs.
187 In that case, reconnect the scanner.