sane-teco2(5)

📦
version 1.4.0 · 8 versions
, in fedora 43, fedora 44, opensuse-leap 16.0

💅 sane-teco2 — ok so this is the vibe

Hey bestie, welcome to the sane-teco2 page from the SANE collection — SANE Scanner Access Now Easy, the manual section 5 situation, yes yes. Grab a snack, we're talking scanners 🎀

✨ NAME ✨

sane-teco2 — the SANE backend for TECO / RELISYS scanners. That's the whole name, that's the whole job 💖

🌸 DESCRIPTION 🌸

Okay so the sane-teco2 library implements a SANE (Scanner Access Now Easy) backend that gives you access to some TECO SCSI flatbed scanners. And like — be aware — this backend should honestly be considered beta-quality software! It's giving "we're so back but also are we". TECO scanners get sold under a whole bunch of brands, like Mustek, Relisys, Piotech, Primax, TRUST. This backend may or may not support yours. No cap. 🙈

The scanners that should work with this backend are:

          Vendor Model               TECO model      status
       --------------------------- --------------  -----------
         Mustek ScanMagic 4830S      VM3575         untested
         Primax Jewel 4800           VM356A         good
         Primax Profi 9600           VM6575         basic
         Primax Profi 19200          VM6586         good
         Relisys APOLLO Express 3    VM356A         basic
         Relisys APOLLO Express 6    VM6565         good
         Relisys APOLLO Express 12   ?              untested
         Relisys AVEC II S3          VM3564         good
         Relisys AVEC Super 3        VM3575         basic
         Relisys SCORPIO Pro         VM6575         good
         Relisys SCORPIO Pro-S       VM6586         untested
         Relisys SCORPIO Super 3     VM3575         good

For all these scanners, lineart and gray mode work well. But lowkey most of them don't support more than a handful of resolutions in color mode. If you want the exact status of each scanner, go check the backend home page — it's linked down in AUTHORS, iykyk. 👑

Real talk: the untested scanners will not be directly supported. You should contact the author for that one. Don't just vibe and hope, bestie 😭

The TECO VM number can usually be found at the back of the scanner. It's also part of the FCC ID. Sleuth it out 🕵️‍♀️

The options the backend supports can either be selected through command line options to programs like scanimage(1), or through GUI elements in xscanimage(1), xsane(1), quiteinsane(1) or kooka(1). Pick your fighter, they all slay ✨

If you have any success with a scanner not listed here, or if you notice any strange behavior, please report to the backend maintainer or to the SANE mailing list. Be the main character who files the bug report 🫶

🦋 OPTIONS 🦋

Want the whole menu? Valid command line options and their syntax can be listed by running:

scanimage --help -d teco2

Look at her go 💅

🎀 Scan Mode

  • --mode Lineart|Gray|Color — selects the basic mode of operation of the scanner. Lineart mode is black and white only (1 bit). Gray mode will produce 256 levels of gray (8 bits). Color will produce a 24 bits color image. Three moods, all iconic.
  • --resolution 1..600 — selects the resolution for a scan. The scanner can do all resolutions between 1 and 600, in increments of 1, for Lineart and Gray. For Color, a restricted set of resolutions are available. Inconsistent queen but we love her 🌈
