sane-cardscan(5)

✨ NAME ✨

okay bestie, meet sane-cardscan(5) - SANE backend for Corex CardScan usb scanners. iconic.


πŸ¦‹ DESCRIPTION πŸ¦‹

The sane-cardscan library implements a SANE (Scanner Access Now Easy) backend that gives you access to the Corex CardScan 800c & 600c small-format scanners. obsessed.

Lowkey important: this backend supports only grayscale and color modes and media of (theoretically) infinite length. <em>theoretically</em> is doing a lot of work there, bestie. 😭

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. fr fr, that's the move.


πŸ’… OPTIONS πŸ’…

The cardscan backend supports the following options, periodt:

  • --mode Gray|Color β€” Selects the mode for the scan.

πŸŽ€ CONFIGURATION FILE πŸŽ€

The config file cardscan.conf is used to tell the backend how to look for scanners and to provide options that control how the backend operates. This file is read each time the frontend asks the backend for a list of scanners, generally only when the frontend starts. If the config file is missing, the backend will use a set of compiled defaults, which are identical to the default configuration file shipped with SANE. no config? no problem, it's got defaults.

Scanners can be specified in the config file in 2 ways:

  • "usb 0x04c5 0x1042" (or other vendor/product ids) β€” Requests the 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 scanners. This method is untested. just so you know.

Additionally, there are two configuration options that 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.

🌈 ENVIRONMENT 🌈

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

😭 KNOWN ISSUES 😭

okay bestie, listen up, because these are the real ones:
  • The scanner does not seem to have much control possible, 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 tools. iykyk.
  • The backend also does not send all the commands that the windows driver does, so it may not function the same. just a heads up.
  • The backend does not have the calibration or ejection options of the windows driver. no cap.

πŸ‘‘ CREDITS πŸ‘‘

The hardware to build this driver was provided to the author by: Jeff Kowalczyk <jtk a t yahoo d o t com>. slay, thank you for your service 🫑


πŸ¦‹ SEE ALSO πŸ¦‹


πŸ’œ AUTHOR πŸ’œ

m. allan noah: <kitno455 a t gmail d o t com> . the icon behind it all.


and that's the whole tea, bestie! this is sane-cardscan(5) from SANE Scanner Access Now Easy, dated 10 Feb 2010. stay slay πŸ’…βœ¨

πŸ“¦ where this page comes from