[sane-devel] Visioneer 4800 USB, unsupported

[Clarence Risher]

My first post to this mailing list...

I have a Visioneer 4800 USB (vendor=0x04a7, product=0x0224).  It is
currently unsupported
(http://www.sane-project.org/unsupported/visioneer-onetouch4800.html).
 The experimental backend hp_rts88xx may be a step in the right
direction (Realtek RTS8801B chipset), but does not support this
scanner in particular.  I don't have access to a Windows computer to
do usb snooping with.  Since the scanner is useless to me, are there
any backend developers out there who would work on support if I sent
the scanner to you?

(CC to hp_rts88xx author)

[sane-devel] Epson CX-5400 supported, but won't work for me

[Clarence Risher]

I am trying to get an Epson Stylus CX-5400 to work with SANE.
sane-find-scanner sees it, and produces the officially documented
output with '-v -v', but when I run xsane or scanimage it is not
detected.  See below for the epson backend debug output (at levels 1,
32, and 128).  I ran all this as root, as as a user.  Any help would
be appreciated.

--

SANE_DEBUG_EPSON=1 scanimage
[sanei_debug] Setting debug level of epson to 1.
[epson] SANE Epson Backend v0.2.46 - 2006-06-11
[epson] SANE Epson Backend v0.2.46 - 2006-06-11
[epson] Found valid EPSON scanner: 0x4b8/0x808 (vendorID/productID)
[epson] typeD 0x44
[epson] level   1 0x31
[epson] no option equipment installed
[epson] resolution (dpi): 100
[epson] resolution (dpi): 300
[epson] resolution (dpi): 600
[epson] resolution (dpi): 1200
[epson] maximum scan area: x 10200 y 14040
[epson] product name 43 58 35 34 30 30 20 20
scanimage: no SANE devices found

--

SANE_DEBUG_EPSON=32 scanimage
[sanei_debug] Setting debug level of epson to 32.
[epson] sane_init: sane-backends 1.0.18
[epson] sane_init, ># epson.conf<
[epson] sane_init, >#<
[epson] sane_init, ># here are some examples for how to configure the
EPSON backend<
[epson] sane_init, >#<
[epson] sane_init, ># SCSI scanner:<
[epson] sane_init, >scsi EPSON<
[epson] sane_init, ># for the GT-6500:<
[epson] sane_init, >scsi "EPSON SC"<
[epson] sane_init, >#<
[epson] sane_init, ># Parallel port scanner:<
[epson] sane_init, >#pio 0x278<
[epson] sane_init, >#pio 0x378<
[epson] sane_init, >#pio 0x3BC<
[epson] sane_init, >#<
[epson] sane_init, ># USB scanner:<
[epson] sane_init, ># There are two different methods of configuring a
USB scanner: libusb and the kernel module<
[epson] sane_init, ># For any system with libusb support (which is
pretty much any recent Linux distribution) the<
[epson] sane_init, ># following line is sufficient. This however
assumes that the connected scanner (or to be more<
[epson] sane_init, ># accurate, it's device ID) is known to the backend.<
[epson] sane_init, >usb<
[epson] attach_one_usb()
[epson] SANE Epson Backend v0.2.46 - 2006-06-11
[epson] attach(, 3)
[epson] attach: opening
[epson] attach_one_usb(libusb:001:004)
[epson] SANE Epson Backend v0.2.46 - 2006-06-11
[epson] attach(libusb:001:004, 3)
[epson] attach: opening libusb:001:004
[epson] Found valid EPSON scanner: 0x4b8/0x808 (vendorID/productID)
[epson] reset()
[epson] send buf, size = 2
[epson] w_cmd_count = 1
[epson] r_cmd_count = 0
[epson] w_cmd_count = 1
[epson] r_cmd_count = 1
[epson] receive buf, expected = 1, got = 1
[epson] get_identity_information()
[epson] send buf, size = 2
[epson] w_cmd_count = 2
[epson] r_cmd_count = 1
[epson] w_cmd_count = 2
[epson] r_cmd_count = 2
[epson] receive buf, expected = 4, got = 4
[epson] code   02
[epson] status 00
[epson] count  19
[epson] w_cmd_count = 2
[epson] r_cmd_count = 3
[epson] receive buf, expected = 19, got = 19
[epson] typeD 0x44
[epson] level   1 0x31
[epson] no option equipment installed
[epson] resolution (dpi): 100
[epson] resolution (dpi): 300
[epson] resolution (dpi): 600
[epson] resolution (dpi): 1200
[epson] maximum scan area: x 10200 y 14040
[epson] send buf, size = 2
[epson] w_cmd_count = 3
[epson] r_cmd_count = 3
[epson] w_cmd_count = 3
[epson] r_cmd_count = 4
[epson] receive buf, expected = 4, got = 4
[epson] code   02
[epson] status 00
[epson] count  42
[epson] w_cmd_count = 3
[epson] r_cmd_count = 5
[epson] receive buf, expected = 42, got = 42
[epson] product name 43 58 35 34 30 30 20 20
[epson] fbf tlx 0.00 tly 0.00 brx 215.84 bry 297.179993 [mm]
[epson] get_identity2_information()
[epson] send buf, size = 2
[epson] w_cmd_count = 4
[epson] r_cmd_count = 5
[epson] w_cmd_count = 4
[epson] r_cmd_count = 6
[epson] receive buf, expected = 4, got = 4
[epson] w_cmd_count = 4
[epson] r_cmd_count = 8
[epson] receive buf, expected = 88, got = 88
[epson] close_scanner(fd = 0)
[epson] w_cmd_count = 4
[epson] r_cmd_count = 8
[epson] w_cmd_count = 4
[epson] r_cmd_count = 8
[epson] sane_init, ># usb 0x04b8 0x0808<
[epson] sane_init, ># For libusb support for unknown scanners use the
following command<
[epson] sane_init, ># usb  <
[epson] sane_init, ># e.g.:<
[epson] sane_init, ># usb 0x4b8 0x110<
[epson] sane_init, ># And for the scanner module, use the following
configuration:<
[epson] sane_init, >#usb /dev/usbscanner0<
[epson] sane_init, >#usb /dev/usb/scanner0<
[epson] sane_get_devices()
scanimage: no SANE devices found

--

SANE_DEBUG_EPSON=128 scanimage
[sanei_debug] Setting debug level of epson to 128.
[epson] sane_init: sane-backends 1.0.18
[epson] sane_init, ># epson.conf<
[epson] sane_init, >#<
[epson] sane_init, ># here are some examples for how to configure the
EPSON backend<
[epson] sane_init, >#<
[epson] sane_init, ># SCSI scanner:<
[epson] sane_init, >scsi EPSON<
[epson] sane_init, ># for the GT-650

[sane-devel] infrared dust removal algorithm

[Clarence Risher]

wouldnt the method be the same as for any other monochrome image?
assume your IR is monochromatic.

On 1/21/07, Alessandro Zummo  wrote:
>   while working with infrared support I just noticed there
>  seems to be no available algorithm for dust removal...
>
>  anyone can point to some source code or wants to write one? :)

[sane-devel] Re: Problems about Lineart mode

[Clarence Risher]

pnm2png takes its input from the command line (your way) or from stdin
(allan's way), and outputs the png data to stdout.  what you want is
this:

pnmtopng document.pnm > document.png


On 1/26/07, Rodolfo Medina  wrote:
> But, when I try to use `pnmtopng' alone, with:
>
>  # pnmtopng document.pnm
>
> , the program fails: I get some messed output and nothing else.

[sane-devel] xsane requires deprecated /proc/scsi support

[Clarence Risher]

My probably irrelevant two cents, completely off on a tangent...

You might want to make sure you arent being bitten by the epson bug in
sane-backends 1.0.18 that causes exactly the behavior that you
describe, downgrade to 1.0.17 or upgrade to debian's 1.0.18-5 to
check.  Also, try "SANE_DEBUG_EPSON=3 scanimage -L" and see if
anything funky shows up.

On 2/5/07, ke6...@arrl.net  wrote:
> anywhere. My Epson 2450 scanner used to work fine with xsane via the
<
> Observation: the symptom was that sane-find-scanner saw the scanner, but
> scanimage -L did not. Possible issue -- check the legacy /proc/scsi
> support in the kernel. (  Now it's in the archives :-)  )