[sane-devel] Genesys, Canon LiDE 35/40/50/60
Hello list and Henning, For Canon LiDE 35 or 50: What steps are to be followed to gain access to the calibration area? I have seen on Ebay that Canon sells separately a service manual on a compact disk. Does anyone know if that disk would contain the instructions to service that scanner? Pierre wrote: That is probably a calibration problem. There is no easy way to fix that. What helped Henning was to clean the calibration area. The backend is currently not able to cope with (much) dirt there. Regards, Gerald
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Gerald Murray schrieb: Quoting Pierre Willenbrock pie...@pirsoft.dnsalias.org: Hi Gerald, Gerald Murray schrieb: Tested: LiDE 35: 150,300,600,1200 using usb-1.1. --snip-- That is probably a calibration problem. There is no easy way to fix that. What helped Henning was to clean the calibration area. The backend is currently not able to cope with (much) dirt there. You can get a distorted raw scan of the calibration area by enabling debugging. That should give you a file named black_white_shading.pnm. When scanned at the higher resolutions(=600dpi), it should have vertically striped area(s), but only very few dirt particles. I have not figured out how to clean the calibration area. There was no instructions that came with the scanner. Is there some guide to how to take the parts apart? There is one possible plastic hook pair on the bottom, but it looks like a manuafacturer-only access point, requiring a special tool. Then i guess you need to live with the vertical stripes. But please send the black_white_shading.pnm from a 1200dpi scan so i can try to find a better calibration algorithm. Also a few slices across the image, possibly from a jerk of the head at that point in the scan. On the whole, an acceptable image. Did this happen because the scanner moved the head back to restart at the buffer overflow position? If that is the case, i need to do some more tuning on the acceleration tables. That should definitely not happen(Though it is no reason not to put the code into sane-backends). It happened at 10 cm of an 11cm postcard scan. The scanner does quite a bit of shuffling, and I thought it might be related to that forward/reverse timing in the shuffle. I guess that did not happen all the time at the same position? HP2400: no change, not working. Not working as in refuses to move head/deliver useful data or as in provides a 2400x1200dpi image? For the latter case i do have a patch, enabling a nearest match interpolation. The head never moves. It goes into a calibration at the beginning, and never completes the calibration correctly, and then times out with a question on the lamp: [genesys] genesys_warmup_lamp: warmup timed out after 46 seconds. Lamp defective? scanimage: sane_start: Error during device I/O Sorry, misread HP2400 to be 2400 dpi.. Regards, Pierre
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Pierre wrote: So, if you own a scanner of the Canon LiDE 35/40/50/60 series, please try the code from the experimental module. The low power mode is used when scanning at resolutions =600dpi, and during calibration. Errors are most likely when the scanner does a fast feed to the scanning area. Also, it would be good if someone owning a gl646 based scanner tests the code, as the gl646 part tends to break whenever i change something :( Regards, Pierre Hello, Tested: LiDE 35: 150,300,600,1200 using usb-1.1. Motor ok. Scans at 150,300 are excellent quality. At 600, 1200 minor image flaws: there is faint but noticable streaks down the longest length of the image, from color reception or brightness not being quite right. Also a few slices across the image, possibly from a jerk of the head at that point in the scan. On the whole, an acceptable image. HP2400: no change, not working. Best regards, Gerald
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Hi Gerald, Gerald Murray schrieb: Tested: LiDE 35: 150,300,600,1200 using usb-1.1. Motor ok. Scans at 150,300 are excellent quality. At 600, 1200 minor image flaws: there is faint but noticable streaks down the longest length of the image, from color reception or brightness not being quite right. That is probably a calibration problem. There is no easy way to fix that. What helped Henning was to clean the calibration area. The backend is currently not able to cope with (much) dirt there. You can get a distorted raw scan of the calibration area by enabling debugging. That should give you a file named black_white_shading.pnm. When scanned at the higher resolutions(=600dpi), it should have vertically striped area(s), but only very few dirt particles. Also a few slices across the image, possibly from a jerk of the head at that point in the scan. On the whole, an acceptable image. Did this happen because the scanner moved the head back to restart at the buffer overflow position? If that is the case, i need to do some more tuning on the acceleration tables. That should definitely not happen(Though it is no reason not to put the code into sane-backends). HP2400: no change, not working. Not working as in refuses to move head/deliver useful data or as in provides a 2400x1200dpi image? For the latter case i do have a patch, enabling a nearest match interpolation. Thanks for testing, Pierre
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Hi, On 4/24/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Hi List, as some of you may have noticed, the genesys backend now has the ability to set a motor power level, leading to much quieter scans in high dpi modes(if it is implemented for the scanner). This feature is currently available in the experimental module, as the settings for this new mode need some more testing on scanners other than mine. So, if you own a scanner of the Canon LiDE 35/40/50/60 series, please try the code from the experimental module. The low power mode is used when scanning at resolutions =600dpi, and during calibration. Errors are most likely when the scanner does a fast feed to the scanning area. Also, it would be good if someone owning a gl646 based scanner tests the code, as the gl646 part tends to break whenever i change something :( Is that experimental module can be used with HP 2400 scanner also? Regards, Parag.
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Hi, Parag N() schrieb: Is that experimental module can be used with HP 2400 scanner also? It can be used for development and other experimental code. So, yes, the experimental cvs module can be used for developing support for the HP 2400 scanner. But no, there is no code supporting the HP 2400 scanner, yet. Regards, Pierre
[sane-devel] Genesys, Canon LiDE 35/40/50/60
Hi List, as some of you may have noticed, the genesys backend now has the ability to set a motor power level, leading to much quieter scans in high dpi modes(if it is implemented for the scanner). This feature is currently available in the experimental module, as the settings for this new mode need some more testing on scanners other than mine. So, if you own a scanner of the Canon LiDE 35/40/50/60 series, please try the code from the experimental module. The low power mode is used when scanning at resolutions =600dpi, and during calibration. Errors are most likely when the scanner does a fast feed to the scanning area. Also, it would be good if someone owning a gl646 based scanner tests the code, as the gl646 part tends to break whenever i change something :( Regards, Pierre
