[sane-devel] HP 5580 suport
Hi all i got a new scanner Hp 5590. I try to test with scanimage -T -v and say that there is no scanner found but with sane-find-scanner i get found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1705 [hp scanjet scanner], chip=HP5550/5590/7650) at libusb:005:006 im usin sane 1.0.19. thanks Tobias
[sane-devel] Canon LiDE 90
Pierre Willenbrock schrieb: Hi, Guillaume Gastebois schrieb: Hello, So, what's the next step ? Re-enabling shading ? Yes, but only after the shading-calibration is able to get black level information.(This really needs a better api..) I commited a prerequisite for shading calibration to work for your scanner. When enabling shading, update from cvs and then use GENESYS_FLAG_DARK_CALIBRATION instead of GENESYS_FLAG_DARK_WHITE_CALIBRATION. Regards, Pierre Do you think that last modification for (i = 150; i... is necessary ? Yes. Some time back, that part of the code just used the middle half of the scan, exactly to drop the dummy black pixels at the begin. That didn't work too well, missing some low black levels. Is it time to fine tune registers 52... ? Try increasing register 53, 55, 57 by one. Attached is a small program, that shows the probability of any two-byte pair appearing in a file. It takes the file as input and dumps an portable anymap(pnm) as output. I created that program for something completely unrelated, but it proved useful. I used it on offset1_1.pnm(as offset1_0.pnm is only black). The image should show a fuzzy vertical and horizontal bar, near top/left. Currently, the horizontal bar is more a line, the vertical bar is correct(it shows the relationship between the low byte of one pixel and the high byte of the _next_ pixel). Regards Guillaume Regards, Pierre Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, Yep, I write for (j = 150; j instead of for (i = 150; i. Now second set seems good. Result is on : http://ggastebois.free.fr/lide90_snoop/20_test1.tar Hi, i am sorry, i actually wanted 450, but didn't realize until just now. I missed that the calibration dump images are really grayscale images, although stored in color pnms. 1 pixel in image is 3 pixels for the calibration... I hope this fixes that part of the calibration. Regards, Pierre Regards Guillaume
[sane-devel] HP 5580 suport
1. try it without -T 2. get a debug log: SANE_DEBUG_HP5590=20 scanimage -L allan On Thu, Feb 21, 2008 at 9:45 AM, tobias alarcon extobias at gmail.com wrote: Hi all i got a new scanner Hp 5590. I try to test with scanimage -T -v and say that there is no scanner found but with sane-find-scanner i get found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x1705 [hp scanjet scanner], chip=HP5550/5590/7650) at libusb:005:006 im usin sane 1.0.19. thanks Tobias -- 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 LiDE 90
Hello, Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: Hi, Guillaume Gastebois schrieb: Hello, So, what's the next step ? Re-enabling shading ? Yes, but only after the shading-calibration is able to get black level information.(This really needs a better api..) How to do that ? Do you mean a better api adapted to lide 90 or for all genesys backend ? Do you have some code ? Do you think that last modification for (i = 150; i... is necessary ? Yes. Some time back, that part of the code just used the middle half of the scan, exactly to drop the dummy black pixels at the begin. That didn't work too well, missing some low black levels. Is it time to fine tune registers 52... ? Try increasing register 53, 55, 57 by one. Attached is a small program, that shows the probability of any two-byte pair appearing in a file. It takes the file as input and dumps an portable anymap(pnm) as output. I created that program for something completely unrelated, but it proved useful. I used it on offset1_1.pnm(as offset1_0.pnm is only black). The image should show a fuzzy vertical and horizontal bar, near top/left. Currently, the horizontal bar is more a line, the vertical bar is correct(it shows the relationship between the low byte of one pixel and the high byte of the _next_ pixel). OK, interesting program. I'll try it tonight. One more thing, what are you thinking about output image quality ? Is that normal with todays calibration or is it another problem ? Regards Guillaume Regards Guillaume Regards, Pierre Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, Yep, I write for (j = 150; j instead of for (i = 150; i. Now second set seems good. Result is on : http://ggastebois.free.fr/lide90_snoop/20_test1.tar Hi, i am sorry, i actually wanted 450, but didn't realize until just now. I missed that the calibration dump images are really grayscale images, although stored in color pnms. 1 pixel in image is 3 pixels for the calibration... I hope this fixes that part of the calibration. Regards, Pierre Regards Guillaume
[sane-devel] Canon LiDe25: error submitting URB
myhost kernel: ioctl32(scanimage:17106): Unknown cmd fd(3)
are you running a 32 bit version of libusb and/or sane on a system
with a 64 bit kernel?
allan
2008/2/20 Ken Bender bender647 at gmail.com:
Hi,
I'm in a tricky situation -- at work I have a Opteron workstation
running the antiquated RHEL3 os with no opportunity by me to upgrade
anything except by installing newer versions of software in my user
prefix (I can gain root access to tweak hotplug scripts, etc, but
shouldn't upgrade system packages). I've installed libusb-0.1.12,
sane-backends-1.0.19 and sane-frontends-1.0.14 in my user prefix.
I'm trying to get a Canon LiDe25 scanner working here (it works fine at
home with my newer machines).
This is the tail of the error I get from scanimage -L:
[sanei_usb] sanei_usb_open: opened usb device `libusb:001:017' (*dn=0)
[sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04a9,
productID: 0x2220
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] : 01 69 00 01
.i..
USB error: error submitting URB: Invalid argument
[sanei_usb] sanei_usb_write_bulk: write failed: Invalid argument
[sanei_usb] sanei_usb_close: closing device 0
And here's an ominous /var/log/messages entry:
Feb 20 10:22:26 myhost kernel: ioctl32(scanimage:17106): Unknown cmd fd(3)
cmd(
802c550a){00} arg(50f0) on /proc/bus/usb/001/017
I've had hotplug USB errors on this box before when too many things were
plugged
in (order of hotplug is important). So I'm using a powered USB hub to power
the scanner
but the results haven't changed.
The scanner is on 1/17:
$ lsusb
Bus 001 Device 017: ID 04a9:2220 Canon, Inc.
Any pointers on what these messages mean?
--
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 LiDE 90
Guillaume Gastebois schrieb: Hello, Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: Hi, Guillaume Gastebois schrieb: Hello, So, what's the next step ? Re-enabling shading ? Yes, but only after the shading-calibration is able to get black level information.(This really needs a better api..) How to do that ? Do you mean a better api adapted to lide 90 or for all genesys backend ? Do you have some code ? It is not as bad as i initially thought, the functions for receiving black/white level information for shading are already available. But there is some code duplication between genesys.c and genesys_gl841.c/genesys_gl646.c. All three need to gather black/white level information, for the various calibrations. Do you think that last modification for (i = 150; i... is necessary ? Yes. Some time back, that part of the code just used the middle half of the scan, exactly to drop the dummy black pixels at the begin. That didn't work too well, missing some low black levels. Is it time to fine tune registers 52... ? Try increasing register 53, 55, 57 by one. Attached is a small program, that shows the probability of any two-byte pair appearing in a file. It takes the file as input and dumps an portable anymap(pnm) as output. I created that program for something completely unrelated, but it proved useful. I used it on offset1_1.pnm(as offset1_0.pnm is only black). The image should show a fuzzy vertical and horizontal bar, near top/left. Currently, the horizontal bar is more a line, the vertical bar is correct(it shows the relationship between the low byte of one pixel and the high byte of the _next_ pixel). OK, interesting program. I'll try it tonight. One more thing, what are you thinking about output image quality ? Is that normal with todays calibration or is it another problem ? Well, i, for one, can see the impurities of the white inside of the scanner lid. There are only very faint vertical lines, if at all. Example attached. Regards Guillaume Regards Guillaume Regards, Pierre Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, Yep, I write for (j = 150; j instead of for (i = 150; i. Now second set seems good. Result is on : http://ggastebois.free.fr/lide90_snoop/20_test1.tar Hi, i am sorry, i actually wanted 450, but didn't realize until just now. I missed that the calibration dump images are really grayscale images, although stored in color pnms. 1 pixel in image is 3 pixels for the calibration... I hope this fixes that part of the calibration. Regards, Pierre Regards Guillaume -- next part -- A non-text attachment was scrubbed... Name: canon-lide-35-example.jpg Type: image/jpeg Size: 6061 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080221/bebc286c/attachment.jpg
[sane-devel] HP 5580 suport
I download sane-backends-1.0.19.tar.gz and install it. and run like you said. It works fine. I wonder why doesn't work with rpm package. thanks. On Thu, Feb 21, 2008 at 2:39 PM, m. allan noah kitno455 at gmail.com wrote: clue? yes. run the command i told you, with the 5590 in it. allan On Thu, Feb 21, 2008 at 12:11 PM, tobias alarcon extobias at gmail.com wrote: i get this when with scanimage -L root at localhost ~]# scanimage -L [sanei_debug] Setting debug level of hp to 20. [hp] sane_init called [hp] hp_init: global.is_up = 1 [hp] sane_init will finish with Success [hp] sane_get_devices called [hp] hp_read_config: hp backend v1.06/$Revision: 1.21 $ starts reading config file [hp] hp_read_config: processing line #scsi HP [hp] hp_read_config: processing line # Uncomment the following if you have Error during device I/O on SCSI [hp] hp_read_config: processing line # option dumb-read [hp] hp_read_config: processing line # [hp] hp_read_config: processing line # The usual place for a SCSI-scanner on Linux [hp] hp_read_config: processing line #/dev/scanner [hp] hp_read_config: processing line # [hp] hp_read_config: processing line # USB-scanners supported by the hp-backend [hp] hp_read_config: processing line # HP ScanJet 4100C [hp] hp_read_config: processing line usb 0x03f0 0x0101 [hp] hp_read_config: processing line # HP ScanJet 5200C [hp] hp_read_config: processing line usb 0x03f0 0x0401 [hp] hp_attach_matching_devices: usb attach matching usb 0x03f0 0x0101 [hp] hp_read_config: processing line # HP ScanJet 62X0C [hp] hp_read_config: processing line usb 0x03f0 0x0201 [hp] hp_attach_matching_devices: usb attach matching usb 0x03f0 0x0401 [hp] hp_read_config: processing line # HP ScanJet 63X0C [hp] hp_read_config: processing line usb 0x03f0 0x0601 [hp] hp_attach_matching_devices: usb attach matching usb 0x03f0 0x0201 [hp] hp_read_config: processing line [hp] hp_read_config: processing line # Uncomment the following if your scanner is connected by USB, [hp] hp_read_config: processing line # but you are not using libusb [hp] hp_read_config: processing line # /dev/usb/scanner0 [hp] hp_read_config: processing line # option connect-device [hp] hp_read_config: attach usb 0x03f0 0x0601 [hp] hp_attach_matching_devices: usb attach matching usb 0x03f0 0x0601 [hp] hp_read_config: reset to default config [hp] sane_get_devices will finish with Success No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [hp] sane_exit called [hp] hp_destroy: global.is_up = 0 [hp] sane_exit will finish any clue? -- The truth is an offense, but not a sin
[sane-devel] Canon LiDe25: error submitting URB
Yes!
We have a mix of 32-bit and 64-bit machines around here, so I usually take
the lazy approach and compile apps on a 32-bit platform and they run on
either platform. This is the first time that didn't work (and to be honest
I don't know why). I recompiled the library and sane apps as well as 9
other dependencies in my 64-bit prefix and it works great.
Thanks for your help and sorry it turned out not to be sane specific.
On Thu, Feb 21, 2008 at 11:19 AM, m. allan noah kitno455 at gmail.com wrote:
myhost kernel: ioctl32(scanimage:17106): Unknown cmd fd(3)
are you running a 32 bit version of libusb and/or sane on a system
with a 64 bit kernel?
allan
2008/2/20 Ken Bender bender647 at gmail.com:
Hi,
I'm in a tricky situation -- at work I have a Opteron workstation
running the antiquated RHEL3 os with no opportunity by me to upgrade
anything except by installing newer versions of software in my user
prefix (I can gain root access to tweak hotplug scripts, etc, but
shouldn't upgrade system packages). I've installed libusb-0.1.12,
sane-backends-1.0.19 and sane-frontends-1.0.14 in my user prefix.
I'm trying to get a Canon LiDe25 scanner working here (it works fine at
home with my newer machines).
This is the tail of the error I get from scanimage -L:
[sanei_usb] sanei_usb_open: opened usb device `libusb:001:017' (*dn=0)
[sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04a9,
productID: 0x2220
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] : 01 69 00 01
.i..
USB error: error submitting URB: Invalid argument
[sanei_usb] sanei_usb_write_bulk: write failed: Invalid argument
[sanei_usb] sanei_usb_close: closing device 0
And here's an ominous /var/log/messages entry:
Feb 20 10:22:26 myhost kernel: ioctl32(scanimage:17106): Unknown cmd
fd(3)
cmd(
802c550a){00} arg(50f0) on /proc/bus/usb/001/017
I've had hotplug USB errors on this box before when too many things were
plugged
in (order of hotplug is important). So I'm using a powered USB hub to
power
the scanner
but the results haven't changed.
The scanner is on 1/17:
$ lsusb
Bus 001 Device 017: ID 04a9:2220 Canon, Inc.
Any pointers on what these messages mean?
--
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
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080221/15f7f29c/attachment-0001.htm
