Lexmark XC2235 Printer Languages and Interfaces Technical Reference - Page 122

Tagged Binary active, Status messages

Get Lexmark XC2235 PDF manuals and user guides View all Lexmark XC2235 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 122 highlights

PostScript emulation 122 - Your printer always selects the PostScript emulation interpreter, and processes a Ctrl+T (x'14') command as a status query when receiving data through the LocalTalk interface. Tagged Binary active When Tagged Binary is active, your printer always responds to Ctrl+T (x'14') command as a status query and selects the PostScript emulation interpreter to process the current print job. Tagged Binary mode is immediately exited at the end of the print job. Note: Status queries cannot be received while the printer is in an error state. Status messages Your printer responds to a Ctrl+T (x'14') status query on an interface by sending a one‑line message back to the host computer over the same interface. If the status query is received between print jobs and the printer is idle with no error conditions, then an idle response is returned to the host computer. The characters %%[ and ]%% enclose the status messages, so the computer software can extract them from other data generated by the current print job. The status message follows a machine‑readable format which consists of one or more key plus value pairs separated by semicolons. Example: %%[job: Project report; status: busy; source: serial]%% To determine which status message keys your printer supports, see the Technical Reference for your printer model at http://support.lexmark.com. Key job status source Value description The name of the print job, as stored in the JobName entry in statusdict. If the current print job has no defined JobName, then this field is omitted. Printer activity while sending the message: • Idle-No job in progress • Busy-Executing a PostScript emulation program or printing pages • Waiting-I/O wait in mid‑job Source of the job the server is executing: • Serial • Parallel • Network • LocalTalk • Infrared • USB • Internal Note: If the server is idle, then the source field is omitted.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
–
Your printer always selects the PostScript emulation interpreter, and processes a Ctrl+T (x’14’)
command as a status query when receiving data through the LocalTalk interface.
Tagged Binary active
When Tagged Binary is active, your printer always responds to Ctrl+T (x’14’) command as a status query and
selects the PostScript emulation interpreter to process the current print job. Tagged Binary mode is immediately
exited at the end of the print job.
Note:
Status queries cannot be received while the printer is in an error state.
Status messages
Your printer responds to a Ctrl+T (x’14’) status query on an interface by sending a one
‑
line message back to the
host computer over the same interface. If the status query is received between print jobs and the printer is idle
with no error conditions, then an idle response is returned to the host computer.
The characters
%%[
and
]%%
enclose the status messages, so the computer software can extract them from
other data generated by the current print job. The status message follows a machine
‑
readable format which
consists of one or more key plus value pairs separated by semicolons.
%%[job: Project report; status: busy; source: serial]%%
To determine which status message keys your printer supports, see the
Technical Reference
for your printer
model at
.
Key
Value description
job
The name of the print job, as stored in the JobName entry in
statusdict
. If
the current print job has no defined JobName, then this field is omitted.
status
Printer activity while sending the message:
•
Idle—No job in progress
•
Busy—Executing a PostScript emulation program or printing pages
•
Waiting—I/O wait in mid
‑
job
source
Source of the job the server is executing:
•
Serial
•
Parallel
•
Network
•
LocalTalk
•
Infrared
•
USB
•
Internal
Note:
If the server is idle, then the source field is omitted.
PostScript emulation
122
Example: