Xerox 850DP - Phaser Color Solid Ink Printer User manual

AccXES Controller Software
Version 10.0
HP-PJL Specification
July 12, 2004

Contents
1 1Intended Audience
2 2Introduction
3 4HP-PJL Commands
3.1 4Kernel Commands
3.1.1 4UEL
3.1.2 4ENTER
3.1.3 5COMMENT
3.2 5Job Separation Commands
3.2.1 5JOB
3.2.2 5EOJ
3.3 5Environment Commands
3.3.1 6DEFAULT
3.3.2 6INITIALIZE
3.3.3 6RESET
3.3.4 6SET
3.4 6Status Readback Commands
3.4.1 6INQUIRE
3.4.2 6DINQUIRE
3.4.3 6ECHO
3.4.4 6INFO
3.4.5 7USTATUS
3.4.6 7USTATUSOFF
3.5 7Device Attendance Commands
3.5.1 7RDYMSG
3.5.2 7OPMSG
3.5.3 7STMSG
3.6 7File System Commands
4 9AccXES Custom Commands
4.1 9COMMENT Commands
4.1.1 9XESACCOUNTING
4.1.1.1 9Pre 6.2 Command Syntax
4.1.1.2 10Returned Status (pre 6.2)
4.1.1.3 11Command Syntax (6.2 and Later Release)
4.1.1.4 11Return Status (6.2 and Later Release)
4.1.2 12XESCANCEL
4.1.3 12XESJOBSET
4.1.4 12XESOBJECTDELETE
4.1.5 13XESOBJECTDOWNLOAD
Version 10.0
Page i

4.1.6 14XESOBJECTUPLOAD
4.1.7 15XESTESTPAGE
4.1.8 15XESPENPALETTE (Obsolete)
4.1.9 15XESCFG
4.1.10 16XESMEDIASET
4.1.11 17XESMEDIADEF
4.1.12 17XESMEDIADICTIONARY
4.2 18DOWNLOAD Language
4.2.2 18IOT Firmware
4.2.2.1 18IOT Executable Firmware
4.2.2.2 18IOT Language Firmware
4.2.3 20Scanner Firmware
4.2.4 20AccXES Controller Firmware
4.2.4.1 20FLASH Boot - controllers prior to HFT
4.2.4.2 22Disk Boot - controllers prior to HFT
4.2.4.3 22HFT Boot code
4.2.4.4 23HFT Application code
4.2.5 23Software Feature Keys
4.2.6 24Peripheral Feature Keys
4.2.7 24System Files
4.2.7.1 24Postscript Font
4.2.7.2 25Generic System Files (Disabled)
4.2.8 25Media Objects
4.2.8.1 25Download format
4.2.8.2 26data values for each command type
528Environment Variables
5.1 28AccXES Environment Variable Organization
5.1.1 28Parameter Classes
5.1.2 28Parameter Groups
5.1.3 28Parameter Environments
5.1.3.1 29Factory Defaults
5.1.3.2 29Default
5.1.3.3 29Current User Job Environment
5.1.3.4 29Modified User Job Environment
5.1.3.5 30Parameter Environment Summary
5.1.4 30AccXES Environment Variables
5.1.5 66Communication Parameter Class
5.1.6 67Printer Parameter Class
5.1.6.1 67Printer Group
5.1.6.2 69Emulation Group
5.1.7 75Processing Parameter Class
5.1.7.1 75Job Processing Group
5.1.7.2 82Page ProcessingGroup
Version 10.0
Page ii

