[sane-devel] Trouble with network scanning and Umax Astra 2200
I have a Umax Astra 2200 (the combo SCSI/USB version) connected to a USB
port. I can scan locally as root or a user using 'scanimage -d
umax:libusb:001:014 foo.pnm'. I also have it configured such that I can
scan over the network locally (scanimage -d
net:localhost:umax:libusb:001:014 foo.pnm). However, I am unable to
scan over the network from another machine (I've tried with two).
scanimage -L shows the scanner on both client machines:
jonhall@tirian:~$ scanimage -L
device `net:10.0.2.10:umax:libusb:001:014' is a UMAX Astra 2200
flatbed scanner
scanimage -T, however, freezes, and renders the scanner unresponsive until
I power cycle it.
jonhall@tirian:~$ scanimage -d net:10.0.2.10:umax:libusb:001:014 -T
scanimage: scanning image of size 850x1170 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 2550 bytes...
I ran an strace on saned on the server machine. Here's the last bit (I
can send the entire strace to someone if it would be helpful):
getpeername(7, {sa_family=AF_INET6, sin6_port=htons(51945),
inet_pton(AF_INET6,
fcntl64(7, F_SETFL, O_WRONLY) = 0M
shutdown(7, 0 /* receive */)= 0M
fcntl64(6, F_SETFL, O_RDONLY|O_NONBLOCK) = 0M
select(8, [4 6], [7], NULL, NULL) = 2 (in [4], out [7])M
read(4, \0\0\0\6\0\0\0\0, 8192) = 8M
write(4, \0\0\0\0\0\0\0\1\0\0\0\1\0\0\t\366\0\0\3R\0\0\4\222\0\0..., 28)
= 28
select(8, [4 6], [7], NULL, NULL) = 1 (out [7])M
select(8, [4 6], [7], NULL, NULL) = 1 (out [7])M
The last line repeates infinately until I Ctrl-C, or power-cycle the scanner.
All three machines (server and two clients) are running Debian testing.
The server is running kernel 2.6.8, one client has 2.6.12.4 and one has
2.4.27. The server's USB host controller is an Intel 82371AB/EB/MB PIIX4.
Does anyone have any idea what's going on? Thanks for any help you can
provide!
-- Jonathan
[sane-devel] CanoScan LiDE 25
Thanks Henning On Wednesday 28 September 2005 03:47, Henning Meier-Geinitz wrote: [...] I don't know if that makes any difference but have you tried the development version of SANE (e.g. a CVS snapshot) yet? The plustek backend has been changed since incooperation of this patch. I've just tried with the development version, and I can acquire an image from the commandline using scanimage. e.g. #scanimage -x 200 -y 290 --resolution=100 -d plustek:libusb:002:011\ --format pnm /tmp/outfile.pnm However under remote scanning saned still locks up after what sounds like a) motor initialization and b)turning the lamp on. I still also get some rather annoying (possibly damaging?) grinding noises from the motor when using scanimage. Could you maybe point me in the right direction where I might tweak the code for the motor controls a little? Cheers Stephan
[sane-devel] Lexmark X1100 backend available
Le Mardi 27 Septembre 2005 15:55, Henning Meier-Geinitz a ?crit?: Hi, On Mon, Sep 26, 2005 at 08:06:09PM -0400, Fred Odendaal wrote: Currently, I use the size to set the window so having a freely selectable range wouldn't be much of a stretch. However, the motion of the scan head is jerky at some sizes so I don't think I have it fully figured out yet. Just to make this clear: My comments about the fixed sizes doesn't mean that the backend can't be added to CVS the way it currently is. I was just curious because most backends use free window sizes. Bye, Henning Hello, since I'm also fiddling with a Dell A920 (a X1100 in fact, only USB id change...), I can tell you that the register details available at http://www.lychnis.net/wiki/HP3500C are really accurate, since the rts8858 is only slightly different. Horizontal position is expressed in pixel at sensor hardware dpi in registers 0x66-0x67 and 0x6c-0x6d. Vertical position is given by registers 0x60-0x61 and 0x62-0x63. Regards, Stef
[sane-devel] CanoScan LiDE 25
Hi,
On Wednesday 28 September 2005 03:49, Stephan wrote:
Thanks Henning
On Wednesday 28 September 2005 03:47, Henning Meier-Geinitz wrote:
[...]
I don't know if that makes any difference but have you tried the
development version of SANE (e.g. a CVS snapshot) yet? The plustek
backend has been changed since incooperation of this patch.
I've just tried with the development version, and I can acquire an image from
the commandline using scanimage. e.g.
#scanimage -x 200 -y 290 --resolution=100 -d plustek:libusb:002:011\
--format pnm /tmp/outfile.pnm
However under remote scanning saned still locks up after what sounds like a)
motor initialization and b)turning the lamp on.
I still also get some rather annoying (possibly damaging?) grinding noises
from the motor when using scanimage.
Could you maybe point me in the right direction where I might tweak the code
for the motor controls a little?
I thought, that this issue + solution has been already sent to the list!
Anyway, again for the records:
As I don't have such a device, the motorclock fine-tuning needs to be done
by a volunteer who owns the LiDE25 - in the meantime, there are at least
3 people, equipped with such a device and the necessary instructions, but I got
no feedback with the correct motor settings. So it's maybe up to somebody else
to do the work (you Stephan? ;)
- get the latest CVS version of SANE
- open the file backend/plustek-usbdevs.c
- find the line: static HWDef Hw0x04A9_0x2220 = around line-nr 2308
* here you could tweak the values for dMaxMotorSpeed and dMaxMoveSpeed
- find the line { MODEL_CANON1200, 8, 51, 3, around line-nr 2575
* here you cloud tweak the MCLK settings for the various resolutions
and scanmodes (color 8+16bit, gray 8+16bit)
- after changing something, to the following:
touch backend/plustek.c
make all install
First you should check the preview scans (all modes), they will be
performed @ 75dpi - here you sould tweak the MCLK settings. If they seem
to work okay, you should scan a portion of the image which is somewhere
in the middle of the scanbed to see if the sensor movement is correct.
If not, tweak the MotorSpeed values.
After that go and do scans @ 100, 150, 200, 300, 400, 600, 800, 1200 and
2400dpi,
to see if the MCLKs are okay...
Any questions so far? Please ask!
Quite a lot of annyoing work, but needs to be done AND please don't forget to
send
us the results!
TIA for helping out
Gerhard
[sane-devel] Epson 3590
I manually clobbered all files in my installation that contained the word sane or were in sane directories, and re-installed the back- and frontends, but the problem with the preview persists. But as the scanner is slower in preview mode than in normal scan mode at low resolution, it might be a good idea to map the preview option to some low-res option in the backend. Another (although theoretical) problem with the Epson/Snapscan backend: The backend reads the path of the firmware file from the snapscan.conf file. What happens if there is more than one scanner? Regards, Ulrich Deiters
[sane-devel] (no subject)
Hello, I am having a Epson 1650 scanner. When using the flatbed device for scanning it works properly. When trying to use the TPU for scanning slides it looks like the scanner is not scanning in the middle (where the light for the TPU is located) of the scan area but as a stripe at the edge of the glass plate. There is no error message when running from xsane or kooka from the console. This happened after I updated from Debian Woody to Debian Sarge. In woody it was working correctly. Where can I look for error message or how can I set the scan area manually? Are there any other information needed to help me here? Thank you very much, Christian -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
[sane-devel] Epson 1650, TPU
sorry, I forgot the subject --- Weitergeleitete Nachricht --- Von: Christian Biermann ma...@gmx.net An: sane-devel@lists.alioth.debian.org Betreff: [sane-devel] (no subject) Datum: Wed, 28 Sep 2005 11:05:50 +0200 (MEST) Hello, I am having a Epson 1650 scanner. When using the flatbed device for scanning it works properly. When trying to use the TPU for scanning slides it looks like the scanner is not scanning in the middle (where the light for the TPU is located) of the scan area but as a stripe at the edge of the glass plate. There is no error message when running from xsane or kooka from the console. This happened after I updated from Debian Woody to Debian Sarge. In woody it was working correctly. Where can I look for error message or how can I set the scan area manually? Are there any other information needed to help me here? Thank you very much, Christian -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen f?r GMX Partner: http://www.gmx.net/de/go/partner -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f?r Mail, Message, More +++
[sane-devel] Trouble with network scanning and Umax Astra 2200
Hi, On Tue, Sep 27, 2005 at 07:21:30PM -0500, Jonathan Hall wrote: I have a Umax Astra 2200 (the combo SCSI/USB version) connected to a USB port. I can scan locally as root or a user using 'scanimage -d umax:libusb:001:014 foo.pnm'. I also have it configured such that I can scan over the network locally (scanimage -d net:localhost:umax:libusb:001:014 foo.pnm). However, I am unable to scan over the network from another machine (I've tried with two). [...] scanimage -T, however, freezes, and renders the scanner unresponsive until I power cycle it. [...] Do you use some kind of firewall or packet filter? saned uses a separate port for data (similar to ftp) and it seems that no data can be transferred using that port. To be sure that it's not a problem with the umax backend you can use the test backend (scanimage -d net:ip_address:test -T). Otherwise send debug logs of the client and server side: Client: SANE_DEBUG_NET=255 scanimage Server: SANE_DEBUG_UMAX=255 saned -d128 Bye, Henning
[sane-devel] Canon LiDE 25 scanner
I read the thread CanoScan LiDE 25 that finished on Mon Jul 18 06:24:08 UTC 2005. I've just bought one of these and found I couldn't get it to work under SuSE 9.2 (though I saw a review of MandrakeMove that seemed to indicate it worked with no special effort there). I have the scanner working okay under MacOS X, so although I can't easily run Windows to snoop any useful info for you, if you can point me at a tool I can use under MacOS X to gather any info for you, I'd be happy to try (and to try any Linux experiments). My experince under SuSE was similar to the poster - scanimage -L reported no supported devices, but sane-find-scanner sees it and gets the manufacturer and model info correct. luke
[sane-devel] Canon LiDE 25 scanner
Hi, On Wed, Sep 28, 2005 at 09:25:29PM +1000, Luke Kendall wrote: I read the thread CanoScan LiDE 25 that finished on Mon Jul 18 06:24:08 UTC 2005. Please also read the current thread about this scanner: http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014791.html Bye, Henning
[sane-devel] Canon LiDE 25 scanner
On 28 Sep, Stephan February wrote: I managed to get this scanner working using the development snapshot from the 27th Sept 05. http://www.sane-project.org/snapshots/ I'm still having some issues with it though. e.g. remote scanning via saned is broken for some reason, and it emits really alarming noises upon starting a scan. Thanks for the tip. I'll give it a try on the weekend and see how I go. Is there an equivalent to usbsnoop for Linux and Mac? Then I could compare the command sequences and report any differences to the list. luke
[sane-devel] Canon LiDE 25 scanner
On Wednesday 28 September 2005 16:03, Luke Kendall wrote: On 28 Sep, Stephan February wrote: I managed to get this scanner working using the development snapshot from the 27th Sept 05. http://www.sane-project.org/snapshots/ I'm still having some issues with it though. e.g. remote scanning via saned is broken for some reason, and it emits really alarming noises upon starting a scan. Thanks for the tip. I'll give it a try on the weekend and see how I go. Is there an equivalent to usbsnoop for Linux and Mac? Then I could compare the command sequences and report any differences to the list. hmmm, I thought my last mail was quite clear! I don't think it's necessary to snoop the USB traffic - it's necessary to find out the correct clock values... Ciao, Gerhard
[sane-devel] Curious about status of Lexmark X75 Linux Driver
I'm wondering if anyone in the linux community has made any efforts in the Lexmark X75 driver. I've found out that Lexmark does provide a developers kit but I've been told it uses binary libraries which Sane cannot include. http://www.lexmark.com/US/products/info/linux/download.html I am new to this driver programming gig so bare with me. -- z0manifest -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050928/f3da6f56/attachment.html From oliver.schwa...@gmx.de Wed Sep 28 18:21:14 2005 From: oliver.schwa...@gmx.de (Oliver Schwartz) Date: Wed Sep 28 18:21:45 2005 Subject: [sane-devel] Epson 3590 In-Reply-To: Pine.HPX.4.61.0509280852220.8885@xenon References: Pine.HPX.4.61.0509280852220.8885@xenon Message-ID: 200509282021.15053.oliver.schwa...@gmx.de Hi, But as the scanner is slower in preview mode than in normal scan mode at low resolution, it might be a good idea to map the preview option to some low-res option in the backend. I don't quite understand that. Are you saying that preview is slower than a normal scan at 200 DPI? (200 DPI should be the lowest resolution for the 3590.) I was under the impression that any frontend would use the lowest available resolution as the default resolution for previewing. Some background: The author of the patch for 3490 support encountered a problem with previews, i.e. the area selected in the preview window of xsane didn't match the area that finally got scanned. Apparently that problem only occurred when using certain resolutions. After setting the lowest possible resolution to 200 DPI that problem was solved, afaik. Another (although theoretical) problem with the Epson/Snapscan backend: The backend reads the path of the firmware file from the snapscan.conf file. What happens if there is more than one scanner? They'll all use the same firmware :-) I know this is a potential problem, but up to now I didn't get any complaints. If anyone needs this feature I'll think of a solution... /Oliver
[sane-devel] Canon LiDE 25 scanner
On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote: hmmm, I thought my last mail was quite clear! I don't think it's necessary to snoop the USB traffic - it's necessary to find out the correct clock values... Thanks Gerhard I'm assuming you're referring to this email: http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014600.html I'm going to try your suggestions now. Will keep the list posted. Cheers Stephan
[sane-devel] Canon LiDE 25 scanner
hello
On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
hmmm, I thought my last mail was quite clear!
I don't think it's necessary to snoop the USB traffic - it's necessary to
find out the correct clock values...
Armed with Gerard's suggestion, I have been playing around with the timings
and motor speed settings for my Canon LiDE 25.
Here is a motor/timing setting which currently works well for me, and without
the previous annoying grinding noises. It also looks like my problems with
saned are related to previously reporting timing issues when network
scanning. The latter I've confirmed by doing a saned scan via localhost.
Please comment if you see anything obviously wrong or dangerous here 'cause I
really just fiddled until I was satisfied.
snip
{ MODEL_CANON1200, 8, 51, 9,
/* Motor settings (PWM and PWM_Duty) */
/* =75dpi =100dpi =150dpi =200dpi =300dpi */
{{ 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 },
/* =400dpi =600dpi =800dpi =1200dpi =2400dpi */
{ 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }},
/* Color mode MCLK settings */
{ 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
{ 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
/* Gray mode MCLK settings */
{ 7.0, 7.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0, 6.0 },
{ 6.5, 6.5, 6.0, 6.0, 6.0, 6.0, 8.0, 12.0, 12.0, 12.0 }
},
snip
... and ...
snip
/** Canon LiDE25 */
static HWDef Hw0x04A9_0x2220 =
{
0.80, /* dMaxMotorSpeed (Max_Speed) */
0.200, /* dMaxMoveSpeed (Max_Speed) */
0.0,/* dHighSpeed */
snip
If I were to create a patch, would it be better if an entirely new section for
the LiDE25 was created e.g.?
.
.
{ MODEL_LIDE25, 8, 51, 9,
/* Motor settings (PWM and PWM_Duty) */
.
.
Cheers
Stephan