⚠️ Note: all values with vertical resolution in dpi > 300 (300 x 600) or 600 (600 x 1200) result in a wrong proportion for the scan. The proportion can be adjusted with the following convert(1) command from imagemagick: convert -geometry (dpi/max_xdpi * 100%)x100% max_xdpi is for the vm3575 constant with 300 dpi — e.g. 600dpi adjust with: convert -geometry 200%x100%
  • --preview — requests a preview scan. The resolution used for that scan is 50 dpi (for VM356A and VM6575 it's 75 dpi) and the scan area is the maximum allowed. The scan mode is user selected. The default is "no". Little sneak peek energy 🍓

💜 Geometry options

  • -l, -t, -x, -y — control the scan area: -l sets the top left x coordinate, -t the top left y coordinate, -x selects the width and -y the height of the scan area. All parameters are specified in millimeters by default. Framing the shot, very director-of-photography of you 📸

🧚 Enhancement options

  • --custom-gamma (no custom gamma option for the VM3564 and VM356A) — (color mode only) allows the user to specify a gamma table (see the next 3 parameters). The "next 3 parameters" are literally the next section, keep reading bestie, we got you 🌸

🔥 OPTIONS FOR COLOR MODE 🔥

These options are valid for scan mode Color only. Color girlies only, everyone else look away 🙈

  • --red-gamma-table — can be used to download a user defined gamma table for the red channel. The table must be 256 bytes long.
  • --green-gamma-table — can be used to download a user defined gamma table for the green channel. The table must be 256 bytes long.
  • --blue-gamma-table — can be used to download a user defined gamma table for the blue channel. The table must be 256 bytes long.

Three tables, three channels, 256 bytes each, no shortcuts 💅

⭐ OPTIONS ONLY FOR VM3564, VM356A, VM3575 and VM6575 ⭐

These options are only available for VM3564, VM356A, VM3575 and VM6575 models. If that's not your model, this whole section is not for you, and that's okay 🫶

  • --white-level-r 0..64 — selects what red radiance level should be considered "white", when scanning some sheets by changing the calibration value loaded into the scanner. Scale 0..64 in steps of 1.
  • --white-level-g 0..64 — selects what green radiance level should be considered "white", when scanning some sheets by changing the calibration value loaded into the scanner. Scale 0..64 in steps of 1.
  • --white-level-b 0..64 — selects what blue radiance level should be considered "white", when scanning some sheets by changing the calibration value loaded into the scanner. Scale 0..64 in steps of 1.

Look at you, tuning whiteness levels like a pro. Calibration icon behavior honestly 💜

🌈 CONFIGURATION FILE 🌈

The configuration file /etc/sane.d/teco2.conf supports only one item: the device name to use (eg /dev/scanner). That's it. One thing. Minimalist queen. She said "I only do one job" 💅

💖 FILES 💖

  • /usr/lib64/sane/libsane-teco2.a — the static library implementing this backend.
  • /usr/lib64/sane/libsane-teco2.so — the shared library implementing this backend (present on systems that support dynamic loading).

Two files, both shipped with love 🎀

✨ ENVIRONMENT ✨

  • SANE_DEBUG_TECO2 — 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. Crank it to 128 when you're in your detective era 🔍
  • SANE_TECO2_CAL_ALGO — either 0 or 1. Selects the algorithm for the calibration. A value of 1 seems to give better scans on the VM356A, VM3575. Feedback on it is welcome. For VM3564, VM356A, VM3575, VM6575 default 1. For other supported types default 0. Ngl this one's a whole vibe experiment, tell them what you find 👑

😭 LIMITATIONS 😭

The windows TWAIN driver has many more options than this SANE backend. But plot twist — those are only software adjustments. This backend only implements what the scanner can support. Hardware honesty era, we respect it 🫶

💀 BUGS 💀

Plenty. Parts of this backend are still under development. Not me reading "Plenty." and cackling 😭 Iconic levels of self-awareness.

🦋 SEE ALSO 🦋

sane(7), sane-scsi(5), scanimage(1), xscanimage(1), xsane(1) — go read these too, they're all linked in the group chat ✨

👑 AUTHORS 👑

🎀 CREDITS 🎀

Thanks to:

  • Gerard Klaver for his relentless VM3575 testings and contributed a patch to support the VM3564 and VM356A. Relentless is the correct word and we're obsessed 🙌
  • Mark Plowman for providing the first SCSI traces from a VM3575.
  • Andreas Klaedtke for providing the first SCSI traces from a VM6586 and for his testing, and to Stefan von Dombrowski for his testing.
  • Nicolas Peyresaubes for providing the first SCSI traces from a VM656A and for his testing.
  • Dave Parker for testing the support for the VM6575.
  • Michael Hoeller for testing the support for the VM356A.
  • Christoph Hoeffner for testing the support for the VM3564 (Relisys AVEC II S3 firmware 1.09).

Absolute legends, every single one 💖

Okay that's the whole page bestie, you're officially a TECO scholar 🎓✨ This one's dated 14 Jul 2008 and comes to you from the SANE Scanner Access Now Easy crew — go forth, scan responsibly, and remember: if it's untested, contact the author before you get any ideas 💅🦋

📦 where this page comes from