[sane-devel] Re: strange problems LIDE30
Gerhard Jaeger wrote: > Hi, > > let's try and shed some light on the plustek-backend and the LiDE30 > scanner: > > - The scanner is a USB1.1 device, as the used chipset, a LM9833 is > only capable to do USB1.1. > - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit > where did you get the "full-color" from? You either scan with the > "color" option, then it's 8bit per channel or you scan with the > "color 42/48" option, then it's 16bit. > - The LiDE30 is able to scan @1200dpi in X direction, because it's the > native resolution of the sensor, and the motor is able to do 2400dpi > steps. Therefore X direction information is doubled. > - The backend does some calibration @ the start of each scan, this > might take a while. This time has also been increased from 1.0.13 up > to 1.0.14 This is necessary to avoid stripes. To reduce the time, > it's now possible to let the backend save the information of the > coarse calibration (option cacheCalData in the config file, or > --calibration-cache=yes for scanimage). This is working for the > latest CVs snapshots. > > Please note, all backend before 1.0.14 are not recommendend for use > with the LiDE devices, as the calibration does not work correctly! > Also using kernel 2.6.x (x < 8) might cause problems with the USB. > > Also note, that full-size scanning using the 2400dpi might not work. > At least I've never tested, because I've not that much memory in my > boxes. 2400dpi also create that much data, that a USB1.1 device > really needs some time to send the data to the box. Here the > bandwidth is the limiting factor. We might can tweak the motor > settings for the 2400dpi to avoid backtracking. > > Before continuing, I suggest to use the latest CVS snapshots, a > kernel > 2.6.7 and the latests libusb. The next step will be to check > if you really need to do scans @2400dpi, at least full-size ones. > > Ciao, > Gerhard Very informative Thanks much No, I at least have no real use for scanning full sheets in color at 2400dpi. I only did it for the purpose of testing the system, it's the worst case combination of all offered options. I never had a problem with "normal" jobs. I've done a few partial pages at 600dpi color, many full pages at 100-600 gray & b&w Never had a problem. Even though I'm just under your recommendation on several fronts. These are all what's currently available from suse pre-built and Yast-installable: bwlin1:~ # uname -a Linux bwlin1 2.6.5-7.108-smp #1 SMP Wed Aug 25 13:34:40 UTC 2004 i686 i686 i386 GNU/Linux bwlin1:~ # scanimage --version scanimage (sane-backends) 1.0.13; backend version 1.0.13 bwlin1:~ # ls /usr/lib/*usb* /usr/lib/libusb-0.1.so.4 /usr/lib/libusb.a /usr/lib/libusb.so /usr/lib/libusb-0.1.so.4.4.0 /usr/lib/libusb.la bwlin1:~ # Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] Re: strange problems LIDE30
Brian K. White wrote: >> It's only at about 10 or 15% progress after 20 minutes so I'll send > > still cranking away > just over 50% > > Now I wish I'd used the time command so I can see just how long this > will take even if I go out to eat and it finishes while I'm gone. > Then we could look at the total data and total time and see if it > transferred at full usb 1.1 speed. Seems like it should be able to go a > lot faster than this > with 12 megabit available. Just crashed, 8:07 pm I sent my original mail at 5:07 pm I probably started that email (and the xsane process) at about 4:30 pm It was xsane in kde so I don't have any error message. It just winked out. It was somewhere near 90% but I don't think it was done. It's speed was constant the whole time and I had looked at it a few minutes before and it was still just under 90% and I don't think it was nearly enough time for it to have gone the rest of the way, maybe only another 1 or 2 %. So I will tentatively say it failed while in progress, not after it was done scanning and tried to do whatever it does next. I was scanning "to viewer". This box is not overclocked at all and has not exhibited any other signs of flaky hardware so I don't suspect ram/cpu/etc It's running 2 seti@home processes 24/7 and I do a fair/medium amount of work on it, lots of rxvt & ssh to other boxes, some gimp, lots of konquerer, xmms is playing some 128 kbit shoutcast stream almost 24/7, I have a fairly large java app that runs 24/7 that interfaces with our voip phone system, I play the occasional dvd. None of these has yet surprised me. I have not used the adaptec usb 2.0 pci card for very much at all although the optical mouse is plugged in to it and the scanner, and I have used the scanner and xsane without incident several times before but only at 300dpi-gray and 200dpi-bw. I wasn't touching the machine at the time. xmms was not playing, the mouse was not moving, the screensaver was up. (I'm working on my laptop but I'm at the same desk) At least I can go eat now and know I won't miss anything :) I'm not above suspecting the usb card. I have not been able to get my unpowered usb2.0 2.5" hard drive to work on it. Sorry, I can't define "not work" since I gave up a few months ago and by now I don't recall what I tried and what I saw because it was never actually important to me. But that could just as easily be the enclosure or drive and not the usb card. The drive & enclosure works on my laptop, but it does give windows delayed write failed error messages once in a while if it's left plugged in and idle a long time. *shrug* I could do some transfers to a 512 meg sd card in a jump drive trio and see if that is reliable. sd cards are normally only about 1 megabit, but I have a 10/9 mb read/write card. that should be an ok test. I'll just to simple large monolithic transfers so as to minimize the number of write cycles I use up. I'll dd 500 megs directly to it a few times, and same thing to read. I'll start with a given file, dd it on, dd it back to a new file and cmp the files to verify that the writes & reads didn't have a silent error that corrupted the data. If that works I'll call the usb card stable at least in usb1 mode. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] Re: strange problems LIDE30
> It's only at about 10 or 15% progress after 20 minutes so I'll send still cranking away just over 50% Now I wish I'd used the time command so I can see just how long this will take even if I go out to eat and it finishes while I'm gone. Then we could look at the total data and total time and see if it transferred at full usb 1.1 speed. Seems like it should be able to go a lot faster than this with 12 megabit available. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] Re: strange problems LIDE30
Chris McKeever wrote: > some more tests get me some new results. > > 1 - I have noticed that with 3 different USB 2.0 cards, that the > scanner will not register itself as a USB 2.0 device, it only > registers as a 1.1 (CD Wiriters register as 2.0, so I know that the > card and the kernel are recognizing it properly) > > 2 - I moved the scanner to the built-in USB 1.1 port, and I was able > to finish a scan at 300 DPI and 600 DPI (although it takes quite some > time) > 3 > > 3 - 1200 DPI still hangs, and letting it sit, I get: error during > read: error during device I/O. > > any suggestions? > > thanks > > > > > On Wed, 6 Oct 2004 13:22:31 -0500, Chris McKeever > wrote: >> I have been wrestling with this for a while now, and not turning up >> much through searching the web. I have installed SANE >> sane-backends-1.0.14 and have a CANON lide30 scanner. >> At low resolutions it will process fine. If I go to 300 is fails at >> about 75% and anyhting higher wont even start. >> >> I had it working with an LIDE20 - until that unit crapped out - the >> optic bar would just pin itself to the edge and grind. >> >> I am connecting to the SANE backend via XSANE from a remote linux box >> as well as a remote windows box - very similar results (the >> connection itself works, just scanning isnt working well) >> >> Any suggestions? >> >> thanks LiDE 30 _IS_ only a usb 1.1 device. There are sloppily written advertisements on various shopping sites that list it as usb2.0 but in truth, the lide30 is usb1.1 Later lide50 is usb2.0 go to the canon site instead of guessing or trusting others (hey, including me :) I have a 30 and a 2.0 card and went through the same motions you are and finally I did what I should have done first and consulted the only authoritative source and all mysteries were solved. I never tried to scan at 1200 though, trying now... Working... It's going but incredibly slowly at 2400 full color (what bit depth is "full color"?) The manufacturer says that it does 1200x2400 optically, but xsane only offers a listbox that says a single value from 0 to 2400, no XXXxYYY choices, so I picked 2400 just to go for a worst case scenario but I have no idea what it's actually going to do. A lie, only actualy produce 1200x1200? a distorted image? silently double every pixel in one direction? silently double every pixel in both directions? or maybe the scanner will do the doubling in one direction in firmware and present sane with 2400x2400 data? It's only at about 10 or 15% progress after 20 minutes so I'll send another post when it's done, or when it crashes. This box has a gig of ram so hopefully it's enough for this worst-case scenario if sane doesn't open a file and work with smaller chunks in ram. This is a dual 1gig p3 too. That might be relevant by making it more likely that there is always a cpu available to service the usb interrups? Or rather, that the one cpu that seems to be the only one that even sees interrupts, is more likely to be able to keep up. It's basically a straight suse personal 9.1 with yast configured to use ftp.ale.org Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] discussion: Future of SANE-project
m. allan noah wrote: > the project is composed of many individuals, each with different > goals/interests. The part of the website you quoted does not suggest > to me that we are gunning for TWAIN, just that SANE is a better > design. > > however, history is FULL of better designs that did not make it for > cost/political reasons. technical superiority != market penetration. > > TWAIN is well established, well supported, and represents 90% of the > existing install-base. This is not likely to change even if we all > dropped our attempts to maintain backends and focussed entirely on > browbeating the mfgs/oems. and since this is something that most of > us are not interested in, we as individuals do not tend to do it. > > if you dont mind my asking, explain your interest in sane. why does it > matter to you if it supplants TWAIN? Twain does exist on linux btw. I saw this company demonstrating it at an AIIM convention in nyc a couple years ago. http://www.jflinc.com/ Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
OT: good scanners (was: Re: [sane-devel] Fujitsu Scan Partner 620c works)
Garrick Sitongia wrote: > I've read suggestions that although the Fujitsu Scan Partner 620c > should work, it is untested. I took a chance and bought one on Ebay, > and it works great under SANE. I've been using Xsane to try it out > and all the imaging features seem to work. Also the Automatic > Document Feeder as well as Flatbed scanning works. > > The only complaint so far is that for a Color scan there is a the 15 > second lag before scanning begins, then scanning takes 15 seconds at > 300dpi. Excellent work, thanks SANE. > > Garrick Sitongia > > FYI, the scanner was $130 on Ebay. Holy cow. That's the scanner we spec for all our customers if they get the scanning add-on to our software. We pay over $1000 each! Recently we got ourselves a 15c for in-house use and testing/development and it seems to be just as good. and that is still over $500. It looks the same and works the same. I can only assume that there are $500 worth of inferiority in there _somewhere_. Another good one is the canon DR3080c. One of our customers uses those and it sure is a neat tidy little unit, fast, quiet, scans in duplex, little desktop space. _Better_ be good at $3000 each. One thing to note however, to load the canon, you put a stack of papers in the input tray and the scanner sort of grabs the whole stack. A that point you can either let it finish the job, or abort the job, but what you cannot do is add more sheets to the job while it is running. This would cause problems where one "document" might be more sheets than the input hopper holds and the application expects all sheets in a document to be part of one twain session. The fujitsu and others like it allow this with no problem, you can keep feeding the scanner continuously as long as you want. It's because the canon draws papers from the top of the stack, requiring an elevator mechanism to push the stack up against the feeder to scan and release it allow loading. Whereas the fujitsu draws from the bottom and there is just a simple rubber pad that holds back the rest of the stack which is not perturbed by adding or removing papers to/from the top while the feeder is taking from the bottom. (since this is sane-devel, I guess I should at least mention that I have no idea if this one is supported in sane) Everyone always complains how big the fujitsu is but anyone who does is overlooking one important feature. The large ungainly size is mostly due to the fact that the paper feeder ejects out the side, requiring even more desktop space than the base unit itself. That is not by accident though. It's like that so that the paper path is practically a straight line with only one roller and no turns and no obstructions. Thus it's very difficult to jam this thing and it almost never "eats" a document. even really thin flimsy and wrinkled carbonless sheets and thigs go through because the paper is not required to have any stiffness of it's own. In our (well, our customers') case this happens to be a big deal because the documents being scanned have been in the tender care of truck drivers for several days and often started out as flimsy sheets to begin with. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] CanoScan LIDE 20 on FreeBSD 5.1 Release
Gerhard Jaeger wrote: > Hi, > > it seems, that this is a FreeBSD related problem, as the backend > works fine on x86-Linux & libusb! > A few days ago we also tried to make a CanoScan 660 work using > FreeBSD and > we had the same problems there. I'Ve installed FreeBSD 4.9 on my box > now, but had not the chance to check it so far... I set up a N670U on freebsd a few months ago on freebsd 4.6 and maintained it through 4.8. (same family as lide20, lide30, and several other N6xxx) I never figured out how to use libusb, but I did figure out how to use uscanner. uscanner requires manually editing a couple files in the kernel source which contain lists of scanner model numbers and identifier strings. I don't remember the exact details now, and I'm a couple thousand miles away from that machine, which isn't running so I can't ssh in to it either. But I figured it out just by poking around in the kernel source looking for uscanner, and there is a file or two (both in the same directory) the stings you need to add/edit are pretty obvious just by looking at all the other ones that are already in there. In the directory I'm talking about, note that there are 3 or 4 files that have lists of model names and matching identifier strings. really you only need to edit one file, or possibly two, the others are generated during the build process from the one or two. There is a perl or awk script in there that tells the story. I forgot where I got the unique identifier from the scanner to add to the kernel source. Maybe the kernel boot messages in syslog, maybe sane_find_scanner, maybe scanimage -L or some other sane command with a debugging option. Again, although I don't recall the details, I can say I figured it out just by blundering around, so presumably it can't be that hard and you could do the same if no one gives you better help than "it works on linux" or "heres how you do it:" and then proceeds to give you a bunch of linux instructions. when the uscanner device driver files are edited to add recognition of this scanner, then you build the kernel, and *only then*, the new kernel will create a /dev/uscanner0 either whenever you plug in the device, or maybe only if the device is plugged in when the kernel boots. You dont create /dev/uscanner0 yourself either btw, either the kernel makes it for you, or just go back and look again at what you edited and maybe build a new kernel. (of course you need "uscanner" in the kernel config file and whatever else uscanner relies upon, like usb uhci ohci or whatever... once you have a /dev/uscanner0 you put that in the plustek config file I put /dev/uscanner0 explicitly, but really /dev/uscanner[0-9] or something is more correct, because the "0" is dynamically assigned when the device is detected, and might not always be "0". but I didn't have any other scanners and so I knew it would always be "0" If there is a searcheable archive of this list somewhere, I did describe this all in more explicit detail, including that actual commands executed and files edited, and how/where they were edited. look back at least 6 months, maybe more. good luck. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] MacOS X 10.2.6 CanoScan N650U
- Original Message - From: "Bill Clyde" To: Sent: Sunday, September 28, 2003 9:10 AM Subject: [sane-devel] MacOS X 10.2.6 CanoScan N650U > I am trying to get my N650U to work through the USB port. scanimage -L > does not see any scanners. > > sane-find-scanner outputs: > found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan]) at > libusb:-07:006. > > I checked through the list archive and found $ SANE_DEBUG_SANEI_USB=5 > scanimage -L. > > This outputs: > [sanei_debug] Setting debug level of sanei_usb to 5. > usb_set_debug: Setting debugging level to 255 (on) > usb_os_find_busses: Found -07 > usb_os_find_busses: Found -08 > usb_os_find_devices: Found 006 on -07 > usb_os_find_devices: Found 005 on -07 > usb_os_find_devices: Found 004 on -07 > usb_os_find_devices: Found 003 on -07 > usb_os_find_devices: Found 002 on -07 > usb_os_find_devices: Found 001 on -07 > usb_os_open: 05ac:8005 > USB error: could not open device > usb_os_open: 050f:0003 > USB error: could not open device > usb_os_open: 04b8:0005 > usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000 > usb_control_msg: 128 6 512 0 0x110260 32 1000 > usb_os_close: 04b8:0005 > usb_os_open: 045e:000b > usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000 > usb_control_msg: 128 6 512 0 0x110260 34 1000 > skipped 1 class/vendor specific interface descriptors > usb_os_close: 045e:000b > usb_os_open: 046d:c00e > usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000 > usb_control_msg: 128 6 512 0 0x111fc0 34 1000 > skipped 1 class/vendor specific interface descriptors > usb_os_close: 046d:c00e > usb_os_open: 04a9:2206 > usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000 > usb_control_msg: 128 6 512 0 0x112000 39 1000 > usb_os_close: 04a9:2206 > usb_os_find_devices: Found 002 on -08 > usb_os_find_devices: Found 001 on -08 > usb_os_open: 05ac:8005 > USB error: could not open device > usb_os_open: 05ac:1101 > usb_control_msg: 128 6 512 0 0xbfffebd8 8 1000 > usb_control_msg: 128 6 512 0 0x117570 239 1000 > skipped 4 class/vendor specific interface descriptors > skipped 2 class/vendor specific interface descriptors > skipping descriptor 0x25 > skipped 1 class/vendor specific endpoint descriptors > skipped 2 class/vendor specific interface descriptors > skipping descriptor 0x25 > skipped 1 class/vendor specific endpoint descriptors > skipped 2 class/vendor specific interface descriptors > skipping descriptor 0x25 > skipped 1 class/vendor specific endpoint descriptors > skipped 1 class/vendor specific interface descriptors > usb_os_close: 05ac:1101 > [sanei_usb] sanei_usb_init: found libusb device (0x04a9/0x2206) > interface 0 at libusb:-07:006 > [sanei_usb] sanei_usb_init: device 0x046d/0xc00e, interface 0 doesn't > look like a scanner (0/3) > [sanei_usb] sanei_usb_init: device 0x046d/0xc00e: no suitable interfaces > [sanei_usb] sanei_usb_init: device 0x045e/0x000b, interface 0 doesn't > look like a scanner (0/3) > ... > > I also tried this: > > $ SANE_DEBUG_DLL=5 scanimage -L > [sanei_debug] Setting debug level of dll to 5. > [dll] sane_init: SANE dll backend version 1.0.10 from sane-backends > 1.0.12 > [dll] sane_init: reading dll.conf > [dll] add_backend: adding backend `plustek' > [dll] sane_get_devices > [dll] load: searching backend `plustek' in `/sw/lib/sane' > [dll] load: trying to load `/sw/lib/sane/libsane-plustek.1.so' > [dll] load: dlopen()ing `/sw/lib/sane/libsane-plustek.1.so' > [dll] init: initializing backend `plustek' > [dll] init: backend `plustek' is version 1.0.0 > [dll] sane_get_devices: found 0 devices > > 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). > [dll] sane_exit: exiting > [dll] sane_exit: calling backend `plustek's exit function > [dll] sane_exit: finished > > The plustek.conf file contains > [usb] 0x04A9 0x2206 > device auto > > I also tried specifying the device in the config file and on the > command line but to no avail. > > Let me know if there is anything else that I can look at to help > resolve this. > > Thanks, > Bill well snail friggies I had this same scanner working, via usb, on my freebsd box, whos hard drive wigged out and no longer boots. I think the key ingredient in my case was adding recognition for the scanner to a couple kernel files so that the kernel reconizes it and creates a /dev/uscanner0 instead of using the generic usb access. I think it would have worke
[sane-devel] TWAIN on SANE
Stephen Williams wrote: > pri...@newgen.co.in said: > >>I have an interface for scanner on TWAIN protocol for windows. Now i >>need to port it on the LINUX. > > > The TWAIN working group occasionally wonders about porting TWAIN to > Linux, or defining a Linux variant of TWAIN. The former is iffy due > to integration with the Windows message pump, and the latter comes > with a lack of motivation from the involved parties. > > There is a SaneTWAIN datasource for Windows that allows Windows TWAIN > apps access scanners over the network via SANE and the scanner's SANE > driver, but I've not heard of any Linux version of that. If to write > such a thing, the TWG might be interested. I saw TWAIN on Linux at the AIIM show the year before this last one. These people may know something about it: http://www.jflinc.com/ Since the booth where I saw this had a guy from this company working it, I later went on to buy a copy of their twain library for a windows/unix/scanning project I was working on(1). --- (1) text-based unix database app (written in filePro) sends a escape-sequence to either FacetWin or AnzioLite/AnzioWin terminal emulators to run a command. command is like: "aljex_scan P:/CompanyX/DocTypeY/DocNumZ-PageN.tif" aka "aljex_scan P:/united/invc/129003-4.tif" aljex_scan is hard-coded to scan a single sheet at fax-quality letter-size and output the file given on the command-line. P: is on the server thanks to FacetWin or Samba. To view the scanned docs I made a pair of pretty simple cgi scripts. one shows a table of thumbnails of all images found with requested doctype & docnumber, click on a thumbnail and the other cgi script displays the image in a single img tage with witdh=100% so the "print" button on the web browser prints a full proper-size copy regardless what the window looks like. the unix app sends the "run-program" sequence to the terminal emulator, with an argument of: "start http://server/cgi-bin/viewthm?encryptedjunk where the cgi decrypts the query string and gets basically a path to the images minus the page numbers. this cgi generates a table of thumbnails and links where the link is the another cgi script and encrypted query string to view a particular page in full-size. (both scripts are very light-weight, just ksh. no perl, but do use sort and ls) The documents are given path & filenames based on the file & they are using within the app. The image viewer is just their web browser (images are converted to png, and png thumbnails generated on the server immediately after being saved). The scanner settings are all hard-coded in the little VB app I put on PC's that have scanners. Voila. plain old unix app now has scanned documents, and users don't have to learn 10 minutes of new material to use it, since the "document management" is just piggybacked off the existing app that they already know how to navigate. Merely now some of their screens have a new hot-key & pull-down menu to "scan/view/fax/email/print/administer". -- Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] sane and scanDoX fujitsu drivers
Peter Santoro wrote: > I'm considering on buying a fujitsu scanparter scanner ( 93GX, fi-4220C, > 15c, or 620c), but I want to be certain that I purchase one that is well > supported by sane (or perhaps scanDoX). > > The folks at scanDoX indicate that fujitsu 15c/620c scanparter scanners > are supported in sane via sp15c driver: > http://www.mu-tec.de/scandox/sdx/features_supported-scanners.html > > The sane website appears to contain conflicting information: > ScanPartner 15C: driver is sane-avision, status is untested > SP15C: driver is sane-sp15c, status is beta > > Am I just misreading something here? Which information is correct? > > > Thank you for your assistance, > > Peter I can't comment on sane support, but I can say that in general the 620c is a very good scanner. My company sells an add-on which I wrote for our main application that basically adds document scanning to any/every screen or file in the database. several customers have been using the add-on for over a year now quite heavily. Before we installed the first guy, I looked at a lot of scanners at a big document imaging convention in NYC (the aiim show) and settled on the 620c. we continued to recommend that model to everyone and mostly that's what they always get (one guy who got other models just got higher-end models in the same family since he needed more speed and they have been excellent as well), and so I have by now seen many of these units in heavy, all day every day use, usually at least two units per site. And they have turned out to be real workhorses. The feeder happily sucks in the worst crumpled, torn, tissue-thin specimens without snagging, and in the rare occasion it snags, the access to free the paper path is the simplest and quickest I've seen. My most idiotic users have not even had a problem with it. The one part that they (fujitsu) know will eventually wear out, a rubber pad that holds back all but the bottom sheet in the feeder input hopper, they supply you with an extra, and my very first user is just over 2 years in use now, has still not needed that part. There is one problem though. The bulb in the scanner does not shut off as far as I have noticed, so you should really turn the scanner off at night so as not to waste 1/2 of the useable hours of life, but, if you don't also turn off your computer, then most computers have been unable to find the scanner once you turn it off even after you turn it back on. You have to have the scanner on before the computer is turned on. On some sites the scanner is used heavily only for a couple hours late in the day, this means they have to either leave the scanner on all the time, burning up 22 hours of bulb for every 2 that are actually used, or they have to power-cycle their pc just after turning on the scanner before using it for a couple hours. by comparison, another guy decided to go with canon 5080's (5080c?) well they are pretty, and they are snappy, and they can scan in duplex, and they are wy more convenient on the desk, but the driver was quite a little puzzle and required non-trivial manual adjusting (forcing the driver to choose the correct one of two possible files at every scan by deleting the the file that doesn't match your particular model) and the hardware is less than relable (chokes on imperfect specimens a lot easier, very easily in fact) less than always true (it tends to grab the sheets and feed them through at a slight tilt and it gets worse with time, better with cleaning and scuffing some of the rollers), less than simple as far as the mechanics and operation of the in & out trays, rollers, paper-path access, and costs about 4x what the sp620c does. All in all, a scanner like that is a mild investment, and I thought you'd appreciate some good hard anecdotal in the field track record. And these are all trucking companies my customers. The users are reasonably careful people being clerical/accounting types, but the papers come from truckers, who do not hand in nice pressed, ironed & starched flat papers :) and the environments are usually very dusty, being attached to big warehouses and garages and truck yards. In the end, my ideal goal was to find a good enough scanner that after I install it, I never get support calls to keep it going. This has turned out to be the case. The thing is built like a good old xerox machine or ibm keyboard :) It is an art form though, trying to put the thing on the desk or close enough to it that the scsi cable reaches, and the user can reach both the in & out trays without straining, and still leave them any desk space left over. :) -- Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] saned
Is there a windows saned client? I would love to just leave my scanner plugged into my freebsd box and once in a while scan something from my windows box or my laptop without moving it. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] well, I'm a retrurning user of sane... got some questions.
technomage wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > ok, > its been a very long time since I have been a part of this group. > I'm glad to be back. > > some issues have arisin and I'd like a little help troubleshooting them. > > it seems I can get sane working fine (using the Mustek Paragon II CD backend) > but I can't get saned working. > > I placed a saned file under the xinet.d folder complete with the details from > the saned man page. I cannot report any success in it allowing hosts from > other boxes in my lan to connect. I have restarted xinetd to make sure things > were go (chkconfig reports saned is on but ps aex |grep saned reports that > there is no process under that name). > > if I manually run saned, I can connect fine until I quite the application on > the remote machine (then saned quits). I'd like it to remain in memory and > offer the service. anything I am missing? > > Technomage the whole point of inetd (and later xinetd) is that the services themselves do not run all the time, only the one service, inetd (or xinetd) runs, listening on all the ports of all the services that have been configured in it. When something tries to open a port it recognizes, it starts up the appropriate service to service that one request and then the service goes away again. what tcp port does saned work on? is that port listed in /etc/services? .. I just looked at man saned and see it's port 6566, so, does /etc/services have a line like this? sane 6566/tcp run netstat -a |less The top of this output shows all the ports that your box is listening on, and all the ports that currently have active connections. Is the saned port listed in there as "... *.* ... LISTEN" did you try running "saned -d" manually? this runs it in a manner where saned itself does stay running, listening on the saned tcp port and debug info will show on the session where you ran it until you ctrl-c in that session. This will probably fail if saned is in fact correctly configured in xinetd because xinetd is already "occupying" the saned port and no other program can listen on that port until xinetd gives it up. you can turn off xinetd, or temporarily disable the saned config and restart xinetd. Then try saned -d (then try to connect) what are the contents of saned.conf? are the names/ip's listed in there really how your box resolves the various machines that try to connect? try putting a single "+" on a line by itself in saned.conf, since (you didn't say but I will presume) this is a linux box and probably you are running tcpd to block unsafe hosts from touching your box anyway. (/etc/hosts.allow /etc/hosts.deny) did you copy the sample xinetd file from the saned man page verbatim? If so, is there any such user and group as "saned" or did you change those to show names that exist on your box? -- Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] freebsd usb
Henning Meier-Geinitz wrote: > Hi, > > On Wed, May 21, 2003 at 08:43:15AM -0400, Brian K. White wrote: >> after utterly _failing_ to figure out the government secret as to >> what exactly is the correct syntax for device "libusb:..." in >> plustek.conf (why can't this be documented somewhere?, >> sane-find-scanner reported "libusb:/dev/usb0:/dev/ugen0" neither >> that nor any of several pointless guesses caused scanimage -L to >> work) > > The syntax of the "device file" is the one that libusb uses plus > "libusb:" at the beginning. It's the one that's printed with > sane-find-scanner. It's operating-system-dependant. For Linux and > FreeBSD there is some docu in man sane-usb. > > It shouldn't be ever necessary to specify libusb:a:b in a config file. > That just doesn't make sense because a and b may vary depending on > when you plug in your scanner and which other devices you have. > > libusb devices are autodetected. Well, they should be. I've no idea > what went wrong in your case. If you want to debug that problem, > set SANE_DEBUG_PLUSTEK=255 and SANE_DEBUG_SANEI_USB=255 and run > scanimage -L. There should only be a [usb] line, no device line in > plustek.conf. OK i'll try that. that's an example of what's not documented :) I'll actually have to comment out my kernel source changes and build a new kernel to test this because now the built-in uscanner device finds the scanner and sane-find-scanner no longer says libusb. But I'm willing to do that to further the cause of clear and complete documentation. >> Here's my question: >> whenever I try to run scanimage or xscanimage, it takes a very long >> time before the program actually does anything, > > Try to find out if that long time apsses in the plustek backend. Does > it also happen if you comment out verything but "plustek" in > dll.conf? If no, please try to find out which backend causes this > problem. Setting SANE_DEBUG_DLL=255 may also help. I'll try that. Thanks. >> and in the mean time I get a lot of this: >> >> umass0: BBB reset failed, TIMEOUT >> umass0: BBB bulk-in clear stall failed, TIMEOUT >> umass0: BBB bulk-out clear stall failed, TIMEOUT >> umass0: BBB reset failed, TIMEOUT >> umass0: BBB bulk-in clear stall failed, TIMEOUT >> umass0: BBB bulk-out clear stall failed, TIMEOUT > > That's the driver for USB mass storgae support? yeah > Do you still have a "device libusb:..." line in plustek.conf? Maybe that line refers to > on of your other usb devices. in plustek.conf I commented out all but one device line and it now says /dev/uscanner0 because that is what sane-find-scanner says since patching my kernel. > Another possibility would be that the > autodetection of the USB devices triggers that timeout for some > reason. A debug log with the above mentioned two variables set may > show the source of the problem. I'll try all this stuff tonight and report back. Thanks a lot. Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] freebsd usb
Hi, I have a CanoScan N670U and freebsd 4.8-stable and sane-backends 1.0.11 after utterly _failing_ to figure out the government secret as to what exactly is the correct syntax for device "libusb:..." in plustek.conf (why can't this be documented somewhere?, sane-find-scanner reported "libusb:/dev/usb0:/dev/ugen0" neither that nor any of several pointless guesses caused scanimage -L to work) I gave up and edited uscanner.c and usbdevs to add my CanoScan N670U to the kernel so that when I plug it in, it now shows up on /dev/uscanner0 instead of /dev/ugen0 I then got scanimage -L to recognize the scanner by putting this in plustek.conf: [usb] 0x04A9 0x220D device /dev/uscanner0 bash-2.05a# scanimage -L device `plustek:/dev/uscanner0' is a Canon N670U/N676U/LiDE20 USB flatbed scanner Great! At this point the scanner works in xscanimage. I can scan and preview and set image quality settings. Ye-ha and thank you sane developers :) Here's my question: whenever I try to run scanimage or xscanimage, it takes a very long time before the program actually does anything, and in the mean time I get a lot of this: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, TIMEOUT umass0: BBB bulk-out clear stall failed, TIMEOUT umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, TIMEOUT umass0: BBB bulk-out clear stall failed, TIMEOUT How/where do I go about figuriung out what's wrong and how to fix it? I would rather not have to choose between being able to scan or being able to use my zip drive & cf/mmc readers. (meaning I'd rather not fix the scanner by removing umass from the kernel) Any ideas? Thanks. -- Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[>+++[>+>+++<<-]<-]>>+.>.+.+++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
