Version 10.0
Page 26 of 160
AccXES PJL Interface
zzzzzzFINESS-Media<CR>
<PRODUCT=
product
><BYTES=
bytes
><CHECKSUM=
checksum>
<VERSION=
version
><CR>
data
<CR>
... repeat for as many media objects as necessary ...
UEL@PJL
@PJL EOJ
UEL
Each of the italicized strings in the format specification is replaced with a value that describes the
AccXES firmware data. The values are:
Specification
Values
product
NILE, 8830, 8855, 8850, 721P, or 88XX, 6050
bytes
the total number of bytes in the
data
section.
checksum
32-bit checksum of
data
(hex format preceded
with “0x” - ex. 0x2BF4D3C8)
version
an integer representing the download media
version that defines what media fields are
mandatory in the download job. The current
value for this is 1.
data
Command, data, and other information for
this media object - refer to sections below.
4.2.8.2
data
values for each command type
4.2.8.2.1 Adding an object
When adding a new media object, the object must contain all of the information listed below. If an ADD
command is received for a media that already exists on the controller, it will be treated as an UPDATE
command.
COMMAND=ADD<TAB>NAME="
shortname"
<CR>
TYPE=POM<TAB>FIELD=TRC<TAB>FILE=”
filename
”<TAB>SIZE=
value
<CR>
binary_data
<CR>
...
repeat for as many tone reproduction curves (TRCs) as are needed for the media ...
TYPE=POM<TAB>FIELD=CXF<TAB>FILE=”
filename
”<TAB>SIZE=
value
<CR>
binary_data
<CR>
...
repeat for as many color transforms (CXFs) as are needed for the media (may not have any)...
TYPE=POM<TAB>FIELD=CRD<TAB>FILE=”
filename
”<TAB>SIZE=
value
<CR>
binary_data
<CR>
...
repeat for as many color rendering dictionaries (CRDs) as are needed for the media (may not have
any)...
TYPE=DATA<TAB>FIELD=PMTABLE<TAB>SIZE=
value
<CR>
binary_data
<CR>
...
this is the print mode table. The format will vary from IOT to IOT ...