Hi,
The Fujitsu fi65-F has recently showed up on the supported device list for the
epjitsu backend, but I'm struggling to get it to scan an image using Ubuntu
14.04. Below are all the details but the gist is:
* sane-find-scanner finds the scanner
* scanimage -L recognizes the scanner
* scani
Well- 'output is not a file' is your first clue. You need to redirect
the output of scanimage somewhere:
scanimage [your options] > file.pnm
see if repeated invocations of that will work for you.
allan
On Sat, Mar 14, 2015 at 7:42 PM, Jonas Neubert wrote:
> Hi,
>
> The Fujitsu fi65-F has recen
Thanks Allan, my mind was so set on thinking of "output" as the scanner output,
I didn't even consider that this error might about the program's output!
When doing 'scanimage > file.pnm' the first attempt at scanning an image now
ends with the same "scanimage: sane_start: Error during device I/O
hmm- I have never actually seen an fi-65f, I only have user reports
from my patches. However, the initial development was done with
firmware 65f_0A01.nal Can you try to extract that version (or later)
from the Fujitsu windows drivers? You might have to get the latest
version from their website. May
I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows
and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter
last time.
Unfortunately, still no change in behavior. The output remains effectively
same, but just in case I'm missing something, below
Wireshark is fine, but this log does not contain the calibration step,
which is where sane seems to fail. Can you unplug and replug the
device while wireshark is running, and get a log of the initialization
process? I'm not sure if wireshark can do that.
allan
On Sun, Mar 15, 2015 at 6:01 PM, Jon
I think this should cover it, started capture before plugging in, then
initialization and then a full page scan:
https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0
-Jonas
On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noah wrote
> Wireshark is fine, but this log does not cont
Hmm- perhaps you can try scanimage again, but at resolution 300? Also
increase the epjitsu debug level to 25, and don't set the dll debug
level, it is not helpful.
I see a couple possible differences that have never been important
with prior scanners, but perhaps are important with yours.
allan
I believe all debug output I sent so far (both SANE and Windows) was with
300dpi setting, for scanimage it's the default value for the --resolution
option in the output of 'scanimage -h'. Anyway, ran it again, this time with
resolution and mode options explicitly set, still same behavior, see de
Hmm- the scanner is upset that we tried to send window data. Perhaps
it wants some other command to be sent first. I will look at your pcap
again and come up with a patch
allan
On Mon, Mar 16, 2015 at 3:30 AM, Jonas Neubert wrote:
> I believe all debug output I sent so far (both SANE and Windows
I have attached a minor patch to the backend. The idea is to send
commands in the same order as the windows driver, starting with get
hardware status. If this does not fix it, I will move on to set
window, which looks like it should be after the initial coarse
calibration payload.
allan
On Mon, M
I just did a few successful scans! The patch does indeed make the scanner work,
with two caveats:
1) Only every other call to scanimage results in a successful scan, the 2nd,
4th, 6th, etc scan fails the same way as before.
2) Even during successful scans the debug output contains an 'Error duri
I'm using USB2, and the git repo checkout was Monday late evening, less than an
hour before I sent my last email. I already destroyed the test environment I
used on Monday which is why I can't tell you the exact time or commit hash that
was checked out. I can try again tomorrow morning if there
There have been no recent changes that would improve the situation.
Can you run scanimage -L repeatedly without error? or maybe scanimage
--help?
allan
On Thu, Mar 19, 2015 at 2:06 AM, Jonas Neubert wrote:
> I'm using USB2, and the git repo checkout was Monday late evening, less than
> an hour
Both scanimage -L and scanimage --help show the same behavior: Works once,
fails second time. Debug outputs:
scanimage -L: https://gist.github.com/jonemo/c0e508baf4533d79a2ea
scanimage --help: https://gist.github.com/jonemo/6879f07a590d8a5f3fe2
-Jonas
On Thu, 19 Mar 2015 05:26:34 -0700 m.
15 matches
Mail list logo
