[sane-devel] Epson (Stylus) CX 5400 confusion
Johannes Meixner writes: > Hello, > > According to the model decription files there are two backends > which support an Epson (Stylus) CX 5400 > epson for "Epson CX-5400" with USB-IDs 0x04b8:0x0808 and 0x04b8:0x0801 > and > epkowa for "Epson Stylus CX5400" with USB-ID 0x04b8:0x0801 > > I assume the "Epson CX-5400" and the "Epson Stylus CX5400" > are the same so that there seems to be a USB ID confusion and > a model name confusion for this model? Yes, these would be the same. It appears that the epkowa backend has the product ID wrong. Stylus CX5100/CX5200 0x0801 Stylus CX5300/CX5400 0x0808 On a related note, the CX6600 is listed with two product IDS, but it appears that the following is correct: Stylus CX6300/CX6400 0x0805 Stylus CX6500/CX6600 0x0808 The Stylus CX5100/CX5200 corresponds to the Japanese CC-600PX and all the other models do not have a corresponding Japanese version. We'll put fixing this on the list the next iscan release. > For details background information see > https://bugzilla.novell.com/show_bug.cgi?id=229250 > > At least for the user who sent us the above bug report, > the epson backend does not work for his scanner 0x04b8:0x0808 > (SANE debug outputs are attached to the bug report) but epkowa > works after adding 0x04b8:0x0808 to epkowa.conf. > > Perhaps there is some subtle difference so that the epson backend > works only for0x04b8:0x0801 but not for 0x04b8:0x0808? The difference is not that subtle and has been mentioned on the list before, IIRC. Yes, here it is: http://lists.alioth.debian.org/pipermail/sane-devel/2006-December/018296.html The epson backend maintainer was Cc:d on that mail. There is also a Debian bug that mentions it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399119 The right thing to do is to remove the block from the code of the epson backend. Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] gl843 & genesys backend
Hello, I bought an HP g4050 scanner a couple of weeks ago, and I've been looking for a couple of days to add support for it in the genesys backend. I have basic communication with the scanner now but there are a lot of things I don't understand yet. This scanner use a gl843, so, has somebody added support for this chip in the genesys backend? It looks like a lot of work to do. I've some logs taken with usbsnoop and although the gl843 is very similar to the gl841 it have also a lot of differences, motor tables are loaded in a different way, more registers ... I don't think I've time to add support for this chip from scratch, but if someone have done something I can try to complete. cheers nacho
[sane-devel] UMAX, more info
Hi Further to my UMAX Astra 2200 message before, I've more info for you. I'm using it with Fedora 6, and it was working OK. Now after a reboot the scanner tool scanned, first of all, 17x0 pixel, 8bit/color, 3 colors, 5dpi x 5dpi, 0.0B. On a second go after I changed the dpi to 300, it gave "Failed to start scanner: invalid argument". Acquire preview failed too (the dotty line in that is certainly bigger than 17x0 pixels and so are the x and y co-ords in the options: 0, 0, 10, 20 or thereabouts. I closed and re-opened the scanner tool and got a 300 dpi scan 1435 x 45 pixels that seemed to start where I wanted it to start (defined by the preview dotty line), but it stopped far short. A second scan gave the error above. I rebooted the whole lot again and got a 1828 x 13 pixel scan, then it failed on second scan. Any thoughts on what might be causing this, where to look, what to think about? It would appear the hardware's connected OK, although pressing the front buttons on the scanner (scan, copy) doesn't cause anything to happen. I did make some changes to umax.conf which made no difference to the errors, and I set SANE_DEBUG_UMAX=128 but that didn't seem to provide me with any additional information, at least to the shell (perhaps I should be looking in the log files .. but which and where (I use Linux every day but I'm no expert in it)). Cheers J
[sane-devel] gl843 & genesys backend
Sorry if you receive this message twice, I sent a similar one yesterday but it looks like it is lost. My question es about the HP G4050 scanner that uses a gl843 chip. I have had one of this for a couple of weeks now, and have been playing a bit with the genesys backend and some captures with an usb sniffer. The chips I've been able to identify in this scanner are: Usb chip: gl843 Motor: allegro a3967 slbt AFE: wolfson WM8196 scds Memory: atmel 628 93c46 I've done some changes to the gl841 part of the genesys backen to initialize the extra registers of the gl843, change the way the motor tables are loaded (different to the gl841) and all the things I've found that need to be changed in some hours reading the genesys code. Right now I have basic communication with the scanner, but the motor moves very slow, I've read several messages in the archives of the list about the configuration of the structures of the genesys backend and I think that the configuration is more or less ok. And I'm not able to get a image although I don't see errors in the logs (SANE_DEBUG_GENESYS_GL841=255) Probably the motor and the gpio parts are wrong. So my question is, have somebody done something to support the gl843? I've read somethings in the archives about some canon scanners using this chip, but have found nothing to look. Thanks for your time nacho
[sane-devel] gl843 & genesys backend
Hi Igncio, J. Ignacio Gij?n schrieb: > Sorry if you receive this message twice, I sent a similar one > yesterday but it looks > like it is lost. It is right there. > My question es about the HP G4050 scanner that uses a gl843 chip. I > have had > one of this for a couple of weeks now, and have been playing a bit with the > genesys backend and some captures with an usb sniffer. > > The chips I've been able to identify in this scanner are: > Usb chip: gl843 > Motor: allegro a3967 slbt > AFE: wolfson WM8196 scds > Memory: atmel 628 93c46 > > I've done some changes to the gl841 part of the genesys backen to > initialize > the extra registers of the gl843, change the way the motor tables are > loaded > (different to the gl841) and all the things I've found that need to be > changed > in some hours reading the genesys code. > > Right now I have basic communication with the scanner, but the motor moves > very slow, I've read several messages in the archives of the list > about the configuration of the structures of the genesys backend and I > think that the configuration is more or less ok. And I'm not able to > get a image although > I don't see errors in the logs (SANE_DEBUG_GENESYS_GL841=255) A moving motor is a good first step, that means the gl843 is basically doing it's job as instructed, and the hardware does not have too special power management features(ever needed to switch gpio pins in a certain order, else the scanner shortcircuits itself and resets?). What you are running into is the complete lack of ccd-support in the gl841 part. Currently, only cis-mode is implemented. You need to collect the register settings for the clock registers, setup the lamp pwm properly and set the scanner into ccd-mode. If i didn't forget some part, that is. > Probably the motor and the gpio parts are wrong. don't worry with the motor. that should be easy to improve. > So my question is, have somebody done something to support the gl843? I've > read somethings in the archives about some canon scanners using this > chip, but > have found nothing to look. To my knowledge, there is no previous work for the gl843. Regards, Pierre
[sane-devel] Recommendations for reliable ADF sheetfed (Fujitsu, Avision, others?)
I'm looking for current recommendations for a fast ADF scanner with reliable paper handling and stable SANE driver support for the desired modes accessed via python PIL/Sane, scanadf, scanner access across network, etc. In the past (I ask every year or so, haven't bought yet) m. allan noah and others have discussed their experiences and driver work with the Fujitsu FI-5xxxC(x) series. Good representations were also made about the Avision AV220C2 series, primarily on the strength of the avision driver support. I was able to find a source to import units from outside the US, but I have concerns about ongoing US availability. Since time has gone by and new models may be out, has anyone got recommendations for models that meet most of the following criteria in the USD $1,000 or under price range? - 1-bit and greyscale modes are the only ones that matter here - 300 dpi, and able to do 300dpi at high speed - ADF with at least 50 sheet capacity, good paper-feed reliability - USB 2.0 interface (or ethernet interface) - Priority is on Linux SANE compatibility, python PIL/Sane usage, scanadf over network. - Limited feature/modes support OK, only need the 300dpi bw,greyscale modes to be reliable and fast. Thanks for the annual repeat of the question, and thanks if anyone has any recommendations of new models, or comments on their ongoing experience with the AV220C2, FI-5120C or updated units.
[sane-devel] Specialized plastic/laminated id card scanner, USB interface?
I need to scan visitors' plastic/laminate identification cards. The scans are to be initiated via web app, signalling a headless SANE linux server to scan via scanadf, network scanning, python PIL/sane, etc. Has anyone got any vendor and model recommendations for a specialised USB card scanner (SANE compatible, obviously) that will handle of various shapes and thicknesses (e.g. flat paper path)? Thanks.
[sane-devel] Re: Specialized plastic/laminated id card scanner, USB interface?
Jeff Kowalczyk wrote: > I need to scan visitors' plastic/laminate identification cards. The scans > are to be initiated via web app, signalling a headless SANE linux server > to scan via scanadf, network scanning, python PIL/sane, etc. > > Has anyone got any vendor and model recommendations for a specialised USB > card scanner (SANE compatible, obviously) that will cards handle of > various shapes and thicknesses (e.g. flat paper path)? > > Thanks. BTW, the cards are typically printed on both sides, so I have to scan front and back in one pass. Thanks.
[sane-devel] gl843 & genesys backend
2007/3/27, Pierre Willenbrock : > Hi Igncio, > > J. Ignacio Gij?n schrieb: > > Sorry if you receive this message twice, I sent a similar one > > yesterday but it looks > > like it is lost. > > It is right there. > Sorry, now I realize that in this list I don't receive the messages that I send > > A moving motor is a good first step, that means the gl843 is basically > doing it's job as instructed, and the hardware does not have too special > power management features(ever needed to switch gpio pins in a certain > order, else the scanner shortcircuits itself and resets?). > > What you are running into is the complete lack of ccd-support in the > gl841 part. Currently, only cis-mode is implemented. You need to collect > the register settings for the clock registers, setup the lamp pwm > properly and set the scanner into ccd-mode. If i didn't forget some > part, that is. > > > Probably the motor and the gpio parts are wrong. > > don't worry with the motor. that should be easy to improve. > Thanks for the tips, I'm going to "clean" the code removing everything specific of the rest of the scanners in order to make everything more manageable, with cleaner code it will be easier look for differences with the win driver. Thanks again nacho
