gmane.comp.graphics.scanning.sane.devel

scanimage and option titles

Jeffrey Ratcliffe — 2013-05-18T21:18:48

GUIs often either use the SANE API directly, or control a scanner by
wrapping scanimage.

Generally, there is no advantage in using scanimage, as it is slower,
but in certain situations, for instance remote access, it is not
possible to use the SANE API directly. Also, debugging a backend
problem is much easier with scanimage.

The major visual difference for the user in these two interface
methods, is that, apart from groups, scanimage does not expose the
option titles. As the option names are not translated, a GUI therefore
cannot use the sane-backend translations and has to use its own.

This could all be avoided if scanimage were to expose the option
titles. The translations from sane-backends could be used, and the two
interface methods would look the same.

I therefore propose an additional option for scanimage that exposes
the option title in the --help output.

Is a patch for scanimage along these lines likely to be accepted?

Regards,

Jeff

iX500 multiple pages

dfriberg23 — 2013-05-18T02:38:03

I got my iX500 to work with the latest git snapshot of sane-backend. 
However, when I load 3 papers into the scanner, and run this:

SANE_DEBUG_FUJITSU=15 scanimage -d fujitsu --format=tiff --resolution=300 >
foo.tif 2> log.txt

The first 2 pages get sucked through, and about a fourth of the third page,
but only the first page is written to foo.tif.  Is there a way to control
the number of pages it brings through, or do we not know how to do that yet?



--
View this message in context: http://sane.10972.n7.nabble.com/iX500-multiple-pages-tp17570.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

canon MX892 scan test OK

Tim — 2013-05-16T20:25:57

Canon MX892 (US model), works

tested:
150/300/600 dpi scans of an IT8 camera target using xsane front end over 
802.11g, auto discovery

not tested:
USB / Ethernet

backend:
git clone as of today (16 May), no changes.

related software:
xsane 0.998
cnijfilter-mx890series-3.70-1.x86_64 from canon-asia
cnijfilter-common-3.70-1.x86_64 from canon-asia
cups-bjnp-1.2.1-x86_64-1_SBo from slackbuilds.org
2.6.37.6c (tim< at >hp_lap) (gcc version 4.5.2 (GCC) ) #8 SMP
Slackware 13.37, x86_64

environment:
PIXMA_EXPERIMENT=1
SANE_DEBUG_PIXMA=11

scanimage -L:

Let me know if different information would be useful.

Cheers,

start

Tiago Zaniquelli — 2013-05-16T20:08:43

Hello,

I am begining with the development the scanner driver.

I have seen these files and directories:


/etc/sane.d/dll.conf

/usr/lib/sane/


How does Sane  work ?


Exist a flowchar of working?


I haven´t found in the documentation.


Best Regards,


Tiago Zaniquelli

HP OfficeJet 6700 ADF Problems

Alex — 2013-05-16T18:18:05

I apologize if this is the wrong place to ask, but I have run into a
couple of problems scanning from my HP OfficeJet 6700's ADF. The flatbed
scanner works perfectly and as expected, though. I'm running x86_64
Gentoo using sane-backends 1.0.23 and hplip 3.13.4 built with scanner
support.

I'm not really entirely sure what's going on with it, but when I use
scanimage like this:

scanimage -d 'hpaio:/usb/Officejet_6700?serial=[SERIAL]' --format=tiff
-p -v--source ADF --mode Color --resolution 300 -x 215.9 -y 279 -b
--batch-start=1 --batch-count=4

it feeds the documents and scans them each to out1.tif, out2.tif,
out3.tif, out4.tif just as expected. The progress percentage, however,
stops at some percentage before it moves on to the next page or
finishes. This percentage varies, and depends a bit on the -y argument.
If I leave it at the default (which I think is A4 sized), it'll stop at
about 75% for each page. If I have it at 279, for US letter sized, it'll
stop around 90%.

The files open fine in EOG (Eye of GNOME), but everything below the end
of the physical page is the transparent checkerboard. Additionally,
tiffinfo complains about a '"Bogus StripByteCounts" field'.

These would be fine if it worked in everything else, but if I run it
through graphicsmagick to convert it, like "gm convert out1.tif
out1.png", it complains "gm convert: Read error at scanline 3247; got 0
bytes, expected 7602. (TIFFFillStrip)." and doesn't create out1.png. If
I run it through imagemagick like "convert out1.tif out1.png", it complains:

convert: Bogus "StripByteCounts" field, ignoring and calculating from
imagelength. `TIFFReadDirectory' < at > warning/tiff.c/TIFFWarnings/820.
convert: Read error at scanline 3248; got 0 bytes, expected 7602.
`TIFFFillStrip' < at > error/tiff.c/TIFFErrors/560.

