[sane-devel] Fix 45-libsane.rules to support Epson V100
I have got a scanner Epson Perfection Photo V100 (which need the proprietary driver Epowka). I have installed it and it works only with root: xsane don't find the scanner when launched with the classical users accounts (tested with two). I have found that the scanner is not included in /etc/udev/rules.d/45-libsane.rules. I have added it and now it works well. A 'diff -u' of the change is joined to this mail. Note that I only do a reference to the 'Epson Perfection V100' in the diff. It seems that the V10 is globally equivalent (due to same driver and the answer of scanimage) but I don't know if they have the same Product ID. If you have questions or comments, please cc me because I have not subscribed to the ml. Stephane. PS: Some infos you could find useful: System : Linux on x86 (32bit) Distro : Ubuntu 7.10 scanimage (sane-backends) 1.0.18-cvs; backend version 1.0.18 The first lines of 45-libsane.rules say: # This file was automatically created based on description files (*.desc) #by sane-desc 3.2 from sane-backends 1.0.18-cvs on Fri Oct 5 15:26:21 2007 Extract of terminal (epowka installed but without modification in 45-libsane.rules : /* * as root: */ # scanimage -L device `epkowa:libusb:003:004' is a Epson Perfection V10/V100 flatbed scanner /* *as user: */ $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04b8, product=0x012d) at libusb:003:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. $ lsusb Bus 003 Device 004: ID 04b8:012d Seiko Epson Corp. Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 001: ID : $ scanimage -L 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). /* * I modify the file and restart the scanner: */ $ scanimage -L device `epkowa:libusb:003:008' is a Epson Perfection V10/V100 flatbed scanner /* * \o/ yoohooo! */ -- next part -- A non-text attachment was scrubbed... Name: 45-libsane.rules.diff Type: text/x-patch Size: 592 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080206/f3a29ca5/attachment.bin
[sane-devel] Canon LiDE 90
Hello,
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
It's a little bit better with these values.
In Genesys_Sensor I have :
regs_0x08_0x0b : {0x00, 0x21, 0x00, 0x00}
regs_0x10_0x1d : {0x02, 0x8b, 0x02, 0x8b, 0x02, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
regs_0x52_0x5e : {0x02, 0x04, 0x02, 0x04, 0x02, 0x04, 0x0a, 0x71, 0x55,
0x00, 0x00, 0x20, 0x41}
looks good so far(very few of these can be found in the log after my
scripts processed them(bug in my scripts), but then they must be okay
when you are able to scan)
In Genesys_Gpo I have :
{0x02, 0x80}{0x7f, 0xe0}
i found these differing settings in your log for register 0x6c:
0x00
0x02
0x0a
0x0e
0x10
0x12
0x18
0x1a
0x38
0x3a
0x3e
0x3c
I tryed all these values :
02 : revert video image with a lot of vertical lines
0a : revert video image with a lot of vertical lines and motor doesn't
stop at the end of the page
0e, 3e : don't know home position anymore
10, 12, 18, 1a : revert video image seems to be in black and white (no
grayscale) but no more vertical images
38, 3a : revert video image in grayscale but take only half of the
screen in height.
3c : motor make noise but don't move
You can find sample at :
http://ggastebois.free.fr/lide90_snoop/toto_18_0_0.jpg
http://ggastebois.free.fr/lide90_snoop/toto_38_0_0.jpg
these two image are original (just saved in jpg) with x y offset set to 0.
How can we explain that images are in reverse video and that with 38 and
3a the image takes only half the place ?
Subsidary question : what is the small white (perhaps black) rectangle
in the middle up off page (for calibration) ?
Regards
Guillaume
it may be interesting to find out what the effects of these are.
and now in Genesys_Frontend :
{{0x00, 0x2f, 0x07, 0x26}
, {0x00, 0x00, 0x00}
, {0x50, 0x50, 0x50}
, {0x28, 0x28, 0x28}
, {0x0d, 0x00, 0x00}
}
Looks good.
Are these value acceptable regarding my log
(http://ggastebois.free.fr/lide90_snoop/UsbSnoop_a4_200dpi.log) ?
I very appreciate your help.
Regards
Guillaume
P.S : attached a sample image with my values.
Regarding the image: is this with x|y_offset == 0? and are the
horizontal bright lines original?
Regards,
Pierre
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
OK, but via which register is it programmed. I find nothing in GL842
datasheet
for frontend.
regards
Guillaume
the analog frontend is programmed through the serial interface accessed
by address registers 0x50(FERDA)/0x51(FEWRA) and data registers
0x46/0x47(FERDDATA)/0x3a/0x3b(FEWRDATA).
I find this sequence in your log:
R/W ! addr ! data ! WM8199 register
+--+---+-
W ! 0x04 ! 0x000 ! reset
R ! 0x07 ! 0x041 ! revision number, ==0x41
W ! 0x04 ! 0x000 ! reset
W ! 0x01 ! 0x02f ! Setup reg 1: mode4==0, pgafs=2, selpd=1, mono=1,
cds=1, en=1
W ! 0x02 ! 0x007 ! Setup reg 2: del=0, rlcdacrng=0, 0=0, vrlcext=0,
invop=1, muxop=3
W ! 0x03 ! 0x026 ! Setup reg 3: chan=0, cdsref=2, rlcv=6
W ! 0x06 ! 0x00d ! Setup reg 4: fm=0, intm=0, rlcint=1, fme=1,
acycnrlc=0, linebyline=1
W ! 0x08 ! 0x000 ! Setup reg 5: 0=0, posnneg=0, vdel=0, vsmpdet=0
W ! 0x20 ! 0x050 ! dac value red(offset value)
W ! 0x21 ! 0x050 ! dac value green(offset value)
W ! 0x22 ! 0x050 ! dac value blue(offset value)
W ! 0x23 ! 0x050 ! dac value rgb(offset value)
W ! 0x28 ! 0x028 ! pga gain red(0x28 is a factor of 0.85)
W ! 0x29 ! 0x028 ! pga gain green
W ! 0x2a ! 0x028 ! pga gain blue
W ! 0x2b ! 0x028 ! pga gain rgb
all WM81xx(at least where datasheets are available) share a similar
register layout, with revision 0x41 at address 7. writing to the rgb
variant of pga gain/dac value results in writes to all the color
specific registers, so it is not needed.
So, you have in Genesys_Frontend: reg[1]=0x2f, reg[2]=0x07, reg[3]=0x26,
reg2[0]=0x0d, reg2[1]=0x00, the rest of reg/reg2 =0, all sign[x]=0,
offset[x]=0x50, gain[x]=0x28.
this does not match anything currently in genesys_devices.c. Just add
one entry to the Wolfson array, #define a DAC_ to 7 in genesys_low.h
and put that in your Genesys_Model.
The gain/offset setting should be good for led calibration and will be
replaced by gain/offset calibration.
After that, get a scan of the calibration area(the area under the
housing at the parking position). For this, put 0 into the x_offset and
y_offset in your Genesys_Model. If this turns out to be similar to the
calibration area of the lide 50, led/offset/gain-calibration should work
with only minor changes.
Regards,
Pierre
[sane-devel] Fix 45-libsane.rules to support Epson V100
thanks. its already listed in our description files, so it should get a udev rule with the next release of sane. allan On 2/6/08, Stephane Blondon stephane.blondon at gmail.com wrote: I have got a scanner Epson Perfection Photo V100 (which need the proprietary driver Epowka). I have installed it and it works only with root: xsane don't find the scanner when launched with the classical users accounts (tested with two). I have found that the scanner is not included in /etc/udev/rules.d/45-libsane.rules. I have added it and now it works well. A 'diff -u' of the change is joined to this mail. Note that I only do a reference to the 'Epson Perfection V100' in the diff. It seems that the V10 is globally equivalent (due to same driver and the answer of scanimage) but I don't know if they have the same Product ID. If you have questions or comments, please cc me because I have not subscribed to the ml. Stephane. PS: Some infos you could find useful: System : Linux on x86 (32bit) Distro : Ubuntu 7.10 scanimage (sane-backends) 1.0.18-cvs; backend version 1.0.18 The first lines of 45-libsane.rules say: # This file was automatically created based on description files (*.desc) #by sane-desc 3.2 from sane-backends 1.0.18-cvs on Fri Oct 5 15:26:21 2007 Extract of terminal (epowka installed but without modification in 45-libsane.rules : /* * as root: */ # scanimage -L device `epkowa:libusb:003:004' is a Epson Perfection V10/V100 flatbed scanner /* *as user: */ $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04b8, product=0x012d) at libusb:003:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. $ lsusb Bus 003 Device 004: ID 04b8:012d Seiko Epson Corp. Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 001: ID : $ scanimage -L 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). /* * I modify the file and restart the scanner: */ $ scanimage -L device `epkowa:libusb:003:008' is a Epson Perfection V10/V100 flatbed scanner /* * \o/ yoohooo! */ -- 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,
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
It's a little bit better with these values.
In Genesys_Sensor I have :
regs_0x08_0x0b : {0x00, 0x21, 0x00, 0x00}
regs_0x10_0x1d : {0x02, 0x8b, 0x02, 0x8b, 0x02, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
regs_0x52_0x5e : {0x02, 0x04, 0x02, 0x04, 0x02, 0x04, 0x0a, 0x71, 0x55,
0x00, 0x00, 0x20, 0x41}
looks good so far(very few of these can be found in the log after my
scripts processed them(bug in my scripts), but then they must be okay
when you are able to scan)
In Genesys_Gpo I have :
{0x02, 0x80}{0x7f, 0xe0}
i found these differing settings in your log for register 0x6c:
0x00
0x02
0x0a
0x0e
0x10
0x12
0x18
0x1a
0x38
0x3a
0x3e
0x3c
I tryed all these values :
02 : revert video image with a lot of vertical lines
0a : revert video image with a lot of vertical lines and motor doesn't
stop at the end of the page
0e, 3e : don't know home position anymore
10, 12, 18, 1a : revert video image seems to be in black and white (no
grayscale) but no more vertical images
38, 3a : revert video image in grayscale but take only half of the
screen in height.
3c : motor make noise but don't move
You can find sample at :
http://ggastebois.free.fr/lide90_snoop/toto_18_0_0.jpg
http://ggastebois.free.fr/lide90_snoop/toto_38_0_0.jpg
these two image are original (just saved in jpg) with x y offset set to 0.
How can we explain that images are in reverse video and that with 38 and
3a the image takes only half the place ?
I don't know why the image colors are reversed, but it may be worth
trying to flip the sign bits in Genesys_Frontend. If that does nothing,
we need to handle that in code(or i am missing some setting of the gl841).
The other thing you have seen is the half-resolution mode, used for
greater speed when doing lower(i.E. not full) resolutions.
Subsidary question : what is the small white (perhaps black) rectangle
in the middle up off page (for calibration) ?
That may be a small metal clamp holding the glass or the calibration
strip. That is the black(i.E. white) part at the very top.
To summarize, it is a good idea to have bit 4 on, bit 5 is the half
resolution switch. I'd put 0x10 into the 0x6c gpio register.
As for the calibration area, you will need to change some code:
* comment out genesys_gl841.c:4220:(line numbers may differ)
status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/
* the same for genesys_gl841.c:4821:
status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/
then you can try what happens when you turn on the led_calibration and
the coarse_gain_calibration. offset_calibration needs a bit more
changes. i think i am having the code needed lying around somewhere.
essentially, the offset calibration needs to be done with leds off.
the shading calibration does need even more changes.
Additionally, if you can't get the afe to switch the sign, you need to
do that in the calibration functions(i.E. 65535-value).
Regards,
Pierre
Regards
Guillaume
it may be interesting to find out what the effects of these are.
and now in Genesys_Frontend :
{{0x00, 0x2f, 0x07, 0x26}
, {0x00, 0x00, 0x00}
, {0x50, 0x50, 0x50}
, {0x28, 0x28, 0x28}
, {0x0d, 0x00, 0x00}
}
Looks good.
Are these value acceptable regarding my log
(http://ggastebois.free.fr/lide90_snoop/UsbSnoop_a4_200dpi.log) ?
I very appreciate your help.
Regards
Guillaume
P.S : attached a sample image with my values.
Regarding the image: is this with x|y_offset == 0? and are the
horizontal bright lines original?
Regards,
Pierre
[sane-devel] A very fast scanner supported by SANE (maybe Epson GT2500?)
i personally have not used one, and they are quite expensive, but i understand that the Epson Perfection v700 or v750 are quite fast, and are reported to work with SANE. allan On 2/5/08, Alex Bernier alex.bernier at free.fr wrote: Hello, I don't know if it is the right place for this question... I'm blind and I want a very fast scanner supported by SANE, mainly to scan books (it should be very fast for 300-DPI black and white scanning). It's not easy to find information about performances of scanners. On the Epson website, I found the GT2500 which can scan 27 PPM using an ADF. But I don't want to use the ADF... Because I want to scan books, it's more useful for me to know how fast the scanner is when using the flatbed mode. If someone has an Epson GT2500, I would really apreciate if he/she can give me some information about the scanning speed. Or if someone knows about an other very fast scanner, suggestions would be apreciated. For the moment, I own an Epson Perfection 1640SU. It scans a page in 17 seconds, but it is old and I think there is better models now... Regards, Alex Bernier -- 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] genesys_gl841.c: infinite loops
Stefan Lucke schrieb: Hi, I guess there are 3 possibilities for infinite loops. Attached patch fixes this and adjusts loop threshold to given comments.. Thanks for spotting these. We have never had a problem with those loops, but it is certainly a good idea to have the code working as the comments in the code suggest. A short test revealed no breakages. I will commit these corrections after the release. Regards, Pierre
[sane-devel] sane reset device everytime
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonsoir, I have an epson usb scanner and it become recently very slow to use: sane rset the usb device everytime I want to use it; message in log file is this one: usb 5-3: reset high speed USB device using ehci_hcd and address 10 lsusb gives: Bus 005 Device 010: ID 04b8:011f Seiko Epson Corp. Perfection 1670 I am quite astonished because my scanner is perfection 3490 photos And everytime I ask sane to do something (detect, get snapshot, numerize...) the device is reset and it takes hours before getting some scan. Why? And what can I do? Thanks for any help. - -- Fran?ois Patte UFR de math?matiques et informatique Universit? Paris Descartes 45, rue des Saints P?res F-75270 Paris Cedex 06 T?l. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHqi71dE6C2dhV2JURAs/eAKCOfUyNedP8p6lWjPsDY4rGgCJ3WACffRLq NEEbkn9MpRPA1QkDZqjFpfc= =F7D1 -END PGP SIGNATURE-
[sane-devel] sane reset device everytime
are you using Fedora 7 or 8 by chance? allan On 2/6/08, Fran?ois Patte francois.patte at math-info.univ-paris5.fr wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonsoir, I have an epson usb scanner and it become recently very slow to use: sane rset the usb device everytime I want to use it; message in log file is this one: usb 5-3: reset high speed USB device using ehci_hcd and address 10 lsusb gives: Bus 005 Device 010: ID 04b8:011f Seiko Epson Corp. Perfection 1670 I am quite astonished because my scanner is perfection 3490 photos And everytime I ask sane to do something (detect, get snapshot, numerize...) the device is reset and it takes hours before getting some scan. Why? And what can I do? Thanks for any help. - -- Fran?ois Patte UFR de math?matiques et informatique Universit? Paris Descartes 45, rue des Saints P?res F-75270 Paris Cedex 06 T?l. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHqi71dE6C2dhV2JURAs/eAKCOfUyNedP8p6lWjPsDY4rGgCJ3WACffRLq NEEbkn9MpRPA1QkDZqjFpfc= =F7D1 -END PGP SIGNATURE- -- 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] Working: HP Laserjet M1120(n) using hpljm1005 backend
Hello list,
I have the HP Laserjet M1120n (network version of M1120) and it works
with the hplm1005 backend over usb
Vendor ID: 0x0370 (of course, HP)
Product-ID: 0x5717
got sane from CVS today (feb 7 2008)
modified backend/hpljm1005.c to include USB id:
/* Zero-terminated USB VID/PID array */
static struct usbdev_s usbid[] = {
{0x03f0, 0x3b17, Hewlett-Packard, LaserJet M1005,
multi-function peripheral},
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
{0, 0, NULL, NULL, NULL},
{0, 0, NULL, NULL, NULL}
};
or as a regular diff:
98a99,100
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
[sane-devel] A very fast scanner supported by SANE (maybe Epson GT2500?)
Hi, Avision has special book scanners, that have a zero edge / book edge feature, which mean one side of the scanner is specially formed to press a book on: http://www.proscan.com.au/avision/FB6080E.htm and are supported by my Avision backend. Yours, Ren? On Wednesday 06 February 2008 22:50:16 m. allan noah wrote: i personally have not used one, and they are quite expensive, but i understand that the Epson Perfection v700 or v750 are quite fast, and are reported to work with SANE. allan On 2/5/08, Alex Bernier alex.bernier at free.fr wrote: Hello, I don't know if it is the right place for this question... I'm blind and I want a very fast scanner supported by SANE, mainly to scan books (it should be very fast for 300-DPI black and white scanning). It's not easy to find information about performances of scanners. On the Epson website, I found the GT2500 which can scan 27 PPM using an ADF. But I don't want to use the ADF... Because I want to scan books, it's more useful for me to know how fast the scanner is when using the flatbed mode. If someone has an Epson GT2500, I would really apreciate if he/she can give me some information about the scanning speed. Or if someone knows about an other very fast scanner, suggestions would be apreciated. For the moment, I own an Epson Perfection 1640SU. It scans a page in 17 seconds, but it is old and I think there is better models now... Regards, Alex Bernier -- 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 -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin Gesch?ftsf?hrer: Susanne Klaus, Ren? Rebe Sitz: Berlin, Amtsgericht Charlottenburg HRB 105 123 B USt-IdNr.: DE251602478 http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'mssa at yahoo.com' 2. Manufacturer (e.g. Mustek): '' 3. Model name (e.g. ScanExpress 1200UB): 'paealiniks' 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.dealdatabase.com/forum/member.php?u=68538;Buy levitra/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://www.wowzamedia.com/forums/member.php?u=1357;generic cialis/abra href=http://forum.springframework.org/member.php?u=34111;generic viagra/abra href=http://www.actionscript.org/forums/member.php3?u=64801;cheap 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://www.actionscript.org/forums/member.php3?u=64953;buy valium/a' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: Hello, I need a little bit more informations befor testing (sorry for my poor knowledge in scanner) Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: I don't know why the image colors are reversed, but it may be worth trying to flip the sign bits in Genesys_Frontend. If that does nothing, we need to handle that in code(or i am missing some setting of the gl841). The other thing you have seen is the half-resolution mode, used for greater speed when doing lower(i.E. not full) resolutions. How do you explain yhat with half resolution the image seems to be grayscale and without it seems to be lineart ? If you look closely, you see that the image is not exactly lineart. When doing half resolution, the sensitivity of the scanner sensor changes, and thus needs a different afe setup. That should be handled gracefully by the offset/gain calibration, once those are working. Subsidary question : what is the small white (perhaps black) rectangle in the middle up off page (for calibration) ? That may be a small metal clamp holding the glass or the calibration strip. That is the black(i.E. white) part at the very top. Under this small rectangle I have a vertical more clear line(same height). Is it because I need to tweek calibration area (without this small rectangle) ? To summarize, it is a good idea to have bit 4 on, bit 5 is the half resolution switch. I'd put 0x10 into the 0x6c gpio register. As for the calibration area, you will need to change some code: * comment out genesys_gl841.c:4220:(line numbers may differ) status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ * the same for genesys_gl841.c:4821: status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ then you can try what happens when you turn on the led_calibration and the coarse_gain_calibration. offset_calibration needs a bit more changes. i think i am having the code needed lying around somewhere. essentially, the offset calibration needs to be done with leds off. the shading calibration does need even more changes. Where to find led_calibration, coarse_gain_calibration ? How to turn them on ? For personnal information : what is shading calibration They are called by genesys_flatbed_calibration, i think i requested to comment them out earlier. There are three things to calibrate for: 1) the mapping from sensor voltages to numbers, to not lose color space by clipping lower brightness to 0 or higher brightness to 65535. ideally, you don't ever see 0 or 65535 from the afe. This is mainly the job of offset/gain calibration, but the led-exposure is a factor to this. 2) the color intensities relative to each other. We try to get each colored LED to lead to similar voltages in the sensor during its exposure. This is calibrated by led_calibration 3) Variations between the sensor cells. each sensor cell has it's own sensitivity and black voltage, so there needs to be a per-pixel-correction. This is done by shading_calibration. Additionally, the shading_calibration is by-color, so this is the place where we map each color channel to the correct range, as the led_calibration is not that exact. Additionally, if you can't get the afe to switch the sign, you need to do that in the calibration functions(i.E. 65535-value). Only in calibration function ? For now, that should be enough. We are not interested in the actual output image, yet. Regards, Pierre Regards Guillaume Regards, Pierre
[sane-devel] Fwd: Working: HP Laserjet M1120(n) using hpljm1005 backend
Excuse me if this is a repost, but I didn't see my own mail, back on the list...
-- Forwarded message --
From: Hans Voss hans.v...@gmail.com
Date: Feb 7, 2008 12:07 PM
Subject: Working: HP Laserjet M1120(n) using hpljm1005 backend
To: sane-devel at lists.alioth.debian.org
Hello list,
I have the HP Laserjet M1120n (network version of M1120) and it works
with the hplm1005 backend over usb
Vendor ID: 0x0370 (of course, HP)
Product-ID: 0x5717
got sane from CVS today (feb 7 2008)
modified backend/hpljm1005.c to include USB id:
/* Zero-terminated USB VID/PID array */
static struct usbdev_s usbid[] = {
{0x03f0, 0x3b17, Hewlett-Packard, LaserJet M1005,
multi-function peripheral},
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
{0, 0, NULL, NULL, NULL},
{0, 0, NULL, NULL, NULL}
};
or as a regular diff:
98a99,100
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
[sane-devel] Fwd: Working: HP Laserjet M1120(n) using hpljm1005 backend
that is because you are using gmail. it does not put things in your
inbox until there is a response.
allan
On Feb 7, 2008 2:29 PM, Hans Voss hans.voss at gmail.com wrote:
Excuse me if this is a repost, but I didn't see my own mail, back on the
list...
-- Forwarded message --
From: Hans Voss hans.voss at gmail.com
Date: Feb 7, 2008 12:07 PM
Subject: Working: HP Laserjet M1120(n) using hpljm1005 backend
To: sane-devel at lists.alioth.debian.org
Hello list,
I have the HP Laserjet M1120n (network version of M1120) and it works
with the hplm1005 backend over usb
Vendor ID: 0x0370 (of course, HP)
Product-ID: 0x5717
got sane from CVS today (feb 7 2008)
modified backend/hpljm1005.c to include USB id:
/* Zero-terminated USB VID/PID array */
static struct usbdev_s usbid[] = {
{0x03f0, 0x3b17, Hewlett-Packard, LaserJet M1005,
multi-function peripheral},
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
{0, 0, NULL, NULL, NULL},
{0, 0, NULL, NULL, NULL}
};
or as a regular diff:
98a99,100
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
--
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] Working: HP Laserjet M1120(n) using hpljm1005 backend
thanks- i will add this now with one change- you misspelled David
Packard's last name :)
allan
On 2/7/08, Hans Voss hans.voss at gmail.com wrote:
Hello list,
I have the HP Laserjet M1120n (network version of M1120) and it works
with the hplm1005 backend over usb
Vendor ID: 0x0370 (of course, HP)
Product-ID: 0x5717
got sane from CVS today (feb 7 2008)
modified backend/hpljm1005.c to include USB id:
/* Zero-terminated USB VID/PID array */
static struct usbdev_s usbid[] = {
{0x03f0, 0x3b17, Hewlett-Packard, LaserJet M1005,
multi-function peripheral},
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
{0, 0, NULL, NULL, NULL},
{0, 0, NULL, NULL, NULL}
};
or as a regular diff:
98a99,100
{0x03f0, 0x5717, Hewlett-Packerd, LaserJet M1120,
multi-function peripheral},
--
Met vriendelijke groeten / With kind regards
Hans Voss
---
* Senior Consultant Open Source, Networking and Security
* General Open Sourcerer
* google talk enabled
* blog: http://jazzterdaily.blogspot.com - Tech and other news that
caught my attention.
* Shared News feed:
https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast
--
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] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'david.hince at yahoo.ca' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'Scanjet G4050' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03F0' 6. Product id (e.g. 0x0002): '0x4605' 7. Chipset (e.g. lm9831): 'GL841' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): '(excerpt from sane-find-scanner -v -v) device descriptor of 0x03f0/0x4605 at 001:005 (Hewlett-Packard HP Scanjet scanner) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x03F0 idProduct 0x4605 bcdDevice 5.00 iManufacturer 1 (Hewlett-Packard) iProduct 2 (HP Scanjet scanner) iSerialNumber 12 (CN7B1A63Y805) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 10 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 bInterval 8 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x200) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x200) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x200) checking for LM983[1,2,3] ... this is not a LM983x (bcdUSB = 0x200) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... This USB chip looks like a GL841 (result from sane-backends 1.0.18) found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x4605 [HP Scanjet scanner], chip=GL841) at libusb:001:005 (excerpt from /proc/bus/usb/devices) T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=03f0 ProdID=4605 Rev= 5.00 S: Manufacturer=Hewlett-Packard S: Product=HP Scanjet scanner S: SerialNumber=CN7B1A63Y805 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms (excerpt from lsusb -vv, probably redondant, but I'm putting it here anyway) Bus 001 Device 005: ID 03f0:4605 Hewlett-Packard Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x03f0 Hewlett-Packard idProduct 0x4605 bcdDevice5.00 iManufacturer 1 Hewlett-Packard iProduct2 HP Scanjet scanner iSerial12 CN7B1A63Y805 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 10mA
[sane-devel] Canon MP470 support
Hello, I just bought a Canon Pixma MP470 printer+scanner device and I cannot get it to work with sane. The printer part seems to work with the MP150 driver. I can pitch in with some usb scan info, if some one tells me where to find the docs. -ashwin Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080207/e05c603d/attachment.htm
[sane-devel] ScanExpress A3 USB scanner Gt68xx backend
Dear All, we want to change GT68xx backend in a way that it will work with ScanExpress A3 USB scanner better than before, who can help us that from where we should start? I don't know why GT68xx backend work with some devices good but it has a basic functionality for ScanExpress A3 USB. Thanks alot -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080209/b34309ec/attachment.htm
[sane-devel] Canon LiDE 80 (2nd try)
On Friday 08 February 2008, Reinhard Biegel wrote: Am Wednesday, 6. February 2008 schrieb Reinhard Biegel: Ohi just remember there was something that had to be called at any price but didn't find any documentation about that. I'm going to look for that in my logs. Hi again, I wanted to capture some logs today. But I had to find out that Canon doen't even provide drivers for 64bit Vista, which i set up some days ago. *goingcrazy* As far as I remember there was a bulk write to gamma address space during initialisation which wrote data beyond the end of gamma table in the logs. When saying 'beyond' I'm refering the GL841 datasheet. You are talking about writes like: set_write_register(0x5b, 0x0c) set_write_register(0x5c, 0x00) set_register(0x28) buf_prepaccess(0x0080,BULK_OUT) Data: 01 00 82 00 80 00 00 00 Index: 0 BULK(128) 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 5b/5c build address 0x0c 00, whereas gamma address is defined as 10bit. I tried a few of them, but without luck. Without writing beyond the end the motors only made ugly noise, but when writing there the initial motor movement (forward-backward-forward...) took place (not the same speed as with windows drivers, either little bit slower or faster, don't remember). Running scanimage alone still produces the ugly motor sound. When I use testprog (mentioned earlier) ahead, scanimage is moving scanhead a back and forward and starts (now with LED on [green]) moving for a complete scan. The only thing which works (standalone) is recognition of home position (thats a hand polished diff): Index: backend/genesys_gl841.c === RCS file: /cvsroot/sane/sane-backends/backend/genesys_gl841.c,v retrieving revision 1.19 diff -p -U 3 -r1.19 genesys_gl841.c --- backend/genesys_gl841.c 3 Feb 2008 10:34:20 - 1.19 +++ backend/genesys_gl841.c 8 Feb 2008 19:51:09 - @@ -2023,6 +2076,9 @@ HOME_FREE: 3 r = sanei_genesys_get_address (reg, 0x69); r-value = 0; +r = sanei_genesys_get_address (reg, 0x6b); +r-value |= 1; /* LiDE 80: turn on motor home sensor */ + r = sanei_genesys_get_address (reg, 0x6a); r-value = (fast_slope_steps 1) + (fast_slope_steps 1); @@ -3475,6 +3552,12 @@ gl841_slow_back_home (Genesys_Device * d wait_until_home); memset (local_reg, 0, sizeof (local_reg)); + + /* LiDE 80: ensure that home sensor is powered on for reading ;-) */ + sanei_genesys_read_register (dev, 0x6b, val); + val |= 1; + sanei_genesys_write_register (dev, 0x6b, val); + val = 0; status = sanei_genesys_get_status (dev, val); if (status != SANE_STATUS_GOOD) -- Stefan Lucke
[sane-devel] Canon LiDE 90
Hello, Why calibration is so long (~50/60s) ? What are /* Start of white strip in mm (y) */ and /* Start of black mark in mm (x) */ in genesys_devices.c ? 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. Another thing : when scaning in color the leds are blue Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, I need a little bit more informations befor testing (sorry for my poor knowledge in scanner) Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: I don't know why the image colors are reversed, but it may be worth trying to flip the sign bits in Genesys_Frontend. If that does nothing, we need to handle that in code(or i am missing some setting of the gl841). The other thing you have seen is the half-resolution mode, used for greater speed when doing lower(i.E. not full) resolutions. How do you explain yhat with half resolution the image seems to be grayscale and without it seems to be lineart ? If you look closely, you see that the image is not exactly lineart. When doing half resolution, the sensitivity of the scanner sensor changes, and thus needs a different afe setup. That should be handled gracefully by the offset/gain calibration, once those are working. Subsidary question : what is the small white (perhaps black) rectangle in the middle up off page (for calibration) ? That may be a small metal clamp holding the glass or the calibration strip. That is the black(i.E. white) part at the very top. Under this small rectangle I have a vertical more clear line(same height). Is it because I need to tweek calibration area (without this small rectangle) ? To summarize, it is a good idea to have bit 4 on, bit 5 is the half resolution switch. I'd put 0x10 into the 0x6c gpio register. As for the calibration area, you will need to change some code: * comment out genesys_gl841.c:4220:(line numbers may differ) status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ * the same for genesys_gl841.c:4821: status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ When I comment out these lines the result is very bad (sample http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_comment.jpg) then you can try what happens when you turn on the led_calibration and the coarse_gain_calibration. offset_calibration needs a bit more changes. i think i am having the code needed lying around somewhere. essentially, the offset calibration needs to be done with leds off. the shading calibration does need even more changes. Where to find led_calibration, coarse_gain_calibration ? How to turn them on ? For personnal information : what is shading calibration They are called by genesys_flatbed_calibration, i think i requested to comment them out earlier. OK, sorry, I did that some days ago. My last mail and sample images were WITH led_calibration and coarse_gain_calibration. There are three things to calibrate for: 1) the mapping from sensor voltages to numbers, to not lose color space by clipping lower brightness to 0 or higher brightness to 65535. ideally, you don't ever see 0 or 65535 from the afe. This is mainly the job of offset/gain calibration, but the led-exposure is a factor to this. 2) the color intensities relative to each other. We try to get each colored LED to lead to similar voltages in the sensor during its exposure. This is calibrated by led_calibration 3) Variations between the sensor cells. each sensor cell has it's own sensitivity and black voltage, so there needs to be a per-pixel-correction. This is done by shading_calibration. Additionally, the shading_calibration is by-color, so this is the place where we map each color channel to the correct range, as the led_calibration is not that exact. Additionally, if you can't get the afe to switch the sign, you need to do that in the calibration functions(i.E. 65535-value). Only in calibration function ? For now, that should be enough. We are not interested in the actual output image, yet. Regards, Pierre Regards Guillaume Regards, Pierre Regards Guillaume
[sane-devel] Canon LiDE 90
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
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'karl-heinzbaumbach at arcor.de' 2. Manufacturer (e.g. Mustek): 'Epson Stylus DX 4050' 3. Model name (e.g. ScanExpress 1200UB): 'All in One' 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): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Canon LiDE 90
Hi guys, I gess I have an answer of my question ;) I just bought a Canon LiDE 90 and can't make it work ... I will try to make a backend, but I wanted to be sure that nobody was doing it ... Is there anybody working on it ? Do you think I could help for anything ? Can I download anywhere what you did until now ? I'd really like to make my new scan to work ;) Thanks for your job.
[sane-devel] scg
I have a Sun Ultra 2 running Solaris 8 in 64-bit mode. My scanner is a Microtek Scanmaker E3 with a SCSI Interface I have the Scanner connected to a second SCSI card (sbus). (Not the built-in one) When I run probe-scsi-all, ok probe-scsi-all Target 4scanner/sbus at 1f,0/dma at 3,81000/esp at 3,8000 Unit 0 I downloaded the general scsi driver: scg-sparc-sol2.7 and copied it to /kernel/drv/scg Downloaded SCHILYscg.sparc.tar.Z uncompress SCHILYscg.sparc.tar.Z tar xpvf SCHILYscg.sparc.tar pkgadd -d ./ SCHILYscg Answered 'No' when asked to overwrite /kernel/drv/scg For 64-bit: Downloaded scg-sparcv9-sol2.7.beta and copied it to /kernel/drv/sparcv9/scg Did a reconfiguration reboot: reboot -- -r After I did the reconfiguration reboot, I did a # modinfo | grep scg Got nothing. Tried /opt/csw/bin/sane-find-scanner: # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. One thing I am wondering about is /kernel/drv/scg.conf I tried changing it to the following: # # Copyright (c) 1992, by Sun Microsystems, Inc. # #ident @(#)sd.conf1.1 95/05/03 J. Schilling name=scg class=scsi target=4 lun=0; # I am wondering if this is correct. # ./sane-find-scanner -v This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scg0a... failed to open (Invalid argument) checking /dev/scg0b... failed to open (Invalid argument) checking /dev/scg0c... failed to open (Invalid argument) checking /dev/scg0d... failed to open (Invalid argument) checking /dev/scg0e... failed to open (Invalid argument) checking /dev/scg0f... failed to open (Invalid argument) checking /dev/scg0g... failed to open (Invalid argument) checking /dev/scg1a... failed to open (Invalid argument) checking /dev/scg1b... failed to open (Invalid argument) checking /dev/scg1c... failed to open (Invalid argument) checking /dev/scg1d... failed to open (Invalid argument) checking /dev/scg1e... failed to open (Invalid argument) checking /dev/scg1f... failed to open (Invalid argument) checking /dev/scg1g... failed to open (Invalid argument) checking /dev/scg2a... failed to open (Invalid argument) checking /dev/scg2b... failed to open (Invalid argument) checking /dev/scg2c... failed to open (Invalid argument) checking /dev/scg2d... failed to open (Invalid argument) checking /dev/scg2e... failed to open (Invalid argument) checking /dev/scg2f... failed to open (Invalid argument) checking /dev/scg2g... failed to open (Invalid argument) checking /dev/sg/0... failed to open (Invalid argument) checking /dev/sg/1... failed to open (Invalid argument) checking /dev/sg/2... failed to open (Invalid argument) checking /dev/sg/3... failed to open (Invalid argument) checking /dev/sg/4... failed to open (Invalid argument) checking /dev/sg/5... failed to open (Invalid argument) checking /dev/sg/6... failed to open (Invalid argument) cannot stat `/dev/scsi/scanner/' (No such file or directory) Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
[sane-devel] scg SCSI Driver for Solaris
Hello, I have a Sun Ultra 2 running Solaris 8 in 64-bit mode. My scanner is a Microtek Scanmaker E3 with a SCSI Interface I have the Scanner connected to a second SCSI card (sbus). (Not the built-in one) When I run probe-scsi-all, ok probe-scsi-all Target 4scanner /sbus at 1f,0/dma at 3,81000/esp at 3,8000 Unit 0 I downloaded the general scsi driver (From ftp.berlios.de): scg-sparc-sol2.7 and copied it to /kernel/drv/scg Downloaded SCHILYscg.sparc.tar.Z uncompress SCHILYscg.sparc.tar.Z tar xpvf SCHILYscg.sparc.tar pkgadd -d ./ SCHILYscg Answered 'No' when asked to overwrite /kernel/drv/scg For 64-bit part of it: Downloaded scg-sparcv9-sol2.7.beta and copied it to /kernel/drv/sparcv9/scg Did a reconfiguration reboot: reboot -- -r After I did the reconfiguration reboot, I did a # modinfo | grep scg Got nothing. Tried /opt/csw/bin/sane-find-scanner: # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. One thing I am wondering about is /kernel/drv/scg.conf I tried changing it to the following: # # Copyright (c) 1992, by Sun Microsystems, Inc. # #ident @(#)sd.conf1.1 95/05/03 J. Schilling name=scg class=scsi target=4 lun=0; # I am wondering if this is correct. # ./sane-find-scanner -v This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scg0a... failed to open (Invalid argument) checking /dev/scg0b... failed to open (Invalid argument) checking /dev/scg0c... failed to open (Invalid argument) checking /dev/scg0d... failed to open (Invalid argument) checking /dev/scg0e... failed to open (Invalid argument) checking /dev/scg0f... failed to open (Invalid argument) checking /dev/scg0g... failed to open (Invalid argument) checking /dev/scg1a... failed to open (Invalid argument) checking /dev/scg1b... failed to open (Invalid argument) checking /dev/scg1c... failed to open (Invalid argument) checking /dev/scg1d... failed to open (Invalid argument) checking /dev/scg1e... failed to open (Invalid argument) checking /dev/scg1f... failed to open (Invalid argument) checking /dev/scg1g... failed to open (Invalid argument) checking /dev/scg2a... failed to open (Invalid argument) checking /dev/scg2b... failed to open (Invalid argument) checking /dev/scg2c... failed to open (Invalid argument) checking /dev/scg2d... failed to open (Invalid argument) checking /dev/scg2e... failed to open (Invalid argument) checking /dev/scg2f... failed to open (Invalid argument) checking /dev/scg2g... failed to open (Invalid argument) checking /dev/sg/0... failed to open (Invalid argument) checking /dev/sg/1... failed to open (Invalid argument) checking /dev/sg/2... failed to open (Invalid argument) checking /dev/sg/3... failed to open (Invalid argument) checking /dev/sg/4... failed to open (Invalid argument) checking /dev/sg/5... failed to open (Invalid argument) checking /dev/sg/6... failed to open (Invalid argument) cannot stat `/dev/scsi/scanner/' (No such file or directory) cannot stat `/dev/scsi/processor/' (No such file or directory) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. Thanks, stephen Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[sane-devel] Canon MP710/740 support request
Hello, I'm about ready to try and use USB snooping under windows to get information abut my MP710 (740 is same except adds fax capability). Nicholas, sinceyou so kindly offered to add the IDs for the MP470, could you add the following to your driver as well so I can try it out? found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x264d [MP710]) at libusb:004:003 Many thanks in advance, Gernot Hassenpflug Tokyo, Japan
[sane-devel] deadlock with sanei_usb_read_bulk
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.
--
Ciao
J?rgen
Microsoft is not the answer. Microsoft is the question.
NO is the answer.
[sane-devel] Correction: deadlock with sanei_usb_read_bulk
Oops. The bulk read and write should have been written this way: status = sanei_usb_write_bulk (0, setup_buffer, count); ... status = sanei_usb_write_bulk (1, setup_buffer, count); ... status = sanei_usb_read_bulk (1, data, count); First endpoint 0 then 2 times endpoint 1. -- Ciao J?rgen Microsoft is not the answer. Microsoft is the question. NO is the answer.
[sane-devel] Visioneer 6100 usb
I have spent hours trying to get this scanner to work with Ubuntu. Can anyone please help me? Thanks! ,-._,-. \/)(\/ (:o:) (!)
[sane-devel] Visioneer 6100 usb
That scanner is not supported by SANE. A backend could be written by an appropriately motivated programmer, generally with access to the hardware, and a bit of time. allan On 2/9/08, rogerdavis at earthlink.net rogerdavis at earthlink.net wrote: I have spent hours trying to get this scanner to work with Ubuntu. Can anyone please help me? Thanks! ,-._,-. \/)(\/ (:o:) (!) -- 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] scanimage -L crashes with HP ScanJet 4100c
Hello, I assume that there is a problem with the communication with that scanner. The backend tries to identify the scanner by inquiring various settings. And if the backend does not get the expected answers from it (Escape-sequences with defined arguments) it will not make use of that scanner. I am using a HP ScanJet 6350 with USB (even on a 64 bit machine) since years and it makes no problem. And the hp-backend uses the same USB-software-interface for all the scanners it supports. Maybe the ScanJet 4100 is a little bit too slow in answering and it does not deliver the expected answers in time. I will see if I can find a workaround. Peter m. allan noah schrieb: well, i think peter might have more clue than anyone else- peter? allan On 2/9/08, Bill Moseley moseley at hank.org wrote: On Sat, Feb 09, 2008 at 01:32:19PM -0500, m. allan noah wrote: does it work without the hub? how about scrapping xsane or the gimp for a minute, and just use scanimage to try and grab data Sorry if I was not clear. I was trying w/o the hub. Here' with the scanner connected directly to the computer: moseley at bumby2:~$ scanimage -L device `hp:libusb:005:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner moseley at bumby2:~$ scanimage image.pnm scanimage: no SANE devices found Hum -- if I try multiple times it sometimes will make the scanner work. Like one in 20 tries. -- Bill Moseley moseley at hank.org -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net
[sane-devel] Canon MP710/740 support request
Hi, MP710 which is similar to MP740, look to be from the same generation as MP730 ? It could be worth trying to use current MP730 Sane driver on your MP710, and see how it goes ? In that case, I can easily produce a test driver version for MP710 to use MP730 driver, that you could try. Gernot Hassenpflug-4 wrote: Hello, I'm about ready to try and use USB snooping under windows to get information abut my MP710 (740 is same except adds fax capability). Nicholas, sinceyou so kindly offered to add the IDs for the MP470, could you add the following to your driver as well so I can try it out? found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x264d [MP710]) at libusb:004:003 -- View this message in context: http://www.nabble.com/Canon-MP710-740-support-request-tp15392016p15394965.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] scanimage -L crashes with HP ScanJet 4100c
Bill, I just tried the ScanJet 4100 C with an OpenSuse 10.3 on a 64 Bit machine without problems. On Suse 10.1 32 Bit the scanner was not detected by the USB-layer because of error messages like Feb 10 11:08:26 capella kernel: usb 1-9: new full speed USB device using ohci_hcd and address 14 Feb 10 11:08:27 capella kernel: usb 1-9: device not accepting address 14, error -62 in /var/log/messages. I needed to unplug the scanner from the power supply and connect the power supply and USB again to get around that. After this I could only access the scanner as root. Otherwise libusb could not open the device because of permission problems. Can you please create a hp.log from a use of xsane that failed: SANE_DEBUG_HP=255 xsane hp.log 21 and send it back to me ? After xsane failed, please have a look at /var/log/messages if you can find some error message which might be related to the failure. BTW: /dev/scanner is not needed for USB. libusb is used to search a device on the USB that matches the description usb 0x03f0 0x0101 which is defined in /etc/sane.d/hp.conf and represents the HP ScanJet 4100 C. --Peter m. allan noah schrieb: well, i think peter might have more clue than anyone else- peter? allan On 2/9/08, Bill Moseley moseley at hank.org wrote: On Sat, Feb 09, 2008 at 01:32:19PM -0500, m. allan noah wrote: does it work without the hub? how about scrapping xsane or the gimp for a minute, and just use scanimage to try and grab data Sorry if I was not clear. I was trying w/o the hub. Here' with the scanner connected directly to the computer: moseley at bumby2:~$ scanimage -L device `hp:libusb:005:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner moseley at bumby2:~$ scanimage image.pnm scanimage: no SANE devices found Hum -- if I try multiple times it sometimes will make the scanner work. Like one in 20 tries. -- Bill Moseley moseley at hank.org -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net
[sane-devel] Canon LiDE 90
Hello, 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. Yes, I know that. But I only see blue and green. No red. Regards, Pierre Regards Guillaume
[sane-devel] Canon LiDE 90
Hello, I forget in my last mail (I'm hill today. It's not good for concentration...) : You can find a scanimage log on : http://ggastebois.free.fr/lide90_snoop/scanimage.log. 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
[sane-devel] Canon LiDE 90
Hello, You can find my modified files for LiDE90 on : http://ggastebois.free.fr/lide90_snoop/sources/ With them you will bee able to scan images (very poor quality) in reversed video (???) and with a calibration during 60s (!!!) Regards Guillaume sane at tsleg.com a ?crit : Hi guys, I gess I have an answer of my question ;) I just bought a Canon LiDE 90 and can't make it work ... I will try to make a backend, but I wanted to be sure that nobody was doing it ... Is there anybody working on it ? Do you think I could help for anything ? Can I download anywhere what you did until now ? I'd really like to make my new scan to work ;) Thanks for your job.
[sane-devel] Canon MP710/740 support request
Could you try the following Pixma package. Download it from sendspace.com at the following link: http://www.sendspace.com/file/ogro4h http://www.sendspace.com/file/ogro4h And use instructions given on this blog to install and test it: http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html http://mp610.blogspot.com/ Gernot Hassenpflug-4 wrote: It could be worth trying to use current MP730 Sane driver on your MP710, and see how it goes ? OK. Give me a day or so. -- View this message in context: http://www.nabble.com/Canon-MP710-740-support-request-tp15392016p15396148.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Canon MP710/740 support request
On Feb 10, 2008 10:28 PM, nicols nicolas.martin at freesurf.fr wrote: Could you try the following Pixma package. Download it from sendspace.com at the following link: http://www.sendspace.com/file/ogro4h http://www.sendspace.com/file/ogro4h Hello and thanks. Whew, I had just downloaded the sourceforge package... And use instructions given on this blog to install and test it: http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html http://mp610.blogspot.com/ Done! (I had already read this page and others on your blog, and have it permanently open in a browser tab. I am amazed by your work here, thank you so much.) ~/Desktop/mp150-0.14.2-1u$ ./scan -x 10 -y 15 -w 51 -h 25 -1 -d 20 -W pixmascan.pnm [lots of stuff snipped, MP710 says on front panel scan mode] ... [pixma-0.14.2] pixma_read_image():completed 100% done (33744 bytes written) [pixma-0.14.2] pixma_close(): Canon MultiPASS MP710 So now I look at the image. Amazing, there is something there, a bit grainy, but it certainly does work! Tick off another victory for your [and the oirignal author's] driver and linux! :-) Now I need to check what quality I can get with the options. Some questions: 1. resolution: -r number in the options. What is the suggestion when the scanner does 1200x2400dpi? Is it possible to specify x and y resolutions, or must I choose the lowest of the two. At the moment the highest resolution I can scan at is apparently 300 (by adding -r 600 to the test as follows): ./scan -x 10 -y 15 -w 51 -h 25 -1 -d 20 -r 300 -W pixmascan_r300.pnm If I choose 600 it runs for quite a long time giving screen output but finally cancels with a hardware error. And for 1200 the cancellation happens quite quickly after starting with screen output. I hope that information is useful, since I do not know how well the driver performs on other scanners and with other OSes. Now I will try to integrate the driver into xsane, and also see how it does with scanning larger areas up to A4. Best regards, Gernot
[sane-devel] Canon MP710/740 support request
On Feb 10, 2008 11:24 PM, Gernot Hassenpflug aikishugyo at gmail.com wrote: Now I will try to integrate the driver into xsane, and also see how it does with scanning larger areas up to A4. Good news, using xsane I could scan an L-size photo and an A4 page in full colour at 300dpi. anything above that works for a short while before being cancelled by the hardware. Is is acceptable to post/email the output file for small scan areas in the hope that this is a simple timing/buffer problem or something? Regards, Gernot
[sane-devel] Canon LiDE 90
On Saturday 09 February 2008 18:59:47 sane at tsleg.com wrote: Hi all, I just bought a Canon LiDE 90 and can't make it work ... I will try to make a backend, but I wanted to be sure that nobody was doing it ... Is there anybody working on it ? Yes, just look into the archive, e.g. even of the last days. Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] Alioth unavailable for some time
Julien BLACHE jb at jblache.org wrote: Especially, SSH has been disabled until a patched kernel can be installed on the machine with a fix for the vmsplice local root exploit that affects kernels 2.6.17 to 2.6.24.1. And this has now happened, so SSH is available again. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'mikeallex at gmail.com' 2. Manufacturer (e.g. Mustek): 'Visioneer' 3. Model name (e.g. ScanExpress 1200UB): 'OneTouch 9000' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 6. Product id (e.g. 0x0002): 'p/n 85-0095-000' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Canon MP710/740 support request
Ok, great! In order to debug the 600 and 1200 dpi, I will need the traces produces by the driver in debug mode. For that: - Recompile the driver with debug information: $ make distclean $ make - Set the Sane debug variable to full debug mode , and run xsane from the same console, to get the debug infos: $ export SANE_DEBUG_PIXMA=10 ; xsane - Then scan with xsane at 600 dpi, you should get lots traces in the console of what's going on. - Put all this stuff in a text file, zip it, you can send it directly by email to me (without sending to mailing list), I'll check that. Then, I propose to send you some different files that will include additional debug code, in order to better understand what's going on Rgds, Nicolas Le dimanche 10 f?vrier 2008 ? 23:37 +0900, Gernot Hassenpflug a ?crit : On Feb 10, 2008 11:24 PM, Gernot Hassenpflug aikishugyo at gmail.com wrote: Now I will try to integrate the driver into xsane, and also see how it does with scanning larger areas up to A4. Good news, using xsane I could scan an L-size photo and an A4 page in full colour at 300dpi. anything above that works for a short while before being cancelled by the hardware. Is is acceptable to post/email the output file for small scan areas in the hope that this is a simple timing/buffer problem or something? Regards, Gernot -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080210/7f6425e5/attachment.htm
[sane-devel] scanimage -L crashes with HP ScanJet 4100c
Bill, in case of the failure no data was received from the scanner. The backend then retries to read the requested data again after waiting 0.1 seconds. You can try to increase the number of retries to see if this helps: 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. --Peter Bill Moseley schrieb: Hi Peter, Thank you for looking at this problem. Yes, it might be a timing issue. Thinking back, this scanner has often required running xsane a few times before it would start, but I moved to a new machine (old machine was usb 1 and this machine is usb 2). Can you please create a hp.log from a use of xsane that failed: SANE_DEBUG_HP=255 xsane hp.log 21 I power cycled the scanner and the first time I ran that command xsane started. That's the hp.log file. When I tried again it failed, and that's the hp.log.failed. and send it back to me ? After xsane failed, please have a look at /var/log/messages if you can find some error message which might be related to the failure. Nothing too interesting in syslog Feb 10 05:58:07 bumby2 kernel: [76000.310631] usb 4-2: new full speed USB device using uhci_hcd and address 23 Feb 10 05:58:17 bumby2 kernel: [76010.470576] usb 4-2: configuration #1 chosen from 1 choice Feb 10 05:58:17 bumby2 NetworkManager: debug [1202651897.952024] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_3f0_101_00MY87R538FT'). Feb 10 05:58:18 bumby2 NetworkManager: debug [1202651898.006600] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_3f0_101_00MY87R538FT_if0'). Feb 10 05:58:18 bumby2 NetworkManager: debug [1202651898.026685] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_3f0_101_00MY87R538FT_usbraw'). BTW: /dev/scanner is not needed for USB. libusb is used to search a device on the USB that matches the description usb 0x03f0 0x0101 which is defined in /etc/sane.d/hp.conf and represents the HP ScanJet 4100 C. --Peter m. allan noah schrieb: well, i think peter might have more clue than anyone else- peter? allan On 2/9/08, Bill Moseley moseley at hank.org wrote: On Sat, Feb 09, 2008 at 01:32:19PM -0500, m. allan noah wrote: does it work without the hub? how about scrapping xsane or the gimp for a minute, and just use scanimage to try and grab data Sorry if I was not clear. I was trying w/o the hub. Here' with the scanner connected directly to the computer: moseley at bumby2:~$ scanimage -L device `hp:libusb:005:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner moseley at bumby2:~$ scanimage image.pnm scanimage: no SANE devices found Hum -- if I try multiple times it sometimes will make the scanner work. Like one in 20 tries. -- Bill Moseley moseley at hank.org -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net
[sane-devel] deadlock with sanei_usb_read_bulk
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] Canon MP470 support
here is the code: Bus 005 Device 002: ID 04a9:1723 Canon, Inc. let me know when the driver is ready. will be better if you can put out a patch, so i can do it via apt-get source. thanks! -Ashwin - Original Message From: Nicolas nicolas.mar...@freesurf.fr To: sane-devel at lists.alioth.debian.org Cc: cybernytrix at yahoo.com Sent: Saturday, February 9, 2008 8:20:02 AM Subject: Canon MP470 support Being a recent Canon model, we could try to check whether it can be driven by Pixma modified driver for MP610, MP520, and MP210. Can you provide the USB PID of this all-in one ? You can get it by a simple: $ lsusb I can declare this scanner in the driver, issue the modified version of the driver, and you could give a try to check it. Instructions on how to install the modified Pixma driver above Sane 1.0.18 are given on this blog: http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html This is for Allan: Concerning new Sane version and Pixma driver: I've ready sitting on my desktop, the patch to add MP610, MP520 and MP210 scanners to patch the pixma files, in the current Sane CVS version. At the moment, compiled and tested successfully with an MP610, on Gutsy and on Mandriva 2007. Nicolas Le jeudi 07 f?vrier 2008 ? 21:02 -0800, Ashwin a ?crit : Hello, I just bought a Canon Pixma MP470 printer+scanner device and I cannot get it to work with sane. The printer part seems to work with the MP150 driver. I can pitch in with some usb scan info, if some one tells me where to find the docs. -ashwin Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080210/8a5eaf2c/attachment.htm
[sane-devel] Canon MP470 support
A test driver for MP470 is ready, you can download it at the following link: http://www.sendspace.com/file/ogro4h Use instructions given on this blog to install and test it: http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html Let us know... Nicolas Le dimanche 10 f?vrier 2008 ? 12:48 -0800, Ashwin a ?crit : here is the code: Bus 005 Device 002: ID 04a9:1723 Canon, Inc. let me know when the driver is ready. will be better if you can put out a patch, so i can do it via apt-get source. thanks! -Ashwin - Original Message From: Nicolas nicolas.martin at freesurf.fr To: sane-devel at lists.alioth.debian.org Cc: cybernytrix at yahoo.com Sent: Saturday, February 9, 2008 8:20:02 AM Subject: Canon MP470 support Being a recent Canon model, we could try to check whether it can be driven by Pixma modified driver for MP610, MP520, and MP210. Can you provide the USB PID of this all-in one ? You can get it by a simple: $ lsusb I can declare this scanner in the driver, issue the modified version of the driver, and you could give a try to check it. Instructions on how to install the modified Pixma driver above Sane 1.0.18 are given on this blog: http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html This is for Allan: Concerning new Sane version and Pixma driver: I've ready sitting on my desktop, the patch to add MP610, MP520 and MP210 scanners to patch the pixma files, in the current Sane CVS version. At the moment, compiled and tested successfully with an MP610, on Gutsy and on Mandriva 2007. Nicolas Le jeudi 07 f?vrier 2008 ? 21:02 -0800, Ashwin a ?crit : Hello, I just bought a Canon Pixma MP470 printer+scanner device and I cannot get it to work with sane. The printer part seems to work with the MP150 driver. I can pitch in with some usb scan info, if some one tells me where to find the docs. -ashwin Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. __ Never miss a thing. Make Yahoo your homepage. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080210/f6017013/attachment.htm
[sane-devel] Epson Perfection 4990 driver
What functionality is missing from this driver other than 1- film area guide mode not supported 2- IEEE1394 untested
[sane-devel] Canon LiDE 80 (2nd try)
On Saturday 09 February 2008, Stefan Lucke wrote:
On Friday 08 February 2008, Reinhard Biegel wrote:
Am Wednesday, 6. February 2008 schrieb Reinhard Biegel:
Ohi just remember there was something that had to be called at any
price but didn't find any documentation about that. I'm going to look for
that in my logs.
Hi again,
I wanted to capture some logs today. But I had to find out that Canon
doen't
even provide drivers for 64bit Vista, which i set up some days ago.
*goingcrazy*
As far as I remember there was a bulk write to gamma address space during
initialisation which wrote data beyond the end of gamma table in the logs.
When saying 'beyond' I'm refering the GL841 datasheet.
You are talking about writes like:
I guess YES.
set_write_register(0x5b, 0x0c)
set_write_register(0x5c, 0x00)
set_register(0x28)
buf_prepaccess(0x0080,BULK_OUT)
Data: 01 00 82 00 80 00 00 00
Index: 0
BULK(128)
0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36,
0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76,
Thats not the right one, see attached diff.
5b/5c build address 0x0c 00, whereas gamma address is defined as 10bit.
I tried a few of them, but without luck.
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.
--
Stefan Lucke
-- next part --
? backend/genesys_low.c
Index: backend/genesys_devices.c
===
RCS file: /cvsroot/sane/sane-backends/backend/genesys_devices.c,v
retrieving revision 1.11
diff -p -U 3 -r1.11 genesys_devices.c
--- backend/genesys_devices.c 22 Nov 2007 14:05:12 - 1.11
+++ backend/genesys_devices.c 10 Feb 2008 21:00:49 -
@@ -218,6 +218,29 @@ static Genesys_Sensor Sensor[] = {
,
1.0, 1.0, 1.0,
NULL, NULL, NULL}
+ ,
+ /* CANOLIDE80 */
+ {600,
+/*TODO: find a good reason for keeping all three following variables*/
+ 87, /*(black) */
+ 87, /* (dummy) */
+ 0, /* (startxoffset) */
+ 10400, /*sensor_pixels */
+ 210,
+ 200,
+ {0x00, 0x00, 0x00, 0x00},
+ {0x06, 0x13, 0x55, 0x02, 0x32, 0x04, 0x32, 0x14, 0x00,
+0x00, 0x00, 0x00, 0x00, 0x04
+},
+ {0x05, 0x07,
+0x00, 0x00, 0x00, 0x00,/*[GB](HI|LOW) not needed for cis */
+0x3a, 0x03,
+0x40, /*TODO: bit7 */
+0x00, 0x00, 0x00, 0x00 /*TODO (these do no harm, but may be neccessery
for CCD) */
+}
+ ,
+ 1.0, 1.0, 1.0,
+ NULL, NULL, NULL}
};
/** for General Purpose Output specific settings:
@@ -280,6 +303,13 @@ static Genesys_Gpo Gpo[] = {
{0xef, 0x80}
,
}
+ ,
+ /* CANONLIDE80 */
+ {
+ {0x00, 0x8f}
+ ,
+ {0x6d, 0x80}
+ }
};
#define MOTOR_ST24 2
@@ -393,6 +423,17 @@ static Genesys_Motor Motor[] = {
0.8,
},},},
},
+ {/* Canon LiDE 80 */
+ 2400, 2400, 1, 2,
+ {
+{{4687, 937, 128, 0.8, },
+ {4687, 937, 128, 0.8, }, /* {4200, 3800, 30, 0.8, },*/
+},
+{{9375, 1875, 128, 0.8, }, /* {3500, 1300, 60, 0.8, }, */
+ {9375, 1875, 128, 0.8, }, /* {3500, 1400, 60, 0.8, }, */
+},
+ },
+ },
};
/* here we have the various device settings...
@@ -521,6 +562,53 @@ static Genesys_Model canon_lide_60_model
400
}; /* this is completely untested -- hmg */
+static Genesys_Model canon_lide_80_model = {
+ canon-lide-80, /* Name */
+ Canon, /* Device vendor string */
+ LiDE 80, /* Device model name */
+ GENESYS_GL841,
+ NULL,
+
+ {2400, 1200, 600, 300, 150, 75, 0}, /* possible x-resolutions */
+ {4800, 2400, 1200, 600, 300, 150, 75, 0},/* possible y-resolutions */
+ {16, 8, 0}, /* possible depths in gray mode */
+ {16, 8, 0}, /* possible depths in color mode */
+
+ SANE_FIX (0.42), /* Start of scan area in mm (x) */
+ SANE_FIX (7.9), /* Start of scan area in mm (y) */
+ SANE_FIX (218.0),/* Size of scan area in mm (x) */
+ SANE_FIX (299.0),/* Size of scan area in mm (y) */
+
+ SANE_FIX (3.0), /* Start of white strip in mm (y) */
+ SANE_FIX (0.0), /* Start of black mark in mm (x) */
+
+ SANE_FIX (0.0), /* Start of scan area in TA mode in mm (x) */
+ SANE_FIX (0.0), /* Start of scan area in TA mode in mm (y) */
+ SANE_FIX (100.0),/* Size of scan area in TA mode in mm (x) */
+ SANE_FIX (100.0),/* Size of scan area in TA mode in mm (y) */
+
+ SANE_FIX (0.0), /* Start of white strip in TA mode in mm (y) */
+
+ 0, 0, 0, /* RGB CCD Line-distance correction in pixel */
+
+ COLOR_ORDER_RGB,
[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 released
SANE-Backends 1.0.19 has been released. Changes since SANE 1.0.18: New backends: cardscan (Corex Cardscan 800c), epjitsu (Epson-based Fujitsu), epson2 (various Epson scanners), hp3900 (HP ScanJet 3970 and more), hp5590 (HP ScanJet 5590 and more), hpljm1005 (HP LaserJet M1005 and more), hs2p (Ricoh IS400 series) Updated backends: abaton, agfafocus, apple, artec, artec_eplus48u, as6e, avision, canon, coolscan, coolscan2, dc25, dell1600n_net, dll, epson, fujitsu, genesys, gt68xx, hp3500, ibm, lexmark, microtek, microtek2, mustek, nec, net, pie, pint, pixma, plustek, plustek_pp, ricoh, s9036, sm3600, sm3840, snapscan, sp15c, st400, tamarack, teco2, test, u12, umax, umax1220u, umax_pp Plus: Scanimage detects more chipsets. Internal scsi, usb, tcp and udp code updates. Basic HAL .fdi creation support Build system updates. Updated translations. Documentation updates. Bugfixes. Note: This will be (hopefully) the last release of the SANE 1.0 series. The next release of SANE will be extended (in a backwards compatible fashion) to support more features of modern scanners. Please join the sane-devel mailing list to take part in the ongoing discussions of the future of SANE. Complete tarball (md5sum: 8c0936272dcfd4e98c51512699f1c06f) and diff against 1.0.18 can be downloaded from http://alioth.debian.org/frs/?group_id=30186 or eventually from ftp://ftp.sane-project.org/pub/sane/ Thanks- allan -- The truth is an offense, but not a sin
[sane-devel] man2html help
My version of man2html does not take any of the arguments given in doc/Makefile, and so all the html manpages on the sane website are garbage at the moment. if someone else has a clue about this program, i could use one. i will dig into it more tomorrow. allan -- The truth is an offense, but not a sin
[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] Canon MP470 support
Hi Nicholas,
Good news! It works. I think the only kink was the order of a few things:
1. compile
2. copy
3. sudo ldconfig -- just in case
4. udev hacks + replug device
5. Try everything else (scanimage -L)
If 3 and 4 are interchanged, I get a scanimage: sane_start: Invalid argument
I added this to /etc/udev/rules.d/45-libsane.rules:
# Canon PIXMA MP470
SYSFS{idVendor}==04a9, SYSFS{idProduct}==1723, MODE=664, GROUP=scanner
Makes sense to push this change upstream.
One problem I notice is that the y-axis offset seems off when I select an area
in the preview and then request a full scan of just that area. This is roughly
off by 1cm - so if I have a bounding box on ubuntu in the standard printer
test page, the top part of b is chopped, so it looks like an o. This is
reproducible but is not a show stopper!
Thanks!
-Ashwin
- Original Message
From: Nicolas nicolas.mar...@freesurf.fr
To: Ashwin cybernytrix at yahoo.com
Cc: sane-devel at lists.alioth.debian.org
Sent: Sunday, February 10, 2008 4:03:36 PM
Subject: Re: Canon MP470 support
A test driver for MP470 is ready, you can download it at the following link:
http://www.sendspace.com/file/ogro4h
Use instructions given on this blog to install and test it:
http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html
Let us know...
Nicolas
Le dimanche 10 f?vrier 2008 ? 12:48 -0800, Ashwin a ?crit :
here is the code:
Bus 005 Device 002: ID 04a9:1723 Canon, Inc.
let me know when the driver is ready. will be better if you can put out a
patch, so i can do it via apt-get source.
thanks!
-Ashwin
- Original Message
From: Nicolas nicolas.martin at freesurf.fr
To: sane-devel at lists.alioth.debian.org
Cc: cybernytrix at yahoo.com
Sent: Saturday, February 9, 2008 8:20:02 AM
Subject: Canon MP470 support
Being a recent Canon model, we could try to check whether it can be driven
by Pixma modified driver for MP610, MP520, and MP210.
Can you provide the USB PID of this all-in one ?
You can get it by a simple:
$ lsusb
I can declare this scanner in the driver, issue the modified version of the
driver, and you could give a try to check it.
Instructions on how to install the modified Pixma driver above Sane 1.0.18
are given on this blog:
http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html
This is for Allan:
Concerning new Sane version and Pixma driver:
I've ready sitting on my desktop, the patch to add MP610, MP520 and MP210
scanners to patch the pixma files, in the current Sane CVS version.
At the moment, compiled and tested successfully with an MP610, on Gutsy and
on Mandriva 2007.
Nicolas
Le jeudi 07 f?vrier 2008 ? 21:02 -0800, Ashwin a ?crit :
Hello,
I just bought a Canon Pixma MP470 printer+scanner device and I cannot
get it to work with sane. The printer part seems to work with the MP150 driver.
I can pitch in with some usb scan info, if some one tells me where to
find the docs.
-ashwin
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
it now.
Never miss a thing. Make Yahoo your homepage.
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080210/c60c7c9a/attachment.htm
[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
Hi Ashwin!
That's good news too then!
For sure, the libsane rule needed to be adjusted for PID 1723,
corresponding to MP470.
When the Sane driver will be updated with the changes for recent Pixma
MFPs, the libsane
rules will be produced automatically when compiling Sane, provided that
the .desc files are
correctly set up.
For the y-axis point, maybe I did not catch exactly the issue.
You must know that the driver rounds up the scan dimensions to 32
(needed by Pixma protocol),
so this will be more sensitive at low dpi than at high dpi values. But
the rounding should be rendered
by the Frontend anyway (Xsane does it)
Be sure to have the Y top left parameter to 0.000 in the Sane standard
options window, in order
to have the scan starting at the very top of the page.
Thanks for your feedback.
So as a summary, we have now those additional Pixma MFPs working, to be
added to the Sane files, and
that seems to present optimal or satisfactory results:
MP610
MP520
MP470
MP210
MP710
MP740
Would be nice to have feedback for MP140 too, if anyone has got one, as
it looks that this competitor has great
chance to be working with this driver too ;-)
Rgds
Nicolas
Le dimanche 10 f?vrier 2008 ? 20:38 -0800, Ashwin a ?crit :
Hi Nicholas,
Good news! It works. I think the only kink was the order of a few
things:
1. compile
2. copy
3. sudo ldconfig -- just in case
4. udev hacks + replug device
5. Try everything else (scanimage -L)
If 3 and 4 are interchanged, I get a scanimage: sane_start: Invalid
argument
I added this to /etc/udev/rules.d/45-libsane.rules:
# Canon PIXMA MP470
SYSFS{idVendor}==04a9, SYSFS{idProduct}==1723, MODE=664,
GROUP=scanner
Makes sense to push this change upstream.
One problem I notice is that the y-axis offset seems off when I select
an area in the preview and then request a full scan of just that area.
This is roughly off by 1cm - so if I have a bounding box on ubuntu
in the standard printer test page, the top part of b is chopped,
so it looks like an o. This is reproducible but is not a show
stopper!
Thanks!
-Ashwin
- Original Message
From: Nicolas nicolas.martin at freesurf.fr
To: Ashwin cybernytrix at yahoo.com
Cc: sane-devel at lists.alioth.debian.org
Sent: Sunday, February 10, 2008 4:03:36 PM
Subject: Re: Canon MP470 support
A test driver for MP470 is ready, you can download it at the following
link:
http://www.sendspace.com/file/ogro4h
Use instructions given on this blog to install and test it:
http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html
Let us know...
Nicolas
Le dimanche 10 f?vrier 2008 ? 12:48 -0800, Ashwin a ?crit :
here is the code:
Bus 005 Device 002: ID 04a9:1723 Canon, Inc.
let me know when the driver is ready. will be better if you can put
out a patch, so i can do it via apt-get source.
thanks!
-Ashwin
- Original Message
From: Nicolas nicolas.martin at freesurf.fr
To: sane-devel at lists.alioth.debian.org
Cc: cybernytrix at yahoo.com
Sent: Saturday, February 9, 2008 8:20:02 AM
Subject: Canon MP470 support
Being a recent Canon model, we could try to check whether it can be
driven by Pixma modified driver for MP610, MP520, and MP210.
Can you provide the USB PID of this all-in one ?
You can get it by a simple:
$ lsusb
I can declare this scanner in the driver, issue the modified version
of the driver, and you could give a try to check it.
Instructions on how to install the modified Pixma driver above Sane
1.0.18 are given on this blog:
http://mp610.blogspot.com/2007/11/new-sane-scanner-driver-for-canon-mp610.html
This is for Allan:
Concerning new Sane version and Pixma driver:
I've ready sitting on my desktop, the patch to add MP610, MP520 and
MP210 scanners to patch the pixma files, in the current Sane CVS
version.
At the moment, compiled and tested successfully with an MP610, on
Gutsy and on Mandriva 2007.
Nicolas
Le jeudi 07 f?vrier 2008 ? 21:02 -0800, Ashwin a ?crit :
Hello,
I just bought a Canon Pixma MP470 printer+scanner device and I
cannot get it to work with sane. The printer part seems to work
with the MP150 driver.
I can pitch in with some usb scan info, if some one tells me where
to find the docs.
-ashwin
__
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.
Try it now.
Never miss a thing. Make Yahoo your homepage.
__
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
it now.
-- next part --
An HTML attachment was scrubbed...
URL:
[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] debug file attached (Re: Canon MP710/740 support request)
On Feb 12, 2008 6:14 AM, m. allan noah kitno455 at gmail.com wrote: Gernot- does the windows driver allow independent resolution controls? what are you going to do with the stretched image that will result? Maybe I misunderstood the issue: the MP710 and others have resolutions of 1200x2400 (or 2400x4800), whereas the driver currently allows only 1200x1200 (or 2400x2400). I thought that this means that the Windows driver is giving better resolution in one dimension. Regards, Gernot
[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
[sane-devel] Canon LiDE 90
Hi,
I've made some progress ...
I changed :
/* CANOLIDE35 */
{1200,
/*TODO: find a good reason for keeping all three following variables*/
87,/*(black) */
87,/* (dummy) */
0,/* (startxoffset) */
10400,/*sensor_pixels */
210,
200,
By :
/* CANOLIDE35 */
{600,
/*TODO: find a good reason for keeping all three following variables*/
87,/*(black) */
87,/* (dummy) */
0,/* (startxoffset) */
10400,/*sensor_pixels */
210,
200,
And used the gpo values :
/* CANONLIDE35 */
{
{0x38, 0x80}
,
{0x7f, 0xe0}
It's no so bad ... (but image is always inverted ...)
To have the white led, in color mode of scanimage, it's ok.
scanimage -d --mode Color image.pnm
PS : I need to be root ... do you know what to do to avoid it ?
Concerning scan borders, we must change scan area (not best, but better) :
SANE_FIX (9.),/* Start of scan area in mm (x) */
SANE_FIX (7.7),/* Start of scan area in mm (y) */
SANE_FIX (218.0),/* Size of scan area in mm (x) */
SANE_FIX (297.0),/* Size of scan area in mm (y) */
Guillaume Gastebois a ?crit :
Hello,
I modified registers 10-1d with :
{0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
0x00, 0x04},
Where do I set this ? (which parameter of which struct ?)
Thanks again for your help.
PS : Reading your comments, I guess you're french ;)
Bonne soir?e ;)
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
[sane-devel] Canon LiDE 90
sane at tsleg.com a ?crit : Where do I set this ? (which parameter of which struct ?) Sorry ... I found where to set this.
[sane-devel] Formulardaten
cgi-mailer at kundenserver.de writes: 2. Manufacturer (e.g. Mustek): 'Epson Stylus DX 4050' Treat as if it's a DX4000 and all should be well. The DX4000 is listed in epkowa.desc, status: good. 3. Model name (e.g. ScanExpress 1200UB): 'All in One' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 0x04b8 6. Product id (e.g. 0x0002): '' 0x082f 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): '' -- Olaf Meeuwissen FLOSS Engineer -- EPSON AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/
[sane-devel] Canon LiDE 80 (2nd try)
On Monday, 11. February 2008, Pierre Willenbrock wrote: 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 bcdDevice of mine is 0302. Reinhard
[sane-devel] Canon LiDE 80 (2nd try)
On Tuesday 12 February 2008 03:41:49 Reinhard Biegel wrote: On Monday, 11. February 2008, Pierre Willenbrock wrote: 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 that was me. But it's not quite clear. got also some info that GK842 starts @ 303 bcdDevice of mine is 0302. So probably it's a GL841. Any chance to disassemble the device? - Gerhard
[sane-devel] Canon LiDE 90
Hello,
I inverted colors with gimp. Sorry I forget this operation.
Selon postmaster postmaster at tsleg.com:
Hi,
How did you get this one :
http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_comment.jpg ??
Colors are not inverted ...
Guillaume Gastebois a ?crit :
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
[sane-devel] Canon LiDE 80 (2nd try)
Gerhard Jaeger schrieb: On Tuesday 12 February 2008 03:41:49 Reinhard Biegel wrote: On Monday, 11. February 2008, Pierre Willenbrock wrote: 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 that was me. But it's not quite clear. got also some info that GK842 starts @ 303 bcdDevice of mine is 0302. So probably it's a GL841. Any chance to disassemble the device? No need to. i just meant to make sure that it is not a version on the edge to GL843(if there is such an edge). My Canon LiDE 35 has 0305, and is said to contain a GL842, according to [1], but the LiDE 50 there is 0303 and GL841. Apart from that the two datasheets show suspiciously few differences. Regards, Pierre [1] http://www.sane-project.org/unsupported/canon-lide-50.html
[sane-devel] Canon LiDE 80 (2nd try)
On Monday 11 February 2008, Pierre Willenbrock wrote: Reinhard Biegel schrieb: Am Monday, 11. February 2008 schrieb Stefan Lucke: 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. So we need to write reserved I/O bits, (0x6b) need to write to undefined gamma addresses (0x5b/5c - 0x0c00). Thats really magic. Both areas are defined for GL843 but not for GL841/2. 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 It is for my scanner: idVendor 0x04a9 Canon, Inc. idProduct 0x2214 bcdDevice3.02 as found on: http://www.sane-project.org/unsupported/canon-lide-80.html -- Stefan Lucke
[sane-devel] Canon LiDE 80 (2nd try)
On Tuesday 12 February 2008 10:24:51 Pierre Willenbrock wrote: Gerhard Jaeger schrieb: On Tuesday 12 February 2008 03:41:49 Reinhard Biegel wrote: On Monday, 11. February 2008, Pierre Willenbrock wrote: 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 that was me. But it's not quite clear. got also some info that GK842 starts @ 303 bcdDevice of mine is 0302. So probably it's a GL841. Any chance to disassemble the device? No need to. i just meant to make sure that it is not a version on the edge to GL843(if there is such an edge). My Canon LiDE 35 has 0305, and is said to contain a GL842, according to [1], but the LiDE 50 there is 0303 and GL841. Apart from that the two datasheets show suspiciously few differences. Okay, I just checked some sources I got and the major differences seem between 843 and 84[1,2]. 841 and 842 seem to be more or less the same. - Gerhard
[sane-devel] Epson 4490 support ?
The Epson 4490 is not listed on http://www.sane-project.org/sane-mfgs.html#Z-EPSON Surfing around i see people have asked about support, there are cases where it does NOT work with out-of-the-box distribs/kooka, but i am not seeing definitive answers of whether it does or doesn't Does anyone here know if this model is supported? If it is not supported, could someone recommend something comparable in price (this one is $160) AND quality? (I am hearing Epson is the best brand in terms of linux support and quality) Thanks Andrew PS:
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'qpadla at gmail.com' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'ScanJet G2710' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x2805' 7. Chipset (e.g. lm9831): '1.00' 8. Comments (e.g. similar to Mustek 1234): 'Probably unsupported.' 9. Data (e.g. sane-find-scanner -v -v): ' # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: device descriptor of 0x/0x at 002:001 (Linux 2.6.22-14-generic ohci_hcd OHCI Host Controller) bLength 18 bDescriptorType 1 bcdUSB1.10 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x idProduct 0x bcdDevice 2.06 iManufacturer 3 (Linux 2.6.22-14-generic ohci_hcd) iProduct 2 (OHCI Host Controller) iSerialNumber 1 (:00:02.0) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize2 bInterval 255 ms bRefresh 0 bSynchAddress 0 device descriptor of 0x03f0/0x2805 at 001:003 (hewlett packard hp scanjet) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x03F0 idProduct 0x2805 bcdDevice 1.00 iManufacturer 1 (hewlett packard) iProduct 2 (hp scanjet) iSerialNumber 3 (CN77SA50Q60530) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 (USB SCANNER) bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 2 mA
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'rimvydas.lauzikas at kf.vu.lt' 2. Manufacturer (e.g. Mustek): 'Canon' 3. Model name (e.g. ScanExpress 1200UB): 'CanoScan LiDe 90' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x04a9' 6. Product id (e.g. 0x0002): '0x1900' 7. Chipset (e.g. lm9831): 'GL842 (Genesys well known scanner chip)' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Formulardaten
El Tuesday 12 February 2008 18:53:19 cgi-mailer at kundenserver.de escribi?: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'qpadla at gmail.com' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'ScanJet G2710' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x2805' ... checking for RTS8822L-01H ... This USB chip looks like a RTS8822L-01H (result from sane-backends 1.0.18-cvs) ... Looking at some photos, this scanner seems to be similar to HP Scanjet 3800 in the same way HP G3010 is similar to HP 4370. So G versions are the same products with different name and, may be, some addition like a switch to turn off/on device manually. I will suppose that G2710 uses a RTS8822BL-03A chipset like HP3800 and I'm adding support for this scanner in few days. Jonathan Bravo Lopez
[sane-devel] Formulardaten
On Tuesday 12 February 2008 20:18:03 JKD wrote: El Tuesday 12 February 2008 18:53:19 cgi-mailer at kundenserver.de escribi?: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'qpadla at gmail.com' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'ScanJet G2710' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x2805' ... checking for RTS8822L-01H ... This USB chip looks like a RTS8822L-01H (result from sane-backends 1.0.18-cvs) ... Looking at some photos, this scanner seems to be similar to HP Scanjet 3800 in the same way HP G3010 is similar to HP 4370. So G versions are the same products with different name and, may be, some addition like a switch to turn off/on device manually. I will suppose that G2710 uses a RTS8822BL-03A chipset like HP3800 and I'm adding support for this scanner in few days. Jonathan Bravo Lopez Hello. Thanks for quick response Jonathan. According to sane-find-scanner it's a chip=RTS8822L-01H. Is this valid information? In any way i am unable to execute scanimage with this device: root at atlas:~# scanimage -L 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). -- == - Best regards, Nikolay Pavlov. --- ==
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb:
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.
http://ggastebois.free.fr/lide90_snoop/scanimage.log
says you have offset_calibration enabled. that cannot work currently.
offset_calibration fiddles with the Frontend offset parameters and will
make the following calibration steps fail. Comment that out in
genesys_flatbed_calibration for now.
Apart from that, please try to toggle the INVOP bit, that is
bit2(counting from 0) of Setup Register 2. This may fix the inverted
image. Looking at the Block diagram of the WM8199, the calibration may
still need to be changed if INVOP=1, but it is worth a try.
Regards,
Pierre
[sane-devel] Canon LiDE 90
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try to reenable offset_calibration and I get :
http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_invop_0.jpg
In the central vertical line we can see a piece of my dinosause not
reverted !!! I think this works. And good news : the frontend seems to
be (or to be compatible) with a wolfson wm8199.
If you remember, this gray line is on the vertical of the small black
piece (in calibration area). So calibration is better with black area !!
Regards
Guillaume
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
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.
http://ggastebois.free.fr/lide90_snoop/scanimage.log
says you have offset_calibration enabled. that cannot work currently.
offset_calibration fiddles with the Frontend offset parameters and will
make the following calibration steps fail. Comment that out in
genesys_flatbed_calibration for now.
Apart from that, please try to toggle the INVOP bit, that is
bit2(counting from 0) of Setup Register 2. This may fix the inverted
image. Looking at the Block diagram of the WM8199, the calibration may
still need to be changed if INVOP=1, but it is worth a try.
Regards,
Pierre
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: Hello, I see that reg[2] was like 0x07. So INVOP was still set !!! I comment out offset_calibration in genesys_flatbed_calibration, set reg[2] to 0x03, and I get a black image with a gray vertical line in the middle !!! I try to reenable offset_calibration and I get : http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_invop_0.jpg In the central vertical line we can see a piece of my dinosause not reverted !!! I think this works. And good news : the frontend seems to be (or to be compatible) with a wolfson wm8199. If you remember, this gray line is on the vertical of the small black piece (in calibration area). So calibration is better with black area !! hmm. the shading calibration currently needs some black to work. But good news. Now, where did i put that alternative offset_calibration code... Regards, Pierre
[sane-devel] Canon LiDE 90
Pierre Willenbrock schrieb: Guillaume Gastebois schrieb: Hello, I see that reg[2] was like 0x07. So INVOP was still set !!! I comment out offset_calibration in genesys_flatbed_calibration, set reg[2] to 0x03, and I get a black image with a gray vertical line in the middle !!! I try to reenable offset_calibration and I get : http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_invop_0.jpg In the central vertical line we can see a piece of my dinosause not reverted !!! I think this works. And good news : the frontend seems to be (or to be compatible) with a wolfson wm8199. If you remember, this gray line is on the vertical of the small black piece (in calibration area). So calibration is better with black area !! hmm. the shading calibration currently needs some black to work. But good news. Now, where did i put that alternative offset_calibration code... obviously, in cvs, while thinking i'd only put the power-mode changes in.. The needed change is a one liner.. This should compile, but i don't know if it works. The shading calibration should still be commented out. offset_calibration, gain_calibration and led_calibration might work. Regards, Pierre -- next part -- A non-text attachment was scrubbed... Name: offset-calib.patch Type: text/x-patch Size: 599 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080213/25da0826/attachment.bin
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'ficmatin01 at solar.com.br' 2. Manufacturer (e.g. Mustek): 'HP' 3. Model name (e.g. ScanExpress 1200UB): 'Scanjet G2710' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x2805' 7. Chipset (e.g. lm9831): 'RTS8822L-01H' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): 'This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: device descriptor of 0x03f0/0x2805 at 001:002 (hewlett packard hp scanjet) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x03F0 idProduct 0x2805 bcdDevice 1.00 iManufacturer 1 (hewlett packard) iProduct 2 (hp scanjet) iSerialNumber 3 (CN79UA53QW0530) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 (USB SCANNER) bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 2 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 0 bInterfaceProtocol 255 iInterface 5 (Bulk-In, Bulk-Out, Interrupt Interface) endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 bInterval 12 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for RTS8822L-01H ... This USB chip looks like a RTS8822L-01H (result from sane-backends 1.0.18) found USB scanner
[sane-devel] Sane-backends 1.0.19 released
Hello, On Feb 12 15:46 m. allan noah wrote (shortened): why would you want to rebuild the configure script from the tarball? At least for us (i.e. the Suse distribution) it is recommended to run autoreconf -fi so that it matches exactly to the tools in our distribution. This does not mean that it is a must - but usually we do it. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] genesys_gl841.c: infinite loops
Pierre Willenbrock schrieb: Stefan Lucke schrieb: Hi, I guess there are 3 possibilities for infinite loops. Attached patch fixes this and adjusts loop threshold to given comments.. Thanks for spotting these. We have never had a problem with those loops, but it is certainly a good idea to have the code working as the comments in the code suggest. A short test revealed no breakages. I will commit these corrections after the release. commited. Regards, Pierre
[sane-devel] genesys_gl841.c: infinite loops
On Feb 13, 2008 9:22 PM, Pierre Willenbrock pierre at pirsoft.dnsalias.org wrote: Pierre Willenbrock schrieb: Stefan Lucke schrieb: Hi, I guess there are 3 possibilities for infinite loops. Attached patch fixes this and adjusts loop threshold to given comments.. /../ Thanks for spotting these. /../ commited. Sorry if this is the wrong place to ask: what is status of GL841 support and how can I help? The docs say GL841 support will be added to genesys backend, but beyond that I don't see any info. I guess you gentlemen are the ones implementing this work. I'd like to help, so that the latest Canon scanners can get support (I have a Canoscan 8800F). What can I do to help? Regards, Gernot
[sane-devel] Canon LiDE 90
Hello, OK, I'll try it tonight. How do I cleanly remove shading_calibration ? Regards Guillaume Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: Pierre Willenbrock schrieb: Guillaume Gastebois schrieb: Hello, I see that reg[2] was like 0x07. So INVOP was still set !!! I comment out offset_calibration in genesys_flatbed_calibration, set reg[2] to 0x03, and I get a black image with a gray vertical line in the middle !!! I try to reenable offset_calibration and I get : http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_invop_0.jpg In the central vertical line we can see a piece of my dinosause not reverted !!! I think this works. And good news : the frontend seems to be (or to be compatible) with a wolfson wm8199. If you remember, this gray line is on the vertical of the small black piece (in calibration area). So calibration is better with black area !! hmm. the shading calibration currently needs some black to work. But good news. Now, where did i put that alternative offset_calibration code... obviously, in cvs, while thinking i'd only put the power-mode changes in.. The needed change is a one liner.. This should compile, but i don't know if it works. The shading calibration should still be commented out. offset_calibration, gain_calibration and led_calibration might work. Regards, Pierre
