| 1 |
.TH "sane\-p5" "5" "15 Feb 2010" "" "SANE Scanner Access Now Easy" |
| 2 |
.IX sane\-p5 |
| 3 |
.SH "NAME" |
| 4 |
sane\-p5 \- SANE backend for the Primax PagePartner |
| 5 |
.SH "DESCRIPTION" |
| 6 |
The |
| 7 |
.B sane\-p5 |
| 8 |
library implements a SANE (Scanner Access Now Easy) backend that |
| 9 |
provides access to the Primax PagePartner parallel port sheet fed scanner. |
| 10 |
.PP |
| 11 |
This backend handles 100, 150, 200, 300 and 600 dpi scan resolutions, |
| 12 |
in color and gray modes. The 600 dpi is actually 300x600 with lines |
| 13 |
enlarged to match the vertical resolution. |
| 14 |
.PP |
| 15 |
.B EPP/ECP MODES ONLY |
| 16 |
The current version of the backend uses only EPP or ECP mode to communicate |
| 17 |
with the scanner. It is |
| 18 |
recommended that you set your parallel port to EPP in BIOS with the current |
| 19 |
version of this backend. ECPEPP will only |
| 20 |
work if you use a 2.4 or 2.6 kernel with ppdev character device support. |
| 21 |
.PP |
| 22 |
|
| 23 |
.SH "DEVICE NAMES" |
| 24 |
This backend expects device names of the form: |
| 25 |
.PP |
| 26 |
.RS |
| 27 |
.I port value |
| 28 |
.RE |
| 29 |
.PP |
| 30 |
Where |
| 31 |
\fBvalue\fR is: |
| 32 |
|
| 33 |
.RS |
| 34 |
.TP |
| 35 |
auto |
| 36 |
autodetect all parallel ports and probe |
| 37 |
them for scanner |
| 38 |
.TP |
| 39 |
/dev/parport0 |
| 40 |
uses linux ppdev device, depending on the |
| 41 |
number of available parallel port, you |
| 42 |
have to use /dev/parport1, /dev/parport2, ... |
| 43 |
.PP |
| 44 |
.RE |
| 45 |
You can rename any device using the |
| 46 |
.PP |
| 47 |
.RS |
| 48 |
.br |
| 49 |
.I option name my_name |
| 50 |
.RE |
| 51 |
.PP |
| 52 |
option. This option apply to the last port option. |
| 53 |
|
| 54 |
.SH "CONFIGURATION" |
| 55 |
Please make sure to edit |
| 56 |
.I dll.conf |
| 57 |
.B before |
| 58 |
you use the backend, since this backend isn't enabled by default. |
| 59 |
.PP |
| 60 |
|
| 61 |
.SH "FILES" |
| 62 |
.TP |
| 63 |
.I /etc/sane.d/p5.conf |
| 64 |
The backend configuration file (see also description of |
| 65 |
.B SANE_CONFIG_DIR |
| 66 |
below). |
| 67 |
.TP |
| 68 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-p5.a |
| 69 |
The static library implementing this backend. |
| 70 |
.TP |
| 71 |
.I /usr/lib/x86_64-linux-gnu/sane/libsane\-p5.so |
| 72 |
The shared library implementing this backend (present on systems that |
| 73 |
support dynamic loading). |
| 74 |
|
| 75 |
.SH "ENVIRONMENT" |
| 76 |
.TP |
| 77 |
.B SANE_CONFIG_DIR |
| 78 |
This environment variable specifies the list of directories that may |
| 79 |
contain the configuration file. On *NIX systems, the directories are |
| 80 |
separated by a colon (`:'), under OS/2, they are separated by a |
| 81 |
semi-colon (`;'). If this variable is not set, the configuration file |
| 82 |
is searched in two default directories: first, the current working |
| 83 |
directory (".") and then in |
| 84 |
.IR /etc/sane.d . |
| 85 |
If the value of the |
| 86 |
environment variable ends with the directory separator character, then |
| 87 |
the default directories are searched after the explicitly specified |
| 88 |
directories. For example, setting |
| 89 |
.B SANE_CONFIG_DIR |
| 90 |
to "/tmp/config:" would result in directories |
| 91 |
.IR "tmp/config" , |
| 92 |
.IR "." , |
| 93 |
and |
| 94 |
.I "/etc/sane.d" |
| 95 |
being searched (in this order). |
| 96 |
.TP |
| 97 |
.B SANE_DEBUG_P5 |
| 98 |
If the library was compiled with debug support enabled, this |
| 99 |
environment variable controls the debug level for this backend. E.g., |
| 100 |
a value of 255 requests all debug output to be printed. Smaller |
| 101 |
levels reduce verbosity. |
| 102 |
|
| 103 |
.PP |
| 104 |
.RS |
| 105 |
.ft CR |
| 106 |
.nf |
| 107 |
level debug output |
| 108 |
\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- |
| 109 |
0 critical errors |
| 110 |
1 errors |
| 111 |
2 warnings & minor errors |
| 112 |
4 information messages |
| 113 |
8 start/stop of functions |
| 114 |
16 tracing messages |
| 115 |
32 I/O functions |
| 116 |
64 I/O functions with traces |
| 117 |
128 scanned/calibration data |
| 118 |
.fi |
| 119 |
.ft R |
| 120 |
|
| 121 |
.SH "SEE ALSO" |
| 122 |
.BR sane (7), |
| 123 |
.BR sane\-net (5), |
| 124 |
.BR saned (8), |
| 125 |
.BR scanimage (1) |
| 126 |
|
| 127 |
.SH "AUTHOR" |
| 128 |
St\['e]phane Voltz |
| 129 |
.RI < [email protected] > |
| 130 |
|
| 131 |
.SH "CREDITS" |
| 132 |
Support for the Prima PagePartner has been made possible thank to an hardware donation |
| 133 |
by S\['e]bastien Lange. |
| 134 |
|
| 135 |
.SH "BUG REPORTS" |
| 136 |
If something doesn't work mail [email protected] or submit an |
| 137 |
issue via |
| 138 |
.I https://gitlab.com/sane-project/backends/issues/new |
| 139 |
with a label of backend/p5. |
| 140 |
Please give as much information as you can. |
| 141 |
|
| 142 |
.TP |
| 143 |
.I SANE version |
| 144 |
run "scanimage \-V" to determine this |
| 145 |
.TP |
| 146 |
.I the backend version and your scanner hardware |
| 147 |
run |
| 148 |
.I "SANE_DEBUG_P5=255 scanimage \-L 2>log" |
| 149 |
as root. If you don't get any output from the p5 backend, make sure a line "p5" is included into |
| 150 |
your |
| 151 |
.IR /etc/sane.d/dll.conf . |
| 152 |
If your scanner isn't detected, make sure you've defined the right port address, or the |
| 153 |
correct device |
| 154 |
in your |
| 155 |
.I p5.conf |
| 156 |
file. |
| 157 |
.TP |
| 158 |
.I the name of your scanner/vendor |
| 159 |
also a worthy information. Please also include the optical resolution and lamp type of your |
| 160 |
scanner, both can be found in the manual of your scanner. |
| 161 |
.TP |
| 162 |
.I any further comments |
| 163 |
if you have comments about the documentation (what could be done better), or you |
| 164 |
think I should know something, please include it. |