sane-hp5400(5)

✨ sane-hp5400 ✨

okay bestie, this is the manual page for sane-hp5400, part of SANE β€” the Scanner Access Now Easy life πŸ’…


🌸 NAME 🌸

sane-hp5400 β€” the SANE backend for Hewlett-Packard 54XX scanners. yes, it's giving "old but iconic" πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

no synopsis section in this one, bestie β€” it's a config/backend page, so just read on πŸ’–


πŸ‘‘ DESCRIPTION πŸ‘‘

so the sane-hp5400 library implements a SANE (Scanner Access Now Easy) backend that gives you access to these Hewlett-Packard USB flatbed scanners:

ScanJet 5400C
ScanJet 5470C
ScanJet 5490C

more details live on the hp5400 backend homepage at http://hp5400backend.sourceforge.net/ 🫢

⚠️ bestie listen to me: this is ALPHA software. keep your hand at the scanner's plug and unplug it if the head bumps at the end of the scan area. seriously. also check the BUGS section below, iykyk πŸ’€

if you own a scanner other than the ones listed above that works with this backend, please let us know! send us the scanner's exact model name and the USB vendor and device ids (e.g. from /proc/bus/usb/devices, sane-find-scanner(1) or syslog). and like β€” even if the scanner's name is only slightly different from the models mentioned above, still tell us, no cap. every data point slays πŸ™ˆ


πŸ’œ CONFIGURATION πŸ’œ

the contents of the hp5400.conf file is a list of usb lines containing vendor and product ids that correspond to USB scanners. the file can also contain the names of device files that correspond to an HP 54XX scanner. empty lines and lines starting with a hash mark (#) are ignored.

the scanners are autodetected by usb vendor_id product_id statements which are already included into hp5400.conf. "vendor_id" and "product_id" are hexadecimal numbers that identify the scanner. if autodetection does not work, add the device name of your scanner to the configuration file, e.g. /dev/usb/scanner0 ✨


πŸŽ€ FILES πŸŽ€

  • /etc/sane.d/hp5400.conf β€” the backend configuration file (see also description of SANE_CONFIG_DIR below).
  • /usr/lib64/sane/libsane-hp5400.a β€” the static library implementing this backend.
  • /usr/lib64/sane/libsane-hp5400.so β€” the shared library implementing this backend (present on systems that support dynamic loading).

🌈 ENVIRONMENT 🌈

  • SANE_CONFIG_DIR β€” this environment variable specifies the list of directories that may contain the configuration file. on *NIX systems, the directories are separated by a colon (:), under OS/2, they are separated by a semi-colon (;). if this variable is not set, the configuration file is searched in two default directories: first, the current working directory (.) and then in /etc/sane.d. if the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. for example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories tmp/config, ., and /etc/sane.d being searched (in this order). 🧚
  • SANE_DEBUG_HP5400 β€” if the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. higher debug levels increase the verbosity of the output.

example:

export SANE_DEBUG_HP5400=4

⭐ SEE ALSO ⭐

sane(7), sane-usb(5), sane-find-scanner(1), http://hp5400backend.sourceforge.net/ πŸ”₯


πŸ“ AUTHOR πŸ“

Martijn van Oosterhout <kleptog@svana.org>, Thomas Soumarmon <soumarmt@nerim.net>. manpage by Henning Meier-Geinitz <henning@meier-geinitz.de>. absolute icons, all three of them πŸ‘‘


πŸ’€ BUGS πŸ’€

scanning is only tested with Linux/ix86/gcc. be careful when testing on other operating systems and especially on big-endian platforms. the scanner may get wrong data. like, actually be careful β€” this is not a drill 😭


that's the whole page, bestie β€” this one's from SANE's sane-hp5400(5) manpage, dated 13 Jul 2008. go forth and scan responsibly 🫢✨

πŸ“¦ where this page comes from