[sane-devel] Canon FS4000

[eric@b.org]

Hi,

For my first post in this _new_ list, I think I've got some good news :-)

I've tested usbsnoopy and Vuescan with success [ *usb and SCSI* ] on 
win98SE  :-)

So : for now the FS4000 works with VuesScan with SCSI/usb in windows, 
only SCSI in Linux.

Not tested other usb-sniffer on Windows. I'll test them next time.


Of course, I have some questions :

1) Is someone in this list interested with the Canon FS4000US 
usbsnoop-logs ?

2) Next time (tomorrow), I'll print them, because, again in Linux, I've 
seen that usbsnoop-logs are binaries :-/
How are this logs readable/usable in Linux ? (how can I read them, 
excepted in Windows ?)

3) I've seen that I can log every action with the scanner. Are all the 
tests necessary, (for login all the commands) or do I need only a few of 
them ? Must I repeat them (are usb commands  "noisy" ? )

4) For sniffing the SCSI bus under Linux (with VueScan), I've planned to 
have a module with debug. So, from my /usr/src/linux.config, I have 
CONFIG_SCSI_DEBUG=m (last 2.4.23pre4 kernel) and there is a scsi_debug 
module in /lib/... ). modprobe scsi_debug give me a lot off information, 
is it enough to can compare the commands ?

First rescan the scsi bus :

Host adapter 2 (scsi_debug) found.
Scanning for device 1 0 1 0 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 00
       Vendor: CANON    Model: IX-40015G        Rev: 1.07
       Type:   Scanner                          ANSI SCSI revision: 02
Scanning for device 1 0 6 0 ...
OLD: Host: scsi1 Channel: 00 Id: 06 Lun: 00
       Vendor:          Model: Scanner          Rev: 1.60
       Type:   Scanner                          ANSI SCSI revision: 04

Sane-find-scanner can see the FS4000 too !  :

  tomate:/home/eric# sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.

sane-find-scanner: found SCSI scanner "CANON IX-40015G 1.07" at device 
/dev/sg2

But (?)

tomate:/home/eric# scanimage -L
device `microtek:/dev/sg10' is a Microtek ScanMaker E3 flatbed scanner

And there is no FS4000 more...


My first log on Linux :

tomate:/home/eric# tail -f /var/log/kern.log
Sep 19 21:32:01 tomate kernel: scsi singledevice 0 0 6 0
Sep 19 21:32:01 tomate kernel: scsi singledevice 0 0 7 0
Sep 19 21:32:59 tomate kernel: scsi2 : scsi_debug, Version: 0.61 
(20020815), num_devs=1, dev_size_mb=8, opts=0x0
Sep 19 21:32:59 tomate kernel:   Vendor: Linux     Model: scsi_debug 
     Rev: 0004
Sep 19 21:32:59 tomate kernel:   Type:   Direct-Access 
     ANSI SCSI revision: 03
Sep 19 21:33:51 tomate kernel: (scsi1:1:0) parity error
Sep 19 21:33:55 tomate kernel: scsi : 2 hosts left.
Sep 19 21:33:59 tomate kernel: scsi2 : scsi_debug, Version: 0.61 
(20020815), num_devs=1, dev_size_mb=8, opts=0x0
Sep 19 21:33:59 tomate kernel:   Vendor: Linux     Model: scsi_debug 
     Rev: 0004
Sep 19 21:33:59 tomate kernel:   Type:   Direct-Access 
     ANSI SCSI revision: 03
Sep 19 21:36:20 tomate kernel: (scsi1:1:0) datai sempty 
timeout<3>(scsi1:1:0) fifos should be empty and phase should have changed
Sep 19 21:36:20 tomate kernel: (scsi1:1:0) manual transfer count differs 
from automatic 
(count=56320;stcnt=56460;diff=140;fifostat=132)<3>(scsi1:1:0) parity error

modinfo say me to load the scsi_debug module with :

modprobe scsi_debug scsi_debug_opts 4

To be continued....



5) the translation of backend-writing_fr.txt is nearly OK (thanks to 
Yann E. Morin). What Can I do with it ? ( in other way : may I use the 
CVS ?). I'm not very good, I know, but I prefer ask before do something 
bad...


Thanks for advance


Regards


-- 
NO ePATENTS / NON AUX BREVETS SUR LES LOGICIELS. Voir / See 
http://swpat.ffii.org/

eric b