[sane-avision] Re: [sane-devel] re: Minolta Dimage scan dual II
On Friday 09 June 2006 14:17, Rene Rebe wrote:
Hi,
The device already contains some comments that it might be neded, look at
this:
{ MINOLTA, FS-V1,
0x0638, 0x026a,
Minolta, Dimage Scan Dual II,
AV_FILMSCANNER}, /* maybe AV_ONE_CALIB_CMD */
/* comment=1 pass, film-scanner */
/* status=good */
Can you try if you make the line:
AV_FILMSCANNER | AV_ONE_CALIB_CMD
You are right. It was not complicated and the comment said all that was
needed. Sorry for not reading carefully.
Can you also please send me a log with calibration with
SANE_DEBUG_AVISION=7 ?
I am attaching the files calib_orig and calib_one_cmd.
A problem is now appearing when scanning, at the end of the process some data
is lost. I am also attaching a scan log, as this situation may eventually
have a solution as simple as the previous
Regards
ZP
-- next part --
A non-text attachment was scrubbed...
Name: calib_orig.gz
Type: application/x-gzip
Size: 5266 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060614/e6411bbe/calib_orig-0001.bin
-- next part --
A non-text attachment was scrubbed...
Name: calib_one_cmd.gz
Type: application/x-gzip
Size: 5139 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060614/e6411bbe/calib_one_cmd-0001.bin
-- next part --
A non-text attachment was scrubbed...
Name: scan_one_cmd.gz
Type: application/x-gzip
Size: 5235 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060614/e6411bbe/scan_one_cmd-0001.bin
From j...@jon.demon.co.uk Wed Jun 14 19:59:56 2006
From: j...@jon.demon.co.uk (Jon Chambers)
Date: Wed Jun 14 20:00:22 2006
Subject: [sane-devel] scanimage --batch
Message-ID: pine.lnx.4.64.0606142051400.26...@vadim1.home
Hi,
I have been testing the dell1600n_net backend against the daily snapshots
and have noticed the following: If I run
scanimage --batch --batch-count=3
then I can scan three pages fine. If I just do
scanimage --batch
and press ctrl-c a couple of times while it is waiting on the 4th page
then my last (3rd) image will be slightly truncated. Multipage scanning
works fine with xsane.
My guess would be an unflushed file buffer that is lost when killed by an
interrupt?
cheers,
Jon
== Jon Chambers =
http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669
=
[sane-avision] Re: [sane-devel] re: Minolta Dimage scan dual II
Hi,
sorry for the delay.
On Tuesday 30 May 2006 10:36, Jose Paulo Moitinho de Almeida wrote:
Using the version in the package (build 182) I had problems that seemed
very similar to your log, but with a (much) older version (build 99) I
could a scan without problems. From files that I found laying around I
would say that build 153 was also working.
In any case I promise to try a more rigorous test later on.
Yesterday I tested several versions and I think that at least one of the
problems has to do with the calibration method, when the backend chooses
between one command or send data channel by channel. The driver is
using the second and hangs. I forced the driver to use the first method and
it seems to work.
Rene, if you please check in the correct voodoo (AV_ONE_CALIB_CMD or
AV_MULTI_CALIB_CMD or ...) I can check more thoroughly how the code
behaves.
The device already contains some comments that it might be neded, look at
this:
{ MINOLTA, FS-V1,
0x0638, 0x026a,
Minolta, Dimage Scan Dual II,
AV_FILMSCANNER}, /* maybe AV_ONE_CALIB_CMD */
/* comment=1 pass, film-scanner */
/* status=good */
Can you try if you make the line:
AV_FILMSCANNER | AV_ONE_CALIB_CMD
Can you also please send me a log with calibration with
SANE_DEBUG_AVISION=7 ?
Yours,
--
Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://exactcode.de | http://t2-project.org | http://rebe.name
+49 (0)30 / 255 897 45
[sane-devel] re: Minolta Dimage scan dual II
On Thursday 25 May 2006 09:03, Jose Paulo Moitinho de Almeida wrote:
...
Using the version in the package (build 182) I had problems that seemed
very similar to your log, but with a (much) older version (build 99) I
could a scan without problems. From files that I found laying around I
would say that build 153 was also working.
In any case I promise to try a more rigorous test later on.
Yesterday I tested several versions and I think that at least one of the
problems has to do with the calibration method, when the backend chooses
between one command or send data channel by channel. The driver is using
the second and hangs. I forced the driver to use the first method and it
seems to work.
Rene, if you please check in the correct voodoo (AV_ONE_CALIB_CMD or
AV_MULTI_CALIB_CMD or ...) I can check more thoroughly how the code behaves.
Old (but working)
out_size = format-pixel_per_line * 2;
/* send data in one command? */
if (format-channels == 1 ||
( (dev-hw-feature_type AV_ONE_CALIB_CMD) ||
! BIT(format-ability1, 0) ) )
/* one command (most scanners) */
{
-- New (but hanging)
out_size = format-pixel_per_line * 2;
/* send data in one command? */
/* FR: HP5370 reports one-pass, but needs multi (or other format in single)
*/
if (format-channels == 1 ||
( ( (dev-hw-feature_type AV_ONE_CALIB_CMD) ||
! BIT(format-ability1, 0) )
! (dev-hw-feature_type AV_MULTI_CALIB_CMD) ) )
/* one command (most scanners) */
{
---
Regards
ZP
[sane-devel] re: Minolta Dimage Scan Dual II
On Tuesday 23 May 2006 20:47, Dietmar Segbert wrote: Hello Rene and Jose, hello list, now i have tested the following commands: scanimage -d avision test.pnm 2error.asc (door was closed an no film holder) scanimage -d avision --frame 1 --resolution 2820 bild.pnm 2error1.asc (doo was half open, film holder with three negatives) But nothing happened, also not without the resolution-option. Here are the error.asc and error1.asc I will need to check the current version and which version was working for me. I hope to be able to do it tonight.
[sane-devel] re: Minolta Dimage Scan Dual II
Hi, From your first log we can see that the scanner is recognised. It sees that there is no film holder, it waits for the lamp to warm up, all perfect, and then it starts the calibration process. Everything seems to be ok, until we get to the portion that I am attaching. There we start having timeouts while reading the calibration data, and the backend complains dark data present - decreasing white aerage data. I suspect that there may be a problem related to libusb (chunk size? invalid parameter?), as the process of reading calibration data should be fairly normal. Nope, it got the calibration data: [avision] get_calib_data: Got 249300 bytes calibration data The line you reffer to just prints the timeouts used for the command (the timeouts vary, because device discover uses shorter timeouts to not stall on locked devices - or to wake up ping crashed firmware). It fails sending the calibration (shading) data back to the scanner: [avision] set_calib_data_calibration: channel: 0 [avision] set_calib_data: sending 5540 bytes now [avision] Timeouts: write: 3, read: 3, status: 1 [avision] === Got error 9 trying to write, wrote: 0. === From that point on every action fails. Yep, from the point corrected above the devices firmware or USB bridge is stalled. Yours, -- Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany) http://exactcode.de | http://t2-project.org | http://rebe.name +49 (0)30 / 255 897 45
[sane-devel] re: Minolta Dimage scan dual II
Hello rene, hello Jose, after a lot of testing, i have looked to the right of the usb device, because i did not find the scanner as user and so i have set the rights of the scanner /roc/bus/usb/004/003 to root:usb (chown root:usb ... Voila, the scanner works. I will send the first scanned negative to my brother, so that he can look for the quality, what i can't do, because i am blind. Regards. dietmar
[sane-devel] re: Minolta Dimage Scan Dual II
Hello Rene and Jose, hello list, now i have tested the following commands: scanimage -d avision test.pnm 2error.asc (door was closed an no film holder) scanimage -d avision --frame 1 --resolution 2820 bild.pnm 2error1.asc (doo was half open, film holder with three negatives) But nothing happened, also not without the resolution-option. Here are the error.asc and error1.asc Regards Dietmar [sanei_debug] Setting debug level of avision to 7. [avision] sane_init:(Version: 1.0 Build: 200) [avision] sane_init: parsing config line [avision] sane_init: config file line 1: ignoring empty line [avision] sane_init: parsing config line # This are the possible options. Normally any scanner [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line # should work just fine without them - and they are only [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line # needed for test and debugging. So if you experience problems [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line # and you solve them with enabling options here, please notify [avision] sane_init: config file line 5: ignoring comment line [avision] sane_init: parsing config line # the SANE/Avision maintainer: Rene Rebe r...@exactcode.de [avision] sane_init: config file line 6: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 7: ignoring empty line [avision] sane_init: parsing config line #option disable-gamma-table [avision] sane_init: config file line 8: ignoring comment line [avision] sane_init: parsing config line #option disable-calibration [avision] sane_init: config file line 9: ignoring comment line [avision] sane_init: parsing config line #option force-a4 [avision] sane_init: config file line 10: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 11: ignoring empty line [avision] sane_init: parsing config line scsi AVISION [avision] sane_init: config file line 12: trying to attach SCSI: scsi AVISION' [avision] sane_init: parsing config line #scsi FCPA [avision] sane_init: config file line 13: ignoring comment line [avision] sane_init: parsing config line scsi MINOLTA [avision] sane_init: config file line 14: trying to attach SCSI: scsi MINOLTA' [avision] sane_init: parsing config line #scsi MITSBISH MCA-S600C [avision] sane_init: config file line 15: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-SS600 [avision] sane_init: config file line 16: ignoring comment line [avision] sane_init: parsing config line #scsi HP [avision] sane_init: config file line 17: ignoring comment line [avision] sane_init: parsing config line #scsi hp [avision] sane_init: config file line 18: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 19: ignoring empty line [avision] sane_init: parsing config line #scsi /dev/sg5 [avision] sane_init: config file line 20: ignoring comment line [avision] sane_init: parsing config line # usb libusb:002:003 [avision] sane_init: config file line 21: ignoring comment line [avision] sane_init: parsing config line # usb 0x03f0 0x0701 [avision] sane_init: config file line 22: ignoring comment line [avision] sane_init: parsing config line usb 0x0638 0x026a [avision] sane_init: config file line 23: trying to attach USB:`usb 0x0638 0x026a' [avision] attach: [avision] attach: opening libusb:004:004 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] attach: Inquiry gives mfg=MINOLTA, model=FS-V1, product revision=1.26. [avision] attach: Found model: 55 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] attach: raw data: [avision] [0] 0110b 6o 6d 6x [avision] [1] 1000b 200o 128d 80x [avision] [2] 0010b 2o 2d 2x [avision] [3] 0110b 102o 66d 42x [avision] [4] 01011011b 133o 91d 5bx [avision] [5] b 0o 0d 0x [avision] [6] b 0o 0d 0x [avision] [7] b 0o 0d 0x [avision] [8] 01001101b 115o 77d 4dx [avision] [9] 01001001b 111o 73d 49x [avision] [10] 01001110b 116o 78d 4ex [avision] [11] 0100b 117o 79d 4fx
[sane-devel] re: Minolta Dimage Scan Dual II
look at the end- scanimage: attempted to set inactive option frame dont set that :) allan On Mon, 22 May 2006, Dietmar Segbert wrote: Hello Rene, hello list, thanks for your answers. At first i have deleted the hpusbsci in /lib/modules/2.4.31/kernel/ I have donwloaded the avision.c and avision.h of the svn repository of the avision-backend-page. I compiled sane by ./configure make make install. I set the rights of the scanner to rwrwrw (666). scanimage -L finds the scanner. i set the SANE_DEBUG-AVISION=7 and then i do the following command: scanimage -d avision --source adf --resolution 2820 --frame 1 out%d.pnm 2error.log Here is the logfile: [sanei_debug] Setting debug level of avision to 7. [avision] sane_init:(Version: 1.0 Build: 200) [avision] sane_init: parsing config line [avision] sane_init: config file line 1: ignoring empty line [avision] sane_init: parsing config line # This are the possible options. Normally any scanner [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line # should work just fine without them - and they are only [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line # needed for test and debugging. So if you experience problems [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line # and you solve them with enabling options here, please notify [avision] sane_init: config file line 5: ignoring comment line [avision] sane_init: parsing config line # the SANE/Avision maintainer: Rene Rebe r...@exactcode.de [avision] sane_init: config file line 6: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 7: ignoring empty line [avision] sane_init: parsing config line #option disable-gamma-table [avision] sane_init: config file line 8: ignoring comment line [avision] sane_init: parsing config line #option disable-calibration [avision] sane_init: config file line 9: ignoring comment line [avision] sane_init: parsing config line #option force-a4 [avision] sane_init: config file line 10: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 11: ignoring empty line [avision] sane_init: parsing config line scsi AVISION [avision] sane_init: config file line 12: trying to attach SCSI: scsi AVISION' [avision] sane_init: parsing config line #scsi FCPA [avision] sane_init: config file line 13: ignoring comment line [avision] sane_init: parsing config line scsi MINOLTA [avision] sane_init: config file line 14: trying to attach SCSI: scsi MINOLTA' [avision] sane_init: parsing config line #scsi MITSBISH MCA-S600C [avision] sane_init: config file line 15: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-SS600 [avision] sane_init: config file line 16: ignoring comment line [avision] sane_init: parsing config line #scsi HP [avision] sane_init: config file line 17: ignoring comment line [avision] sane_init: parsing config line #scsi hp [avision] sane_init: config file line 18: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 19: ignoring empty line [avision] sane_init: parsing config line #scsi /dev/sg5 [avision] sane_init: config file line 20: ignoring comment line [avision] sane_init: parsing config line # usb libusb:002:003 [avision] sane_init: config file line 21: ignoring comment line [avision] sane_init: parsing config line # usb 0x03f0 0x0701 [avision] sane_init: config file line 22: ignoring comment line [avision] sane_init: parsing config line usb 0x0638 0x026a [avision] sane_init: config file line 23: trying to attach USB:`usb 0x0638 0x026a' [avision] attach: [avision] attach: opening libusb:004:002 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] attach: Inquiry gives mfg=MINOLTA, model=FS-V1, product revision=1.26. [avision] attach: Found model: 55 [avision] inquiry: 96 [avision] attach: sending INQUIRY [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 1500, status: 1500 [avision] avision_usb_status: timeout 1500, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] attach: raw data: [avision] [0] 0110b 6o 6d 6x [avision] [1] 1000b 200o 128d 80x [avision] [2] 0010b 2o 2d 2x [avision]
