[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'mail at test.ws' 2. Manufacturer (e.g. Mustek): '' 3. Model name (e.g. ScanExpress 1200UB): 'Bober' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 6. Product id (e.g. 0x0002): '' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'a href=http://www.digitalcamerainfo.com/bbs/member.php?u=1860;buy viagra online/abra href=http://www.gamecareerguide.com/forums/member.php?u=2520;buy cialis online/abra href=http://extjs.com/forum/member.php?u=24461;buy cialis/abra href=http://www.gamecareerguide.com/forums/member.php?u=2478;cheap cialis/abra href=http://forum.springframework.org/member.php?u=34111;generic viagra/abra href=http://www.layersmagazine.com/forum/member.php?u=4276;buy viagra/abra href=http://ringtones.forum5.com;download free ringtones/abra href=http://forum.springframework.org/member.php?u=34397;buy valium/abra href=http://forums.ipodhacks.com/member.php?u=35372;buy tramadol/abra href=http://www.layersmagazine.com/forum/member.php?u=4313;replica watch/a' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Canon LiDE 80 (2nd try)
You are talking about writes like: I guess YES. Yes, I do. Now I found the right one AND the right time: Before doing the reset ;-). So now I've the initial motor movement with LED blinking and a scan movement with green LED. But no (strange) data arrives. I tried your diff, but I get the known 'invalid argument error'. Regards, Reinhard Debug output of scanimage: [genesys_gl841] gl841_init [genesys_gl841] gl841_init_registers [genesys_gl841] gl841_setup_sensor [genesys_gl841] gl841_init_registers complete [genesys] sanei_genesys_write_register (0x60, 0x06) completed [genesys] sanei_genesys_write_register (0x61, 0x13) completed [genesys] sanei_genesys_write_register (0x62, 0x55) completed [genesys] sanei_genesys_write_register (0x63, 0x02) completed [genesys] sanei_genesys_write_register (0x64, 0x34) completed [genesys] sanei_genesys_write_register (0x65, 0x04) completed [genesys_gl841] gl841_set_buffer_address_gamma: setting address to 0x0c000 [genesys] sanei_genesys_write_register (0x5c, 0x00) completed [genesys] sanei_genesys_write_register (0x5b, 0x0c) completed [genesys_gl841] gl841_set_buffer_address_gamma: completed [genesys_gl841] gl841_bulk_write_data_gamma writing 128 bytes [genesys_gl841] genesys_bulk_write_data:gamma wrote 128 bytes, 0 remaining [genesys_gl841] genesys_bulk_write_data_gamma: completed [genesys] sanei_genesys_write_register (0x0e, 0x00) completed [genesys] sanei_genesys_write_register (0x6b, 0x0c) completed [genesys] sanei_genesys_write_register (0x6e, 0x6d) completed [genesys] sanei_genesys_write_register (0x6c, 0x00) completed [genesys_gl841] gl841_bulk_write_register (elems = 104) [genesys_gl841] reg[0x01] = 0xa0 [genesys_gl841] reg[0x02] = 0x38 ... [genesys_gl841] reg[0x6b] = 0x02 [genesys_gl841] reg[0x6e] = 0x6d [genesys_gl841] gl841_bulk_write_register: failed while writing command: Invalid argument scanimage: open of device genesys:libusb:001:010 failed: Invalid argument
[sane-devel] General technical docs for flatbed scanners
Hi list, anybody knows if/where to find $subject on the web? Something that describes some details of motor control, lamp control and analog/digital postprocessing, as well as the general scanning operating. Just enough for a developer of a driver for a dumb chip(like the genesys chips). If noone comes up with anything, i will try to create such a thing and post it here for comments. Regards, Pierre
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
Hello all, sane-backends-1.0.19.tar.gz.md5 file was expected to be 62 bytes; but downloads as 87977 bytes This needs correction. The commands I executed are shown below. Thanks Gerald What the download page at http://alioth.debian.org/frs/?group_id=30186 says sane-backends-1.0.19.tar.gz.md5 62 bytes 0 Any Other % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 87977 2008-02-11 00:19 sane-backends-1.0.19.tar.gz.md5 % file sane-backends-1.0.19.tar.gz.md5 sane-backends-1.0.19.tar.gz.md5: gzip compressed data, was sane-backends-1.0.18-1.0.19.dif, from Unix, last modified: Sun Feb 10 17:57:05 2008
[sane-devel] Canon LiDE 80 (2nd try)
On Monday 11 February 2008, Reinhard Biegel wrote: You are talking about writes like: I guess YES. Yes, I do. Now I found the right one AND the right time: Before doing the reset ;-). So now I've the initial motor movement with LED blinking and a scan movement with green LED. But no (strange) data arrives. I tried your diff, but I get the known 'invalid argument error'. Regards, Reinhard Debug output of scanimage: [genesys_gl841] genesys_bulk_write_data_gamma: completed [genesys] sanei_genesys_write_register (0x0e, 0x00) completed [genesys] sanei_genesys_write_register (0x6b, 0x0c) completed Writing value 0x08 is enough for me. Following 2 register writes can be skipped. That's around line 5166 in genesys_gl841.c Additional you may prevent register 0x6b from further writes by excluding it around line 409. In file genesys_devices.c you can change around line 585 the y start position from 7.9 mm to 4.9 mm, as my scan head reaches opposite of home position audible. [genesys] sanei_genesys_write_register (0x6e, 0x6d) completed [genesys] sanei_genesys_write_register (0x6c, 0x00) completed [genesys_gl841] gl841_bulk_write_register (elems = 104) [genesys_gl841] reg[0x01] = 0xa0 [genesys_gl841] reg[0x02] = 0x38 ... [genesys_gl841] reg[0x6b] = 0x02 [genesys_gl841] reg[0x6e] = 0x6d [genesys_gl841] gl841_bulk_write_register: failed while writing command: Invalid argument scanimage: open of device genesys:libusb:001:010 failed: Invalid argument At that moment, I guess you'll see messages like: new high speed USB device using ehci_hcd and address nn via dmesg. Which way is your scanner connected ? Mine is connected via a self powered USB 2 hub. -- Stefan Lucke
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
unable to reproduce. can you try again? allan On 2/11/08, Gerald Murray gmurray at cloudnet.com wrote: Hello all, sane-backends-1.0.19.tar.gz.md5 file was expected to be 62 bytes; but downloads as 87977 bytes This needs correction. The commands I executed are shown below. Thanks Gerald What the download page at http://alioth.debian.org/frs/?group_id=30186 says sane-backends-1.0.19.tar.gz.md5 62 bytes 0 Any Other % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 87977 2008-02-11 00:19 sane-backends-1.0.19.tar.gz.md5 % file sane-backends-1.0.19.tar.gz.md5 sane-backends-1.0.19.tar.gz.md5: gzip compressed data, was sane-backends-1.0.18-1.0.19.dif, from Unix, last modified: Sun Feb 10 17:57:05 2008 -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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
[sane-devel] General technical docs for flatbed scanners
i would LOVE to see such a doc, but never have. but its not just flatbeds- cheaper adfs use the same chips... allan On 2/10/08, Pierre Willenbrock pierre at pirsoft.dnsalias.org wrote: Hi list, anybody knows if/where to find $subject on the web? Something that describes some details of motor control, lamp control and analog/digital postprocessing, as well as the general scanning operating. Just enough for a developer of a driver for a dumb chip(like the genesys chips). If noone comes up with anything, i will try to create such a thing and post it here for comments. Regards, Pierre -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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
[sane-devel] Epson Perfection 4990 driver
there are 3 backends which support this machine. the one which lists these two points is external to sane, so you might want to ask avasys directly. of the other two, one is unmaintained, and the other is new, so we may not be able to provide you with an answer. maybe you can get one and tell us :) allan On 2/10/08, JD jd1008 at gmail.com wrote: What functionality is missing from this driver other than 1- film area guide mode not supported 2- IEEE1394 untested -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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
[sane-devel] deadlock with sanei_usb_read_bulk
excellent work. please keep us informed.
allan
On 2/10/08, J?rgen Ernst jrernst at gmx.de wrote:
Hi!
I managed to solve the problem.
Here it is:
Canon driver sends a dummy bulk write as shown in the log. It only
produces errors and I think it's only for delaying bulk reads. We can
omit that and use a fix delay of 1 ms instead.
Sanei_USB sets the right endpoints. I can read and write data on
endpoint 0. It's all as it should be. Now initializing scanner and
reading buttons is working. Getting access to scandata is following.
J?rgen Ernst wrote:
Hi!
I'm trying to write the backend for Canon LiDE 600F and now I'm stuck
with sanei_usb_read_bulk. I tried 10 hours but I don't understand how to
get sanei_usb working with bulk_read. Can somebody help me out?
Here are some details:
Canon LiDE 600F is similar to Canon LiDE 70. I checked this with two
guys owning a LiDE 70. So you can read some info on
http://www.sane-project.org/unsupported/canon-lide-70.html
...
endpoint 0
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
...
endpoint 0
bEndpointAddress 0x83 (in 0x03)
bmAttributes 2 (bulk)
...
For short:
LiDE 600F has only two endpoints. Both bulk no interrupt. In the log
file no control messages are used. Only simple bulk read and write.
I programmed a perl script with which I was able to access the scanner
and retrieve scan data.
So this was the point to start writing the sane backend in C.
Okay, let's look first on a perl code snippet:
sub canon_get
{
my ( $reg ) = @_ ;
my $data = '01 ' . $reg . ' 01 00' ;
my $err = $dev-bulk_write(hex('02'), hex2bin($data), $timeout);
my $data = \0 x 512 ;
my $cnt = $dev-bulk_write(hex('03'), $data, $timeout);
my $data = ' ' ;
my $cnt = $dev-bulk_read(hex('83'), $data, 1, $timeout) ;
return ( $data ) ;
}
This is the procedure to get 1 byte of data from the CP2155 chip.
Suppose we called canon_get('91'); then $reg is '91' in hex.
$data is set to '01 91 01 00'.
I made it this way to better check with output from log.
hex2bin converts this string to binary.
Then a first bulk_write is made. In perl I had to give the
bEndpointAddress '02' while in sanei_usb I saw I had to give the
endpoint number as an integer (endpoint 0).
Second is a dummy write on the other endpoint (endpoint 1) with 512
bytes of data.
Third we can get the result with a 1 byte bulk_read on endpoint 1.
That's it.
But it doesn't work in sane.
Here's the snippet of my test procedure in C:
static byte setup_buffer[] = { 0, 0, 0, 0, ... ,0 };
static SANE_Status
CP2155get (CP2155_Register reg, byte *data)
{
SANE_Status status;
size_t count;
setup_buffer[0] = 0x01;
setup_buffer[1] = (reg) 0xFF;
setup_buffer[2] = 0x01;
setup_buffer[3] = 0x00;
count = 4;
status = sanei_usb_write_bulk (0, setup_buffer, count);
if (status != SANE_STATUS_GOOD)
DBG (1, CP2155get: sanei_usb_write_bulk.1 error\n);
count = 512;
status = sanei_usb_write_bulk (0, setup_buffer, count);
if (status != SANE_STATUS_GOOD)
DBG (1, CP2155get: sanei_usb_write_bulk.2 error\n);
count = 1;
status = sanei_usb_read_bulk (0, data, count);
if (status != SANE_STATUS_GOOD)
DBG (1, CP2155get: sanei_usb_read_bulk error\n);
return status;
}
setup_buffer is an array with 512 bytes.
The first two bulk_writes didn't return any error.
It seems that they worked fine.
On the last bulk_read the program hangs forever.
I surely did a mistake but I don't know where and why.
Please help.
--
sane-devel mailing list: sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/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
[sane-devel] Epson Perfection 4990 driver
I went to the epson-avasys web site and found they provide these files for this scanner: iscan-2.10.0-1.c2.i386.rpm iscan_2.10.0-1.tar.gz userg_revG_e.pdf I have not trie their driver yet. Will let you know once I have the scanner. JD m. allan noah wrote: there are 3 backends which support this machine. the one which lists these two points is external to sane, so you might want to ask avasys directly. of the other two, one is unmaintained, and the other is new, so we may not be able to provide you with an answer. maybe you can get one and tell us :) allan On 2/10/08, JD jd1008 at gmail.com wrote: What functionality is missing from this driver other than 1- film area guide mode not supported 2- IEEE1394 untested -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080211/159c99e2/attachment-0001.htm
[sane-devel] Canon LiDE 80 (2nd try)
Am Monday, 11. February 2008 schrieb Stefan Lucke: ... [genesys_gl841] reg[0x6b] = 0x02 [genesys_gl841] reg[0x6e] = 0x6d [genesys_gl841] gl841_bulk_write_register: failed while writing command: Invalid argument scanimage: open of device genesys:libusb:001:010 failed: Invalid argument At that moment, I guess you'll see messages like: new high speed USB device using ehci_hcd and address nn via dmesg. Hi, Yes, thats right. Changing the write to reg 0x6b from 0x0c to 0x08 fixes that. Scanner is producing noisy image now. Do I see right that the two bits (0x04 and 0x08 of register 0x6b) affect two pins which are marked as 'reserved' in the datasheet? They are only documented for GL843. After scanning I have to replug the scanner, otherwise I get an error message telling me the document feeder is jammed. Curiously, if I set SANE_DEBUG_GENESYS, there comes up another error about a failed bulk_write. Also I noticed that the LED isn't continuously illuminated. In one half it's continuous, but in the other there are small gaps (about 1mm) with about 4mm spacing between. In the middle there are a few with bigger spacing. Which way is your scanner connected ? Directly to the computer, no hubs. Regards, Reinhard
[sane-devel] Canon LiDE 80 (2nd try)
Reinhard Biegel schrieb: Am Monday, 11. February 2008 schrieb Stefan Lucke: ... [genesys_gl841] reg[0x6b] = 0x02 [genesys_gl841] reg[0x6e] = 0x6d [genesys_gl841] gl841_bulk_write_register: failed while writing command: Invalid argument scanimage: open of device genesys:libusb:001:010 failed: Invalid argument At that moment, I guess you'll see messages like: new high speed USB device using ehci_hcd and address nn via dmesg. Hi, Yes, thats right. Changing the write to reg 0x6b from 0x0c to 0x08 fixes that. Scanner is producing noisy image now. Do I see right that the two bits (0x04 and 0x08 of register 0x6b) affect two pins which are marked as 'reserved' in the datasheet? They are only documented for GL843. Register 0x6b is very different between GL841/2 and GL843. But the documentation around the pins controlled with 0x6b is a bit lacking. Did someone post the bcdDevice value of a LiDE 80? GL841 goes up to 3.0.5, as someone said, and GL842 begins with 3.0.6 After scanning I have to replug the scanner, otherwise I get an error message telling me the document feeder is jammed. Curiously, if I set SANE_DEBUG_GENESYS, there comes up another error about a failed bulk_write. The feeder jammed error happens when the backend thinks your scanning head is stuck. For example when someone forgot to open the lock. I guess we need SANE2 for more/better error messages. It is probably not really stuck, but the sensor input is incorrect. Also I noticed that the LED isn't continuously illuminated. In one half it's continuous, but in the other there are small gaps (about 1mm) with about 4mm spacing between. In the middle there are a few with bigger spacing. Sounds like it would normally be backtracking between the lighted areas, but does not for some reason. Just guessing. The LiDE 80 support is far from complete. Which way is your scanner connected ? Directly to the computer, no hubs. Regards, Reinhard Regards, Pierre
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
Quoting m. allan noah kitno455 at gmail.com: unable to reproduce. can you try again? allan Hello Allan, I tried again today, using the http mirror for the United States. It downloaded as the diff file. I also check some other mirrors, and 1.0.19 has not been propagated to them for update. % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 1245399 2008-02-11 11:01 sane-backends-1.0.19.tar.gz.md5 I got the md5sums off of the sane site, and it does check OK with the 1.0.19 package. The problem seems to be limited to this one http mirror, so far. Gerald On 2/11/08, Gerald Murray gmurray at cloudnet.com wrote: Hello all, sane-backends-1.0.19.tar.gz.md5 file was expected to be 62 bytes; but downloads as 87977 bytes This needs correction. The commands I executed are shown below. Thanks Gerald What the download page at http://alioth.debian.org/frs/?group_id=30186 says sane-backends-1.0.19.tar.gz.md5 62 bytes 0 Any Other % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 87977 2008-02-11 00:19 sane-backends-1.0.19.tar.gz.md5 % file sane-backends-1.0.19.tar.gz.md5 sane-backends-1.0.19.tar.gz.md5: gzip compressed data, was sane-backends-1.0.18-1.0.19.dif, from Unix, last modified: Sun Feb 10 17:57:05 2008
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
can you paste the full url you downloaded from? allan On Feb 11, 2008 1:48 PM, Gerald Murray gmurray at cloudnet.com wrote: Quoting m. allan noah kitno455 at gmail.com: unable to reproduce. can you try again? allan Hello Allan, I tried again today, using the http mirror for the United States. It downloaded as the diff file. I also check some other mirrors, and 1.0.19 has not been propagated to them for update. % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 1245399 2008-02-11 11:01 sane-backends-1.0.19.tar.gz.md5 I got the md5sums off of the sane site, and it does check OK with the 1.0.19 package. The problem seems to be limited to this one http mirror, so far. Gerald On 2/11/08, Gerald Murray gmurray at cloudnet.com wrote: Hello all, sane-backends-1.0.19.tar.gz.md5 file was expected to be 62 bytes; but downloads as 87977 bytes This needs correction. The commands I executed are shown below. Thanks Gerald What the download page at http://alioth.debian.org/frs/?group_id=30186 says sane-backends-1.0.19.tar.gz.md5 62 bytes 0 Any Other % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 87977 2008-02-11 00:19 sane-backends-1.0.19.tar.gz.md5 % file sane-backends-1.0.19.tar.gz.md5 sane-backends-1.0.19.tar.gz.md5: gzip compressed data, was sane-backends-1.0.18-1.0.19.dif, from Unix, last modified: Sun Feb 10 17:57:05 2008 -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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
[sane-devel] Epson Perfection 4990 driver
I have made the part of epson2 backend that special for the Perfection 4990 scanner. Every thing should work, but more testing would be nice. I have too made the part of the epson backend (the old driver) for 4990, but there are a few thing not working, especial with the transperant unit. Claus Boje Mandag den 11. Februar 2008 skrev JD: I went to the epson-avasys web site and found they provide these files for this scanner: iscan-2.10.0-1.c2.i386.rpm iscan_2.10.0-1.tar.gz userg_revG_e.pdf I have not trie their driver yet. Will let you know once I have the scanner. JD m. allan noah wrote: there are 3 backends which support this machine. the one which lists these two points is external to sane, so you might want to ask avasys directly. of the other two, one is unmaintained, and the other is new, so we may not be able to provide you with an answer. maybe you can get one and tell us :) allan On 2/10/08, JD jd1008 at gmail.com wrote: What functionality is missing from this driver other than 1- film area guide mode not supported 2- IEEE1394 untested -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] debug file attached (Re: Canon MP710/740 support request)
Hi Gernot, That sounds great news, and we can inform the Sane list then! I had a look at the debug trace you sent me, and everything looks right, working as expected. I'll keep it anyway as a reference, if needed. Let us know if you are able to reproduce the problem you had before, and if you can get such a trace with the error, please send it, as to investigate more. One point that could be done to improve the driver is to implement the send_time function, as the scanner asks for it. Would be needed for that, a Snoop of the usb port with the Windows driver. But why a scanner would need time? It seems to work fine without it anyway. For now, I'll update the current stand-alone Pixma driver with Pixma MP710 and MP740, as well as the patch to Sane files, so as to have it included in future Sane releases too. Thanks again for your participation and help for enhancing the Pixma Sane driver Regards Nicolas Le lundi 11 f?vrier 2008 ? 09:33 +0900, Gernot Hassenpflug a ?crit : On Feb 11, 2008 3:30 AM, Nicolas nicolas.martin at freesurf.fr wrote: Ok, great! In order to debug the 600 and 1200 dpi, I will need the traces produces by the driver in debug mode. Dear Nicholas, Your driver is apparently working perfectly for me now, no idea why I got a hardware error last night with all resolutions above 300. I even tried again to use the scan program sending output to the console, and although for 1200dpi it took a *long* time(!), there was no error and the program scanned to completion eventually. I am nevertheless attaching for you the debug output of a successful 1200dpi scan in case there is any content that appears suspicious or dubious. I would also like to ask at this point: is it possible with not too much effort to add independent x and y resolutions, so that 1200x2400, or 2400x4800 etc will be available in the pixma series? Many thanks, Gernot Hassenpflug -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080211/a91748d5/attachment.htm
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
Quoting m. allan noah kitno455 at gmail.com: can you paste the full url you downloaded from? allan I did not keep track of the url page for the first and second. Pastes are for the file on the page. (results pasted) The very first: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 The second: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 I checked just now and got the correct result from http://alioth.debian.org/frs/?group_id=30186 The actual file now is: (typed) http://alioth.org/frs/download.php/2320/sane-backends-1.0.19.tar.gz.md5 The path to the file has changed or the download.php is giving a different path. It looks like all is OK now. Thanks. Gerald On Feb 11, 2008 1:48 PM, Gerald Murray gmurray at cloudnet.com wrote: Quoting m. allan noah kitno455 at gmail.com: unable to reproduce. can you try again? allan Hello Allan, I tried again today, using the http mirror for the United States. It downloaded as the diff file. I also check some other mirrors, and 1.0.19 has not been propagated to them for update. % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 1245399 2008-02-11 11:01 sane-backends-1.0.19.tar.gz.md5 I got the md5sums off of the sane site, and it does check OK with the 1.0.19 package. The problem seems to be limited to this one http mirror, so far. Gerald On 2/11/08, Gerald Murray gmurray at cloudnet.com wrote: Hello all, sane-backends-1.0.19.tar.gz.md5 file was expected to be 62 bytes; but downloads as 87977 bytes This needs correction. The commands I executed are shown below. Thanks Gerald What the download page at http://alioth.debian.org/frs/?group_id=30186 says sane-backends-1.0.19.tar.gz.md5 62 bytes 0 Any Other % ls -l sane-backends-1.0.19.tar.gz.md5 -rw-r--r-- 1 gerald gerald 87977 2008-02-11 00:19 sane-backends-1.0.19.tar.gz.md5 % file sane-backends-1.0.19.tar.gz.md5 sane-backends-1.0.19.tar.gz.md5: gzip compressed data, was sane-backends-1.0.18-1.0.19.dif, from Unix, last modified: Sun Feb 10 17:57:05 2008 -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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 -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
On Feb 11, 2008 3:56 PM, gmurray at cloudnet.com wrote: Quoting m. allan noah kitno455 at gmail.com: can you paste the full url you downloaded from? allan I did not keep track of the url page for the first and second. Pastes are for the file on the page. (results pasted) The very first: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 The second: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 I checked just now and got the correct result from http://alioth.debian.org/frs/?group_id=30186 The actual file now is: (typed) http://alioth.org/frs/download.php/2320/sane-backends-1.0.19.tar.gz.md5 The path to the file has changed or the download.php is giving a different path. It looks like all is OK now. Thanks. is there any chance you typo'd the url the first time? with gforge's download.php, all that matters is the 4 digit number before the filename. the filename could be anything. i've actually posted a bug report with them for that reason. allan -- The truth is an offense, but not a sin
[sane-devel] sane-backends-1.0.19.tar.gz.md5 incorrect ?
On Feb 11, 2008 4:08 PM, m. allan noah kitno455 at gmail.com wrote: On Feb 11, 2008 3:56 PM, gmurray at cloudnet.com wrote: Quoting m. allan noah kitno455 at gmail.com: can you paste the full url you downloaded from? allan I did not keep track of the url page for the first and second. Pastes are for the file on the page. (results pasted) The very first: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 The second: http://alioth.debian.org/frs/download.php/2319/sane-backends-1.0.19.tar.gz.md5 I checked just now and got the correct result from http://alioth.debian.org/frs/?group_id=30186 The actual file now is: (typed) http://alioth.org/frs/download.php/2320/sane-backends-1.0.19.tar.gz.md5 The path to the file has changed or the download.php is giving a different path. It looks like all is OK now. Thanks. is there any chance you typo'd the url the first time? with gforge's download.php, all that matters is the 4 digit number before the filename. the filename could be anything. i've actually posted a bug report with them for that reason. and- 2319 is the diff.gz... allan -- The truth is an offense, but not a sin
[sane-devel] debug file attached (Re: Canon MP710/740 support request)
Gernot- does the windows driver allow independent resolution controls? what are you going to do with the stretched image that will result? Nicolas- cvs is open for business again, so we can accept your patch at any time. keep up this level of interaction and you'll get maintainership too :) allan 2008/2/11 Nicolas nicolas.martin at freesurf.fr: Hi Gernot, That sounds great news, and we can inform the Sane list then! I had a look at the debug trace you sent me, and everything looks right, working as expected. I'll keep it anyway as a reference, if needed. Let us know if you are able to reproduce the problem you had before, and if you can get such a trace with the error, please send it, as to investigate more. One point that could be done to improve the driver is to implement the send_time function, as the scanner asks for it. Would be needed for that, a Snoop of the usb port with the Windows driver. But why a scanner would need time? It seems to work fine without it anyway. For now, I'll update the current stand-alone Pixma driver with Pixma MP710 and MP740, as well as the patch to Sane files, so as to have it included in future Sane releases too. Thanks again for your participation and help for enhancing the Pixma Sane driver Regards Nicolas Le lundi 11 f?vrier 2008 ? 09:33 +0900, Gernot Hassenpflug a ?crit : On Feb 11, 2008 3:30 AM, Nicolas nicolas.martin at freesurf.fr wrote: Ok, great! In order to debug the 600 and 1200 dpi, I will need the traces produces by the driver in debug mode. Dear Nicholas, Your driver is apparently working perfectly for me now, no idea why I got a hardware error last night with all resolutions above 300. I even tried again to use the scan program sending output to the console, and although for 1200dpi it took a *long* time(!), there was no error and the program scanned to completion eventually. I am nevertheless attaching for you the debug output of a successful 1200dpi scan in case there is any content that appears suspicious or dubious. I would also like to ask at this point: is it possible with not too much effort to add independent x and y resolutions, so that 1200x2400, or 2400x4800 etc will be available in the pixma series? Many thanks, Gernot Hassenpflug -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/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
[sane-devel] Canon MP470 support
-devel/attachments/20080211/399299ee/attachment.htm
[sane-devel] scanimage -L crashes with HP ScanJet 4100c
Seems to me that the hp-backend can do a workaround, but not worth for daily use. Could be that the HP ScanJet 4100 C is a little bit problematic concerning USB in certain environments. BTW, did you try to connect the scanner directly to an USB-connector on the back of the PC ? I am giving up here on the HP ScanJet 4100 C. Not in general, because it is working for me on two different systems. Just for certain USB-environments. I have no recommendation for a scanner. At least I would look for a scanner that supports USB 2.0. All the scanners which are supported by the hp-backend only support USB 1.x, because USB 2.0 was not available at that time when HP stopped the production. And USB 1.x is too slow for scanning color images at higher resolutions. The scanner stops, goes back and restarts very often. Good luck Peter Bill Moseley schrieb: On Sun, Feb 10, 2008 at 08:19:51PM +0100, Peter Kirchgessner wrote: export SANE_HP_RDREDO=20 xsane hp This will do 20 retries (2 seconds in total) before giving up. Please try if at least the xsane-GUI comes up. Maybe you then will run into an I/O-error during scanning. Yes, that seemed to help get xsane started, and yes when I try and do a preview it seems to take a very long time to scan, if at all. Have any scanner recommendations? ;) Thanks for your help, Peter. -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net
[sane-devel] debug file attached (Re: Canon MP710/740 support request)
Ok, Allan, thanks for your kind present ;-) AFAIK, (for MP610 at least), different resolution on x and y axis are always rejected by the scanner (tested it already). The Windows driver (MP610's) always use same x y, and you cannot specify different x/y values, only _one_ value can be entered as dpi parameter in Canon's driver form. So the good question now: why does Canon specify resolutions of a x 2a, if you can only use a x a ? If someone's got a clue ... Le lundi 11 f?vrier 2008 ? 16:14 -0500, m. allan noah a ?crit : Gernot- does the windows driver allow independent resolution controls? what are you going to do with the stretched image that will result? Nicolas- cvs is open for business again, so we can accept your patch at any time. keep up this level of interaction and you'll get maintainership too :) allan 2008/2/11 Nicolas nicolas.martin at freesurf.fr: Hi Gernot, That sounds great news, and we can inform the Sane list then! I had a look at the debug trace you sent me, and everything looks right, working as expected. I'll keep it anyway as a reference, if needed. Let us know if you are able to reproduce the problem you had before, and if you can get such a trace with the error, please send it, as to investigate more. One point that could be done to improve the driver is to implement the send_time function, as the scanner asks for it. Would be needed for that, a Snoop of the usb port with the Windows driver. But why a scanner would need time? It seems to work fine without it anyway. For now, I'll update the current stand-alone Pixma driver with Pixma MP710 and MP740, as well as the patch to Sane files, so as to have it included in future Sane releases too. Thanks again for your participation and help for enhancing the Pixma Sane driver Regards Nicolas Le lundi 11 f?vrier 2008 ? 09:33 +0900, Gernot Hassenpflug a ?crit : On Feb 11, 2008 3:30 AM, Nicolas nicolas.martin at freesurf.fr wrote: Ok, great! In order to debug the 600 and 1200 dpi, I will need the traces produces by the driver in debug mode. Dear Nicholas, Your driver is apparently working perfectly for me now, no idea why I got a hardware error last night with all resolutions above 300. I even tried again to use the scan program sending output to the console, and although for 1200dpi it took a *long* time(!), there was no error and the program scanned to completion eventually. I am nevertheless attaching for you the debug output of a successful 1200dpi scan in case there is any content that appears suspicious or dubious. I would also like to ask at this point: is it possible with not too much effort to add independent x and y resolutions, so that 1200x2400, or 2400x4800 etc will be available in the pixma series? Many thanks, Gernot Hassenpflug -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080211/bff08f38/attachment.htm
[sane-devel] Canon LiDE 90
Hello,
I modified registers 10-1d with :
{0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
0x00, 0x04},
and now the led is really white (red green and blue by moving eyes).
Led calibration seems to be good.
But calibration is always 60s long.
I need help.
Thanks
Regards
Guillaume
Pierre Willenbrock a ?crit :
Hi Guillaume,
Guillaume Gastebois schrieb:
Hello,
Why calibration is so long (~50/60s) ?
It is probably failing. Should take about 3-5 seconds. Look at the logs,
the calculated averages and calibration are dumped there.
What are /* Start of white strip in mm (y) */ and /* Start of black mark
in mm (x) */ in genesys_devices.c ?
Those are configuration values for calibration steps. I don't know if
any of these are currently used or if the values are hardcoded.
I think the start-of-black-mark is used to detect the beginning of the
document area for some gl646 scanners. The start-of-white-strip was once
used in shading calibration. Currently, the shading calibration is setup
for a calibration area looking like this:
home position
+
! black area
+
! white area
+
The border between black area and white area is autodetected per pixel,
as the border is usually not straight.
You scanner seems to offer only a white area, so we will need to do
shading calibration differently. My current idea is this:
* always gather data on a white area
* for black data, reduce the led exposure time to the minimum(0x101,
those registers cannot be set to 0. per byte.).
* for white data, use the normal exposure times
I tried something like this for offset calibration, to see if there is
any difference between white area+0x101 exposure time and black
area+normal exposure time. There was no difference in the final images,
and i think the resulting calibration was the same as well.
Regarding the log file you said :
W ! 0x23 ! 0x050 ! dac value rgb(offset value)
W ! 0x2b ! 0x028 ! pga gain rgb
But on debug, I see that these two registers are never written.
0x23 and 0x2b are merely convenience registers. Writing to 0x23 and 0x2b
is equivalent to a write to each of 0x20-0x22 and 0x28-0x2a. For
cis-sensors, there is only one channel used, so we could get away with
only two registers writes(for the correct channel or 0x23/0x2b), but
this won't work for ccd-sensors.
Another thing : when scaning in color the leds are blue
I'd expect a shade of white, perhaps blueish. my scanner does a
magentaish white. You may also see the single colors when quickly moving
your eyes relatively to the scanner.
Regards,
Pierre
