[sane-devel] Plustek ST24
hi all recently i've discover that in backend/gensys_devices.c is placed sort of values for ST24. iv done small change in backend/gensys_devices.c:728 from COLOR_ORDER_BGR to COLOR_ORDER_RGB and in same file at line 726 value 0,8,16 to 0,18,30. that gives correct colors on my plustek st 24 and good correction of ccd line-distance. Sadly only for resolution 600dpi which has wrong number of engine steps what can leads to damange of hardware. For simple workaround i limited y size of scan area to 1/4 of nominal size but its givs 600dpi x150dpi :/. If sobody have any ideas how can i correct number of steps for resolutions larger then 150 dpi plz msg me. Also i have fears that corect number of steps dosnt resolve problem with ccd line distance in resolutions difirent then 600 dpi(for 150 dpi those values are difirent 2,18,32 perhaps). Any ideas are welcome :) ps. sorry for my bad anglish ;) its 03:00 am and anglish isnt my native lang :
[sane-devel] CanoScan LiDE 25 not found on Win XP
Thanks. As far as I can tell the problem is not that the dlls are not found, but that they are not built at all. The usr/local/lib/sane directory contains .a and .la files, and not .dll files. I couldn't find the plustek dll anywhere. When are these dlls supposed to be built? Is there some special setting I need to set? Thanks, Guy On 11/25/06, sane-devel-requ...@lists.alioth.debian.org sane-devel- Message: 1 Date: Fri, 24 Nov 2006 14:04:36 +0100 From: Gerhard Jaeger gerh...@gjaeger.de Subject: Re: [sane-devel] CanoScan LiDE 25 not found on Win XP To: sane-devel@lists.alioth.debian.org Message-ID: 200611241404.37138.gerh...@gjaeger.de Content-Type: text/plain; charset=iso-8859-15 On Friday 24 November 2006 12:50, Guy Yitzhaki wrote: Hi, I am trying to get my CanoScan LiDE 25 to work with the sane library on Windows XP, using Cygwin. When I run sane-find-scanner it detects the scanner correctly (I think) - this is the output: *found 4 busses found USB scanner (vendor=0x1690 [GlobeSpan Inc.], product=0x0211 [USB-ADSL Modem]) at libusb:bus-1:\\.\libusb0-0005--0x1690-0x0211 found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan]) at libusb:bus-1:\\.\libusb0-0006--0x04a9-0x2220 * But when I try running scanimage -L (with SANE_DEBUG_DLL=7) it does not find the scanner. It seems as though it cannot find the backends at all. Here is the output: *[sanei_debug] Setting debug level of dll to 7. [dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.0.18 [dll] sane_init: reading dll.conf [SNIPSNAP] [dll] add_backend: adding backend `plustek' [SNIPSNAP] [dll] load: searching backend `plustek' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/cygsane- plustek-1.dll' [dll] load: couldn't open `/usr/local/lib/sane/cygsane-plustek-1.dll' (No such file or directory) [dll] load: couldn't find backend `plustek' (No such file or directory) [SNIPSNAP] - Get rid of the other backends by commenting them out in dll.conf - Fix the path issues within your Cygwin environment - don't know how, but all your dlls couldn't be found... Gerhard -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061125/6839e996/attachment.html From azummo-li...@towertech.it Sat Nov 25 10:14:02 2006 From: azummo-li...@towertech.it (Alessandro Zummo) Date: Sat Nov 25 10:14:30 2006 Subject: [sane-devel] strange SCSI behaviour Message-ID: 20061125101402.0fde7857@inspiron Hello, I just discovered the problem I had with my FilmScan 200 is not related to any particular command but just to the first one sent to the scanner (just after modprobe) After that one, which receives a sense condition, everything works perfectly. So, if there's a way to have the control immediately returned to the driver as soon as the sense condition is issued, I would just try reissuing the command and that should fix my problem. Any hint on how to do that? thanks! [epson2] inquiry: EPSON FilmScan 2001.01 [epson2] model : FilmScan 2001.01 [epson2] reset [epson2] epson_cmd_simple: size = 2 [epson2] epson_send: ESC @ [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 02 host status: driver status: 0008 [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 2 [sanei_scsi] NOTE: This value may be bogus [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [~2 min delay here, the the aic7xxx driver queues an ABORT and the scanner resets ] [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 00 host status: 0001 driver status: [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 1 [sanei_scsi] NOTE: This value may be bogus [epson2] epson_recv: expected = 1, got = 0 [epson2] epson_cmd_simple: failed, Device busy this command has failed, but subsequent ones work correctly. -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] strange SCSI behaviour
On Sat, 25 Nov 2006, Alessandro Zummo wrote: Hello, I just discovered the problem I had with my FilmScan 200 is not related to any particular command but just to the first one sent to the scanner (just after modprobe) After that one, which receives a sense condition, everything works perfectly. So, if there's a way to have the control immediately returned to the driver as soon as the sense condition is issued, I would just try reissuing the command and that should fix my problem. Any hint on how to do that? but your inquiry command worked? its just the first epson_cmd_simple that fails? try calling test unit ready before this, and see if that works. do you have a request sense callback setup? allan thanks! [epson2] inquiry: EPSON FilmScan 2001.01 [epson2] model : FilmScan 2001.01 [epson2] reset [epson2] epson_cmd_simple: size = 2 [epson2] epson_send: ESC @ [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 02 host status: driver status: 0008 [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 2 [sanei_scsi] NOTE: This value may be bogus [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [~2 min delay here, the the aic7xxx driver queues an ABORT and the scanner resets ] [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 00 host status: 0001 driver status: [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 1 [sanei_scsi] NOTE: This value may be bogus [epson2] epson_recv: expected = 1, got = 0 [epson2] epson_cmd_simple: failed, Device busy this command has failed, but subsequent ones work correctly. -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Epson DX 5000
Hi! i have this all-in-one printer, and scanner it's working perfect
with sane adding this line on epson.conf:
usb 0x04b8 0x082b
I've added on /etc/udev/libsane-extras.rules this line too:
SYSFS{idVendor}==04b8, SYSFS{idProduct}==082b, MODE=664,
GROUP=scanner
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y m?viles desde 1 c?ntimo por minuto.
http://es.voice.yahoo.com
[sane-devel] strange SCSI behaviour
Alessandro, I just discovered the problem I had with my FilmScan 200 is not related to any particular command but just to the first one sent to the scanner (just after modprobe) After that one, which receives a sense condition, everything works perfectly. So, if there's a way to have the control immediately returned to the driver as soon as the sense condition is issued, I would just try reissuing the command and that should fix my problem. Any hint on how to do that? thanks! [epson2] inquiry: EPSON FilmScan 2001.01 [epson2] model : FilmScan 2001.01 [epson2] reset [epson2] epson_cmd_simple: size = 2 [epson2] epson_send: ESC @ [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 02 host status: driver status: 0008 [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 2 [sanei_scsi] NOTE: This value may be bogus [sanei_scsi] scsi_req_enter: entered 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 Perhaps I am missing the point, but here one SCSI command finished with an error, and below another SCSI command is sent to the device. Can't you check for the error here and decide to wait? Or handle the sense data in another way? Admitted, the data of the sense buffer is not very enlightening: UNIT ATTENTION does not tell very much by itself, but you know which command caused the error, and the documentation of the scanner may give a better clue what might have happened. Calling TEST UNIT READY before a real command is often also a good way to avoid longer hangs. Abel [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c75008 [sanei_scsi] sanei_scsi.issue: 0xb7c75008 [~2 min delay here, the the aic7xxx driver queues an ABORT and the scanner resets ] [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success [sanei_scsi] sense buffer: 70 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 00 host status: 0001 driver status: [sanei_scsi] sanei_scsi_req_wait: SG driver returned resid 1 [sanei_scsi] NOTE: This value may be bogus [epson2] epson_recv: expected = 1, got = 0 [epson2] epson_cmd_simple: failed, Device busy this command has failed, but subsequent ones work correctly.
