kopia lustrzana https://gitlab.com/sane-project/website
502 wiersze
22 KiB
HTML
502 wiersze
22 KiB
HTML
![]() |
<HTML>
|
||
|
<HEAD>
|
||
|
<TITLE>sane-plustek.5</TITLE>
|
||
|
</HEAD>
|
||
|
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../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 Plustek parallel port and USB flatbed
|
||
|
scanners. The USB support is part of the SANE package but for usage
|
||
|
with parallel port scanners you will need a kernel module, called
|
||
|
pt_drv which currently can be downloaded from
|
||
|
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||
|
|
||
|
<B>!!!Please</B> <B>note</B> <B>that</B> <B>you</B> <B>need</B> <B>the</B> <B>kernel</B> <B>module</B> <B>only</B> <B>for</B> <B>parallel</B> <B>port</B>
|
||
|
<B>scanners!!!</B>
|
||
|
|
||
|
|
||
|
</PRE>
|
||
|
<H2>PARALLEL PORT SUPPORT</H2><PRE>
|
||
|
At present, the following scanners should work with this backend and
|
||
|
the corresponding kernel module:
|
||
|
|
||
|
<B>PLUSTEK</B> <B>SCANNERS</B>
|
||
|
|
||
|
Parallelport Model: ASIC: Properties:
|
||
|
---------------------- ----- ------------------------
|
||
|
OpticPro PT12 98003 600x1200 dpi 36bit 512Kb
|
||
|
OpticPro P12 98003 600x1200 dpi 36bit 512Kb
|
||
|
OpticPro 9636T/12000T 98001 600x1200 dpi 36bit 512Kb
|
||
|
OpticPro 12000P Turbo 98001 600x1200 dpi 36bit 512Kb
|
||
|
OpticPro 9636P+/Turbo 98001 600x1200 dpi 36bit 512Kb
|
||
|
OpticPro 9636P 96003 600x1200 dpi 36bit 128Kb
|
||
|
OpticPro 12000P/96000P 96003 600x1200 dpi 36bit 128Kb
|
||
|
OpticPro 1236P 96003 600x1200 dpi 30bit 128Kb
|
||
|
OpticPro 9600P 96003 600x1200 dpi 30bit 128Kb
|
||
|
OpticPro 9630P/FBIV 96003 600x1200 dpi 30bit 128Kb
|
||
|
OpticPro 9630PL (14") 96003 600x1200 dpi 30bit 128Kb
|
||
|
OpticPro A3I 96003 400x800 dpi 36bit 128Kb
|
||
|
OpticPro 600P/6000P 96003 300x600 dpi 30bit 32Kb
|
||
|
OpticPro 4831P 96003 300x600 dpi 30bit 32Kb
|
||
|
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
|
||
|
OpticPro 4800P/FBII 96001 300x600 dpi 24bit 32Kb
|
||
|
|
||
|
<B>PRIMAX</B> <B>SCANNERS</B>
|
||
|
|
||
|
There are some scanners sold by Primax, but they are in fact Plustek
|
||
|
devices. These scanners are also supported. The following table will
|
||
|
show the relationship:
|
||
|
|
||
|
Model: Plustek Model: Remarks:
|
||
|
--------------------------- -------------- ------------
|
||
|
Colorado 4800 OpticPro 4800 not tested
|
||
|
Compact 4800 Direct OpticPro 600 mov=2
|
||
|
Compact 4800 Direct 30bit OpticPro 4830 mov=7
|
||
|
Compact 9600 Direct 30bit OpticPro 9630 works
|
||
|
|
||
|
<B>GENIUS</B> <B>SCANNERS</B>
|
||
|
|
||
|
The following devices are sold as Genius Scanners, but are in fact
|
||
|
Plustek devices. The table will show the relationship:
|
||
|
|
||
|
Model: Remarks:
|
||
|
--------------------------- ----------------------------
|
||
|
Colorpage Vivid III V2 Like P12 but has two buttons
|
||
|
and Wolfson DAC
|
||
|
|
||
|
<B>ARIES</B> <B>SCANNERS</B>
|
||
|
|
||
|
There's one scanner sold as Aries Scanner, but is in fact a Plustek
|
||
|
device. The following table will show the relationship:
|
||
|
|
||
|
Model: Plustek Model: Remarks:
|
||
|
--------------------------- -------------- ------------
|
||
|
Scan-It 4800 OpticPro 600 mov=2
|
||
|
|
||
|
<B>BrightScan</B> <B>SCANNERS</B>
|
||
|
|
||
|
There's one scanner sold as BrightScan OpticPro Scanner, this is also
|
||
|
rebadged Plustek device. The following table will show the relation-
|
||
|
ship:
|
||
|
|
||
|
Model: Remarks:
|
||
|
--------------------------- ----------------------------
|
||
|
BrightScan OpticPro OpticPro P12
|
||
|
|
||
|
|
||
|
</PRE>
|
||
|
<H2>USB SUPPORT</H2><PRE>
|
||
|
The Backend is able to support USB scanner based on the National Semi-
|
||
|
conductor chipset 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 unsupported ASICs 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>
|
||
|
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
|
||
|
is supported by the <B>Artec</B> backend.
|
||
|
Only the National Semiconductor LM9831/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>DEVICE NAMES</H2><PRE>
|
||
|
This backend expects a default device called:
|
||
|
|
||
|
<I>/dev/pt</I><B>_</B><I>drv</I>
|
||
|
|
||
|
This default device will be used, if no configuration file can be
|
||
|
found.
|
||
|
|
||
|
The device-driver is currently not part of the SANE distribution. It
|
||
|
has to be downloaded from:
|
||
|
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||
|
See the INSTALL file there for a proper setup. Currently only Linux is
|
||
|
supported by this driver (Kernel 2.2.x and higher).
|
||
|
|
||
|
As the backend and the driver support up to four devices per system, it
|
||
|
is possible to specify them in the configuration file
|
||
|
|
||
|
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||
|
|
||
|
See the plustek.conf file for examples.
|
||
|
|
||
|
|
||
|
</PRE>
|
||
|
<H2>CONFIGURATION</H2><PRE>
|
||
|
The configuration of this backend can be divided into two sections:
|
||
|
|
||
|
<B>CONFIGURATION</B> <B>-</B> <B>parallel</B> <B>port</B> <B>scanner</B>
|
||
|
|
||
|
<B>CONFIGURATION</B> <B>-</B> <B>USB</B> <B>scanner</B>
|
||
|
|
||
|
Please make sure, that the configuration matches the real world, namely
|
||
|
your configuration. And note again, .I pt_drv is only needed
|
||
|
|
||
|
|
||
|
</PRE>
|
||
|
<H2>CONFIGURATION - PARALLEL PORT SCANNER</H2><PRE>
|
||
|
Beside the kernel-module options, which are described below, you need
|
||
|
to enable the parallel port device in the configuration file
|
||
|
|
||
|
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||
|
|
||
|
For a proper setup, you will need at least two entries:
|
||
|
|
||
|
<I>[parport]</I>
|
||
|
|
||
|
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||
|
|
||
|
<I>parport</I> tells the backend, that the following devicename (here
|
||
|
<I>/dev/pt</I><B>_</B><I>drv</I> ) has to be interpreted as parallel port scanner device.
|
||
|
|
||
|
To have this device, you will need to setup the kernel module. As the
|
||
|
driver is a loadable kernel module, it is configured by invoking insmod
|
||
|
with the appropriate parameters or appending the options to the file
|
||
|
<B>/etc/conf.modules</B>
|
||
|
|
||
|
<B>The</B> <B>Options:</B>
|
||
|
lampoff=lll
|
||
|
The value <I>lll</I> tells the driver, after how many seconds to
|
||
|
switch-off the lamp(s). The default value is 180. 0 will dis-
|
||
|
able this feature.
|
||
|
<B>HINT:</B> Do not use a value that is too small, because often
|
||
|
switching on/off the lamps will reduce their lifetime.
|
||
|
|
||
|
port=ppp
|
||
|
<I>ppp</I> specifies the port base address, where the scanner is con-
|
||
|
nected to. The default value is 0x378 which normaly is standard.
|
||
|
|
||
|
warmup=www
|
||
|
<I>www</I> specifies the time in seconds, how long a lamp has to be on,
|
||
|
until the driver will start to scan. The default value is 30.
|
||
|
|
||
|
lOffonEnd=e
|
||
|
<I>e</I> specifies the behaviour when unloading the driver, 1 -->
|
||
|
switch lamps off, 0 --> do not change lamp status
|
||
|
|
||
|
slowIO=s
|
||
|
<I>s</I> specifies which I/O functions the driver should use, 1 --> use
|
||
|
delayed functions, 0 --> use the non-delayed ones
|
||
|
|
||
|
forceMode=fm
|
||
|
<I>fm</I> specifies port mode which should be used, 0 --> autodetec-
|
||
|
tion, 1 --> use SPP mode and 2 --> use EPP mode
|
||
|
|
||
|
mov=m
|
||
|
<I>m</I> =0 - default: no override
|
||
|
<I>m</I> =1 - OpticPro 9630PL override (works if OP9630
|
||
|
has been detected) forces legal size (14")
|
||
|
<I>m</I> =2 - Primax 4800Direct override (works if OP600
|
||
|
has been detected) swaps red/green color
|
||
|
<I>m</I> =3 - OpticPro 9636 override (works if OP9636 has
|
||
|
been detected) disables backends
|
||
|
transparency/negativ capabilities
|
||
|
<I>m</I> =4 - OpticPro 9636P override (works if OP9636 has
|
||
|
been detected) disables backends
|
||
|
transparency/negativ capabilities
|
||
|
<I>m</I> =5 - OpticPro A3I override (works if OP12000 has
|
||
|
been detected) enables A3 scanning
|
||
|
<I>m</I> =6 - OpticPro 4800P override (works if OP600
|
||
|
has been detected) swaps red/green color
|
||
|
<I>m</I> =7 - Primax 4800Direct 30bit override (works if OP4830
|
||
|
has been detected)
|
||
|
|
||
|
Sample entry for file <B>/etc/modules.conf</B> :
|
||
|
<I>alias</I> <I>char-major-40</I> <I>pt</I><B>_</B><I>drv</I>
|
||
|
<I>pre-install</I> <I>pt</I><B>_</B><I>drv</I> <I>modprobe</I> <I>-k</I> <I>parport</I>
|
||
|
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>lampoff=180</I> <I>warmup=15</I> <I>port=0x378</I> <I>lOffonEnd=0</I> <I>mov=0</I>
|
||
|
<I>slowIO=0</I> <I>forceMode=0</I>
|
||
|
|
||
|
For multidevice support, simply add values separated by commas to the
|
||
|
different options
|
||
|
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>port=0x378,0x278</I> <I>mov=0,4</I> <I>slowIO=0,1</I> <I>forceMode=0,1</I>
|
||
|
|
||
|
Remember to call depmod after changing /etc/conf.modules.
|
||
|
|
||
|
<B>PARALLEL</B> <B>PORT</B> <B>MODES</B>
|
||
|
|
||
|
The current driver works best, when the parallel port has been set to
|
||
|
EPP-mode. When detecting any other mode such as ECP or PS/2 the driver
|
||
|
tries to set to a faster, supported mode. If this fails, it will use
|
||
|
the SPP mode, as this mode should work with all Linux supported paral-
|
||
|
lel ports.
|
||
|
|
||
|
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
|
||
|
adapter card. This card is <B>not</B> supported by the driver.
|
||
|
|
||
|
The ASIC 96001/3 based models have sometimes trouble with high resolu-
|
||
|
tion modes. If you encounter sporadic corrupted images (parts dupli-
|
||
|
cated or shifted horizontally) kill all other applications before scan-
|
||
|
ning and (if sufficient memory available) disable swapping.
|
||
|
|
||
|
|
||
|
</PRE>
|
||
|
<H2>CONFIGURATION - USB SCANNER</H2><PRE>
|
||
|
To use the USB device 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/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
|
||
|
dor- 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 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.
|
||
|
|
||
|
|
||
|
</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).
|
||
|
|
||
|
<I>/lib/modules/<Kernel-Version>/misc/pt</I><B>_</B><I>drv.o</I>
|
||
|
The Linux Kernelmodule.
|
||
|
|
||
|
|
||
|
</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 Halftoning works, but the quality is poor
|
||
|
* Printers (especially HP models) will start to
|
||
|
print during scanning. This in fact is a problem
|
||
|
to other printers too, using bidirectional protocol
|
||
|
(see www.plustek.com (TAIWAN) page for further details)
|
||
|
* 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.
|
||
|
* On some devices, the pictures seems to be bluished
|
||
|
|
||
|
ASIC 98001 based models:
|
||
|
* The 300dpi transparency and negative mode does not work
|
||
|
correctly.
|
||
|
* There is currently no way to distinguish a model with
|
||
|
and without transpareny unit.
|
||
|
* The scanned images seem to be too dark (P9636T)
|
||
|
|
||
|
ASIC 96003/1 based models:
|
||
|
* 30bit mode is currently not supported.
|
||
|
* On low-end systems and under heavy system load, the
|
||
|
driver will loosing data, this might causes the sensor
|
||
|
to hit the scan-bed and/or the picture is corrupted.
|
||
|
* The scanspeed on 600x1200 dpi models is slow.
|
||
|
* The scanquality of the A3I is poor
|
||
|
|
||
|
USB models:
|
||
|
* 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 scanning quality is poor.
|
||
|
|
||
|
sane-backends 1.0.12-cvs 17 September 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>
|