CONFIGURATION


 
 

CONFIGURATION:

The configuration file for this backend resides in
/usr/local/etc/sane.d/umax.conf.
Its contents is a list of device names that correspond to UMAX scanners. Empty lines and lines starting with a hash mark (#) are ignored. A sample configuration file is shown below:
 
#scsi Vendor Model Type Bus Channel ID LUN
scsi UMAX * Scanner * * * * *
/dev/scanner
# this is a comment
/dev/sge
The special device name must be a generic SCSI device or a symlink to such a device. To find out to which device your scanner is assigned and how you have to set the permissions of that device, have a look at sane-scsi.

SCSI ADAPTER TIPS:

The UMAX-scanners do block the scsi-bus for a few seconds while scanning. It is not necessary to connect the scanner to its own SCSI-adapter. But if you need short response time for your SCSI-harddisk (e.g. if your computer is a file-server), I suggest you use an own SCSI-adapter for your UMAX-scanner.
The SCSI-adapters that are shipped with some Umax-scanners are very simple ones. I suggest not to use them. If you really want to try: the UDS-IS11 uses a DTC3181E chip (compatible to NCR5380). On linux you may have the chance to get it work with the recent g_NCR5380-driver. The card does not have IRQ/DMA. Try the following option for kernel boot option:

        dtc_3181e=0x280,255

 or use the following command:

        insmod g_NCR5380 ncr_irq=255 ncr_addr=0x280 dtc_3181e=1

     - ncr_irq=255 : no IRQ, no DMA
     - ncr_irq=254 : autoprobe IRQ
     - ncr_addr       : can be: 0x220 0x240 0x280 0x2A0 0x2C0 0x300 0x320 0x340
 

For  informations about the umax-scsi-cards take a look here.

See the relevant hardware FAQs and HOWTOs for your platform for more information.
See also: sane-scsi

FILES:

  • The backend configuration file: /usr/local/etc/sane.d/umax.conf
  • The static library implementing this backend: /usr/local/lib/sane/libsane-umax.a
  • The shared library implementing this backend : /usr/local/lib/sane/libsane-umax.so
    • (present on systems that support dynamic loading)

    ENVIRONMENT:

  • SANE_DEBUG_UMAX
  • see backends
  • see frontends
    • If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity:
    SANE_DEBUG_UMAX values
    Number
    Remark
    0 
    		 print important errors (printed each time) 
    1 
    		 print errors 
    2 print sense
    3
    		 print warnings 
    4 print scanner-inquiry
    5 
    		 print informations
    6 print less important informations
    7 print called procedures
    8 print reader_process messages
    10 
    		 print called sane-init-routines 
    11
    		 print called sane-procedures
    12
    		 print sane-infos
    13
    		 print sane option control messages

    Example:

    export SANE_DEBUG_UMAX=8
    SANE-UMAX-index

    This page has been changed on 3rd.  june 1999