though it replaces the transparent part with black, or sometimes white
with a few black vertical lines through it.

If I try to run the same thing, with the -y decreased well below page
length, like at 100, the scanner audibly stops scanning half way through
the page and finishes sending the page through the ADF, though scanimage
says it "read more data than announced by backend". The .tif's made like
this open fine, with no transparent sections, and no errors or warnings
from imagemagick or graphicsmagick.

If I run it with SANE_DEBUG_HPAIO=50, the sane_hpaio_read() bytes_read=0
status=5, though it seems to do this with the small and regular -y values.

If I use --format=pnm, then in EOG below the page is black, gm convert
complains "gm convert: Unexpected end-of-file (out1.pnm).", and convert
complains:

convert: unable to read image data `out1.pnm' < at >
error/pnm.c/ReadPNMImage/899.
convert: no images defined `out1.png' < at >
error/convert.c/ConvertImageCommand/3044.

and doesn't create out1.png.

So, what I'm thinking is that the Officejet 6700 stops scanning a page
going through the ADF when it reaches the end of the page, and stops
sending any image data at that point. I'm guessing that scanimage
doesn't just fill any remaining space it expects because of -y with
white or black or anything and just writes out the file as it is, with
the expected remainder of the file missing, as far as other programs are
concerned.



Additionally, though less important, and likely due to how the scanner
actually works, if I use --batch-count and set it to less than the
number of pages in the ADF, the ADF will continue and feed all pages
through the scanner, though it is easy to see that due to their speed
and the sounds, it doesn't actually scan them.


Anyway, does anyone know of anyway to fix this problem, because I have
to scan a few thousand pages over the next few weeks into several pdfs,
and I'd like to write a bash script to sort-of automate a lot of it.

Thanks,
Alex

resolution problem with HP 4400c

Amit Ramon — 2013-05-16T08:25:39

Hello,

I've got a HP scanjet 4400c, and I'm trying to scan with xsane and
xscanimage on Debian.

When I scan at 75 DPI all is fine, with either color or
grayscale. However, whenever I try to scan at a higher resolution I
get an image which is all solid color, some shade of gray.

Any ideas?

Thanks,

Amit

Canon Lide 110 driver hangs under kernel 3.2

Adolf Szabo — 2013-05-15T15:56:30

Hi All,

So far I used Canon Lide 110 fine, but after a kernel update it started not
working. Symptoms are: scanning first page works, scanning second page does
not work. Unplugging then re-plugging and it is working again. So in effect
I need to disconnect and reconnect after every page.

Before first page lsusb says:
Bus 003 Device 002: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110

scanimage -L says:
device `genesys:libusb:003:002' is a Canon LiDE 110 flatbed scanner

after first page neither are showing my scanner.

kernel version:
3.2.0-41-generic #66-Ubuntu SMP Thu Apr 25 03:27:11 UTC 2013

Please advise,
Thx, Dolfy

Looking to get my Mustek A3 1200S flatbed Scanner with GL128 chip working with XSANE

Aaron Silver — 2013-05-14T22:54:55

I've got a Mustek A3 1200S flatbed scanner that I'd like to use with XSANE.
The sane-find-scanner reported the USB ID as 0x055f and the Device ID as
0x0502. It thought the scanner had a GL848+ chip, but when I opened the
case I see a chip with GL128 stamped on it.

I had USBlyzer listen while I did a couple of scans (one full A3 size, and
one of the lower half of the page), but I don't know what the next step is
or how to take it. If someone can walk me through it I'd be happy to do as
much of the work as I can, but I'm also willing (and some would say very
able) to play dumb monkey and feed someone knowledgeable the information
they ask for.

Thanks in advance,

Aaron Silver

Looking to get my Mustek A3 1200S flatbed Scanner with GL128 chip working with XSANE

Aaron Silver — 2013-05-14T22:57:02

I've got a Mustek A3 1200S flatbed scanner that I'd like to use with XSANE.
The sane-find-scanner reported the USB ID as 0x055f and the Device ID as
0x0502. It thought the scanner had a GL848+ chip, but when I opened the
case I see a chip with GL128 stamped on it.

I had USBlyzer listen while I did a couple of scans (one full A3 size, and
one of the lower half of the page), but I don't know what the next step is
or how to take it. If someone can walk me through it I'd be happy to do as
much of the work as I can, but I'm also willing (and some would say very
able) to play dumb monkey and feed someone knowledgeable the information
they ask for.

Thanks in advance,

Aaron Silver

USB device 05a9:1550 OmniVision Technologies,Inc. VEHO Filmscanner

Aidan Karley — 2013-05-07T11:29:32

Back in 2011 I asked about support for the Veho OmniVision slide scanner.

http://lists.alioth.debian.org/pipermail/sane-devel/2011-July/028776.html

Although I've been scanning this mailing list ever since (and not terribly fussed over the machine - my need for slide scanning urgently abated with the funeral), there has been no substantive response from
"Glenn Howald glenn.howald at gmail.com wrote

So it seems there is no further work on this project. Or have I just been missing any contributions from Glenn?

I'm going through the "old stuff" boxes now, and don't know if I should throw this away, or try to get it to work.

lsusb returns :

05a9:1550 OmniVision Technologies, Inc. VEHO Filmscanner

aidank< at >aidank-laptop:~$ sane-find-scanner

# blah

found USB scanner (vendor=0x05a9, product=0x1550) at libusb:001:006
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

Probing the device with scanimage :

aidank< at >aidank-laptop:~$ scanimage -V
scanimage (sane-backends) 1.0.22; backend version 1.0.22
aidank< at >aidank-laptop:~$ 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).

My system is a somewhat mucked-about Ubuntu 11 - it started as Ubuntu 10, and when the upgrade to 11 foisted that horrible Unity thing on me, I had to fight to get it back to something usable and have rejected an OS upgrade since. I'm wondering which way to go on that front, but that's a separate question.

So, any progress on these chips? Or shall I just junk the machine and let it fade into history.

Incidentally, as a contributor to the OpenVizsela project, there should be OpenHardware USB sniffers on the market in the fairly near future. That's another sideline to this saga.

Back in the box it goes.

Help needed diagnosing strange failure to scan withSamsung SCX-4500W

Mike Cloaked — 2013-05-06T20:12:36

I have a strange scanner failure to try to resolve, and I am hoping that an
expert on this list may be able to help me fix the problem.

I have a Samsung SCX-4500W multifunction printer that is plugged in to the
usb port of my main machine running arch linux x86_64.  The printer part
works fine with the Splix driver, but the scanner fails to work.

When I unplug the device and plug it into a laptop running arch linux, it
works fine. On a second laptop also running arch linux the scanner
functions also work fine (xsane). However plugging the same device back in
to my main desktop the scanner fails to work.

Some information is as follows:

sane-find-scanner works as either root or user and yields lines including:

found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.],
product=0x342b [SCX-4500W Series]) at libusb:001:007
  # Your USB scanner was (probably) detected. It may or may not be
supported by
  # SANE. Try scanimage -L and read the backend's manpage.

scanimage -L works the first time I issue the command but then subsequently
fails:

scanimage -L
device `xerox_mfp:libusb:001:006' is a Samsung Samsung SCX-4500W Series
multi-function peripheral

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).

The device is listed correctly with the lsusb command:
Bus 001 Device 007: ID 04e8:342b Samsung Electronics Co., Ltd


The file /etc/sane.d/xerox_mfp.conf does have the correct line for the
device:
# Samsung SCX-4500W
usb 0x04e8 0x342b

The system log files contain lines like:
May  6 16:43:27 localhost kernel: [ 8041.053060] usb 1-4: usbfs: interface
1 claimed by usblp while 'xsane' sets config #1

I have tried unplugging the device and replugging it but nothing I do ever
seems to make any difference.  I also removed the .sane directory from the
user and started from new and nothing changed.

The udev rules file seems fine and in less
/lib64/udev/rules.d/53-sane.rules the lines relevant to the device are:

# Samsung SCX-4500W
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0664",
GROUP="scanner", ENV{libsane_matched}="yes"


The system is fully up to date, and runs with systemd. The two laptops one
of which is x86_64 and the other i386 are both the same arch setup, and
both up to date. They work but the main machine does not.

Can anyone suggest how I might be able to narrow down where the problem may
lie?

Many thanks for any help.

Kodak i2600

Brian DeRocher — 2013-04-30T03:07:14

Hey,

I just wanted to report that the driver from Kodak for the i2600 works
very well.  They are 32 bit only.  Kind of a pain to get it all
working.  Lots of stracing to see where files were being loaded from.

In other news, i'm using Xsane + Scan Tailor + libdjvu + a radial arm
saw to convert all my books to digital.

Brian

Linux drivers for scanjet 3000

Bruce Markey — 2013-04-26T01:02:51

I was wondering if someone could point me in the right direction for
getting an hp scanjet 3000 working with sane.  From what I see its  not
supported by hplip .

Thanks
Bruce

troubleshooting Xerox WC3220 network scanning

Henrieta Marmorstein — 2013-04-25T18:51:43

Hello !

I tried all in this excellent tutorial
https://help.ubuntu.com/community/sane.d%20tutorial but I cannot access the
scanner installed in my little network. This model of XEROX MFP is working
on Windows system, I used it in my office, but I cannot used it with Ubuntu
12.10. As a network printer everything is OK.

Can you help me, please ? Maybe also with a method to fax from PC ?

Thank you.

Henrieta Marmorstein

ADF - Calibration problem

arobase er — 2013-04-24T20:51:45

Hello,

I have started using sane to scan using an ADF.

$ scanimage -V
scanimage (sane-backends) 1.0.22; backend version 1.0.22

$ scanimage -L
device `hp5590:libusb:036:003' is a HP 4500C/5550C Workgroup scanner

$ scanimage --batch --format=tiff --mode Gray --resolution 75 --source ADF
--batch-increment 2

Here's the output for the first 3 pages: *http://tinyurl.com/b3shh4v*

The problem is that a portion of the left hand side shows on the rhs and
conversely. This portion grows with the number of scanned pages.

Any advice on fixing this calibration problem?

Platform: OS X 10.6+ - MacPorts 2.1.3

Out of memory (Brother MFC-9465CDN)

martin f krafft — 2013-04-23T10:08:20

[repost, in dire hope of someone who can help…]

Hey there,

I have a problem with a Brother MFC-9465CDN that I access through
a "scanner server" running saned. The problem is that most scans
fail with an "out of memory" message.

However, I can scan fine when using scanimage on the server
directly, the problem is when going through saned.

This machine does not have a whole lot of ooomph, but 1Gb of RAM
should be enough. In any case, there is still free memory (according
to top) at the time of the error.

Is this a problem with saned or the machine it's running on, or
a problem with the scanner?

To me, it seems that the out-of-memory message comes from the
scanner, but maybe I am misinterpreting the debug output (see
below).

Thanks for any help!

Here is the client output:

  % scanimage -d 'net:scanner.is:brother4:net1;dev0' -p --mode 'Black & White' --resolution 300 --source 'Automatic Document Feeder(left aligned)' >| /tmp/s
  scanimage: rounded value of br-x from 215.9 to 215.88
  scanimage: rounded value of br-y from 355.6 to 355.567
  scanimage: sane_read: Out of memory

Here is the server debug output:

  [saned] start_scan: trying to bind data port 0
  [saned] start_scan: using port 36052 for data
  [saned] process_request: waiting for data connection
  [saned] process_request: access to data port from 2001:a60:f10a:0:224:d7ff:fe04:c82c
  [saned] do_scan: start
  [saned] do_scan: trying to read 8188 bytes from scanner
  [saned] do_scan: read 8188 bytes from scanner
  [saned] do_scan: processing RPC request on fd 4
  [saned] process_request: waiting for request
  [saned] process_request: got request 6
  [saned] do_scan: trying to write 8192 bytes to client
  [saned] do_scan: wrote 8192 bytes to client
  [saned] do_scan: trying to read 8188 bytes from scanner
  [saned] do_scan: read 8188 bytes from scanner
  […]
  [saned] do_scan: trying to write 7976 bytes to client
  [saned] do_scan: wrote 7976 bytes to client
  [saned] do_scan: trying to read 212 bytes from scanner
  [saned] do_scan: read 0 bytes from scanner
  [saned] do_scan: status = `Out of memory'
  [saned] do_scan: statuscode `Out of memory' was added to buffer
  [saned] do_scan: trying to write 9 bytes to client
  [saned] do_scan: wrote 9 bytes to client
  [saned] do_scan: done, status=Out of memory

Testing Sane + Canon MG6250

Ashley Arnold — 2013-04-22T13:04:18

Hi,

I'm not really sure how to do this, but the
http://www.sane-project.org/sane-mfgs.html page said "Testers needed", so
here is what I did to get my Canon MG6250 scanner going.

This is on xubuntu 12.10 64-bit with all current updates as at 13th Apr
2013. Here is my xsane version info:

$ xsane --version
xsane-0.998 (c) 1998-2010 Oliver Rauch
  E-mail: Oliver.Rauch< at >xsane.org
  package xsane-0.996
  compiled with GTK-2.24.12
  with color management function
  with GIMP support, compiled with GIMP-2.8.0
  XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.), tiff, txt

After installing xsane, initially it wouldn't detect the MG6250 (which was
on the network via wireless connection). It would look for devices and then
the process would end.

After reading the man docs and finding the "backend name" for my printer is
"pixma", I did:

   - man sane-pixma (seems to be a man entry for each backend) tells you to
   that network scanners should normally be detected, but if not, add them
   directly to /etc/sane.d/pixma.conf
   - Edited /etc/sane.d/pixma.conf and added:

   bjnp://<ip_address>

   - The sane daemon wasn't running, so I started it manually (a friend of
   mine running Arch said it was for him...):
      - Edited /etc/default/saned and set RUN=yes.
      - Then started the sane service: service saned start
   - Run xsane, it discovered the scanner and worked perfectly.

The only issue I had is for multi-page documents, it didn't wait between
pages, but scanned the same page over and over. This might be user error
and nothing to do with xsane though.

Hopefully this is of use to someone. Again, apologies if this is not the
forum for this kind of stuff.

Cheers,
Ash

sane-backends 1.0.23 source code tar.gz file withincorrect MD5 hash?

Andre Leite — 2013-04-19T14:42:33

Hello to sane-devel,
  
  today I downloaded a copy of the source code related to Sane 1.0.23 (HTTP: alioth.debian.org (USA, provided by Debian))
  
  from the following links:
  https://alioth.debian.org/frs/download.php/3752/sane-backends-1.0.23.tar.gz.1
  https://alioth.debian.org/frs/download.php/3752/sane-backends-1.0.23.tar.gz.2
  https://alioth.debian.org/frs/download.php/3752/sane-backends-1.0.23.tar.gz.3
  
  The file was split in 3 parts as it was explained on the README.txt (Due to limitations in alioth's file upload software). 
  After downloading each part I executed cat to join them into the tar.gz file:
  
  (1) cat sane-backends-1.0.23.tar.gz.[1-3] > sane-backends-1.0.23.tar.gz
  
  In the end I had the complete file: sane-backends-1.0.23.tar.gz
  
  Then I downloaded the MD5 hash file: sane-backends-1.0.23.tar.gz.md5
  from the link: https://alioth.debian.org/frs/download.php/3756/sane-backends-1.0.23.tar.gz.md5
  which contains the MD5 hash
  e226a89c54173efea80e91e9a5eb6573  sane-backends-1.0.23.tar.gz
  
  Verifying the MD5 hash from the downloaded files after joining then in a single tar.gz file I get:
  (2) $ openssl md5 sane-backends-1.0.23.tar.gz
  I get
  MD5 (sane-backends-1.0.23.tar.gz) = 0023e8dda2a879dab07061938098432e
  which doesn't match the original MD5 hash indicated in the file sane-backends-1.0.23.tar.gz.md5
  
Also checking the original MD5 hash file indicated on the link:
http://www.sane-project.org/sane-md5sums.txt
It states that the original md5 hash must be:
e226a89c54173efea80e91e9a5eb6573  sane-backends-1.0.23.tar.gz

Any clues?

thanks,
Andre.

HP Scanjet 3000

Zvi Herschman — 2013-04-18T18:53:23

Is there any way to make an HP Scanjet 3000 work on Ubuntu?  Ubuntu does
not even recognize a device has been plugged in.  Any help would be
appreciated. Thanks.

Pulstek OpticBook 3800

Nikolay Shaplov — 2013-04-18T18:39:17

Hi!

I've recently bought Pulstek OpticBook 3800, hoping that it is almost the same 
thing as 3600, and I wont need much configuring with it. 

This hopes died when I did sane-find-scanner, it said

found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0 
SCANNER], chip=GL847) at libusb:001:020

and 3600 is GL841 :-(

What did I do:

I've cloned Genesys_Model plustek_3600_model in backend/genesys_devices.c
replaced GENESYS_GL841 with GENESYS_GL847, added correct vendor and product id 
for this clone in device list there, built and installed it, and also added 
vendor and product id into /etc/sane.d/genesys.conf 

Result was the following

scanimage makes the scanner move it's head (not always sane, sometimes it 
tries to move out of device physical limits) and turn the lamp on and off.

Scanning goes with turned off lamp, and the result file if always filled with 
0x00, even if i put external light source over the scanner.


This is my limits of what I can do myself without your help.

I did not found any info about how to turn some debugging output (-v -v -v -v 
-v does not give much information about what sane is trying to do with the 
scanner)
I did not found any guides about how to debug devices in such cases.

If you can help me with these question, or even can guide me through the 
debugging process, this would be great.

As I can understand GL847 chip is supported by SANE and we should do 
calibration and other staff like these...

What I should do first?

(no subject)

耿明霞 — 2013-04-18T08:45:52

Hi

         Does Kodak i40 support SANE?