designjet(1)
designjet - HP DesignJet printer/plotter driver
As shipped in IRIX 6.5. First release of IRIX 6.5.
NAME designjet - HP DesignJet printer/plotter driver SYNOPSIS designjet -P printername [ options ] [ inputfile ] DESCRIPTION The designjet driver is a device specific driver for HP DesignJet printer/plotters. The 650C and 750C plotters are supported. designjet reads STIFF format image files and writes RTL commands to standard out (the output is intended to be directed to the printer with an output device specific driver). The driver opens and maintains the POD printer database files for the specified printer. The file <printername>.config contains the detailed information on the printer's capabilities, <printername>.status contains the information on operational status of the printer, and <printername>.log contains the information on print job history. For more information on the POD files refer to the libpod(3) man page. INPUT FILE FORMAT designjet assumes that its input is coming from its standard input (stdin) unless a filename is specified after any and all command line options. designjet accepts the input files in chunky STIFF format and supports 1 bit K and 1 bit RGB colorspaces. STIFF is a streamable subset of TIFF 6.0. For more information on the STIFF image file format, see the libstiff(3) man pages. USAGE -P printername Specifies the printer with which designjet is communicating. printername is the name under which the SystemVR3 spooler recognizes the printer, as given on the lp command line. This option is required. -s Specifies that the driver should exit after ascertaining printer status and updating the POD status file. -D Turns on debugging information. Five levels of debugging information are supported: none, coarse detail, medium detail, fine detail, and extra finer detail. These correspond to 0, 1, 2, 3, and 4 or more -D switches given on the command line. That is, multiple -D options given on the command line result in progressively more detailed debugging information. -X HorizontalResolution Specifies the horizontal resolution at which to print, one of the following: 300 or 600 (only the 750C supports 600DPI and 600DPI is only supported in monochrome mode). -Y VerticalResolution Specifies the vertical resolution at which to print, one of the following: 300 or 600 (only the 750C supports 600DPI and 600DPI is only supported in monochrome mode). -S PaperSize Specifies the papersize to request from the printer. This may be any papersize recognized by libpod(3), but only those sizes listed in the printer configuration file should be used. This is normally derived from the printer status database, but if given, it overrides and will be written to the printer status database. -h Print a usage statement. -F FileFormat Format of file to print. FileFormat can be "hpgl" or "stiff". If "hpgl" is specified the input stream is sent to the plotter unaltered. -j QualityMode Specifies the quality mode to use. QualityMode can be "economode", "normal" or "presentation". -o dMediaType Specifies media type loaded in plotter. MediaType can be "plain", "special", "glossy", or "transparency:. -R Rotate Plot. Should be specified to rotate plot 90 degrees (swaps X and Y axis). This saves paper on roll sheets by printing the long edge of the paper size along the leading edge of the paper roll. If the image size will not fit after being rotated then the rotation is not done (E size plots can not be rotated so -R is ignored if paperize is E). -B buffer_size Size of buffer to use to read and write data. Specified in bytes. EXIT CODES The driver normally exits with an exit code of zero (0), denoting no error. A number of exit codes are supported to give more information about unsuccessful exits. The error codes 1 through 18 denote the following meanings, in order: CODE REASON 1 unknown error 2 bad command line or img header args 3 bad POD database access 4 bad device name 5 bad device type 6 bad status update 7 unsuccessful device access 8 bad memory reference 9 failed memory allocation 10 invalid data format 11 invalid data header 12 short or empty input data file 13 short or empty firmware code file 14 bad or short input data file 15 failed transmission 16 data buffer invalid 17 test print failed 18 firmware download failed. A common error exit is on empty input: the driver will return error code 12, indicating a short or empty input file, whenever the PostScript interpreter (or another upstream filter) dies before a full page of data was written to the driver. This can happen when bad PostScript code is sent to be printed, for instance. In this case, the spooler log file (/var/spool/lp/log) should be consulted to determine which filter failed; an error should have been written to this file by the dying filter or driver. KNOWN BUGS Manual feed requests are currently ignored: since the driver does not implement manual feed timeouts, manual feed has been disabled. SEE ALSO impressario(1), printstatus(1), printpanel(1), libpod(3), libspool(3), libstiff(3), lp(1)