sane-project-website/man/sane-canon630u.5.html

136 wiersze
5.4 KiB
HTML

<HTML>
<HEAD>
<TITLE>sane-canon630u.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-canon630u.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-canon630u - SANE backend for the Canon 630u USB flatbed scanner
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-canon</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Canon flatbed scanners:
CanoScan 630u
CanoScan 636u (hopefully)
IMPORTANT: this is alpha code. Although there are no known bugs at
this time, this code uses the Linux USB kernel drivers, which are cur-
rently in active development. So it may not work, your computer might
even hang, and it cannot be excluded (although I consider it extremely
unprobable) that your scanner will be damaged.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Nathan Rutman &lt;nathan@gordian.com&gt;
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a USB scanner or a symlink to such a device. The program <I>sane-find-</I>
<I>scanner</I> helps to find out the correct device. Under Linux, such a
device name could be <I>/dev/usb/scanner0</I> for example. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>canon630u.conf</I> file is a list of device names that
correspond to Canon USB scanners. Empty lines and lines starting with
a hash mark (#) are ignored. Only one device name can be listed in
<I>canon630u.conf</I>.
</PRE>
<H2>NOTES</H2><PRE>
Due to Canon's unwillingness to provide scanner documentation, this
software was developed by analyzing the USB traffic of the Windows 2000
driver. So things like the calibration procedure I kind of made up; it
seems to work for my scanner. If you have complaints, let me know.
This driver requires the ability to send USB Control Messages, avail-
able in kernel 2.4.12 or later.
This scanner may not be recognized (yet) by the USB kernel driver.
Check for "Driver=usbscanner" under /proc/bus/usb/devices. If
"Driver=(none)", try forcing it with "modprobe scanner vendor=0x04a9
product=0x2204"
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/canon630u.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-canon630u.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-canon630u.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>/tmp/canon.cal</I>
The calibration file used to normalize pixel brightness. This
is calculated every time the scanner is first used after it has
lost power. It can be forced to recalibrate by simply deleting
this file.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
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
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_CANON630U</B>
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: SANE_DEBUG_CANON630U=12 scanimage &gt; /dev/null
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
http://canon-fb630u.sourceforge.net/
</PRE>
<H2>AUTHOR</H2><PRE>
Nathan Rutman
sane-backends 1.0.12-cvs 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(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>