[sane-devel] FI-5750C Error 4?

2007-06-26 Thread Oliver Schirrmeister
Am Dienstag, 26. Juni 2007 11:15 schrieb Simon Glass:
 Hi,
 
 Now that I am able to build SANE (thanks Alan, but no I have no idea
 about libtool) I have the FI-5750C working. It's a wonder to behold.
 However, I am puzzled by an error that I get. It seems that if I try to
 scan a page larger than the setting I have for the ADF size then I get
 an error 4 (Unknown Error).
 
 Further to that, if I try to scan A3 (even with the right ADF setting) I
 get error 4. Maybe it is something slightly wrong with the paper size.
 
 Any ideas on this one?
 
 Another point is that the scanner seems to pause after some pages. Not
 every time, it might scan 6 pages and then pause for a second. But it is
 quite noticeable. I wonder if that is SANE or Fujitsu...

That's a fujitsu problem. You'll see the same behaviour with windows and twain. 
I guess the scanner scans faster than it can transmit the data via usb/scsi. 
The 
scanner has some memory where it can buffer some data. If it's full the scanner 
pauses
an recalibrates. 

Oliver

Geschaeftsfuehrer: Dipl.-Inform. Christopher Asp
Amtsgericht Mannheim HRB 105845



[sane-devel] problems with Fujitsu M3093DG with USB/SCSI

2005-10-17 Thread Oliver Schirrmeister
 [fujitsu] calculateDerivedValues
 [fujitsu]top_margin: 0
 [fujitsu]left_margin: 0
 [fujitsu]scan_width: 10199
 [fujitsu]scan_height: 14031
 [fujitsu] calculateDerivedValues: ok
 [fujitsu]depth 8
 [fujitsu]lines 3507
 [fujitsu]pixels_per_line 2549
 [fujitsu]bytes_per_line 2549
 [fujitsu] sane_read, object_count=1
 [fujitsu]0/0/0: Scanner ready
 [fujitsu] sanei_scsi_cmd: returning 0x0005
 [fujitsu] sanei_scsi_cmd: returning 30588 bytes:
 [fujitsu] rslt
 [fujitsu] 000: 00 00 00 00 00 00 00 40 00 00 01 2c 01 2c 00 00
 [fujitsu] 010: 00 00 00 00 00 00 00 00 27 d7 00 00 36 cf 00 00
 [fujitsu] 020: 00 02 08 00 00 00 00 00 00 00 00 00 00 00 00 00
 [fujitsu] 030: 00 00 00 00 00 00 00 a0 20 00 00 00 00 84 00 00
 [fujitsu] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 [fujitsu] 050: 00 00 ff ff ff 00 48 38 ff 60 e0 00 00 00 00 00
 [fujitsu] reader_process: EOM (no more data) length = 30588
 [fujitsu] sane_read: read 28672 bytes of 32768
 [fujitsu] sane_read, object_count=1
 [fujitsu] sane_read: read 1916 bytes of 32768
 [fujitsu] sane_read, object_count=1
 [fujitsu] reader_process(generic): buffer of 0 bytes read; 0 bytes to go
 [fujitsu] sane_read: read 0 bytes of 32768
 [fujitsu] sane_read: pipe closed
 [fujitsu] sane_cancel
 [fujitsu] do_cancel
 [fujitsu] do_cancel: kill reader_process
 [fujitsu] wait for scanner to stop
 [fujitsu] free_scanner
 [fujitsu] release_unit
 [fujitsu] 000: 17 00 00 00 00 00
 [fujitsu] cmd
 [fujitsu] 000: 17 00 00 00 00 00
 [fujitsu] sanei_scsi_cmd: returning 0 bytes:
 [fujitsu] free_scanner: ok
 [fujitsu] do_cancel: close filedescriptor
 [fujitsu] sane_close
 [fujitsu] sane_exit

-- 
Mit freundlichen Gr??en

Oliver Schirrmeister
--
AB+M GmbH 
Haid-und-Neu-Str. 7
76131 Karlsruhe
Tel: 0721/66488-13
Fax: 0721/66488-18


[sane-devel] Anybody has any idea about the duplex scan problem of fi-4120c

2005-05-17 Thread Oliver Schirrmeister
Am Samstag, 14. Mai 2005 17:22 schrieb qian hui:
 hi,
 I tried to do a duplex scan with a fujitsu fi-4120c
 and USB interface ( the source code is 2004-08-24
 version). It can not correctly scan with the duplex
 mode of both(paper are half locked in the machine).
 When set duplex mode to back, it scan the same side
 as mode front.

 I found an article at
 http://lists.alioth.debian.org/pipermail/sane-devel/2004-April/010688.html,
 but no more information about the solution. I find a

There is no solution, yet (as far as I know).  Ok, you can use the SCSI
interface.

 [fujitsu]  5/38/0: Invalid field in parm list  in
 the error log. what's mean?

It means that there is something wrong with the parameter block the
backend sends to the scanner.

sorry, 
Oliver



[sane-devel] Fujitsu backend questions

2004-11-15 Thread Oliver Schirrmeister
Am Montag, 15. November 2004 17:53 schrieb Mattias Kregert:
 Hello list,

 I have some questions about my fujitsu FI-4120C... (using the fujitsu
 backend):

 - The scanner lamp is always on. From what I have heard, that is a Bad
 Thing because it will shorten the lamp's lifetime... If this is correct,
 then how can I turn off the lamp? Is there some magic hidden command to do
 that?

There is an option 'sleeptimer'. I think it's the time in minutes(?) until the
lamp is turned off. I've not tried it with the 4120.

 - Is there some way to make the scanner recognize the physical papersize
 and scan only that size? Right now I have to select between A4 / A5 paper
 format... If i use A4 then i know that the whole paper will always be
 scanned.. but if i scan a lot of A5 then i want to scan only A5 because it
 it twice as fast as A4 now when i mix A4 and the smaller A5, I have to
 change settings all the time...   If I use adfscan then I have to set it to
 A4 (the largest format) but then i loose a lot of speed... A
 'papersize=auto' feature would be nice... is there some way to do this with
 the current backend?

I don't know about the 4120, but the big brothers of that scanner are able to 
do a paper length detection. It works fine with TWAIN but I've not 
implemented it in SANE, yet. 

-- Oliver




[sane-devel] SCSI sniffer

2004-11-04 Thread Oliver Schirrmeister
Hi all,

I'd like to know what the windows twain driver sends to my SCSI-scanner.
I remember there was a posting about several SCSI sniffers several month
ago, but I can't find it in the archive.

Could somebody give me a hint, please.

Thanks

Oliver




[sane-devel] memory problem

2004-08-26 Thread Oliver Schirrmeister
Am Donnerstag 26 August 2004 10:12 schrieb Gerhard Jaeger:
 [SNIPSNAP]
  I've linked the sane backends statically with the 'frontend'. The problem
  is the same. The pthread lib is linked dynamically.
  I've tried valgrind. That revealed only two 'real' memory leaks in some
  init-routines of sanei_usb, the test backend and the pthread library,
  nothing severe.

 Is the sanei_usb memory-leak related to the patch you've sent me?

Yes. 

  Under control of valgrind the vm-size doesn't increase !?!

 Hmmm, strange...
 anybody out there with some ideas?

valgrind supplies its own libpthread.so, probably without that bug?

 On what box are you working? Kernel-Version and glibc Version?

Linux version 2.4.20-8 (bhcomp...@porky.devel.redhat.com) (gcc version 3.2.2 
20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003

RedHat 9.0 P4-2.8, libc-2.3.2

Ciao

Oliver




[sane-devel] Fujitsu papersize problems, sane-backends-1.0.14

2004-06-03 Thread Oliver Schirrmeister
Am Donnerstag 03 Juni 2004 16:36 schrieb Lee Howard:
   I am having trouble when using the --papersize options other than
   A4/Letter.
  
   If I do:
  
   scanimage --source ADF --papersize Autodetect
  
   or:
  
   scanadf --source ADF --papersize Autodetect
  
   I get:
  
   sane_start: Invalid argument
 
  Seems that autodetect doesn't work with the 4097. I've tried that
  option with
  the 3093 but it wasn's reliable.

 Oh, alright.

 By your comments here I assume that --papersize is used solely to
 indicate to the ADF the size of the paper that it is supposed to pull
 through, but does not indicate the size of the area that is to be
 scanned.  Is this correct?

Correct.

 I don't really understand the value of the --papersize option, then,
 since the scanner seems to deal with mixed-size and other-size paper
 regardless of what --papersize option I use.  E.g., if I use
 --papersize Letter, then it seems to be quite happy about scanning
 Letter and Legal sized paper mixed in the ADF.

Your scanner has a DIN A3 ADF and you use those plastic bars (how
are they called?) to center your letter sized paper. The origin of the
scanning area (-x -y -l -t) is 0/0 in the picture below if you use 
--papersize Letter, not the left side of the A3 ADF.

| --- DIN A3 --|
|| 0/0 |   |
|| - Letter - |   |
||  |   |
||  |   |
|  |

If you put mixed-size paper in the adf with different paper width (e.g 
letter and A5) you'll more likely get a paper jam and the A5 paper 
will probably be skewed. 
The resulting image of the A5 paper will have letter size if -x and -y
are set to letter size.

I think this subject is better described in one of that guides of your
scanner (have a look at the fujitsu home page).

-- Oliver



[sane-devel] Fi-4120c duplex color

2004-06-02 Thread Oliver Schirrmeister
Am Freitag 30 April 2004 16:44 schrieb Krzysztof Cieniuch:
 Hi,

 Is it possible to scan duplex in color with this scanner ?
 I've tried scanadf --rif=yes --duplex=both --resoluton=72 -d
 fujitsu:/dev/sg0
 but i've ended up with one properly scaned image and one
 totally black. Is this feature missing in fujitsu backend ?
 In what time if ever will be this functionality available in
 fujitsu backend ?


That was a bug in the fujitsu backend. I've fixed that, checkout the
latest version.

Oliver




[sane-devel] Fi-4120c duplex color

2004-04-30 Thread Oliver Schirrmeister
Am Freitag 30 April 2004 18:18 schrieb Oliver Schirrmeister:
 Am Freitag 30 April 2004 16:44 schrieb Krzysztof Cieniuch:
  Hi,
 
  Is it possible to scan duplex in color with this scanner ?
  I've tried scanadf --rif=yes --duplex=both --resoluton=72 -d
  fujitsu:/dev/sg0
  but i've ended up with one properly scaned image and one
  totally black. Is this feature missing in fujitsu backend ?
  In what time if ever will be this functionality available in
  fujitsu backend ?

 scanadf overwrites the first image.
 scanadf -o /tmp/image_%04d --duplex both --mode gray
 works with my fi4120c


Sorry, I should read what you ask.
Yes, when I scan duplex color the second page is blank. I don't know
if thats the fault of the backend or scanadf.

Oliver




[sane-devel] fujitsu duplex scan with usb

2004-04-06 Thread Oliver Schirrmeister
Thanks,
I think the status of the fujitsu scanners with USB interface should not
be reported 'good'.

Oliver

Am Montag 05 April 2004 22:23 schrieb m. allan noah:

 so, i tracked it down using usb snoopy in windows. the problem is simple
 to explain, but harder to fix:

 most scsi commands that use a data block after the command block (mode
 select, set window, scan) are formatted differently when sent via usb. the
 command block is sent first, in a single urb, padded to 31 bytes with null
 bytes. then the data block(s) are sent in another urb, not padded.

 the existing fujitsu code is very scsi specific, and only uses one buffer
 for scsi cmd/data to the do_cmd() function. this means that the caller has
 to either pad the single buffer with just the right number of 0's in the
 middle of the buffer, or the do_usb_cmd() function will have to break the
 buffer inhalf, and pad the data itself.

 for an example, see fujitsu_set_sleep_mode().

 you see this problem only with scanning duplex or back side because the
 code at line 3112 (talks about opcode==SCAN) is wrong. it should take the
 last one or two bytes and send as adifferent urb, rather than assuming 00.

 i have started a new version of the fujitsu backend, which uses a command
 and a data buffer to do_cmd() but have been far too busy to make much
 headway. take a shot if you would like.




[sane-devel] fujitsu duplex scan with usb

2004-03-26 Thread Oliver Schirrmeister
Hi,

has anybody tried to do a duplex scan with a fujitsu fi-4x20
and USB interface?

I've tried
scanimage --duplex both /tmp/out

and the scanner returns and error in the start_scan command
block. I can't see what's wrong. The same block with SCSI
works fine. Siplex scanning with USB works as well.

Any ideas?

Alan, don't you have the oem manual of that scanner? Can
you mail that to me?

Thanks

Oliver




[sane-devel] how to return paper size

2004-02-24 Thread Oliver Schirrmeister
Hi,

when I use the document feeder my scanner can tell me the paper size
(e.g. A4, ...)
How do I return this information with sane?

Oliver




[sane-devel] SANE support for Ricoh is410

2004-02-16 Thread Oliver Schirrmeister
Am Donnerstag 12 Februar 2004 22:02 schrieb John Lei:
 To whom it may concern,

   I have an old Ricoh is410 SCSI scanner that I was hoping to be 
 able
 to pull out of our graveyard. I've hooked it up to a PowerMac G4
 running OS X.2.8 using a Grappler 906F (current firmware) and the
 TWAIN-SANE interface. The scanner is not being detected by SANE;
 although it is showing up in my system profiler.
 I was hoping someone could assist me in this experiment; whether or
 not I'd be able to get this scanner working again.
 Thanks for your help.

 John.

I've played with the IS410 and the ibm backend some years ago. I was able
to move the paper through the ADF or even scan with some minor patches of the
backend (don't know if I've commited them to Henning). The ricoh backend
didn't work at all with that scanner. If you want to use the scanner seriously
there is some work to do. I wasn't able to get some documentation of the
scanner from ricoh. 

Oliver.



[sane-devel] has feeder loaded

2003-12-16 Thread Oliver Schirrmeister
is there a function in sane to ask if the document feeder
is loaded (like the 'has feeder loaded' option in TWAIN)?

Thanks

Oliver




[sane-devel] has feeder loaded

2003-12-16 Thread Oliver Schirrmeister
The fujitsu backend offers a SOFT_DETECT, HARD_SELECT option 'startbutton'
to query button1. The same thing could be done with 'paper in hopper' or else.
But these options should have the same name for all backends. Is there such
a known name or other interface?

Oliver

Am Dienstag 16 Dezember 2003 15:41 schrieben Sie:
 there was some discussion about having one or more sane options that could
 provide scanner status. they would have to be in a specific group, or have
 specific indexes into the options array, or have specific names, so
 finding them could be sort of ugly.

 i can think of a few things that the fujitsu scanners tell us:

 button1 pressed
 button2 pressed
 character on 'function' readout
 number on 'copy' wheel
 paper in hopper
 cover open
 lamp warm

 is there a general purpose way to expose this?

 allan

 On Tue, 16 Dec 2003, Oliver Schirrmeister wrote:
  is there a function in sane to ask if the document feeder
  is loaded (like the 'has feeder loaded' option in TWAIN)?
 
  Thanks
 
  Oliver




[sane-devel] Why is the background of the scanned image not a constant grayscale

2003-05-14 Thread Oliver Schirrmeister

Am Mit, 2003-05-14 um 02.37 schrieb Peter Chen:
 Hi,
 
 I found an option named 'paper_size' for fujitsu fi-4120c. Does this
matter?

This option spezifies the size of the paper in the adf, for exaple A4, 
A5 ...
This has nothing to do with your gray background.

Oliver



[sane-devel] Problem with setting Fujitsu fi-4120c to Grayscale

2003-04-25 Thread Oliver Schirrmeister
Use the strings 'Lineart', 'Halftone', 'Gray' or 'Color' to set option
scan_mode. As far as I can see, value=3 does not work.
Which function returned SANE_STATUS_INVAL? sane_control_option with
option SANE_NAME_SCAN_MODE? That should only happen when you try
to set mode 'Halftone'.

Oliver


Am Don, 2003-04-24 um 22.43 schrieb Peter Chen:
 Hi all,
 
 I tried to set fi-4120c to Grayscale. I used the following code flow:
 
 status = sane_init(version_code, NULL);
 status = sane_get_devices(device_list, true);
 ...
 sane_exit();
 
 status = sane_init(version_code, NULL);
 status = sane_open(dev/usb/scanner0, device );
 sane_control_option (device, 0, SANE_ACTION_GET_VALUE,
 num_dev_options, 0);
   for (i = 0; i  num_dev_options; ++i)
 {
   opt = sane_get_option_descriptor (device, i);
   // Set the resolutions to 300 dpi
   if ( strcmp(opt-name, SANE_NAME_SCAN_X_RESOLUTION) == 0)
   {
   value = 300;
   sane_control_option (device, i, SANE_ACTION_SET_VALUE, value,
 info);
   }
   if ( strcmp(opt-name, SANE_NAME_SCAN_Y_RESOLUTION) == 0)
   {
   value = 300;
   sane_control_option (device, i, SANE_ACTION_SET_VALUE, value,
 info);
   }
   // Set the scan mode to GrayScale
   if ( strcmp(opt-name, SANE_NAME_SCAN_MODE) == 0)
   {
   value = 3;
   sane_control_option (device, i, SANE_ACTION_SET_VALUE, value,
 info);
   }
 }
 
 The first time I ran it, it successfully set fi-4120c to GrayScale (when I
 debug, I could see that), but then later when I did that, it always returned
 SANE_STATUS_INVAL, even after I rebooted my linux box and fi-4120c. I could
 set the resolutions successfully. What did I do wrong?
 
 Thanks,
 
 Peter
 ___
 Sane-devel mailing list
 sane-de...@www.mostang.com
 http://www.mostang.com/mailman/listinfo/sane-devel




[sane-devel] Fujitsu fi-4120Cdj errors (repeat)

2003-03-26 Thread Oliver Schirrmeister
set_WD_paper_width_X/Y spezifies the size of your sheet of paper. You
also have to define the scan area (option -x -y).
The height of your scan area is 0x24e8/1200 inch = 20cm (see window
descriptor block).

Oliver

Am Mit, 2003-03-26 um 15.34 schrieb m. allan noah:
 update: i hard-set the gamma byte (0x29) to 0x80, and the paper byte 
 (0x35) to 0xC0, and then forced the lines:
 
  set_WD_paper_width_X (buffer, s-page_width);
  set_WD_paper_length_Y (buffer, s-page_height);
 
 to always run, and the scanner runs.
 
 but now, the output images from the program 'scanadf' are truncated.
 
 any ideas?
 
 allan
 
 On Wed, 26 Mar 2003, m. allan noah wrote:
 
  just got a Fujitsu fi-4120C scanner. was previously using an M3091DCd. i 
  am running latest cvs snapshot. i use the scsi port, not usb. i get the 
  following error:
  
  [fujitsu] Window set
  [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
  [fujitsu] 016: 25 00 00 00 24 e8 00 80 00 00 01 00 00 00 00 00
  [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
  [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
  [fujitsu] cmd
  [fujitsu] 000: 24 00 00 00 00 00 00 00 48 00 00 00 00 00 00 00
  [fujitsu] 016: 00 40 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00
  [fujitsu] 032: 00 00 25 00 00 00 24 e8 00 80 00 00 01 00 00 00
  [fujitsu] 048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  [fujitsu] 064: 00 a0 20 00 00 00 00 84 00 00 00 00 00 00 00 00
  [fujitsu] 080: 00 00
  [fujitsu]   5/38/0: Invalid field in parm list
  [fujitsu] offending byte is 49. (Byte 41 in window descriptor block)
  [fujitsu] sanei_scsi_cmd: returning 0x0004
  [fujitsu] sanei_scsi_cmd: returning 0 bytes:
  [fujitsu] sane_start: ERROR: failed to set window
  
  from the command line:
  
  SANE_DEBUG_FUJITSU=128 SANE_DEBUG_SANEI_SCSI=0 scanadf -d fujitsu --mode 
  Lineart -x 200 -y 200
  
  byte 41 (0x29) is gamma/pattern according to fujitsu-scsi.h
  
  i have tried hard-setting this to all the possible (and some un-listed) 
  options, no change. i have tried different modes, no change.
  
  what is this option for (is is gamma correct or a pattern?) and what 
  should it be for lineart? 
  
  how easy is it to get programming docs from fujitsu, since the 4120 seems 
  to need some help?
  
  allan 
  
  
 
 -- 
 so don't tell us it can't be done, putting down what you don't know.
 money isn't our god, integrity will free our souls - Max Cavalera
 
 ___
 Sane-devel mailing list
 sane-de...@www.mostang.com
 http://www.mostang.com/mailman/listinfo/sane-devel
 
 




[sane-devel] Re: Fujitsu USB patches

2003-03-14 Thread Oliver Schirrmeister
Your patch is in the CVS now. 
I had to do your patch by hand because I've changed the backend after
March 3. I hope I didn't mess up your code. Please test.

Oliver


Am Die, 2003-03-11 um 22.26 schrieb Ron Cemer:
 The attached patch fixes the broken ADF empty detection on the Fujitsu 
 scanners when connected via USB.  It also fixes a sense-request issues, 
 which were required in order to determine whether the ADF is empty.  It 
 also eliminates some duplicate code blocks.
 
 The patch is against the March 3, 2003, CVS snapshot.
 
 Can you apply this to the latest CVS?
 
 Thanks!
 Ron
 




[sane-devel] lost with FUJITSU scanner M3096G

2003-03-10 Thread Oliver Schirrmeister
Am Sam, 2003-03-08 um 23.15 schrieb Frank Zago:
 
  
  I've tried it with RedHat 8.0 linux. The sense bytes 16 and 17 really
  point to the offending byte (I've tried to set a invalid resolution 
  an others). There is a 8 byte window header you can't 
  see in the hexdump above. The offending byte is at position 25 (0x02).
  This means 'grayscale monochrome'. Dirks M3096G doesn't seem to support
  grayscale (probably that firmware bug?).
  
  
 
 Or it support grayscale, but not with a 8 bits depth. What about 4? See 
 set_WD_bitsperpixel in setWindowParam().
 
 Frank
 

According to the M3096GX OEM manual the M3096 only supports 8 and 1 bit.
Setting 'bits per pixel' to 4 returns an error (M3097 and M4097).

Oliver




[sane-devel] lost with FUJITSU scanner M3096G

2003-03-07 Thread Oliver Schirrmeister
Am Fre, 2003-03-07 um 17.12 schrieb Frank Zago:
 abel deuring wrote:
  Frank Zago wrote:
  
 [fujitsu] set_window_param
 [fujitsu] Window set
 [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
 [fujitsu] 016: 03 b0 00 00 05 89 00 00 00 02 08 00 00 00 00 00
 [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
 [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
 [fujitsu]   5/38/0: Invalid field in parm list
 [fujitsu] sanei_scsi_cmd: returning 0x0004
 [fujitsu] sane_start: ERROR: failed to set window
 
 The scanner rejected the window parameter. If the scsi implementation is 
 decent,
 the sense might contain the offset of the offending byte somewhere around 
 byte
 16 oy 17. To get that, at the beginning of scsi_sense_handler, add this 
 line:
 
hexdump (MSG_IO, Sense, sensed_data, sensed_data[7]+8);
  
  
  Frank,
  
  you're right, the sense bytes 16 and 17 should point to the offending
  byte, but unfortunately the Linux SCSI system returns only the first 16
  bytes of a SCSI command.
 
 
 Are you sure of that? There are devices out there that return more than 100 
 bytes of data in the sense. I assume someone would have fixed such a problem.
 
 
  But it might help to issue a REQUEST SENSE manually after the failing
  SET WINDOW and print the result of this command. 
 
 Unless the system caches the sense (and more than 16 bytes), the next request 
 sense isn't going to return anything.
 
 Frank.
 
 ___
 Sane-devel mailing list
 sane-de...@www.mostang.com
 http://www.mostang.com/mailman/listinfo/sane-devel
 
 
Hi Frank,

I've tried this. The result is:

[fujitsu] Window set
[fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
[fujitsu] 016: 03 b0 00 00 05 89 00 00 00 02 08 00 00 00 00 00
[fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
[fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
[fujitsu] Sense
[fujitsu] 000: f0 00 45 00 00 00 00 0a 00 00 00 00 26 00 00 80
[fujitsu] 016: 00 21
[fujitsu]   5/38/0: Invalid field in parm list
[fujitsu] sanei_scsi_cmd: returning 0x0004
[fujitsu] sane_start: ERROR: failed to set window

What is the meaning of the these bytes?

Oliver.



[sane-devel] lost with FUJITSU scanner M3096G

2003-03-07 Thread Oliver Schirrmeister
Am Fre, 2003-03-07 um 17.12 schrieb Frank Zago:
 abel deuring wrote:
  Frank Zago wrote:
  
 [fujitsu] set_window_param
 [fujitsu] Window set
 [fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
 [fujitsu] 016: 03 b0 00 00 05 89 00 00 00 02 08 00 00 00 00 00
 [fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
 [fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
 [fujitsu]   5/38/0: Invalid field in parm list
 [fujitsu] sanei_scsi_cmd: returning 0x0004
 [fujitsu] sane_start: ERROR: failed to set window
 
 The scanner rejected the window parameter. If the scsi implementation is 
 decent,
 the sense might contain the offset of the offending byte somewhere around 
 byte
 16 oy 17. To get that, at the beginning of scsi_sense_handler, add this 
 line:
 
hexdump (MSG_IO, Sense, sensed_data, sensed_data[7]+8);
  
  
  Frank,
  
  you're right, the sense bytes 16 and 17 should point to the offending
  byte, but unfortunately the Linux SCSI system returns only the first 16
  bytes of a SCSI command.
 
 
 Are you sure of that? There are devices out there that return more than 100 
 bytes of data in the sense. I assume someone would have fixed such a problem.
 


I've tried it with RedHat 8.0 linux. The sense bytes 16 and 17 really
point to the offending byte (I've tried to set a invalid resolution 
an others). There is a 8 byte window header you can't 
see in the hexdump above. The offending byte is at position 25 (0x02).
This means 'grayscale monochrome'. Dirks M3096G doesn't seem to support
grayscale (probably that firmware bug?).


[fujitsu] Window set
[fujitsu] 000: 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00 00 00
[fujitsu] 016: 03 b0 00 00 05 89 00 00 00 02 08 00 00 00 00 00
[fujitsu] 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
[fujitsu] 048: 20 00 00 00 00 84 00 00 00 00 00 00 00 00 00 00
[fujitsu] cmd
[fujitsu] 000: 24 00 00 00 00 00 00 00 48 00 00 00 00 00 00 00
[fujitsu] 016: 00 40 00 00 01 2c 01 2c 00 00 00 00 00 00 00 00
[fujitsu] 032: 00 00 03 b0 00 00 05 89 00 00 00 02 08 00 00 00
[fujitsu] 048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[fujitsu] 064: 00 a0 20 00 00 00 00 84 00 00 00 00 00 00 00 00
[fujitsu] 080: 00 00
[fujitsu] Sense
[fujitsu] 000: f0 00 45 00 00 00 00 0a 00 00 00 00 26 00 00 80
[fujitsu] 016: 00 21
[fujitsu]   5/38/0: Invalid field in parm list


Oliver



[sane-devel] How to scan monorome with fujitsu 3091DC.

2003-02-20 Thread Oliver Schirrmeister
I've commited a new version of the fujitsu backend that makes the
option --rif available for the 3091 to the CVS. 

You can try
scanimage --rif=yes --mode Lineart 
and the image should not be inverted anymore.

Oliver

Am Sam, 2003-02-15 um 23.04 schrieb Richard Reina:
 Oliver,  
 
 Thanks for the response but I never was able to find a file called 
 fujitsu.c ( or even anything similar) to edit.  Does anyone have any 
 other suggestions?
 
 Thanks,
 
 Richard
 
 Oliver Schirrmeister wrote:
 
 Am Don, 2002-12-19 um 18.03 schrieb Richard Reina:
   
 
 Does anyone know how I can get my fujitsu 3091DC to scan monochrome 
 (simple black  white)?  My choice of modes that are listed in scanimage 
 --help --device are:  Gray, Lineart, Halftone and Color.  I'm not sure 
 what Halftone is but it does not work.  Lineart gives me a nice small 
 image but the black and white is inverted, Gray is too big.  Any help 
 would be greatly appreciated.
 
 
 
 Halftone does not work with the 3091 because the driver doesn't
 implement it. 
 Lineart returns black  white images (1bit/pixel). If the image is
 inverted you might try to set the RIF (reverse image format) option.
 In file fujitsu.c function setWindowParam you can find the following
 line:  
   if (s-model == MODEL_3092)
 {
   set_WD_rif (buffer, SANE_TRUE);
 }
   else
 {
   set_WD_rif (buffer, s-reverse);
 }
 
 You can try the same for MODEL_3091.
 
 Oliver
 
 ___
 Sane-devel mailing list
 sane-de...@www.mostang.com
 http://www.mostang.com/mailman/listinfo/sane-devel




[sane-devel] How to scan monorome with fujitsu 3091DC.

2002-12-20 Thread Oliver Schirrmeister
Am Don, 2002-12-19 um 18.03 schrieb Richard Reina:
 Does anyone know how I can get my fujitsu 3091DC to scan monochrome 
 (simple black  white)?  My choice of modes that are listed in scanimage 
 --help --device are:  Gray, Lineart, Halftone and Color.  I'm not sure 
 what Halftone is but it does not work.  Lineart gives me a nice small 
 image but the black and white is inverted, Gray is too big.  Any help 
 would be greatly appreciated.

Halftone does not work with the 3091 because the driver doesn't
implement it. 
Lineart returns black  white images (1bit/pixel). If the image is
inverted you might try to set the RIF (reverse image format) option.
In file fujitsu.c function setWindowParam you can find the following
line:  
  if (s-model == MODEL_3092)
{
  set_WD_rif (buffer, SANE_TRUE);
}
  else
{
  set_WD_rif (buffer, s-reverse);
}

You can try the same for MODEL_3091.

Oliver



[sane-devel] how to detect the scan_source

2002-11-11 Thread Oliver Schirrmeister
Hi,

Wouldn't it be usefull to make it a well known option or provide a
function where a program can ask if the feeder is enabled?

Oliver

 Hi,
 
 
 On Fri, Nov 08, 2002 at 02:07:36PM +0100, Oliver Schirrmeister wrote:
 
  Is there a way to detect if the user wants to scan with
 
  the ADF or from flatbed? I've found SANE_NAME_SCAN_SOURCE
 
  but the value of that option depends on the backend?
 
 
 Yes, it's not a well-known option.
 
 
  I'd like to write a tool like scanimage. The user can
 
  select the scanner and the scansource. If flatbed is 
 
  selected I want to scan one image only. If the ADF is
 
  selected I want to scan as long the ADF is not empty.
 
 
 XSane has an option setting that allows the user to select which of
 
 the scan sources is an ADF. Maybe you can go that way.
 




[sane-devel] SANE2 standard proposal

2002-11-11 Thread Oliver Schirrmeister

Hi,

some scanners support hardware compression, for example jpeg or
CCITT FAX3. 
I think there should be a well known option 'compression' with
values 'fax3', 'fax4', 'jpeg', others?

Oliver



[sane-devel] how to detect the scan_source

2002-11-08 Thread Oliver Schirrmeister
Is there a way to detect if the user wants to scan with
the ADF or from flatbed? I've found SANE_NAME_SCAN_SOURCE
but the value of that option depends on the backend?

I'd like to write a tool like scanimage. The user can
select the scanner and the scansource. If flatbed is 
selected I want to scan one image only. If the ADF is
selected I want to scan as long the ADF is not empty.


Thanks

Oliver



[sane-devel] Duplex and Halftone Problem with Fujitsu M3091DC

2002-08-14 Thread Oliver Schirrmeister
Hi Frank,

 Scanimage works basically but the option -duplex both doesn't work and
 -mode Halftone generates an invalid argument error. -mode Lineart
 only generates inverse images (white characters on black paper).

I don't have a Fujitsu M3091 to try this.
To get the reason of the invalid argument error you can set the
environment variable SANE_DEBUG_FUJITSU to 20. Try to scan again
and mail me the output.

inverse image in mode lineart: According to the M3091 manual there
is an option to inverse the image but it's not available in the driver.
You can try to change the line
  set_WD_rif (buffer, s-reverse);
to
  set_WID_rif (buffer, SANE_TRUE);
in function setWindowParam() in file fujitsu.c
If this works I can make this option available for the 3091.

Oliver


[sane-devel] Support for A£ scanners

2002-07-09 Thread Oliver Schirrmeister
nofillI am in the market for an A3 scanner.
I cannot tell from your supported list which are A3.

Cann anyone point me to a list of linux  supported A3 scanners

I don't know about others but the fujitsu M3096 and M3097 are A3 scanners.

Oliver
/nofill


[sane-devel] Sane on Acer 320U 320P, Fujitsu M3096G, HP3300C

2002-04-24 Thread Oliver Schirrmeister
3. Fujitsu M3096G (SCSI) - This is a Black  White high speed scanner.
The Sane driver recognizes the scanner, but when it attempts to scan in
Lineart mode, give an error.

I have no problems with the 3097 (I thought this scanner is almost equal
to the 3096). What error do you get? If you like you can set the debug-level
to 20 and mail me the output.

Regards,

Oliver


[sane-devel] Support for Panasonic scanners

2002-02-21 Thread Oliver Schirrmeister
nofillOn Wed, Feb 20, 2002 at 09:40:07AM -0800, Joe Hudson wrote:
I'd like to use SANE to work with a Panasonic KV-S2025 but I don't
 see any support for any Panasonic scanners at all. 
 Does anybody know if they're available under another name or such?

If it's a SCSI or USB scanner, what does sane-find-scanner print?

 If not, does anyone know why there's no support, I mean, it is just
 that it happens that nobody's gotten around to it yet, or is it
 because Panasonic won't release specs?

Maybe the problem is that there are not very many of these scanners?
At least I have didn't even know that there are Panasonic scanners.

It's not easy to get the SCSI specification of the KV-S2025 from Panasonic. 
You also have to sign a 'non disclosure'  contract. So you are not allowed to 
publish a SANE driver.

Oliver/nofill


[sane-devel] Ricoh IS410

2001-11-15 Thread Oliver Schirrmeister
nofillI've found the Ricoh IS410 in the list of sane backends (IBM backend).
Is it compatible with the ibm2456? Can anybody tell me where to find
the oem manual of this scanner?

Thanks

Oliver/nofill


[sane-devel] m3096g changes

2001-08-30 Thread Oliver Schirrmeister
nofillHi, 

I've added the following features to the m3096g scanner backend:
- support of the ipc2/3 and cmp2 options
- duplex scanner support (M3093DG or M4097D)
- some constraint checking for the M3093GX
- use of the Virtual product data
- paper format spezification when ADF is used.

I've informed the author of the backend about the changes several
times by mail but he didn't answer.
If anybody is intrested in the changes or even want's to include these
changes to the main stream send me an e-mail or tell me where to
put the changes.

Oliver/nofill