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 or through GUI elements in
45       xscanimage, xsane, quiteinsane or kooka.
46
47       If you have any success with a scanner not listed here, or if you  have
48       any strange behavior, please report to the backend maintainer or to the
49       SANE mailing list.
50
51       Valid command line options and their syntax can be listed by using
52              scanimage --help -d teco2
53
54
55       Scan Mode
56
57
58       --mode selects the basic mode of operation of the scanner valid choices
59              are Lineart , Gray and Color The Lineart mode is black and white
60              only (1 bit). Gray mode will  produce  256  levels  of  gray  (8
61              bits). Color will produce a 24 bits color image.
62
63
64       --resolution
65              Lineart  and Gray selects the resolution for a scan. The scanner
66              can do all resolutions between 1 and 600, in increments of 1.
67
68
69              Color selects the resolution for a scan. The scanner can do only
70              the resolutions listed.
71
72              All  values  with  ydpi  >  300  (300 x 600) or 600 (600 x 1200)
73              result in a wrong proportion for the scan. The proportion can be
74              adjusted with the following imagemagick command: convert -geome‐
75              try (dpi/max_xdpi * 100%)x100% max_xdpi is for the  vm3575  con‐
76              stant  with  300  dpi e.g. 600dpi adjust with: convert -geometry
77              200%x100%
78
79
80       Geometry options
81
82
83       -l -t -x -y
84              control the scan area: -l sets the top left x coordinate, -t the
85              top left y coordinate, -x selects the width and -y the height of
86              the scan area. All parameters are specified  in  millimeters  by
87              default.
88
89
90
91       Enhancement options
92
93
94       --custom-gamma (no custom gamma option for the VM3564 and VM356A)
95              (color  mode only) allows the user to specify a gamma table (see
96              the next 3 parameters).
97
98
99       --red-gamma-table
100              (color mode only) can be used to download a user  defined  gamma
101              table for the red channel. The table must be 256 bytes long.
102
103
104       --green-gamma-table
105              (color  mode  only) can be used to download a user defined gamma
106              table for the green channel. The table must be 256 bytes long.
107
108
109       --blue-gamma-table
110              (color mode only) can be used to download a user  defined  gamma
111              table for the blue channel. The table must be 256 bytes long.
112
113
114       --white-level-r
115              (VM3564,  VM356A, VM3575 and VM6575 only) Selects what red radi‐
116              ance level should be  considered  "white",  when  scanning  some
117              sheets  by  changing the calibration value loaded into the scan‐
118              ner. Scale 0..64 in steps of 1.
119
120
121       --white-level-g
122              (VM3564, VM356A, VM3575 and  VM6575  only)  Selects  what  green
123              radiance  level should be considered "white", when scanning some
124              sheets by changing the calibration i value loaded into the scan‐
125              ner. Scale 0..64 in steps of 1.
126
127
128       --white-level-b
129              (VM3564, VM356A, VM3575 and VM6575 only) Selects what blue radi‐
130              ance level should be  considered  "white",  when  scanning  some
131              sheets  by  changing the calibration value loaded into the scan‐
132              ner. Scale 0..64 in steps of 1.
133
134
135       --preview
136              requests a preview scan. The resolution used for that scan is 50
137              dpi (for VM356A and VM6575 75 dpi) and the scan area is the max‐
138              imum allowed.  The scan mode is user selected.  The  default  is
139              "no".
140
141
142

CONFIGURATION FILE

144       The  configuration file /etc/sane.d/teco2.conf supports only one infor‐
145       mation: the device name to use (eg /dev/scanner).
146
147
148

FILES

150       /usr/lib*/sane/libsane-teco2.a
151              The static library implementing this backend.
152
153       /usr/lib*/sane/libsane-teco2.so
154              The shared library implementing this backend (present on systems
155              that support dynamic loading).
156
157
158

ENVIRONMENT

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

LIMITATIONS

175       The  windows TWAIN driver has many more options than this SANE backend.
176       However they are only software adjustments. This  backend  only  imple‐
177       ments what the scanner can support.
178
179
180

BUGS

182       Plenty. Parts of this backend are still under development.
183
184
185

SEE ALSO

187       sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
188
189
190

AUTHORS

192       Frank Zago
193              http://www.zago.net/sane/#teco2
194
195       The package is actively maintained by Gerard Klaver.
196              http://gkall.hobby.nl/teco2.html
197
198
199
200
201

CREDITS

203       Thanks to:
204
205       Gerard  Klaver  for  his  relentless  VM3575 testings and contributed a
206       patch to support the VM3564 and VM356A.
207
208       Mark Plowman for providing the first SCSI traces from a VM3575.
209
210       Andreas Klaedtke for providing the first SCSI traces from a VM6586  and
211       for his testing, and to Stefan von Dombrowski for his testing.
212
213       Nicolas  Peyresaubes  for providing the first SCSI traces from a VM656A
214       and for his testing.
215
216       Dave Parker for testing the support for the VM6575.
217
218       Michael Hoeller for testing the support for the VM356A.
219
220       Christoph.Hoeffner for testing the support for the VM3564 (Relisys AVEC
221       II S3 firmware 1.09).
222
223
224
225sane-backends 1.0.18             29 July 2005                    sane-teco2(5)
Impressum