1sane-teco2(5)            SANE Scanner Access Now Easy            sane-teco2(5)
2
3
4

NAME

6       sane-teco2 - SANE backend for TECO / RELISYS scanners
7

DESCRIPTION

9       The  sane-teco2  library  implements  a  SANE (Scanner Access Now Easy)
10       backend that provides access to some TECO SCSI flatbed  scanners.  This
11       backend  should  be considered beta-quality software! TECO scanners are
12       sold under various brands like Mustek, Relisys, Piotech, Primax, TRUST.
13       This backend may or may not support yours.
14
15       The scanners that should work with this backend are:
16
17                 Vendor Model               TECO model      status
18              --------------------------- --------------  -----------
19                Mustek ScanMagic 4830S      VM3575         untested
20                Primax Jewel 4800           VM356A         good
21                Primax Profi 9600           VM6575         basic
22                Primax Profi 19200          VM6586         good
23                Relisys APOLLO Express 3    VM356A         basic
24                Relisys APOLLO Express 6    VM6565         good
25                Relisys APOLLO Express 12   ?              untested
26                Relisys AVEC II S3          VM3564         good
27                Relisys AVEC Super 3        VM3575         basic
28                Relisys SCORPIO Pro         VM6575         good
29                Relisys SCORPIO Pro-S       VM6586         untested
30                Relisys SCORPIO Super 3     VM3575         good
31
32       For  all these scanners, lineart and gray mode work well. However, most
33       of them do not support more than a  handful  of  resolutions  in  color
34       mode.  See the backend home page (under AUTHOR) for the exact status of
35       each scanner.
36
37       Note that the untested scanner will  not  be  directly  supported.  You
38       should contact the author for that.
39
40       The  TECO VM number can usually be found at the back of the scanner. It
41       is also part of the FCC ID.
42
43       The options the backend supports can either be selected through command
44       line  options  to programs like scanimage(1) or through GUI elements in
45       xscanimage(1), xsane(1), quiteinsane(1) or kooka(1).
46
47       If you have any success with a scanner not listed here, or if  you  no‐
48       tice  any  strange behavior, please report to the backend maintainer or
49       to the SANE mailing list.
50
51

OPTIONS

53       Valid command line options and their syntax can be listed by using:
54
55              scanimage --help -d teco2
56
57
58       Scan Mode
59
60
61       --mode Lineart|Gray|Color
62              selects the basic mode of operation of the scanner.  The Lineart
63              mode  is  black  and white only (1 bit).  Gray mode will produce
64              256 levels of gray (8 bits).  Color will produce a 24 bits color
65              image.
66
67
68       --resolution 1..600
69              Selects  the resolution for a scan. The scanner can do all reso‐
70              lutions between 1 and 600, in increments of 1, for  Lineart  and
71              Gray.  For Color, a restricted set of resolutions are available.
72
73              Note: All values with ydpi > 300 (300 x 600) or 600 (600 x 1200)
74              result in a wrong proportion for the scan. The proportion can be
75              adjusted with the following convert(1) command from imagemagick:
76              convert -geometry (dpi/max_xdpi * 100%)x100%
77              max_xdpi is for the vm3575 constant with 300 dpi e.g. 600dpi ad‐
78              just with: convert -geometry 200%x100%
79
80
81       --preview
82              requests a preview scan. The resolution used for that scan is 50
83              dpi (for VM356A and VM6575 75 dpi) and the scan area is the max‐
84              imum allowed.  The scan mode is user selected.  The  default  is
85              "no".
86
87
88       Geometry options
89
90
91       -l, -t, -x,  -y
92              Control the scan area: -l sets the top left x coordinate, -t the
93              top left y coordinate, -x selects the width and -y the height of
94              the  scan  area.  All parameters are specified in millimeters by
95              default.
96
97
98
99       Enhancement options
100
101
102       --custom-gamma (no custom gamma option for the VM3564 and VM356A)
103              (color mode only) allows the user to specify a gamma table  (see
104              the next 3 parameters).
105
106

