[#315649] Duplex scanning fails with epson2 backend for Epson Workforce 645 all in one.

View Trackers | Bugs | Export CSV

2017-03-10 19:58
Submitted by:
Jim Mayer (pentastich-guest)
Assigned to:
Nobody (None)
backends (drivers)
Duplex scanning fails with epson2 backend for Epson Workforce 645 all in one.

Detailed description
The epson2 backend is not able to scan duplex documents with an Epson Workforce 645 all-in-one. The backend reports duplex capability, and scans the first side, but, instead of sucking the page back in, fully ejects it and reports an error. The device panel then reports a paper jam. The same operation works with the epkowa driver. The problem is 100% repeatable.

Here's some system information:

Linux distribution: Fedora 25

$ uname -srvmpio
Linux 4.9.13-200.fc25.x86_64 #1 SMP Mon Feb 27 16:48:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ scanimage --version
scanimage (sane-backends) 1.0.25; backend version 1.0.25

Printer Model: Epson Workforce 645 (model C422A)
Printer Firmware Version: KR04G3 6B.6B
Printer connectivity: wireless network


I've attached a file with debugging output while scanning a single page. The command line used is in the file.


Jim Mayer

Followups: Sort comments antichronologically

Date: 2017-03-11 02:31
Sender: Olaf Meeuwissen

Looking at the end of your debug.log, it looks like an I/O issue, maybe a time out? The epsonds backend is currently not maintained, so I suggest you use the epkowa backend if that works for you.

# Yes, I'm aware you want to file a bug report against that for missing resolutions ;-)

[epson2] e2_scan_finish
Scanned page 1. (scanner status = 5)
Scanning page 2
[epson2] * sane_epson2_start
[epson2] e2_check_adf
[epson2] esci_request_scanner_status
[epson2] e2_send: size = 2, reply = 16
[epson2] e2_send: FS F
[epson2] buf[0] 1c .
[epson2] buf[1] 46 F
[epson2] allocated 16 bytes at 0x557d7b7e1070
[epson2] sanei_epson_net_write: cmd = 2000, buf = 0x7fffd4ad6380, buf_size = 2, reply_len = 16
[epson2] H1[0]: 49 53 20 00
[epson2] H1[6]: 00 00 00 0a (10)
[epson2] H2[0]: 00 00 00 02 (2)
[epson2] H2[4]: 00 00 00 10 (16)
[epson2] e2_recv: size = 16, buf = 0x7fffd4ad63d0
[epson2] sanei_epson_net_read_raw: select failed: 0
[epson2] e2_recv: expected = 16, got = 0, canceling: 0
[epson2] e2_txrx: rx err, Error during device I/O
scanimage: sane_start: Error during device I/O
[epson2] * sane_epson2_cancel
[epson2] * sane_epson2_close
Date: 2017-03-11 03:09
Sender: Jim Mayer


I don't think it's purely an I/O issue, as the scanner works with the flatbed and with the ADF in simplex mode. Perhaps its related to the fact that the scanner always reports a paper jam (though there's no paper in the scanner).

Also, your comment mentioned the "epsonds" backend, which looks distinct from "epson2". Is that a typo or is a distinction that matters?

As I noted to you privately, I've patched the epkowa driver to do what I need, so I can get by that way.
Date: 2017-03-11 03:21
Sender: Olaf Meeuwissen

Sorry about the mixup. My bad. You're using the epson2 backend. The epsonds backend doesn't support your scanner.

Neither backend is maintained :-(

Paper jams would normally be reported to the backend. If the backend doesn't get a reply (in time), there's not much it can do.

Attached Files:

Size Name Date By Download
1.98 MiBdebug.log2017-03-10 19:58pentastich-guestdebug.log


Field Old Value Date By
File Added7387: debug.log2017-03-10 19:58pentastich-guest
Powered By FusionForge