scanDoX - The Linux  Scanner Driver for your Fujitsu Scanner Linux scanner software certified by Fujitsu Germany
scanDoX - The Fujitsu Scanner Driver for Linux
quickoverview features documentation frequently asked questions order and buy download
overview features documentation and how to frequently asked questions order and buy download


  The CLI-Examples

The following parameters are examples !
Because the parameters depend on the connected scanner.
These examples were made on a Fujitsu 4220 duplex scanner with flatbed unit:
 
Back to CLI-index

The syntax of scanDoX follows always the same principle.

Example 1: Scanning one page

Take a look at this line:
scanDoX --device /dev/sg2 --mode Gray --resolution 300 --format tiff > scanDoX-test.tif
Let's split this line:
                            
scanDoX Ok, this is the commad you are calling. Not much to say about that
--device /dev/sg2 Selects the device to scan from. This is needed since scanDoX can trigger more than one scanner at same time. To figure out on which device the scanner is connected use sane-find-scanner or use scanDoX-setup
--mode Gray Selects the scan mode. In this case we want to scan a grayscale image
--resolution 300 Selects the dpi resolution for scanning. If not given scanDoX will use the scanner default value.
--format tiff Selects the output format. The default is pnm (portable anymap - a Linux specific exchange format).
On some scanners there is a possibility to scan with hardware jpeg-compression (we surely support that feature).
But in this case we want to aquire a tiff image.
> output redirect
A cool feature of Linux is that you can easily send the info that normally gets printed on the screen into a file instead. This is called redirecting output. For example, ls > newFile.txt, will list all files in a directory and write them to a file called "newFile.txt". If "newFile.txt" already exists, the contents will be overwritten, otherwise a new file will be created.
scanDoX_test.tif This is the filename to place the scanned data.

Example 2: ADF Scanning

Now we are going to use the ADF for a so called batch-scan.
scanDoX --device /dev/sg2 --mode Lineart --format tiff --batch-count=10 --batch=scanDoX%03d.tif 2>&1
                            
scanDoX The command again
--device /dev/sg2 The device again
--mode Lineart This time we scan linart
--format tiff Again we want tiff
--batch-count=10 batch-count tells scanDoX that you want to scan more than one page. How much more is defined with the value given. In this case 10. This commands scanDoX to scan 10 pages. If the feeder is out of documents before 10 is reaches scanDoX will show a message.
--batch=scanDoX%03d.tif

This is an addition to batch-count the batch parameter is needed. Batch defines a name pattern for the names of the output-file.
%03d means reserve 3 decimal digits for consecutive numbering.
This means the files are numbered like this:
scanDoX001.tif
scanDoX002.tif
scanDoX003.tif etc.

2>&1 This is optional. It is another variant of the output redirect.
It redirects STDERR to STDOUT.
So you can see all the errors that might occur on your console instead of looking in the log file.
Tipp: If you want to scann everything till there is no more paper in the feeder, just give a value like --batch-count=999.

Example 3: Duplex Scanning

Ok let's look behind it. Now we are performing a single page duplex scan.
scanDoX --device /dev/sg2 --mode Lineart --format tiff --duplex=both --batch-count=2 --batch=scanDoX%03d.tif 2>&1
                            
scanDoX The command again
--device /dev/sg2 The device again
--mode Lineart This time we scan linart
--format tiff Again we want tiff
--duplex=both I guess this is self explaining. It enables the duplex support to scan both sides of the page.
--batch-count=2 With the duplex option comes an important specialty in batch-count.
It has to be doubled when duplex scanning.
So if you want to scan 10 pages duplex, batch-count has to be 20 !
--batch=scanDoX%03d.tif

The same as in Example 2

2>&1 Again it's optional.

 

  Back to CLI-index
 

<< PreviousNext >>
  2002-2006 mu-tec GmbH • we consult • we program • we secure • ContactAdressesLinksImpressum