Lexmark Forms Printer 2480 Technical Reference - Page 101

Errors, Data Flow Control, DTR Protocol Timing

Page 101 highlights

When No parity is selected, the pritner expects no parity bit when it receives data. The printer transmits data without parity bits. When Ignore parity is selected, the printer expects a parity bit when it receives a data frame. Although the printer expects a parity bit, it ignores the bit and does not check for a parity error condition. The printer uses even parity when it transmits data. Errors The serial interface recognizes the following three error conditions: Parity Error, Framing Error, and Buffer Overrun. When a parity error is detected, the interface prints an upside down question mark. Although the printer continues to receive data, it prints an upside down question mark for each byte that has a parity error. A framing error is similar to a parity error. When a framing error is detected, the interface also prints an upside down question mark and continues to receive data. However, unlike a parity error which causes the interface to print question marks only for the bytes with incorrect parity, a framing error causes the interface to print question marks for all bytes transmitted. A buffer overrun error occurs when the host does not obey the selected protocol and continues to send data even after the buffer is full. The buffer can only hold 128 bytes of data after the printer signals that it is busy. If the host sends more than this amount, the data is lost and a buffer overrun error occurs. Data Flow Control Flow control is accomplished by way of software or the hardware DTR (Data Terminal Ready). Three flow control protocols are available: • DTR Pacing (hardware) • XON/XOFF (software) • Multi XON/XOFF (software) DTR Protocol Timing You use DTR to control the data flow from the computer. DTR goes from high to low to indicate to the computer that the printer cannot receive more data due to one of the following conditions: • Buffer full • Attendance error (paper out, printer error) • Printer not in ready state Section 6: Using the Printer Interface 101

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227

101
Section 6: Using the Printer Interface
When
No
parity is selected, the pritner expects no parity bit when it receives
data. The printer transmits data without parity bits.
When
Ignore
parity is selected, the printer expects a parity bit when it receives a
data frame. Although the printer expects a parity bit, it ignores the bit and does
not check for a parity error condition. The printer uses even parity when it
transmits data.
Errors
The serial interface recognizes the following three error conditions:
Parity Error
,
Framing Error
, and
Buffer Overrun
.
When a
parity error
is detected, the interface prints an upside down question
mark. Although the printer continues to receive data, it prints an upside down
question mark for each byte that has a parity error.
A
framing error
is similar to a parity error. When a framing error is detected, the
interface also prints an upside down question mark and continues to receive
data. However, unlike a parity error which causes the interface to print question
marks only for the bytes with incorrect parity, a framing error causes the
interface to print question marks for
all
bytes transmitted.
A buffer overrun error occurs when the host does not obey the selected protocol
and continues to send data even after the buffer is full. The buffer can only hold
128 bytes of data after the printer signals that it is busy. If the host sends more
than this amount, the data is lost and a buffer overrun error occurs.
Data Flow Control
Flow control is accomplished by way of software or the hardware DTR (Data
Terminal Ready). Three flow control protocols are available:
DTR Pacing (hardware)
XON/XOFF (software)
Multi XON/XOFF (software)
DTR Protocol Timing
You use DTR to control the data flow from the computer. DTR goes from high to
low to indicate to the computer that the printer cannot receive more data due to
one of the following conditions:
Buffer full
Attendance error (paper out, printer error)
Printer not in ready state