|sane-magicolor(5)||SANE Scanner Access Now Easy||sane-magicolor(5)|
sane-magicolor - SANE backend for KONICA MINOLTA magicolor scanners
The sane-magicolor backend supports KONICA MINOLTA magicolor scanners connected via USB or LAN. Currently, only the magicolor 1690MF device is supported, no other devices with the same scanning protocol are known.
The following scanner should work with this backend:
Vendor: KONICA MINOLTA
Model: magicolor 1690MF
This section describes the backend's configuration file entries. The file is located at:
For a proper setup, at least one of the following entries are needed:
- net autodiscovery
net [IP ADDRESS] [DEVICE-ID]
usb [VENDOR-ID] [DEVICE-ID]
- The backend configuration file
- The static library implementing this backend.
- The shared library implementing this backend (present on systems that support dynamic loading).
- This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, 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).
- 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_MAGICOLOR=127
To obtain debug messages from the backend, set this environment variable before calling your favorite frontend (e.g. xscanimage(1)).
Example: SANE_DEBUG_MAGICOLOR=65 xscanimage
KNOWN BUGS AND RESTRICTIONS¶
Large color scans may sometimes timeout due to unknown reasons (the scanner simply stops returning data)
Cancelling large scans may lock up the scanner.
Reinhold Kainhofer <firstname.lastname@example.org>
|10 Jan 2011|