5.1.8 98Printer State Class
5.1.8.1 98Marking Engine Group
5.1.8.2 99Media Group
5.1.8.3 100Configuration Group
5.1.8.4 101ESS Group
6103INFO Command Responses
6.1 103ID
6.2 103CONFIG
6.3 104FILESYS
6.4 105MEMORY
6.5 105PAGECOUNT
6.6 105STATUS
6.7 106VARIABLES
6.8 106USTATUS
6.9 107XESACCOUNTING
6.9.1 107Command Syntax (pre 6.2)
6.9.2 107Returned Status (pre 6.2)
6.9.3 108Release 6.2 Returned Status
6.10 109Job Accounting Status
6.11 111XESFONTS
6.12 112XESPALETTES
6.13 112XESPATTERNS
6.14 113XESPENPALETTE (obsolete)
6.15 114XESRASTERSTAMPS
6.16 114XESQUEUE
6.17 115XES_SYS_STAT
6.18 116XESFEATURES
6.19 117XESFINISHER
6.20 120XESMEDIA
7122Printer Object Download/Upload Format
7.1 122Palettes
7.2 123Patterns
7.3 124Fonts
7.4 125Raster Stamps
8126Factory Installed Printer Objects
8.1 126Fonts, Release 2.0
8.2 127Patterns, Release 2.0
8.3 128Palettes, Release 2.0
9129Status Codes
9.1 129Status Codes and Informational Messages [10xxx]
9.2 129Auto-Continuable conditions [30xxx]
Version 10.0
Page iii

9.3 129Operator Intervention Conditions [40xxx]
9.4 130Hardware Errors [50xxx]
9.5 130STATUS Precedence
10 131Examples
10.1 131Changing a Job’s Priority and Canceling
10.2 131Listing and Uploading Printer Objects
10.3 132Downloading a Printer Object into Non-volatile Memory
10.4 133<UEL>Using a Printer Object in a Job
10.5 134Deleting a Printer Object
10.6 134Job and Page Control Options in a Multifile Document
10.7 135Page Composition Job
10.8 136Getting Job and Printer Status
10.9 137Setting Default Printer Parameters
10.10 137Adding a Label to a Plot
11 139XES AccXES HP-PJL Support by Printer Model
Version 10.0
Page iv

Version 10.0
Page 1 of 160
A
ccXES PJL Interface
1 Intended Audience
This document is intended for use by the AccXES software development team and other Xerox technical
personnel interested in reviewing the AccXES definition and implementation of the HP-PJL Job
Control language. Third party integrators, host client printer driver and utility developers, and related
printing system developers will also find useful information in this document. No familiarity with the
AccXES software architecture is assumed or required for understanding this document. However, the
reader should have a thorough understanding of HP-PJL as defined in Hewlett-Packard’s “Printer Job
Control Language Technical Reference Manual,” [HP96].
Persons interested in the general technology platform and requirements of the Xerox/AccXES should
refer to the “Architecture Requirements and Technologies” document also listed below.

