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

NAME

6       sane-u12  -  SANE  backend  for  Plustek USB flatbed scanners, based on
7       older parport designs
8

DESCRIPTION

10       The sane-u12 library implements a SANE (Scanner Access Now Easy)  back‐
11       end  that  provides  access  to USB flatbed scanners based on Plusteks'
12       ASIC 98003 (parallel-port  ASIC)  and  a  GeneSys  Logics'  USB-parport
13       bridge chip.
14
15

SUPPORTED DEVICES

17       The  backend  is  able  to support some early Plustek USB scanners that
18       based their old parport design around the ASIC 98003 and other rebadged
19       Plustek devices. The following tables will give you a short overview.
20
21       If  your Plustek scanner has another Product ID, then the device is NOT
22       supported by this backend.
23
24       Vendor Plustek - ID: 0x07B3
25       ----------------------------------------------------------
26       Model:                   Vendor-ID:       Product-ID:
27       ----------------------------------------------------------
28       OpticPro U12             0x07B3           0x0001
29       OpticPro U1212           0x07B3           0x0001
30       OpticPro UT12            0x07B3           0x0001
31
32       Vendor KYE/Genius
33       --------------------------------------------------------
34       USB Model:               Vendor-ID:       Product-ID:
35       --------------------------------------------------------
36       ColorPage Vivid III USB  0x07B3           0x0001
37       ColorPage HR6 V1         0x0458           0x2004
38

CONFIGURATION

40       To use your scanner with this backend, you need at least two entries in
41       the configuration file /etc/sane.d/u12.conf
42
43              [usb] vendor-id product-id
44              device /dev/usbscanner
45
46       [usb]  tells the backend, that the following devicename (here /dev/usb‐
47       scanner) has to be interpreted as USB scanner device.  If  vendor-  and
48       product-id  has not been specified, the backend tries to detect this by
49       its own. If device is set to auto then  the  next  matching  device  is
50       used.
51
52       The Options:
53
54       option warmup t
55              t specifies the warmup period in seconds
56
57       option lampOff t
58              t  is the time in seconds for switching off the lamps in standby
59              mode
60
61       option lOffonEnd b
62              b specifies the behaviour when closing the backend, 1 --> switch
63              lamps off, 0 --> do not change lamp status
64
65
66       See the u12.conf file for examples.
67
68       Note: You have to make sure, that the USB subsystem is loaded correctly
69       and  you  have  access  to  the  device-node.  For  more  details   see
70       sane-usb(5)  manpage.  You might use sane-find-scanner(1) to check that
71       you have access to your device.
72
73       Note:
74       If there's no configuration file, the backend defaults to device auto
75
76

FILES

78       /etc/sane.d/u12.conf
79              The backend configuration file
80
81       /usr/lib64/sane/libsane-u12.a
82              The static library implementing this backend.
83
84       /usr/lib64/sane/libsane-u12.so
85              The shared library implementing this backend (present on systems
86              that support dynamic loading).
87
88

ENVIRONMENT

90       SANE_CONFIG_DIR
91              This environment variable specifies the list of directories that
92              may contain the configuration file.  On *NIX systems, the direc‐
93              tories are separated by a colon (`:'), under OS/2, they are sep‐
94              arated by a semi-colon (`;').  If this variable is not set,  the
95              configuration  file  is  searched  in  two  default directories:
96              first,  the  current  working  directory  (".")  and   then   in
97              /etc/sane.d.  If the value of the environment variable ends with
98              the directory separator character, then the default  directories
99              are  searched  after  the explicitly specified directories.  For
100              example, setting SANE_CONFIG_DIR to "/tmp/config:" would  result
101              in directories tmp/config, ., and /etc/sane.d being searched (in
102              this order).
103
104       SANE_DEBUG_U12
105              If the library was compiled with debug support enabled, this en‐
106              vironment  variable  controls  the debug level for this backend.
107              Higher debug levels increase the verbosity of the output.
108
109              Example: export SANE_DEBUG_U12=10
110
111

SEE ALSO

113       sane(7), sane-usb(5), sane-plustek(5),  sane-find-scanner(1),  xscanim‐
114       age(1), scanimage(1)
115       /usr/share/doc/sane-backends/u12/U12.changes
116
117

CONTACT AND BUG-REPORTS

119       Please send any information and bug-reports to:
120       SANE Mailing List
121
122       Additional info and hints can be obtained from our
123       Mailing-List archive at:
124       http://www.sane-project.org/mailing-lists.html
125
126       To  obtain debug messages from the backend, please set the environment-
127       variable SANE_DEBUG_U12  before  calling  your  favorite  scan-frontend
128       (i.e.  xscanimage(1)), i.e.:
129
130       export SANE_DEBUG_U12=20 ; xscanimage
131
132       The value controls the verbosity of the backend.
133
134

KNOWN BUGS & RESTRICTIONS

136       * The driver is in alpha state, so please don't expect too much!!!
137
138       *  When  using  libusb,  it  might be, that the backend hangs.  In that
139       case, reconnect the scanner.
140
141
142
143                                  14 Jul 2008                      sane-u12(5)
Impressum