kopia lustrzana https://gitlab.com/sane-project/backends
Added Yakumo Scan50. Minor cleanup.
Henning Geinitz
rodzic
4370559a08
commit
31a2b3ff35
|
|
@ -4,6 +4,9 @@
|
|||
doc/descriptions/hp5400.desc doc/descriptions/niash.desc
|
||||
doc/descriptions/unsupported.desc: Added USB vendor and product
|
||||
ids. Minor cleanup.
|
||||
* backend/artec_eplus48u.conf.in doc/sane-artec_eplus48u.man
|
||||
doc/descriptions/artec_eplus48u.desc: Added Yakumo Scan50. Minor
|
||||
cleanup.
|
||||
|
||||
2006-01-15 Ulrich Deiters <ulrich.deiters@uni-koeln.de>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,11 @@
|
|||
# artec_eplus48u - SANE Backend configuration file
|
||||
# For use with the Artec E+ 48U scanner
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# This section is for use with the Artec E+ 48U scanner
|
||||
# This scanner is also sold as
|
||||
# Tevion MD 9693, Medion MD 9705, Medion MD 9693,
|
||||
# Trust Easy Webscan 19200, Memorex Mem 48U or Umax AstraSlim SE.
|
||||
# Tevion MD 9693, Medion MD 9705, Medion MD 9693, Medion MD4394
|
||||
#
|
||||
# For other scanners, see below.
|
||||
#
|
||||
# The USB section:
|
||||
# each device needs at least the following line:
|
||||
|
|
@ -57,13 +60,13 @@ option modelString "E+ 48U"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# Since the Trust Easy Webscan 19200 uses a different product id, we add
|
||||
# another usb section here.
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# Since the Trust Easy Webscan 19200 uses a different product id, we add
|
||||
# another usb section here.
|
||||
|
||||
usb 0x05d8 0x4006
|
||||
|
||||
|
|
@ -116,12 +119,13 @@ option modelString "Easy Webscan 19200"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# Since the Memorex Mem48U uses a different product id, we add
|
||||
# another usb section here.
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# Since the Memorex Mem48U uses a different product id, we add
|
||||
# another usb section here.
|
||||
|
||||
usb 0x05d8 0x4005
|
||||
|
||||
|
|
@ -154,7 +158,7 @@ option greenExposure 0x116
|
|||
option blueExposure 0xdc
|
||||
|
||||
# The vendor and model string
|
||||
# This string is displayed by the frontends. The Umax AstraSlim SE
|
||||
# This string is displayed by the frontends. The Memorex MEM 48U
|
||||
# has a different product id, therefore we can overwrite the vendor and model
|
||||
# string here.
|
||||
|
||||
|
|
@ -174,12 +178,13 @@ option modelString "MEM 48U"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# Since the Trust 240H Easy Webscan Gold uses a different product id, we add
|
||||
# another usb section here.
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# Since the Trust 240H Easy Webscan Gold uses a different product id, we add
|
||||
# another usb section here.
|
||||
|
||||
usb 0x05d8 0x4007
|
||||
|
||||
|
|
@ -232,12 +237,14 @@ option modelString "240H Easy Webscan Gold"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# Since the UMAX AstraSlim SE uses a different product id, we add
|
||||
# another usb section here.
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# Since the Umax AstraSlim SE uses a different product id, we add
|
||||
# another usb section here.
|
||||
|
||||
usb 0x05d8 0x4009
|
||||
|
||||
|
|
@ -270,7 +277,7 @@ option greenExposure 0x116
|
|||
option blueExposure 0xdc
|
||||
|
||||
# The vendor and model string
|
||||
# This string is displayed by the frontends. The Umax AstraSlim SE
|
||||
# This string is displayed by the frontends. The UMAX AstraSlim SE
|
||||
# has a different product id, therefore we can overwrite the vendor and model
|
||||
# string here.
|
||||
|
||||
|
|
@ -290,13 +297,14 @@ option modelString "AstraSlim SE"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# This section is for the Artec E+ Pro
|
||||
# Note, that the name of the firmware file is called 1200.usb for
|
||||
# this device
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# This section is for the Artec E+ Pro
|
||||
# Note, that the name of the firmware file is called 1200.usb for
|
||||
# this device
|
||||
|
||||
usb 0x05d8 0x4004
|
||||
|
||||
|
|
@ -336,7 +344,7 @@ option greenExposure 0x116
|
|||
option blueExposure 0xdc
|
||||
|
||||
# The vendor and model string
|
||||
# This string is displayed by the frontends. The Umax AstraSlim SE
|
||||
# This string is displayed by the frontends. The Artec E+ Pro
|
||||
# has a different product id, therefore we can overwrite the vendor and model
|
||||
# string here.
|
||||
|
||||
|
|
@ -356,13 +364,15 @@ option modelString "E+ Pro"
|
|||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# This section is for the UMAX AstraSlim 1200 SE
|
||||
# Note, that the name of the firmware file is called 1200.usb for
|
||||
# this device
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
# This section is for the UMAX AstraSlim 1200 SE
|
||||
# Note, that the name of the firmware file is called 1200.usb for
|
||||
# this device
|
||||
|
||||
usb 0x05d8 0x4010
|
||||
|
||||
|
|
@ -395,7 +405,7 @@ option greenExposure 0x116
|
|||
option blueExposure 0xdc
|
||||
|
||||
# The vendor and model string
|
||||
# This string is displayed by the frontends. The Umax AstraSlim 1200 SE
|
||||
# This string is displayed by the frontends. The UMAX AstraSlim 1200 SE
|
||||
# has a different product id, therefore we can overwrite the vendor and model
|
||||
# string here.
|
||||
|
||||
|
|
@ -414,3 +424,64 @@ option modelString "AstraSlim 1200 SE"
|
|||
|
||||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
|
||||
# ----------------------------------------------------------------------------
|
||||
# Since the Yakumo Scan50 uses a different product id, we add
|
||||
# another usb section here.
|
||||
# Another USB section:
|
||||
# each device needs at least the following line:
|
||||
# usb vendor-ID and product-ID
|
||||
# Every device configuration in this file must begin with an usb entry.
|
||||
|
||||
usb 0x05d8 0x4011
|
||||
|
||||
#
|
||||
# Path to the firmware file
|
||||
# This file comes with the Windows driver
|
||||
# The scanner won't work without it
|
||||
#
|
||||
|
||||
option artecFirmwareFile @DATADIR@/sane/artec_eplus48u/Artec48.usb
|
||||
|
||||
#
|
||||
# for adjusting the default gamma values
|
||||
#
|
||||
option ePlusPro 1
|
||||
option redGamma 1.0
|
||||
option greenGamma 1.0
|
||||
option blueGamma 1.0
|
||||
option masterGamma 1.9
|
||||
|
||||
#Use this options to set the default offset and exposure time values.
|
||||
#If calibrate device is set to 0, this values are used instead of the values
|
||||
#which were calculated during calibration.
|
||||
|
||||
option redOffset 0x28
|
||||
option greenOffset 0x2f
|
||||
option blueOffset 0x2f
|
||||
option redExposure 0xa7
|
||||
option greenExposure 0x116
|
||||
option blueExposure 0xdc
|
||||
|
||||
# The vendor and model string
|
||||
# This string is displayed by the frontends. The Yakumo Scan50
|
||||
# has a different product id, therefore we can overwrite the vendor and model
|
||||
# string here.
|
||||
|
||||
option vendorString "Yakumo"
|
||||
option modelString "Scan50"
|
||||
|
||||
#
|
||||
# device-name
|
||||
#
|
||||
# If autodetection does not work, then you can specify the device here
|
||||
# The device entry must be the last one in this config file (or the last one before a
|
||||
# new usb entry).
|
||||
|
||||
#If you are using libusb, a device looks like this:
|
||||
#device libusb:001:002
|
||||
|
||||
#If you are using the scanner module (kernel driver), a device looks like this:
|
||||
#device /dev/usbscanner
|
||||
|
|
|
|||
|
|
@ -10,12 +10,20 @@
|
|||
|
||||
:mfg "Artec/Ultima"
|
||||
:url "http://www.artecusa.com/"
|
||||
|
||||
:model "E+ 48U"
|
||||
:status :good
|
||||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4003"
|
||||
:comment "CIS scanner based on the GT6816 chip. Apparently all other devices are re-badged Artec scanners."
|
||||
|
||||
:model "E+ Pro"
|
||||
:status :minimal
|
||||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4004"
|
||||
:comment "Experimental! Please report your results!"
|
||||
|
||||
|
||||
:mfg "Medion/Lifetec/Tevion/Cytron"
|
||||
:url "http://www.medion.com"
|
||||
:comment "Sold by Aldi and Tchibo."
|
||||
|
|
@ -36,6 +44,7 @@
|
|||
:usbid "0x05d8" "0x4003"
|
||||
:comment "Only scanners with product id 0x4003 will work; try the gt68xx backend, if your scanner has product id 0x4002 "
|
||||
|
||||
|
||||
:mfg "Trust"
|
||||
:url "http://www.trust-site.com"
|
||||
|
||||
|
|
@ -50,20 +59,25 @@
|
|||
:usbid "0x05d8" "0x4007"
|
||||
:comment "Works up to 600 dpi"
|
||||
|
||||
|
||||
:mfg "Memorex"
|
||||
:url "http://www.artecusa.com/"
|
||||
|
||||
:model "MEM 48U"
|
||||
:status :good
|
||||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4005"
|
||||
|
||||
|
||||
:mfg "Microstar"
|
||||
:url "http://www.microstar.de/"
|
||||
|
||||
:model "MR 9791"
|
||||
:status :good
|
||||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4003"
|
||||
|
||||
|
||||
:mfg "UMAX"
|
||||
:url "http://www.umax.com/"
|
||||
:url "http://www.umax.com.tw/"
|
||||
|
|
@ -82,10 +96,11 @@
|
|||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4010"
|
||||
|
||||
:mfg "Artec/Ultima"
|
||||
:url "http://www.artecusa.com/"
|
||||
:model "E+ Pro"
|
||||
:status :minimal
|
||||
|
||||
:mfg "Yakumo"
|
||||
:url "http://www.yakumo.com/"
|
||||
|
||||
:model "Scan50"
|
||||
:status :good
|
||||
:interface "USB"
|
||||
:usbid "0x05d8" "0x4004"
|
||||
:comment "Experimental! Please report your results!"
|
||||
:usbid "0x05d8" "0x4011"
|
||||
|
|
|
|||
|
|
@ -1,40 +1,22 @@
|
|||
.TH sane-artec_eplus48u 5 "19 Nov 2002" "@PACKAGEVERSION@" "SANE"
|
||||
.TH sane-artec_eplus48u 5 "15 Jan 2006" "@PACKAGEVERSION@" "SANE"
|
||||
.SH NAME
|
||||
sane-artec_eplus48u \- SANE backend for the scanner Artec E+ 48U and re-badged models
|
||||
.SH DESCRIPTION
|
||||
The
|
||||
.B sane-artec_eplus48u
|
||||
library implements a SANE (Scanner Access Now Easy) backend that at present provides
|
||||
access to the USB flatbed scanners
|
||||
.PP
|
||||
Artec E+ 48U,
|
||||
.br
|
||||
Tevion MD 9693,
|
||||
.br
|
||||
Medion MD 9693,
|
||||
.br
|
||||
Medion MD 9705 and
|
||||
.br
|
||||
Trust Easy Webscan 19200.
|
||||
.br
|
||||
.PP
|
||||
library implements a SANE (Scanner Access Now Easy) backend that provides
|
||||
access to several USB flatbed scanners using the GT6816 chipset like the Artec E+ 48U.
|
||||
These scanners have a contact image sensor (CIS) and an USB interface.
|
||||
.PP
|
||||
VendorID: 0x05d8
|
||||
.br
|
||||
ProductID: 0x4003
|
||||
.PP
|
||||
The Trust Easy Webscan 19200 is an exception. It's ProductID is 0x4006.
|
||||
.PP
|
||||
More details can be found on
|
||||
.IR http://www.angelfire.com/linux/crapsite/ .
|
||||
A complete list of supported devices can be found on
|
||||
.IR http://www.sane-project.org/sane-supported-devices.html .
|
||||
.PP
|
||||
This is ALPHA software. Especially if you test new or untested scanners, keep
|
||||
your hand at the scanner's plug and unplug it, if the head bumps at the end of
|
||||
the scan area.
|
||||
.PP
|
||||
If you own a scanner other than the ones listed above that works with this
|
||||
backend, please let me know this by sending the scanner's exact model name and
|
||||
If you own a scanner other than the ones mentioned on the list that works with this
|
||||
backend, please let us know this by sending the scanner's exact model name and
|
||||
the USB vendor and product ids (e.g. from /proc/bus/usb/devices,
|
||||
sane-find-scanner or syslog) to me. Even if the scanner's name is only
|
||||
slightly different from the models mentioned above, please let me know.
|
||||
|
|
@ -50,10 +32,10 @@ required.
|
|||
.SH FIRMWARE FILE
|
||||
You need a firmware file for your scanner. That's a small file containing
|
||||
software that will be uploaded to the scanner's memory. For the scanners
|
||||
mentioned above, it's usually named Artec48.usb. You can find it on the
|
||||
installation CD that was provided by the manufacturer, normally in the
|
||||
directory Win98, WinMe or similar. If the Windows-driver is installed on
|
||||
your computer, then you can also find the firmware file under
|
||||
mentioned above, it's usually named Artec48.usb or 1200.usb. You can find it on
|
||||
the installation CD that was provided by the manufacturer, normally in the
|
||||
directory Win98, WinMe or similar. If the Windows-driver is installed on your
|
||||
computer, then you can also find the firmware file under
|
||||
c:\\windows\\system32\\drivers.
|
||||
.SH CONFIGURATION
|
||||
The contents of the
|
||||
|
|
@ -143,7 +125,7 @@ export SANE_DEBUG_ARTEC_EPLUS48U=3
|
|||
sane(7), sane-usb(5)
|
||||
|
||||
.SH AUTHOR
|
||||
Michael Herder <crapsite@gmx.net>
|
||||
Michael Herder
|
||||
.br
|
||||
This backend is based on the gt68xx test-program written by Sergey Vlasov, Andreas Nowack, and
|
||||
David Stevenson. Thanks to everyone who tested the backend or reported bugs.
|
||||
|
|
@ -151,14 +133,12 @@ David Stevenson. Thanks to everyone who tested the backend or reported bugs.
|
|||
This man page is based on man sane-gt68xx, written by Henning Meier-Geinitz.
|
||||
.SH BUGS
|
||||
This backend has been tested on Linux only. If you are using it on a different platform, please
|
||||
contact me.
|
||||
contact us.
|
||||
.PP
|
||||
Interpolation with 1200 dpi is weak.
|
||||
.PP
|
||||
Support for buttons is missing due to missing support in SANE.
|
||||
.PP
|
||||
More detailed bug information is
|
||||
available at
|
||||
.IR http://www.angelfire.com/linux/crapsite .
|
||||
Please contact me if you find a bug or missing feature:
|
||||
<crapsite@gmx.net>
|
||||
Please contact us if you find a bug:
|
||||
.IR http://www.sane-project.org/bugs.html .
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue