sane-cardscan(5)          (10 Feb 2010)          sane-cardscan(5)

          sane-cardscan - SANE backend for Corex CardScan usb scanners

          The sane-cardscan library implements a SANE (Scanner Access
          Now Easy) backend which provides access to the Corex Card-
          Scan 800c & 600c small-format scanners.

          The backend supports only grayscale and color modes and
          media of (theoretically) infinite length.

          This backend may support other scanners. The best way to
          determine level of support is to get a trace of the windows
          driver in action, and send it to the author.

          The cardscan backend supports the following options:

          --mode Gray|Color
               Selects the mode for the scan.

          The configuration file cardscan.conf is used to tell the
          backend how to look for scanners, and provide options con-
          trolling the operation of the backend.  This file is read
          each time the frontend asks the backend for a list of scan-
          ners, generally only when the frontend starts. If the con-
          figuration file is missing, the backend will use a set of
          compiled defaults, which are identical to the default con-
          figuration file shipped with SANE.

          Scanners can be specified in the configuration file in 2

          "usb 0x04c5 0x1042" (or other vendor/product ids)
               Requests backend to search all usb buses in the system
               for a device which uses that vendor and product id. The
               device will then be queried to determine if it is a
               cardscan scanner.

          "usb /dev/usb/scanner0" (or other device file)
               Some systems use a kernel driver to access usb scan-
               ners. This method is untested.

          Additionally, there are two configuration options that

     Page 1                       Plan 9             (printed 5/26/22)

     sane-cardscan(5)          (10 Feb 2010)          sane-cardscan(5)

          control the protocol used by the backend:

          "lines_per_block 16" (or other number from 1 to 32)
               Controls the number of lines of image data which will
               be acquired in each pass.  Older scanners will require
               this number set lower, often 1.

          "has_cal_buffer 1" (1 or 0)
               Causes the backend to get calibration data from scanner
               during initialization.  Older scanners do not support
               this request, and must be set to 0.

          The backend uses a single environment variable,
          SANE_DEBUG_CARDSCAN, which enables debugging output to
          stderr. Valid values are:

               5  Errors
               10 Function trace
               15 Function detail
               20 Option commands
               25 SCSI/USB trace
               30 SCSI/USB detail
               35 Useless noise

               The scanner does not seem to have much control possi-
               ble, so the backend cannot set x/y coordinate values,
               resolutions, etc. These things could be simulated in
               the backend, but there are plenty of command line
               The backend also does not send all the commands that
               the windows driver does, so it may not function the
               The backend does not have the calibration or ejection
               options of the windows driver.

          The hardware to build this driver was provided to the author
          by: Jeff Kowalczyk <jtk a t yahoo d o t com>.

          sane(7), sane-usb(5)

          m. allan noah: <kitno455 a t gmail d o t com> .

     Page 2                       Plan 9             (printed 5/26/22)