kopia lustrzana https://gitlab.com/sane-project/website
294 wiersze
13 KiB
HTML
294 wiersze
13 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>sane-plustek.5</TITLE>
|
|
</HEAD>
|
|
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
|
<H1>sane-plustek.5</H1>
|
|
<HR>
|
|
<PRE>
|
|
<!-- Manpage converted by man2html 3.0.1 -->
|
|
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
|
|
|
|
|
</PRE>
|
|
<H2>NAME</H2><PRE>
|
|
sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
|
|
based USB flatbed scanners
|
|
|
|
|
|
</PRE>
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
|
|
backend that provides access to USB flatbed scanners based on National
|
|
Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're look-
|
|
ing for parallel-port support for Plustek scanner please refer to the
|
|
<B>sane-plustek_pp</B> backend.
|
|
|
|
|
|
</PRE>
|
|
<H2>SUPPORTED DEVICES</H2><PRE>
|
|
The Backend is able to support USB scanner based on the National Semi-
|
|
conductor chipsets LM9831, LM9832 and LM9833. The following tables show
|
|
various devices which are currently reported to work. If your Plustek
|
|
scanner has another Product ID, then the device is <B>NOT</B> supported, as it
|
|
contains an unsupported ASIC inside.
|
|
|
|
Vendor Plustek - ID: 0x07B3
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
OpticPro U12 LM9831 600x1200dpi 42bit 512Kb 0x0010
|
|
OpticPro UT12 LM9831 600x1200dpi 42bit 512Kb 0x0013
|
|
OpticPro UT12 LM9832 600x1200dpi 42bit 512Kb 0x0017
|
|
OpticPro UT16 LM9832 600x1200dpi 42bit 512Kb 0x0017
|
|
OpticPro U24 LM9831 1200x2400dpi 42bit 2Mb 0x0011
|
|
OpticPro U24 LM9832 1200x2400dpi 42bit 2Mb 0x0015
|
|
OpticPro UT24 LM9832 1200x2400dpi 42bit 2Mb 0x0017
|
|
|
|
Vendor KYE/Genius - ID: 0x0458
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2007
|
|
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2008
|
|
Colorpage HR6A LM9832 600x1200dpi 42bit 512Kb 0x2009
|
|
Colorpage HR7 LM9832 600x1200dpi 42bit 512Kb 0x2013
|
|
Colorpage HR7LE LM9832 600x1200dpi 42bit 512Kb 0x2015
|
|
Colorpage HR6X LM9832 600x1200dpi 42bit 512Kb 0x2016
|
|
|
|
Vendor Hewlett-Packard - ID: 0x03F0
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
ScanJet 2100C LM9831 600x1200dpi 42bit 512Kb 0x0505
|
|
ScanJet 2200C LM9832 600x1200dpi 42bit 512Kb 0x0605
|
|
|
|
Vendor Mustek - ID: 0x0400
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
|
|
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
|
|
|
|
Vendor UMAX - ID: 0x1606
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
|
|
UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
|
|
|
|
Vendor COMPAQ - ID: 0x049F
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
S4-100 LM9832 600x1200dpi 42bit 512Kb 0x001A
|
|
|
|
Vendor Epson - ID: 0x04B8
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
Perfection 1250 LM9832 1200x2400dpi 42bit 512Kb 0x010F
|
|
Perfection 1260 LM9832 1200x2400dpi 42bit 512Kb 0x011D
|
|
|
|
Vendor CANON - ID: 0x04A9
|
|
----------------------------------------------------------
|
|
USB Model: ASIC: Properties: Prod-ID
|
|
----------------------------------------------------------
|
|
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
|
|
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
|
|
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
|
|
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
|
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
|
|
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
|
|
|
|
|
</PRE>
|
|
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
|
|
For parallelport device support see the <B>plustek_pp</B> backend.
|
|
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
|
|
is supported by the <B>Artec</B> backend.
|
|
Only the National Semiconductor LM983[1/2/] based devices of Plustek
|
|
are supported by this driver. Older versions of the U12, the UT12, the
|
|
U1212 and U1248 (GrandTech chipset) are not supported.
|
|
|
|
Model Chipset backend
|
|
---------------------------
|
|
U1248 GrandTech gt68xx
|
|
UT16B GrandTech gt68xx
|
|
|
|
|
|
</PRE>
|
|
<H2>CONFIGURATION</H2><PRE>
|
|
To use your scanner with this backend, you need at least two entries in
|
|
the configuration file
|
|
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
|
|
|
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
|
|
|
<I>device</I> <I>/dev/usbscanner</I>
|
|
|
|
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
|
|
<I>scanner</I> ) 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 ist set to <I>auto</I>
|
|
then the next matching device is used.
|
|
|
|
<B>The</B> <B>Options:</B>
|
|
|
|
option warmup t
|
|
<I>t</I> specifies the warmup period in seconds
|
|
|
|
option lampOff t
|
|
<I>t</I> is the time in seconds for switching off the lamps in standby
|
|
mode
|
|
|
|
option lOffonEnd b
|
|
<I>b</I> specifies the behaviour when closing the backend, 1 --> switch
|
|
lamps off, 0 --> do not change lamp status
|
|
|
|
option invertNegatives b
|
|
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
|
invert picture
|
|
|
|
option cacheCalData b
|
|
<I>b</I> 0 --> do not save coarse calibration results, 1 --> save
|
|
results of coarse calibration in ~/.sane/ directory
|
|
|
|
option altCalibration b
|
|
<I>b</I> 0 --> use standard calibration routines, 1 --> use alternate
|
|
calibration (only non Plustek
|
|
devices, standard for CIS devices)
|
|
|
|
option skipFine b
|
|
<I>b</I> 0 --> perform fine calibration, 1 --> skip fine calibration
|
|
(only non Plustek devices)
|
|
|
|
option skipFineWhite b
|
|
<I>b</I> 0 --> perform white fine calibration, 1 --> skip white fine
|
|
calibration (only non Plustek devices)
|
|
|
|
option skipCalibration b
|
|
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
|
Plustek devices)
|
|
|
|
option enableTPA b
|
|
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
|
--> override internal tables and allow TPA mode (EPSON only)
|
|
|
|
option posOffX x
|
|
option posOffY y
|
|
option tpaOffX x
|
|
option tpaOffY y
|
|
option negOffX x
|
|
option negOffY y
|
|
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
|
|
positions. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B>
|
|
<B>for</B> <B>this</B> <B>feature.</B>
|
|
|
|
option posShadingY p
|
|
option tpaShadingY p
|
|
option negShadingY p
|
|
<I>p</I> overrides the internal shading position. The values are in
|
|
steps. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B> <B>for</B>
|
|
<B>this</B> <B>feature.</B>
|
|
|
|
option redGamma r
|
|
option greenGamma g
|
|
option blueGamma b
|
|
option grayGamma gr
|
|
<I>r</I> <I>g</I> <I>b</I> <I>gr</I>
|
|
By using these values, the internal linear gamma table (r,g,b,gr = 1.0)
|
|
can be adjusted.
|
|
|
|
option red_gain r
|
|
option green_gain g
|
|
option blue_gain b
|
|
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
|
|
gain values of the AFE for each channel. The range is between 0
|
|
and 63.
|
|
|
|
See the plustek.conf file for examples.
|
|
|
|
<B>Note:</B>
|
|
You have to make sure, that the USB subsystem is loaded correctly and
|
|
the module <I>scanner</I> has been loaded too. To make this module recognize
|
|
your scanner, you might have to add the following line to your
|
|
<B>/etc/modules.conf</B> :
|
|
<I>options</I> <I>scanner</I> <I>vendor=0x7b3</I> <I>product=0x17</I>
|
|
|
|
If you're not sure about the vendor and product id of your device, sim-
|
|
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
|
|
<I>/proc/bus/usb/devices</I> and look for the scanner.
|
|
Alternatively, the backend is able to access your scanner via libusb.
|
|
You might use <B>sane-find-scanner</B> to check that you have access to your
|
|
device.
|
|
|
|
<B>Note:</B>
|
|
If there's no configuration file, the backend defaults to <B>device</B> <B>auto</B>
|
|
|
|
|
|
</PRE>
|
|
<H2>FILES</H2><PRE>
|
|
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
|
The backend configuration file
|
|
|
|
<I>/usr/local/lib/sane/libsane-plustek.a</I>
|
|
The static library implementing this backend.
|
|
|
|
<I>/usr/local/lib/sane/libsane-plustek.so</I>
|
|
The shared library implementing this backend (present on systems
|
|
that support dynamic loading).
|
|
|
|
|
|
</PRE>
|
|
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
|
Please send any information and bug-reports to:
|
|
<B>Plustek</B> <B>Driver</B> <B>Mailing</B> <B>List</B> <B><plustek@linuxhacker.org></B>
|
|
or directly to:
|
|
<B>Gerhard</B> <B>Jaeger</B> <B><gerhard@gjaeger.de></B>
|
|
|
|
Additional info and hints can be obtained from our
|
|
Mailing-List archive at:
|
|
<B>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3</B>
|
|
|
|
or directly from the projects' homepage at:
|
|
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
|
|
|
To obtain debug messages from the backend, please set the environment-
|
|
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
|
|
(i.e. xscanimage).
|
|
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
|
|
|
|
The value controls the verbosity of the backend. Please note, that val-
|
|
ues greater than 19 force the backend to output raw data files, which
|
|
could be rather large. The ending of these files is ".raw". For prob-
|
|
lem reports it should be enough the set the verbosity to 13.
|
|
|
|
|
|
</PRE>
|
|
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
|
|
* The driver does not support these manic scalings up
|
|
to 16 times the physical resolution. The only scaling
|
|
is done on resolutions between the physical resolution
|
|
of the CDD-sensor and the stepper motor i.e. you have a
|
|
600x1200 dpi scanner and you are scanning using 800dpi,
|
|
so scaling is necesary, because the sensor only delivers
|
|
600dpi but the motor is capable to perform 800dpi steps.
|
|
* Plusteks' model policy is somewhat inconsistent. This
|
|
means, they sell technical different devices under the
|
|
same product name. Therefore it is possible that some
|
|
devices like the UT12 or U12 won't work - please check
|
|
the model list above and compare the product-id to
|
|
the one your device has.
|
|
* Negative/Slide scanning quality is poor.
|
|
|
|
sane-backends 1.0.13 27 October 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
|
</PRE>
|
|
<HR>
|
|
<ADDRESS>
|
|
Man(1) output converted with
|
|
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|