sane-u12 man page on OpenMandriva

Man page or keyword search:  
man Server   8135 pages
apropos Keyword Search (all sections)
Output format
OpenMandriva logo
[printable version]

sane-u12(5)		 SANE Scanner Access Now Easy		   sane-u12(5)

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

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

SUPPORTED DEVICES
       The  backend  is	 able  to support some early Plustek USB scanner based
       their old parport design around the ASIC 98003 and other rebadged Plus‐
       tek devices. The following tables will give you a short overview.

       If  your Plustek scanner has another Product ID, then the device is NOT
       supported by this backend.

       Vendor Plustek - ID: 0x07B3
       ----------------------------------------------------------
       Model:			Vendor-ID:	 Product-ID:
       ----------------------------------------------------------
       OpticPro U12		0x07B3		 0x0001
       OpticPro U1212		0x07B3		 0x0001
       OpticPro UT12		0x07B3		 0x0001

       Vendor KYE/Genius
       --------------------------------------------------------
       USB Model:		Vendor-ID:	 Product-ID:
       --------------------------------------------------------
       ColorPage Vivid III USB	0x07B3		 0x0001
       ColorPage HR6 V1		0x0458		 0x2004

CONFIGURATION
       To use your scanner with this backend, you need at least two entries in
       the configuration file /etc/sane.d/u12.conf
	      [usb] vendor-id product-id
	      device /dev/usbscanner

       [usb]  tells the backend, that the following devicename (here /dev/usb‐
       scanner) has to be interpreted as USB scanner device.  If  vendor-  and
       product-id  has not been specified, the backend tries to detect this by
       its own. If device is set to auto then  the  next  matching  device  is
       used.

       The Options:

       option warmup t
	      t specifies the warmup period in seconds

       option lampOff t
	      t	 is the time in seconds for switching off the lamps in standby
	      mode

       option lOffonEnd b
	      b specifies the behaviour when closing the backend, 1 --> switch
	      lamps off, 0 --> do not change lamp status

       See the u12.conf file for examples.

       Note:
       You  have  to make sure, that the USB subsystem is loaded correctly and
       you have access to the device-node. For more details see	 sane-usb  (5)
       manpage.	 You might use sane-find-scanner to check that you have access
       to your device.

       Note:
       If there's no configuration file, the backend defaults to device auto

FILES
       /etc/sane.d/u12.conf
	      The backend configuration file

       /usr/lib64/sane/libsane-u12.a
	      The static library implementing this backend.

       /usr/lib64/sane/libsane-u12.so
	      The shared library implementing this backend (present on systems
	      that support dynamic loading).

ENVIRONMENT
       SANE_CONFIG_DIR
	      This environment variable specifies the list of directories that
	      may contain the configuration file.  Under UNIX, the directories
	      are  separated  by a colon (`:'), under OS/2, they are separated
	      by a semi-colon (`;').  If this variable is not set, the config‐
	      uration  file is searched in two default directories: first, the
	      current working directory (".") and then in /etc/sane.d.	If the
	      value  of the environment variable ends with the directory sepa‐
	      rator character, then the default directories are searched after
	      the  explicitly  specified  directories.	 For  example, setting
	      SANE_CONFIG_DIR to "/tmp/config:" would  result  in  directories
	      "tmp/config",  ".",  and	"/etc/sane.d"  being searched (in this
	      order).

       SANE_DEBUG_U12
	      If the library was compiled with	debug  support	enabled,  this
	      environment  variable controls the debug level for this backend.
	      Higher debug levels increase the verbosity of the output.

	      Example: export SANE_DEBUG_U12=10

SEE ALSO
       sane(7), sane-usb(5), sane-plustek(5),
       /usr/doc/sane-1.0.24/u12/U12.changes
       http://www.gjaeger.de/scanner/u12/

CONTACT AND BUG-REPORTS
       Please send any information and bug-reports to:
       SANE Mailing List

       Additional info and hints can be obtained from our
       Mailing-List archive at:
       http://www.sane-project.org/mailing-lists.html

       or directly from the projects' homepage at:
       http://www.gjaeger.de/scanner/u12/

       To obtain debug messages from the backend, please set the  environment-
       variable	 SANE_DEBUG_U12	 before	 calling  your	favorite scan-frontend
       (i.e. xscanimage).
       i.e.: export SANE_DEBUG_U12=20 ; xscanimage

       The value controls the verbosity of the backend.

KNOWN BUGS & RESTRICTIONS
       * The driver is in alpha state, so please don't expect too much!!!

       * When using libusb, it might be, that  the  backend  hangs.   In  that
       case, reconnect the scanner.

				  14 Jul 2008			   sane-u12(5)
[top]

List of man pages available for OpenMandriva

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net