I have no way of knowing what the firmware does inside the scanner. However, you could try to get a log of the S1300i in action making a small, low resolution scan using something like Wireshark on windows. Then we could try to compare the protocol. Unfortunately, I don't have much time right now, but maybe it will be an easy fix.
allan On Tue, Nov 20, 2012 at 12:00 PM, Simon Matter <simon.matter at invoca.ch> wrote: >> This is the first I have heard of the S1300i, so its not surprising it >> does not work :) > > I don't have an S300 or S1300 here but I'm wondering if they have > different hardware or they are exactly the same? What about the firmware, > if those devices were the same, was it possible to load the S300 firmware > on all the devices somehow so they behave the same? > >> >> I have a partially completed merger of the S1100 code, but its pretty >> broken now. I will finish it some day. > > That's sad :( > What about the code to generate devices names based on serial? Do you have > a separate patch (or is it already a big change)? That's one of the things > I like with the fujitsu backend and I'd like to have the same here. > > Simon > >> >> Hiroshi Miura has done a great deal of work on his own to merge this >> driver, and he has a github repo with his branch. It does not contain >> all the features of my S1100 patch. I probably should abandon my work >> and use his merger instead. >> >> https://github.com/miurahr/sane-backends/commits/epjitsu-s1100 >> >> allan >> >> On Tue, Nov 20, 2012 at 9:02 AM, Simon Matter <simon.matter at invoca.ch> >> wrote: >>> Hi, >>> >>> I'm trying to get two scanners to work for our mobile users. They are >>> Fujitsu ScanSnap S1100 and S1300i. >>> >>> Since the S1300 is known to work like the S300 I was hoping the S1300i >>> will also work. I've configured the USB id in epjitsu.conf to load >>> Firmware 1300i_0D12.nal and it all seems well but once I start a scan I >>> only get I/O errors. Here's the log from where it seems to fail: >>> >>> [epjitsu] read_from_scanner: start rB:24584 len:24584 >>> [epjitsu] do_cmd: start >>> [epjitsu] in: memset 24584 bytes >>> [epjitsu] in: reading 24584 bytes, timeout 10000 >>> [epjitsu] in: retVal 9 >>> [epjitsu] in: return error 'Error during device I/O' >>> [epjitsu] read_from_scanner: error reading status = 9 >>> [epjitsu] read_from_scanner: finish rB:24576 len:0 >>> [epjitsu] coarsecal: cant read from scanner >>> [epjitsu] sane_start: ERROR: failed to coarsecal >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> scanimage: sane_start: Error during device I/O >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> [epjitsu] sane_close: start >>> [epjitsu] sane_cancel: start >>> [epjitsu] sane_cancel: finish >>> [epjitsu] lamp: start (0) >>> [epjitsu] do_cmd: start >>> [epjitsu] cmd: writing 2 bytes, timeout 10000 >>> [epjitsu] cmd: >> >>> [epjitsu] 000: 1b d0 >>> [epjitsu] cmd: wrote 2 bytes, retVal 0 >>> [epjitsu] in: memset 1 bytes >>> [epjitsu] in: reading 1 bytes, timeout 10000 >>> [epjitsu] in: retVal 0 >>> [epjitsu] in: read 1 bytes >>> [epjitsu] in: << >>> [epjitsu] 000: 15 >>> [epjitsu] do_cmd: finish >>> >>> So my question is did anybody have luck with the S1300i and got it to >>> work? >>> >>> The other question is about the S1100: I found the epjitsu-21.diff which >>> seems promising. I saw nice things like the device names being set >>> according to the name and serial number of the device. But, is it still >>> the current version? Since it's said that it works with the S1100 but >>> breaks the other devices, was there any progress made in the mean time? >>> >>> Regards, >>> Simon >>> >>> >>> -- >>> sane-devel mailing list: sane-devel at lists.alioth.debian.org >>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel >>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>> to sane-devel-request at lists.alioth.debian.org >> >> >> >> -- >> "The truth is an offense, but not a sin" >> > > -- "The truth is an offense, but not a sin"