selphy_print/README

370 lines
12 KiB
Plaintext
Raw Normal View History

2012-10-28 11:18:29 -04:00
***************************************************************************
2012-10-26 22:18:27 -04:00
2013-07-18 21:23:34 -04:00
Unified Gutenprint/CUPS Backend for various Dye-Sublimation photo printers
2012-10-28 11:18:29 -04:00
(c) 2007-2014 Solomon Peachy <pizza@shaftnet.org>
2012-10-28 11:18:29 -04:00
2013-07-18 21:23:34 -04:00
The latest version can be found at
2012-10-28 11:18:29 -04:00
http://git.shaftnet.org/cgit/selphy_print.git
2013-07-08 11:44:06 -04:00
For a list of known bugs and development plans, see:
http://bugs.shaftnet.org/index.php?project=4
2012-10-28 11:18:29 -04:00
***************************************************************************
Supported Printers:
2013-07-18 21:23:34 -04:00
Canon SELPHY ES series
Canon SELPHY CP series (except CP520, CP790, and CP910)
2013-07-18 21:23:34 -04:00
Kodak Professional 1400
2013-11-20 21:35:17 -05:00
Kodak 605 Photo Printer
2013-07-18 21:23:34 -04:00
Kodak 805 Photo Printer
Kodak 6800 Photo Printer
2013-07-26 21:36:24 -04:00
Kodak 6850 Photo Printer
2013-12-14 20:55:37 -05:00
Shinko CHC-S2145 (aka "Sinfonia S2")
2013-07-18 21:23:34 -04:00
Sony UP-DR150
DNP DS40
DNP DS80
2013-12-14 20:55:37 -05:00
Work-in-progress printers:
Mitsubishi CP-D70DW, CP-D707DW and CP-K60DW
Sony UP-DR200
***************************************************************************
This intelligent backend is needed to utilize many common dye-sublimation
photo printers under Linux, OSX, and other UNIX-like operating systems.
Although these printers advertise themselves as standard USB Printer Class
devices, they do not actually obey those specifications, and require
two-way communications in order to successfully print.
If you do not have one of the printers listed above, this backend is
not relevant for you and you can just ignore everything below.
In order to properly utilize this backend, you must have an up-to-date
version of Gutenprint (5.2.10) installed.
Once Gutenprint and this backend are installed, if you are using up-to-date
versions of CUPS (1.6.4 or newer) on Linux, then your system will
automatically select this backend if you plug in one of its supported
printers. No further intervention on the user's part should be necessary.
Unfortunately, if you are using an older version of CUPS or a non-Linux
2014-01-20 14:27:18 -05:00
system (particularly OSX) then you will probably need to manually
configure the use of this backend, as the system may attempt to use the
default usb backend which does not work properly with these printers.
2014-01-17 21:24:18 -05:00
To check which backend your printers are using, run the 'lpstat -s' command.
Below is an example of its output:
device for Canon_SELPHY_ES1: gutenprint52+usb://Canon/SELPHY%20ES1?serial=221CD10131&backend=canonselphy
device for Canon_SELPHY_ES3: usb://Canon/Canon%20SELPHY%20ES3
In this example, the SELPHY ES1 is using the correct gutenprint backend, but
2014-01-20 14:27:18 -05:00
the ES3 is using the incorrect 'usb' backend. In order for the ES3 to
function properly, you need to configure it to use the correct backend.
2014-01-17 21:24:18 -05:00
The most expedient way to accomplish this is to remove the printer via your
system's printer configuration interface, then manually add a new one, taking
care to select the correct backend ("gutenprint52+usb"). This backend name
is present in the device URI for the printer, as demonstrated in the above
example. An alternative to the system printer configuration interface is to
use your local system's CUPS web interface, if it is enabled. Step-by-step
instructions for using any of these interfaces is beyond the scope of this
document.
Once the printer is properly configured, this backend will be automatically
invoked as needed; the user will never invoke the backend directly.
***************************************************************************
This backend also supports a "standalone" mode that performs various
utility functions for selected printers, such as querying status.
The exact commands supported for each printer are documented below.
***************************************************************************
2013-06-30 12:48:46 -04:00
Compilation:
2013-07-19 10:14:55 -04:00
You will need libusbx to build this tool.
2013-06-30 12:48:46 -04:00
Fedora/RedHat:
2013-07-19 10:14:55 -04:00
yum install libusbx-devel
2013-06-30 12:48:46 -04:00
Debian/Ubuntu
2013-07-19 10:14:55 -04:00
apt-get install libusbx-dev
2013-06-30 12:48:46 -04:00
And all you need to do after that is type 'make'
***************************************************************************
2013-06-30 12:48:46 -04:00
CUPS backend usage:
2013-07-18 21:23:34 -04:00
DEVICE_URI=someuri \
gutenprint52+usb job-id user title num-copies options [ filename ]
2013-07-18 21:23:34 -04:00
***************************************************************************
2013-06-30 12:48:46 -04:00
Standalone usage:
2013-07-18 21:23:34 -04:00
This backend is set up as a multi-call executable; that is to say
behaivor changes based on the name used to invoke the executable.
When compiled, a set of symlinks are created, corresponding to each
of the internal backends. Alternatively you may set the BACKEND
environment variable to force a specific backend to be used:
BACKEND=backend \
gutenprint52+usb [ args ]
2013-07-18 21:23:34 -04:00
(OR)
backend [ args ]
That said, all internal backends support these invocation options
backend filename
backend - < filename
somecommand | backend -
2013-07-18 21:23:34 -04:00
backend [ backend-specific-argument ]
2013-07-18 21:23:34 -04:00
The 'filename' here refers to the raw spool data generated by
Gutenprint (eg via its gimp plugin) or the Windows print-to-file
output.
2013-06-30 12:48:46 -04:00
You can enable full data dumps by defining the DYESUB_DEBUG
environment variable.
2013-07-18 21:23:34 -04:00
If there is more than one device present that the backend handles,
the backend will choose the first supported device it finds. If you
wish to specify the specific device when operating in standalone
mode, set the 'DEVICE' environment variable to the target device's
serial number. For example:
2013-07-18 21:23:34 -04:00
DEVICE=N782 backend filename
2013-07-18 21:23:34 -04:00
All backends support an additional operational mode, to test out
unknown models. To use this mode, specify the VID, PID and its
type as environment variables. For example:
2013-07-18 21:23:34 -04:00
EXTRA_VID=04a9 EXTRA_PID=3ab1 EXTRA_TYPE=3 backend filename
2013-07-18 21:23:34 -04:00
EXTRA_VID is the USB VID, in hex
EXTRA_PID is the USB PID, in hex
EXTRA_TYPE is: 3 for SELPHY CP790
4 for SELPHY CP520 (or other CP-series model)
2013-12-17 07:21:24 -05:00
(See P_ANY enum in backend_common.h for more types)
2013-07-18 21:23:34 -04:00
If you have a model the spooler doesn't recognize but it works with
a VID/PID/TYPE specification, please let me know via e-mail.
2013-07-18 21:23:34 -04:00
Finally, some backends may support additional arguments; see below:
2013-06-30 12:48:46 -04:00
***************************************************************************
2013-07-18 21:23:34 -04:00
BACKEND=canonselphy
2013-06-30 12:48:46 -04:00
Verified supported printers:
ES1, ES2, ES3, ES30, ES40, CP-10, CP-100, CP-200, CP-300, CP-330, CP400,
2013-06-30 12:48:46 -04:00
CP500, CP510, CP710, CP720, CP730, CP740, CP750, CP760, CP770, CP780,
CP800, CP900
Unverified/untested, but should work:
ES20, CP-220, CP530, CP600, CP810
2013-07-18 21:23:34 -04:00
NOT currently supported by libusb backend: (USB PIDs unknown)
2013-06-30 12:48:46 -04:00
CP520, CP790, CP910
2013-06-30 12:48:46 -04:00
2013-07-18 21:23:34 -04:00
This backend does not support additional commands
2013-06-30 12:48:46 -04:00
***************************************************************************
2013-07-18 21:23:34 -04:00
BACKEND=kodak1400
Verified supported printers:
2013-06-30 12:48:46 -04:00
2013-07-18 21:23:34 -04:00
Kodak 1400
Kodak 805
2013-06-30 12:48:46 -04:00
This backend supports additional commands:
2013-07-18 21:23:34 -04:00
kodak1400 [command [arg] ]
Valid commands:
-stc filename Set tone curve [1]
Notes:
[1] Format of curvedata file:
256 entries each of Yellow, Magenta, Cyan mappings:
Values are unsigned 16-bit big endian, between 0 and ???
(unsure as to the bit usage)
2013-06-30 12:48:46 -04:00
***************************************************************************
2013-07-18 21:23:34 -04:00
BACKEND=kodak6800
2013-06-30 12:48:46 -04:00
2013-07-18 21:23:34 -04:00
Verified supported printers:
Kodak 6800
Kodak 6850
This backend supports additional commands:
2013-07-18 21:23:34 -04:00
kodak6800 [command [arg] ]
Valid commands:
-qtc filename Query tone curve [1]
-stc filename Set tone curve [1]
Notes:
[1] Format of curvedata file:
256 entries each of Yellow, Magenta, Cyan mappings:
Values are unsigned 16-bit big endian, between 0 and 16383
(ie 14-bit)
2013-11-20 21:35:17 -05:00
***************************************************************************
BACKEND=kodak605
2013-11-24 11:01:44 -05:00
Verified supported printers:
2013-11-20 21:35:17 -05:00
Kodak 605
Valid commands:
-qs Query printer status (Not fully decoded yet)
-qm Query supported media (Not fully decoded yet)
2013-11-24 11:01:44 -05:00
-stc filename Set tone curve [1]
Notes:
[1] Format of curvedata file:
256 entries each of Yellow, Magenta, Cyan mappings:
Values are unsigned 16-bit big endian, between 0 and ???
(unsure as to the bit usage)
2013-11-20 21:35:17 -05:00
***************************************************************************
2013-07-18 21:23:34 -04:00
BACKEND=shinkos2145
2013-07-18 21:23:34 -04:00
Verified supported printers:
2013-08-08 08:53:48 -04:00
Shinko/Sinfonia CHC-S2145 (aka "S2")
Development was sponsored by:
LiveLink Technology [ www.livelinktechnology.net ]
In order to use this backend, you will need to ensure the printer is
configured to use the 'DRV' (as opposed to 'DLL') operating mode. See
the printer documentation for details on how to set this.
This backend supports additional commands:
2013-07-18 21:23:34 -04:00
shinkos2145 [command [arg] ]
Valid commands:
-qs Query printer status
-qm Query media information
-qf Query firmware version
-qe Query Error log
-qu Query User String
-qtu filename Query User tone curve (stored in flash) [2]
-qtc filename Query Current tone curve (stored in RAM) [2]
-su somestring Set User String to 'somestring'
-stu filename Set User tone curve (stored in flash) [2]
-stc filename Set Current tone curve (stored in RAM) [2]
-pc id Cancel print job 'id' [1]
-fl Flash printer LEDs for five seconds.
-ru Reset User tone curve to default [3]
-rp Reset printer to factory defaults
-b1 Enable printer control panel buttons
-b0 Disable printer control panel buttons
-f Enable fast return [4]
Notes:
[1] Job ID is the Internal Job ID (reported via status)
This cancels a multi-copy print job.
To see which jobs are active/pending, see the output of the
'-qs' command, specifically the 'Bank' output.
[2] Format of curvedata file:
256 entries each of Yellow, Magenta, Cyan mappings:
Values are unsigned 16-bit big endian, between 0 and 2047
(ie only 11 bits used)
[3] Default printer tone curve is a linear 'val << 3'
[4] This terminates the backend as soon as the printer has acknowledged
the print job, without waiting for the print job to complete.
This can also be enabled by setting the 'FAST_RETURN' environment
variable.
2013-07-14 17:47:11 -04:00
***************************************************************************
2013-07-18 21:23:34 -04:00
BACKEND=sonyupdr150
Verified supported printers:
Sony UP-DR150
2013-07-14 17:47:11 -04:00
Theoretically supportable printers: (Unknown USB PID)
Sony UP-DR200
2013-07-18 21:23:34 -04:00
This backend does not support additional commands
***************************************************************************
BACKEND=mitsu70x
NOTE: This backend is not yet present in mainline Gutenprint
Theoretically supported printers: (Untested)
Mitsubishi CP-D70DW
Mitsubishi CP-D707DW
Theoretically supportable printers: (Unknown USB PID)
Mitsubishi CP-K60DW-S
This backend supports additional commands:
mitsu70x [command [arg] ]
Valid commands:
-qs Query printer status (Not fully decoded yet)
***************************************************************************
BACKEND=dnpds40
Verified supported printers:
DNP DS40
DNP DS80
Development was sponsored by:
Marco Di Antonio and ilgruppodigitale.com
This backend supports additional commands:
dnpds40 [command [arg] ]
Valid commands:
-qs Query printer status
2013-12-17 07:21:24 -05:00
-qi Query printer info (resolution, etc)
-qc Query printer counters
-cca Clear 'A' Counter
-ccb Clear 'B' Counter
-ccm Clear 'M' Counter
-scp num Set 'P' Counter to 'num'