sane-u12(5)

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 scanner based
18       their old parport design around the ASIC 98003 and other rebadged Plus‐
19       tek 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              [usb] vendor-id product-id
43              device /dev/usbscanner
44
45       [usb]  tells the backend, that the following devicename (here /dev/usb‐
46       scanner) has to be interpreted as USB scanner device.  If  vendor-  and
47       product-id  has not been specified, the backend tries to detect this by
48       its own. If device is set to auto then  the  next  matching  device  is
49       used.
50
51       The Options:
52
53       option warmup t
54              t specifies the warmup period in seconds
55
56       option lampOff t
57              t  is the time in seconds for switching off the lamps in standby
58              mode
59
60       option lOffonEnd b
61              b specifies the behaviour when closing the backend, 1 --> switch
62              lamps off, 0 --> do not change lamp status
63
64
65       See the u12.conf file for examples.
66
67       Note:
68       You  have  to make sure, that the USB subsystem is loaded correctly and
69       you have access to the device-node. For more details see  sane-usb  (5)
70       manpage.  You might use sane-find-scanner to check that you have access
71       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.  Under UNIX, the directories
93              are  separated  by a colon (`:'), under OS/2, they are separated
94              by a semi-colon (`;').  If this variable is not set, the config‐
95              uration  file is searched in two default directories: first, the
96              current working directory (".") and then in /etc/sane.d.  If the
97              value  of the environment variable ends with the directory sepa‐
98              rator character, then the default directories are searched after
99              the  explicitly  specified  directories.   For  example, setting
100              SANE_CONFIG_DIR to "/tmp/config:" would  result  in  directories
101              "tmp/config",  ".",  and  "/etc/sane.d"  being searched (in this
102              order).
103
104       SANE_DEBUG_U12
105              If the library was compiled with  debug  support  enabled,  this
106              environment  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

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       or directly from the projects' homepage at:
127       http://www.gjaeger.de/scanner/u12/
128
129       To obtain debug messages from the backend, please set the  environment-
130       variable  SANE_DEBUG_U12  before  calling  your  favorite scan-frontend
131       (i.e. xscanimage).
132       i.e.: export SANE_DEBUG_U12=20 ; xscanimage
133
134       The value controls the verbosity of the backend.
135
136

KNOWN BUGS & RESTRICTIONS

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