OPTIONS FOR COLOR MODE

108       These options are valid for scan mode Color only.
109
110
111       --red-gamma-table
112              Can  be  used to download a user defined gamma table for the red
113              channel. The table must be 256 bytes long.
114
115
116       --green-gamma-table
117              Can be used to download a user defined gamma table for the green
118              channel. The table must be 256 bytes long.
119
120
121       --blue-gamma-table
122              Can  be used to download a user defined gamma table for the blue
123              channel. The table must be 256 bytes long.
124
125

OPTIONS ONLY FOR VM3564, VM356A, VM3575 and VM6575

127       These options are only available for VM3564, VM356A, VM3575 and  VM6575
128       models.
129
130       --white-level-r 0..64
131              Selects  what  red  radiance level should be considered "white",
132              when scanning some sheets  by  changing  the  calibration  value
133              loaded into the scanner. Scale 0..64 in steps of 1.
134
135
136       --white-level-g 0..64
137              Selects  what green radiance level should be considered "white",
138              when scanning some sheets  by  changing  the  calibration  value
139              loaded into the scanner. Scale 0..64 in steps of 1.
140
141
142       --white-level-b 0..64
143              Selects  what  blue radiance level should be considered "white",
144              when scanning some sheets  by  changing  the  calibration  value
145              loaded into the scanner. Scale 0..64 in steps of 1.
146
147
148

CONFIGURATION FILE

150       The  configuration  file /etc/sane.d/teco2.conf supports only one item:
151       the device name to use (eg /dev/scanner).
152
153
154

FILES

156       /usr/lib64/sane/libsane-teco2.a
157              The static library implementing this backend.
158
159       /usr/lib64/sane/libsane-teco2.so
160              The shared library implementing this backend (present on systems
161              that support dynamic loading).
162
163
164

ENVIRONMENT

166       SANE_DEBUG_TECO2
167              If the library was compiled with debug support enabled, this en‐
168              vironment variable controls the debug level  for  this  backend.
169              E.g.,  a  value  of 128 requests all debug output to be printed.
170              Smaller levels reduce verbosity.
171
172       SANE_TECO2_CAL_ALGO
173              Either 0 or 1. Selects the  algorithm  for  the  calibration.  A
174              value  of  1  seems  to give better scans on the VM356A, VM3575.
175              Feedback on it is welcome.  For VM3564, VM356A,  VM3575,  VM6575
176              default 1.  For other supported types default 0.
177
178
179

LIMITATIONS

181       The  windows TWAIN driver has many more options than this SANE backend.
182       However they are only software adjustments. This  backend  only  imple‐
183       ments what the scanner can support.
184
185
186

BUGS

188       Plenty. Parts of this backend are still under development.
189
190
191

SEE ALSO

193       sane(7), sane-scsi(5), scanimage(1), xscanimage(1), xsane(1)
194
195
196

AUTHORS

198       Frank Zago
199              http://www.zago.net/sane/#teco2
200
201       The package is actively maintained by Gerard Klaver.
202              http://gkall.hobby.nl/teco2.html
203
204
205
206
207

CREDITS

209       Thanks to:
210
211       Gerard  Klaver  for  his  relentless  VM3575 testings and contributed a
212       patch to support the VM3564 and VM356A.
213
214       Mark Plowman for providing the first SCSI traces from a VM3575.
215
216       Andreas Klaedtke for providing the first SCSI traces from a VM6586  and
217       for his testing, and to Stefan von Dombrowski for his testing.
218
219       Nicolas  Peyresaubes  for providing the first SCSI traces from a VM656A
220       and for his testing.
221
222       Dave Parker for testing the support for the VM6575.
223
224       Michael Hoeller for testing the support for the VM356A.
225
226       Christoph Hoeffner for testing the support for the VM3564 (Relisys AVEC
227       II S3 firmware 1.09).
228
229
230
231                                  14 Jul 2008                    sane-teco2(5)
Impressum