Version 10.0
Page 2 of 160
A
ccXES PJL Interface
2 Introduction
Many of the data formats and page description languages supported by the AccXES architecture do not
have a mechanism to control many job processing attributes. Other languages have some job control,
but cannot control the more specialized features of the printer, such as finisher options. To access
advanced printer functionality, a separate mechanism is required. This is the responsibility of the Job
Control Language. Specifically, AccXES architecture supports HP-PJL, which is an industry standard
printer job control language originally developed by Hewlett-Packard. The specific implementation of
HP-PJL on the AccXES architecture is a superset of the core HP-PJL functionality. The HP-PJL
superset is tailored to the feature set required for the Xerox printing and plotting systems.
It is intended that this language be well documented and easily available for external third party
integrators to use in their development of host based print servers employing the AccXES controller in
the printer as well as client platform print drivers and utilities.
A
nother goal of the
j
ob control language implementation is to allow remote configuration and
j
ob
control/status. All operations that can be performed at the printer front panel interface should be
available through the job control language implementation. Of course, client host software is required
to produce the appropriate job control constructs.
HP-PJL is used to encapsulate the user jobs to provide job and printer control information. In this
respect, it can be viewed as functioning “above” the level of HPGL/2, TIFF, and other printer languages.
The following figure shows how HP-PJL may be combined with user print jobs. Notice that HP-PJL
can be used independently of user print jobs as well.
HP-PJL Job Control Language
User Job (HPGL/2, TIFF, PostScript, ...
HP-PJL Only Printer Control Job
Unencapsulated User Job (HPGL/2, TIFF, ...
Figure: Combinations of HP-PJL and User Jobs
A
ccepted by
A
ccXES
The use of HP-PJL is not required so that host systems with print drivers which don’t utilize HP-PJL
can still be supported; however, using HP-PJL makes the work of job segmentation and data format
detection error proof.
Examples of
j
ob specific control information provided by HP-PJL when encapsulating a user
j
ob
include:
•
A
utomatic Collation
•Automatic Scaling and Rotation
•Emulation Switching (explicit or automatic)

Version 10.0
Page 3 of 160
A
ccXES PJL Interface
•Multiple Copies and Electronic Collation
•Plot Nesting
•Job
A
ccounting information
•Tray and Media Selection
•Raster Stamps, Plot Overlays, Forms
•Many others...
When HP-PJL is sent independent of user print
j
ob, it can be used to query printer status and spool
queue information, change host interface parameters, or perform any action the user can perform from
the printer front panel. Specific HP-PJL only jobs can be sent to:
•Change printer defaults
•Configure host interfaces
•Manipulate the printer
j
ob queue
•Obtain printer status
•Perform printer system diagnostics
•Perform Job
A
ccounting administration.
•Program internal system FLASH memory
Hewlett-Packard’s “Printer Job Language Technical Reference Manual,” [HP96], provides the complete
definition of HP-PJL. Only exceptions and extensions to the standard language defined by [HP96] are
discussed in the sections that follow. This document provides a full specification of the AccXES
customizations and extensions of the HP-PJL language. The reader is urged to review [HP96] prior to
reading this document.

Version 10.0
Page 4 of 160
A
ccXES PJL Interface
3 HP-PJL Commands
This section defines the HP-PJL commands that are utilized by the AccXES software architecture as
well as the custom commands defined by the AccXES architecture. A user job with custom AccXES
HP-PJL commands embedded within it is required to run without error on a standard HP-PJL printer.
In practice, this means that new HP-PJL commands are embedded within the HP-PJL COMMENT
command.
Conversely, standard HP-PJL
j
obs should run without error, albeit with loss of printer feature control,
on a AccXES printer. Consequently, all HP-PJL commands defined in [HP96] are implemented in
AccXES printers. The AccXES printer will most closely resemble a Hewlett-Packard LaserJet 4V/4MV
printer in its HP-PJL implementation.
3.1 Kernel Commands
The kernel commands detailed in the following sections are implemented in the
A
ccXES printer.
3.1.1 UEL
The UEL command will be implemented as defined on page 4-2 of [HP96]. From the HP-PJL
specification, it is defined to be the following character sequence:
<ESC>%-12345X
3.1.2 ENTER
This command is implemented as defined on page 4-4 of [HP-PJL]. The possible values to be taken by
the LANGUAGE parameter are:
•AUTO
•CALCOMP
•CALS1
•CALS2
•VDS
•VCGL
•C4
•CGM
•VRASTER
•HPGL2 {Alternately, HP-GL/2}
•HPGL7585 {
A
lternately, HPGL}
•PCL
•POSTSCRIPT
•TIFF6

Version 10.0
Page 5 of 160
A
ccXES PJL Interface
•JPEG
•ASCII
•FLASH
•DOWNLOAD
•FILENET
The FLASH and DOWNLOAD values are special values used for upgrading printer firmware and
downloading rendering objects such as raster stamps and fonts, respectively. The objects supported by
the DOWNLOAD facility are detailed in the DOWNLOAD Language section
A
s in standard HP-PJL, the INFO CONFIG command can be used to query the printer for the list of
currently supported data formats. Note that the LANGUAGE parameter to the HP-PJL ENTER
command detailed above is distinct from the standard HP-PJL Environment variable LANG which is
used to set the user interface language to English, French, Italian, etc. Note also, that there is another
environment variable called PERSONALITY which can take on the same values as the LANGUAGE
parameter above.
As specified in the HP-PJL specification [HP96], the next byte following the line feed at the end of the
ENTER command must be the actual job data. In particular, no further HP-PJL commands can be
placed between this command and the specified data format’s job data.
3.1.3 COMMENT
The COMMENT command is implemented as defined on page 4-6 of [HP96]. In addition, custom
commands specific to AccXES functionality are implemented within a COMMENT command. See the
Comment Command section for details.
3.2 Job Se
p
aration Commands
3.2.1 JOB
This command is supported as defined on page 5-2 in [HP96].
A
ll parameters are supported: NAME,
START, PASSWORD, and END. The maximum length of a valid NAME parameter is 80 characters.
Longer names will be truncated. The START and END parameters may not be supported in all AccXES
implementations.
From the HP-PJL Reference Manual (10 Edition, Oct 1997), the following requirement is explicitly
re-stated here for clarity:
"JOB commands can be nested. For example, a spooling application can send a PJL job that uses the
JOB command to another spooler that encapsulates the spooled job with another JOB/EOJ command
pair. When this is done, note that the job name from the outer JOB command is cleared or overwritten
by the inner command."
3.2.2 EOJ
The EOJ command is supported as defined on page 5-7 of [HP96]. The maximum length of the NAME
parameter supported is 80 characters. Currently, while the NAME parameter is accepted, it is
effectively ignored.
3.3 Environment Commands

Version 10.0
Page 6 of 160
A
ccXES PJL Interface
3.3.1 DEFAULT
The default command is supported as defined on page 6-31 of [HP96]. The list of supported
environment variables is detailed in Environment Variables section.
3.3.2 INITIALIZE
This command is supported generally as defined on page 6-32 in [HP-95]. One exception is that the only
environment variables that are reset are the page and job processing groups. All parameters in the
communication class and the ESS and engine state class are not reset. Communication class variables
are not reset so as to avoid disrupting communications on this channel and others at the time the
command is received. State variables are modified as the system boots or as system events occur. They
are “read-only” to HP-PJL.
3.3.3 RESET
This command is defined exactly as on page 6-38 of [HP96].
3.3.4 SET
This command is defined as described on page 6-41 of [HP96]. See Environment Variables section for a
list of the supported environment variables. Note that in the AccXES implementation, the Current
User Job Environment supports only processing related commands (Job and Page Group parameters).
Requests to change variables that modify basic printer parameters such as host interface operational
parameters are ignored in a SET command. These parameters should be modified using the DEFAULT
command.
3.4 Status Readback Commands
3.4.1 INQUIRE
This command is implemented exactly as described on page 7-4 of [HP96].
3.4.2 DINQUIRE
This command is implemented exactly as defined on page 7-9 of [HP96].
3.4.3 ECHO
This command is implemented exactly as defined on page 7-14 of [HP-95].
3.4.4 INFO
This command is implemented as defined on page 7-16 of [HP-PJL]. The responses to the INFO
command are detailed in INFO Command Responses section. Most standard categories to the INFO
command are supported including ID, CONFIG, FILESYS, MEMORY, PAGECOUNT, STATUS,
VARIABLES, and USTATUS. USTATUS and PAGECOUNT are not supported on all AccXES
controllers.
The
A
ccXES implementation supports many additional categories such as:
JOB_ACCOUNTING -reports
j
ob accounting settings
XESQUEUE - reports on the jobs and their status in the AccXES printer job queue.

Version 10.0
Page 7 of 160
A
ccXES PJL Interface
XES_SYS_STAT - reports on the status of the printer and provides more detailed information on the
processing status of the most mature job in the printer.
XESPALETTES - reports the color pallet settings.
XESFONTS - reports font settings
XESACCOUNTING – reports media usage by account number or for all accounts if accompanied by
valid password.
XESRASTERSTAMPS – reports raster stamp information
XESFEATURES – reports the status of software features as enabled or disabled
XESFINISHER – reports information about the attached finisher, if any
XESMEDIA - reports media supported by the printer as well as parameters associated with that
media.
3.4.5 USTATUS
USTATUS is generally not supported in
A
ccXES printers. Currently, status information is obtained by
clients through requesting the information, rather than reading unsolicited packets such as would be
provided by this command. Other printer administration / job control mechanisms such as SNMP will
be used in AccXES printers to provided unsolicited status.
The primary reason that USTATUS is not supported is that this mechanism is very crude and does not
extend very well to networked environments. In particular, there is no method for addressing clients or
broadcasting to some set of clients.
3.4.6 USTATUSOFF
As above, this command is generally not implemented in AccXES printers.
3.5 Device Attendance Commands
3.5.1 RDYMSG
This command is implemented as defined on page 8-2 of [HP96]. Not all
A
ccXES implementations may
implement this command.
3.5.2 OPMSG
This command is implemented as defined on page 8-4 of [HP96]. Not all
A
ccXES implementations may
implement this command.
3.5.3 STMSG
This command is implemented as defined on page 8-6 of [HP96]. Not all AccXES implementations may
implement this command.
3.6 File S
y
stem Commands

Version 10.0
Page 8 of 160
A
ccXES PJL Interface
These commands are not yet supported in the
A
ccXES controller. These commands include
FSAPPEND, FSDELETE, FSDIRLIST, FSDOWNLOAD, FSINIT, FSMKDIR, FSQUERY, and
FSUPLOAD.

Version 10.0
Page 9 of 160
A
ccXES PJL Interface
4 AccXES Custom Commands
4.1 COMMENT Commands
This section overviews theXerox custom commands unique to AccXES. These new commands are
defined innocuously to HP-PJL by embedding them in the existing COMMENT function. For example,
the syntax for theXESCANCEL command is:
@PJL COMMENT XESCANCEL (USERJOBID=<user
j
ob id> | NAME=“<JOB name>“)
4.1.1 XESACCOUNTING
This command is used for managing copy, scan, and print
j
ob accounting. For this command to be
valid, the job containing this command must also have a valid password.
4.1.1.1 Pre 6.2 Command S
y
ntax
The syntax for the XESACCOUNTING command is:
@PJL COMMENT XESACCOUNTING
A
CTION=<action> [ACCTNUM=<account #>
SUBACCTNUM=<subaccount #>] [UNITS=<units>] [B=<bond area #> V=<vellum area #> F=<film
area #> S=<scan area #>]
A
CTION is a mandatory entry. It can be followed with
A
CCTNUM and SUBACCTNUM, which if valid
will restrict the action to an account or a single subaccount. The following table lists the valid
assignments to ACTION, as well as the additional entries required to successfully parse the command.
For those commands which apply to all accounts (deleteall, resetuser, resetsystem, resetall) an account
number MUST NOT be supplied. If an account is supplied the PJL command will be rejected.
Table: XESACCOUNTING Options
ACTION ACCT NUM MEDIA(B,V,F or S) UNITS
CREATE
Will not overwrite
an existing
account
Required Ignored.
All media values are set to
‘0’
Ignored
DELETE Required Ignored Ignored
DELETEALL None Ignored Ignored
RESET Required Ignored.
All media values are set to
‘0’
Ignored
RESETUSER None Ignored.
All media values are set to
‘0’
Ignored
RESETSYSTEM None Ignored.
All media values are set to
‘0’
Ignored
RESETALL None Ignored.
All media values are set to
‘0’
Ignored
RESTORE
Will overwrite
existing accounts
Required Optional.
unspecified values set to
‘0’
Require
d

Version 10.0
Page 10 of 160
A
ccXES PJL Interface
The functional detail of each
A
CTION is more fully described in the “AccXES Job
A
ccounting
Specification”.
4.1.1.2 Returned Status
(p
re 6.2
)
After parsing the XESACCOUNTING command, the controller will echo the command, the appropriate
status, and a form-feed back on the sending channel as shown below:
@PJL COMMENT XESACCOUNTING
A
CTION=<action>
A
CCTNUM=<acctnum>
SUBACCTNUM=<subacctnum> UNITS=<units> B=<bond area #> V=<vellum area #> F=<film area #>
S=<scan area #>
STATUS=<status>
<FF>
Possible status values are:
STATUS = invalid ACTION
STATUS = No Hard Disk -
A
ccounting Disabled
STATUS = invalid Password
STATUS = invalid
A
CTION
STATUS = invalid
A
ccount/SubAccount Num.
STATUS = invalid UNITS
STATUS = error parsing
A
CTION
STATUS = error parsing
A
CCTNUM
STATUS = error parsing SUBACCTNUM
STATUS = error parsing BOND
STATUS = error parsing VELLUM
STATUS = error parsing FILM
STATUS = error parsing SCAN
STATUS = UNITS error, Using default units, DM.
STATUS = error parsing UNITS
STATUS =
A
ccount(s) reset
STATUS = RESET error
STATUS = Account(s) deleted
STATUS = CREATE error
STATUS =
A
ccount created

Version 10.0
Page 11 of 160
A
ccXES PJL Interface
STATUS = DELETE error
STATUS = Account(s) deleted
STATUS = RESTORE error
STATUS =
A
ccount(s) restored
STATUS = Accounting Disabled
STATUS = UNITS required for restore
STATUS = Max
A
ccts exceeded
STATUS = Max Subaccts exceeded
STATUS = pjlErr in procXesAccounting
STATUS = INFO error
4.1.1.3 Command S
y
ntax
(
6.2 and Later Release
)
4.1.1.3.1 XESACCOUNTING Command
The XESACCOUNTING command was used for copy, scan, and print job accounting. With this release
of the software the AccXES Controller no longer provides a stand-alone accounting solution. The legacy
job accounting commands will be recognized and responded to, with an appropriate error.
The syntax for the XESACCOUNTING command is:
@PJL COMMENT XESACCOUNTING
A
CTION=<action> [ACCTNUM=<account #>
SUBACCTNUM=<subaccount #>] [UNITS=<units>] [B=<bond area #> V=<vellum area #> F=<film
area #> S=<scan area #>]
Where ACTION values are:
•CREATE
•DELETE
•DELETEALL
•RESET
•RESETUSER
•RESETSYSTEM
•RESETALL
•RESTORE
4.1.1.4 Return Status
(
6.2 and Later Release
)
After parsing the XESACCOUNTING command, the controller will echo the command, the appropriate
status, and a form-feed back on the channel as shown below:

Version 10.0
Page 12 of 160
A
ccXES PJL Interface
@PJL COMMENT XESACCOUNTING
A
CTION=<action> [ACCTNUM=<account #>
SUBACCTNUM=<subaccount #>] [UNITS=<units>] [B=<bond area #> V=<vellum area #> F=<film
area #> S=<scan area #>]
STATUS=<status>
<FF>
Possible status values are:
STATUS = invalid ACTION
4.1.2 XESCANCEL
This command cancels a
j
ob specified with either the user
j
ob id or
j
ob name.
A
user
j
ob id is an integer
number assigned by the AccXES printer to the job when it is created in the printer. It is guaranteed to
be unique in the printing system for as long as the job exists in the printer.
The syntax for the command is:
@PJL COMMENT XESCANCEL (USERJOBID=<user job id> | NAME=“<JOB name>“)
If the
j
ob has completed processing within the printer, then this command will be safely ignored.
Otherwise, the printer attempts to cancel the job as quickly as possible, while not affecting the
processing of other jobs in the system. There is no response returned from the printer to the host in this
command.
4.1.3 XESJOBSET
This command changes the value of the
j
ob or page processing parameter specified. No other parameter
groups are changeable with this command. In general, only jobs currently stored in the AccXES printer
job spool queue may be affected. If the job has already begun its processing within the printer, then this
command is safely ignored. The one exception to this is that you can change the job queue scheduling
priority even after the job has been processed and is awaiting printing.
This command is used mainly for changing job queue scheduling priority, although all other job and
page processing parameters are changeable as well. The job is specified with either the user job id or
the job name. There is no response returned from the printer to the host in this command.
The syntax of the XESJOBSET command is:
@PJL COMMENT XESJOBSET (USERJOBID=<user
j
ob id> | NAME=“<JOB name>“) <Variable
Name>=<New Variable Value>
4.1.4 XESOBJECTDELETE
This command deletes a printer object. The syntax of the XESOBJECTDELETE command is:
@PJL COMMENT XESOBJECTDELETE TYPE = <PrinterObjectType> NAME =
“<PrinterObjectName>”
The possible types of printer objects specified in the TYPE field are:
•XESFONTS

Version 10.0
Page 13 of 160
A
ccXES PJL Interface
•XESPALETTES
•XESPATTERNS
•XESRASTERSTAMPS
The printer object name specified in the NAME field is a string name of the printer object to delete.
This string must be less than 48 characters in length. For a successful deletion, the object must be
present in the file system, it must be deletable, and its type must match that of the specified object
type. Also, there must be a valid printer password in the associated job command or the printer must
have its password disabled. A list of printer object names which are available, including their sizes and
permissions, can be obtained through the @PJL INFO command with the corresponding type specified.
There is no response for this command.
4.1.5 XESOBJECTDOWNLOAD
This command should be inserted in a
j
ob that is encapsulated with an JOB/EOJ pair to specify that
the associated job is actually a printer object which is being downloaded to the printer with the
specified type and name. The syntax of this command is:
@PJL COMMENT XESOBJECTDOWNLOAD TYPE = <PrinterObjectType> NAME =
“<PrinterObjectName>” MODE = <DownloadMode>
There should be only one object of one type downloaded in a single job. This object will be stored in
nonvolatile memory in a device dependent manner in the printer. The type of object is specified with
the TYPE field. The possible types of printer objects are:
•XESFONTS
•XESPALETTES
•XESPATTERNS
•XESRASTERSTAMPS
The PrinterObjectName string should specify the object name using the NAME field and be of the
previously specified object type. Object names are case sensitive. This string should be less than 48
characters and may be composed of any combination of upper case letters (ASCII 65 – 90), lower case
letters (ASCII 97 – 122) and digits (ASCII 48 – 57).
There are two classes of object type collections – those whose number can increase with download
operations and those that function as a fixed set of numbered “bins.” With object types in this category,
the printer has a fixed number of bins which can be modified (if that bin has read/write permission).
The download operation must specify the name of one of these bins and the download will modify the
contents of that bin. XESPATTERNS and XESPALETTES are examples of this type.
In the other category, the number of objects for a given type can change depending on the number of
objects downloaded. A download of an object with the same name and type as another previously
downloaded object will overwrite the previously downloaded object without notice or error if the
previous object is not read-only. XESFONTS and XESRASTERSTAMPS are objects of this type.
The MODE field specifies whether the printer object downloaded should be associated with the current
job only (i.e. Current User Job Environment) or downloaded into non-volatile memory within the
printer (i.e. User Default). The two possible values are:

Version 10.0
Page 14 of 160
A
ccXES PJL Interface
•SET
•DEFAULT
SET is used to associate the object with the currently defined
j
ob.
A
ny
j
ob data to which this object
applies must follow the actual object download; preceding print files in the job will not have access to
the object. DEFAULT is used to download the object into printer memory where it will persist over
power cycles until the object is deleted. It is typically referenced by other jobs by the name in the
NAME field. Objects downloaded with the DEFAULT mode will be read-write; therefore they can be
deleted (or modified) with a subsequent download of the same name and type or an
XESOBJECTDELETE command.
Currently, XESRASTERSTAMPS, XESPATTERNS, and XESFONTS do not support the SET option.
An ENTER LANGUAGE command should be used as well in the job to specify the correct interpreter
for processing the printer object. XESRASTERSTAMPS objects can be described by any of the
supported data formats of the destination printer, and therefore, any data format interpreter matching
the objects description is possible. Specifying AUTO for the language is possible as well. In contrast,
XESPALETTES, XESPATTERNS, and XESFONTS must specify the DOWNLOAD interpreter. See the
@PJL ENTER command description.
The format for each of the object types is described in Printer Object Download/Upload Format section
below. This format is the same format used in the XESOBJECTUPLOAD command to upload printer
objects.
The format of a full printer object is therefore:
@PJL COMMENT XESOBJECTDOWNLOAD TYPE = <PrinterObjectType> NAME =
“<PrinterObjectName>” MODE = <DownloadMode>
@PJL ENTER LANGUAGE = <languageName>
<Object data><UEL>
If this is sent down to the printer as a single isolated object, then this command sequence is typically
wrapped with a JOB/EOJ pair. There is no response for this command.
4.1.6 XESOBJECTUPLOAD
This command uploads a printer object. The syntax of the XESOBJECTUPLOAD command is:
@PJL COMMENT XESOBJECTUPLOAD TYPE = <PrinterObjectType> NAME =
“<PrinterObjectName>”
The possible types of printer objects specified in the TYPE field are:
4.1.6.1
•XESPALETTES
•XESPATTERNS
4.1.6.2
4.1.6.3

Version 10.0
Page 15 of 160
A
ccXES PJL Interface
The “PrinterObjectName” is a string name (specified in the NAME field) of the printer object to upload.
This string must be less than 48 characters in length. For a successful upload, the object must be
present in the file system and its type must match that of the specified object type. A list of printer
object names which are available, including their sizes and permissions, can be obtained through the
@PJL INFO command with the corresponding type specified.
The response for this command is dependent on the type of object requested. These responses are
always the native representation of the object representation. Note that this representation is always
exactly the same format used to download the object. In all cases, the response will take the form:
@PJL COMMENT XESOBJECTUPLOAD TYPE = <PrinterObjectType> NAME =
“<PrinterObjectName>”
<Object data><FF>
The first line is simply the command the host sent repeated. After a carriage return/line feed
combination, object specific data is presented. This is immediately terminated with a form feed. Note
that if the requested object type is not one currently supported for upload, then there will be NO object
data returned and only the command will be echoed back.
4.1.7 XESTESTPAGE
This command causes the printer to schedule the internal test page for processing and printing. This
“internally” generated job will have a very high scheduling priority allowing it to print very soon in the
print queue. The test page will print printer configuration information and current parameter settings.
There is no response to this command from the printer to the host. The syntax of the command is:
@PJL COMMENT XESTESTPAGE
4.1.8 XESPENPALETTE
(
Obsolete
)
This command changes the printer’s pen palette for a given pen. The three attributes that may be set
for a pen are the pen’s width, RGB color, and assigned pattern number. The first parameter in this
command specifies the name of the palette to be changed within the printer. This is a string parameter.
The second specifies the (integer) pen number to be modified. The third parameter specifies the width
of the pen in a floating point number with dimensions of mm. The fourth parameter specifies the pen
color with three color components ranging in value from 0 to 255 which determine the Red, Green, and
Blue values of the color, respectively. The formula for the color is:
<color> = (<red> * (216)) + (<green> * (28)) + <blue>
The last parameter specifies the index of the printer resident pattern assigned to the pen in the form of
an integer.
@PJL COMMENT XESPENPALETTE PALETTE=”<Palette Name>” PENNUMBER=<Pen#>
PENWIDTH=<Pen width in mm> PENCOLOR=<color> PENPATTERN=<Pattern#>
4.1.9 XESCFG
The name of the machine can be set by the SA to uniquely identify the
A
ccXES Controller. It is the
responsibility of the SA to ensure that this name is unique and not duplicated. This name will be used
in the Job Record as attribute jba-device-name to indicate which machine processed each job. The
maximum length for the machine name is specified as 20 characters. The syntax of the command is: