RV: [sane-devel] Agfa Scanner
Le Lundi 12 D?cembre 2005 20:35, dmeret...@repsolypf.com a ?crit?: All/Oliver, how can I do a logic analysis? should i make it on Windows or Linux?. I would like to write a driver, but, i never did it before, if you help me, we'll do it. Thanks Hello, what you can do is to make the scanner under windows, record all the I/O flowing through parallel port, then try to understand it so that you can write a backend doing the same. This takes time, and for parallel port scanners, you are almost alone since the protocol used differ from one scanner model to another. If you still feel like doing it I can send you a custom VxD (win 98/win me only) that set hardware breakpoint on parallel port to log all in/out into a file. Since it does file access in ring 0, it has some stability issues. But it proved usefull enough to record the data (typical log is ~ 30 MB) I needed to analyse Umax 610P and 1220P protocols. Regards, Stef
[sane-devel] Progress on CanoScan 3200F
Hello, I have no such technical information that I could say if CanoScan 3000F is sufficiently close to 3200F so that the same driver would work. In fact I doubt it. But it is possible to check the case, if you could take an USB log of booting the scanner and scanning a small image, I could take a look at it and see if the engine in 3000F is same or similar. With best regards, Lauri Pirttiaho Oulu Finland Ralf Nachtsheim on Mon Dec 12 21:22:35 UTC 2005 Hello, is there a chance that the CanoScan 3000F is also working? Or is this a total diffrent model? best regards Ralf ... Luukku Plus paketilla p??set eroon tila- ja turvallisuusongelmista. Hanki Luukku Plus ja helpotat el?m??si. http://www.mtv3.fi/luukku
[sane-devel] Progress on CanoScan 3200F
Hi, On Tue, Dec 13, 2005 at 08:39:35AM +0200, Lauri Pirttiaho wrote: I have no such technical information that I could say if CanoScan 3000F is sufficiently close to 3200F so that the same driver would work. In fact According to our web page about the 3000, it uses Genesys Logic GL660+GL646 chips. Bye, Henning
[sane-devel] Minolta Dimage Scan Dual SCSI problems (repeat)
Hi, the driver support for your device is not yet complete. For some strange reason the i/o ends very early during the TEST_UNIT_READY command. Some trial'n error would be needed to find out what your scanner does respond to and where are issues. Do you have some C knowledge to comment some calls out and modify a value here and there or do you need to send a patch for any of those test? Yours, On Monday 12 December 2005 19:37, Morten Hulden wrote: Hi, tested latest sane-backend (sane-backends-2005-12-10.tar.gz) on Minolta Dimage Scan Dual I (SCSI) film scanner but was unable to get an image. The scanner is connected to a AHA154x card on Linux FC4. A UMAX S-6E flatbed scanner on the same bus works just fine. dmesg: scsi0 : Adaptec 1542 Vendor: Minolta Model: #2882 Rev: 1.10 Type: ScannerANSI SCSI revision: 02 -- Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany) http://www.exactcode.de | http://www.t2-project.org +49 (0)30 255 897 45 -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051213/6b185f4e/attachment.pgp From a...@suomi24.fi Tue Dec 13 11:41:21 2005 From: a...@suomi24.fi (amth) Date: Tue Dec 13 11:57:21 2005 Subject: Vs: [sane-devel] Progress on CanoScan 3200F Message-ID: 17019942.1134474081024.javamail.r...@eni-cpps05.sth.basefarm.net Alkuper?inen viesti L?hett?j?: lauri.pirtti...@luukku.com P?iv?m??r?: 2005/12/13 8:39 Vastaanottaja: sane-devel@lists.alioth. debian.org Aihe: [sane-devel] Progress on CanoScan 3200F Hello, I have no such technical information that I could say if CanoScan 3000F is sufficiently close to 3200F so that the same driver would work. In fact I doubt it. But it is possible to check the case, if you could take an USB log of booting the scanner and scanning a small image, I could take a look at it and see if the engine in 3000F is same or similar. I have some scan/init logs captured from the CanoScan 3000F, but unfortunately can't seem to find enought time to dev the backend for it, I could email them directly to you if you would like to have a look at them... ? And in case you happen to be stationary at hel.fi, I could even loan such unit for you (with RF shielding soldered off). :-) -- amth
RV: RV: [sane-devel] Agfa Scanner
Stef, can you send it? Diego -Mensaje original- De: sane-devel-boun...@lists.alioth.debian.org [mailto:sane-devel-boun...@lists.alioth.debian.org]En nombre de St?phane VOLTZ Enviado el: Martes, 13 de Diciembre de 2005 02:46 Para: sane-devel@lists.alioth.debian.org Asunto: Re: RV: [sane-devel] Agfa Scanner Le Lundi 12 D?cembre 2005 20:35, dmeret...@repsolypf.com a ?crit?: All/Oliver, how can I do a logic analysis? should i make it on Windows or Linux?. I would like to write a driver, but, i never did it before, if you help me, we'll do it. Thanks Hello, what you can do is to make the scanner under windows, record all the I/O flowing through parallel port, then try to understand it so that you can write a backend doing the same. This takes time, and for parallel port scanners, you are almost alone since the protocol used differ from one scanner model to another. If you still feel like doing it I can send you a custom VxD (win 98/win me only) that set hardware breakpoint on parallel port to log all in/out into a file. Since it does file access in ring 0, it has some stability issues. But it proved usefull enough to record the data (typical log is ~ 30 MB) I needed to analyse Umax 610P and 1220P protocols. Regards, Stef -- 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
[sane-devel] USB scanner slow, hopping back and forward
Hi, Thanks everybody for the reactions. Even though I haven't solved the backtracking problem yet, I now know a bit more. The exact name of the scanner I'm using is indeed Trust Direct WebScan 19200 (see http://www.trust.nl/products/product.aspx?artnr=12389). Apart from the backtracking (which might be NSLU2-related) it works correctly, so I suppose it can be added to the list of supported devices. If you need more info, feel free to ask. When I have time I will test it on a regular PC running Linux (don't have Linux installed currently, so will try a live CD). I didn't get scantime.c working yet, I will look into that later on as well (probably need to upgrade sane to a later version). Kind regards, Ruud Senden. Henning Meier-Geinitz wrote: Hi, On Fri, Dec 09, 2005 at 02:29:31PM +0100, s...@rsenden.speedlinq.nl wrote: I've got sane installed on a LinkSys NSLU2 embedded linux device running the OpenSlug Linux distribution (see http://www.nslu2-linux.org) for use with my Trust Direct WebScan 19200 scanner. Is Trust Direct WebScan 19200 the exact name of the scanner? I'm asking because a scanner with this exact name is not yet on our the list of supported devices. Are these the ids of the scanner? Bus 001 Device 005: ID 055f:021c Mustek Systems, Inc. BearPaw 1200 CU Plus The scanner basically works, but scanning is slow due to the scanner hopping backwards quite often. E.g. basically it scans one centimeter, and then hops back half a centimeter. This happens when scanning A4-width at 300dpi. The higher the resolution, the smaller the steps get. That's called backtracking and happens when the internal buffer of the scanner is filled completely. As the buffer has a size of only 16 kB (kilo not mega), this can happen quite quickly. In high resolutions, this is only one scan line. I guess every now and then some data gets lost so the scanner has to rescan a line. When doing an 'export SANE_DEBUG_GT68XX=5', I see the following for about every 13th line (at 300dpi A4 width): [gt68xx] sane_read: getting line 190 of 3531 [gt68xx] sane_read: getting line 191 of 3531 [gt68xx] sane_read: exit (line 192 of 3531, byte_count 1987 of 2563, 32768 bytes, 491520 total) [gt68xx] sane_read: start (line 192 of 3531, byte_count 1987 of 2563) [gt68xx] sane_read: getting line 192 of 3531 Does anybody know a solutions for this? Using the scanner on a regular PC running Windows, scans are smooth. I don't have this exact scanner, but with similar gt68xx devices backtracking also occurs on Windows, but it happens less often. Scanning is also smooth on the nslu2 when scanning at low resolutions (preview) or scanning only a small width. Could it be that the NSLU2 is too slow for handling the amount of data? I've also read something about different ohci-drivers, but I'm not sure whether that is applicable to my situation, and how to find/build/use another version. Hardware performance in general and the speed of USB drivers can make a difference. On the same computer I have no backtracking with the one USB host adapter and some backtracking with another one. With kernel 2.4 there were two uhci kernel drivers IIRC and one was a bit faster. As far as I know, there is only one in 2.6. Other tips that may reduce backtracking: Use a lower width. Sometimes even a few mm less help. Use 8 bit/color instead of higher depths. The gt68xx backend does its best to get the USB data as fast as possible. It uses a reader process which is forked and constantly tries to get data from the scanner. The only thing I'll try once it's implemented in libusb is using non-blocking I/O. But I'm not sure yet if that's better. For comparison here are the scan speeds I get with Mustek Bearpaw 1200 CU Plus which has the same USB ids as your scanner. They are measured with the scanimate.c tool which is in experimental SANE CVS. In the modes which result in below 20 lines/s I also get backtracking. Checking scan speed of device gt68xx:libusb:004:003 (Mustek Bearpaw 1200 CU Plus flatbed scanner) mode:Color, depth: 8, dpi: 50, KB: 246 (100%), secs: 4, KB/s: 61, lines/s: 49, mm/s: 25.0 mode:Color, depth: 8, dpi: 75, KB: 553 (100%), secs: 11, KB/s: 50, lines/s: 26, mm/s:9.1 mode:Color, depth: 8, dpi: 150, KB: 2217 (100%), secs: 10, KB/s: 221, lines/s: 59, mm/s: 10.0 mode:Color, depth: 8, dpi: 300, KB: 8867 (100%), secs: 21, KB/s: 422, lines/s: 56, mm/s:4.8 mode:Color, depth: 8, dpi: 600, KB:35471 (100%), secs: 42, KB/s: 844, lines/s: 56, mm/s:2.4 mode:Color, depth: 8, dpi: 1200, KB: 100352 ( 70%), secs: 60, KB/s: 1672, lines/s: 55, mm/s:1.2 mode:Color, depth: 12, dpi: 50, KB: 492 (100%), secs: 4, KB/s: 123, lines/s: 49, mm/s: 25.0 mode:Color, depth: 12, dpi: 75, KB: 1107 (100%), secs: 11, KB/s: 100, lines/s: 26, mm/s:
[sane-devel] Agfa Scanner
Hi, On Mon, Dec 12, 2005 at 09:22:58AM -0300, dmeret...@repsolypf.com wrote: Sorry for disturbing, but I would like to know if there are someone with experience in Agfa SnapScan 1212p (parallel). Or some place to go. I just got the following mail about this scanner. As I don't have such a device, please contact the author of this mail if there are any questions. Bye, Henning --- snip --- From: =?iso-8859-2?q?M=E9sz=E1ros_Csaba?= csab...@freemail.hu To: hmg-gu...@users.alioth.debian.org Date: Tue, 13 Dec 2005 10:51:49 +0100 Subject: agfa snapscan 1212P to be in action Hello Henning Meier-Geinitz! I was to prove Agfa SnapScan 1212P on Mandriva 2006 And scanner work! Tryout this scanner with plustek driver. To be in action. /etc/sane.d/dll.conf plustek_pp.conf /etc/sane.d/plustek_pp.conf [direct] device 0x378 device parport0 option lampOff 300 option warmup 15 option IOffOnEnd 1 /etc/sane.d/saned.conf plustek_pp.conf scanimage -L device `plustek_pp:parport0' is a Plustek 9636P+/Turbo parallel port=20 flatbed scanner Less refinement possible need. =2D-=20 Best regards: M=E9sz=E1ros Csaba csablak kukac freemail pont hu
RV: [sane-devel] Agfa Scanner
Thanks, really thanks I'll prove it Diego -Mensaje original- De: sane-devel-boun...@lists.alioth.debian.org [mailto:sane-devel-boun...@lists.alioth.debian.org]En nombre de Henning Meier-Geinitz Enviado el: Martes, 13 de Diciembre de 2005 11:51 Para: sane-devel@lists.alioth.debian.org Asunto: Re: [sane-devel] Agfa Scanner Hi, On Mon, Dec 12, 2005 at 09:22:58AM -0300, dmeret...@repsolypf.com wrote: Sorry for disturbing, but I would like to know if there are someone with experience in Agfa SnapScan 1212p (parallel). Or some place to go. I just got the following mail about this scanner. As I don't have such a device, please contact the author of this mail if there are any questions. Bye, Henning --- snip --- From: =?iso-8859-2?q?M=E9sz=E1ros_Csaba?= csab...@freemail.hu To: hmg-gu...@users.alioth.debian.org Date: Tue, 13 Dec 2005 10:51:49 +0100 Subject: agfa snapscan 1212P to be in action Hello Henning Meier-Geinitz! I was to prove Agfa SnapScan 1212P on Mandriva 2006 And scanner work! Tryout this scanner with plustek driver. To be in action. /etc/sane.d/dll.conf plustek_pp.conf /etc/sane.d/plustek_pp.conf [direct] device 0x378 device parport0 option lampOff 300 option warmup 15 option IOffOnEnd 1 /etc/sane.d/saned.conf plustek_pp.conf scanimage -L device `plustek_pp:parport0' is a Plustek 9636P+/Turbo parallel port=20 flatbed scanner Less refinement possible need. =2D-=20 Best regards: M=E9sz=E1ros Csaba csablak kukac freemail pont hu -- 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
[sane-devel] rules for scsi scanner
Hi list, I have a UMAX scanner in the SCSI bus, which is correctly detected as /dev/sg3. The .udevdb entry for this device is: P:/class/scsi_generic/sg3 N:sg3 S: scsi/host1/bus0/target5/lun0/generic M:21:3 A:0 R:0 On boot /dev/sg3 is assigned to group cdrw. I have to manually chgrp it to scanner, to allow designated users to access it. I have been fiddling for days now to set up a udev rule to automatically assign it to the correct group, but without success. I'm also slightly concerned that after any configuration change it may not come up as /dev/sg3, so would really prefer it to be called /dev/scanner. Given my miserable failure to learn udev rules, has anyone out there cracked the code? How's it done? TIA, Tony -- Tony van der Hoff | mailto:t...@vanderhoff.org Buckinghamshire, England
[sane-devel] rules for scsi scanner
On Tue, 13 Dec 2005 17:38:14 +
Tony van der Hoff li...@nospam.vanderhoff.org wrote:
Hi list,
I have a UMAX scanner in the SCSI bus, which is correctly detected as
/dev/sg3. The .udevdb entry for this device is:
P:/class/scsi_generic/sg3
N:sg3
S: scsi/host1/bus0/target5/lun0/generic
M:21:3
A:0
R:0
On boot /dev/sg3 is assigned to group cdrw. I have to manually chgrp it to
scanner, to allow designated users to access it.
I have been fiddling for days now to set up a udev rule to automatically
assign it to the correct group, but without success. I'm also slightly
concerned that after any configuration change it may not come up as
/dev/sg3, so would really prefer it to be called /dev/scanner.
Given my miserable failure to learn udev rules, has anyone out there cracked
the code? How's it done?
TIA, Tony
--
Tony van der Hoff | mailto:t...@vanderhoff.org
Hi Tony,
here is what do to have my scanner working. It is an Umax Astra 220 linked via
SCSI on a Tekram 395 (no bios). System is a gentoo with kernel 2.6.12 on an
amd64. As I use the scanner only rarely (usually scanner is switched off at
boot) I do/did the following:
- during boot I load already the dc395x kernel module
- I have an udev rule (filename: 10-udev-rules) to make sure it is loaded
before the standard udev rules:
BUS==scsi, SYSFS{model}==Astra 2200 , NAME=scanner, GROUP=scanner
The rules creates a device called /dev/scanner/ with group 'scanner'. Users
belong to group scanner. Device is only created after switching on and
accessing the scanner.
- I put a kind of wrapper script around xsane: I start xsane with the command
'xsane-start':
#!/bin/sh
if [ `grep -c UMAX /proc/scsi/scsi` = 0 ] ; then
sudo /usr/local/bin/add_to_scsi
fi
exec xsane
The script 'add_to_scsi' insert the proper line to /proc/scsi/scsi so that
xsane detect the scanner:
#!/bin/sh
channel=`dmesg | grep 395 | grep scsi | tail -n 1 | cut -c 5`
/bin/echo scsi add-single-device $channel 0 1 0 /proc/scsi/scsi
Finally, I edited '/etc/sudoers' to get the sudo command above working without
password.
After switching the scanner on, it takes a little moment for scanner detection,
but it works fine
HTH and good luck,
Klaus
