Tektronix 2714, Руководство программиста

Страница: 183 / 308

Status Reporting
2714 & 2715 Programmer Manual
5–3
There are three types of errors that are related to RS-232 communications: parity,
framing, and overrun. Parity and framing errors may result from mismatches
between configuration settings (baud rate, parity, etc.) or from noise on the
system. Overrun errors are often caused by a design problem, such as when
interrupts cannot be handled at the required rate.
When an error occurs, the appropriate event is declared and all unparsed data are
discarded until a terminator is received. Table 5–1 lists the complete set of 2714
or 2715 event codes and status bytes, including three RS-232-specific event
codes (numbers 410, 411, and 412).
The status bytes listed in Table 5–1 assume that the Busy bit is off. When the
Busy bit is on, add values of 16 (decimal) or 10 (hexadecimal) to the table entry.
Table 5–1: Event Codes
ve
Status Byte
ve e cri i
Event
Code
Dec Hex Event Description
0 128 80 No Device-dependent Status To Report
0 0 00 No System Status To Report
101 97 61 Command Header Error
102 97 61 Header Delimiter Error
103 97 61 Command Argument Error
104 97 61 Argument Delimiter Error
105 97 61 Non-numeric Arg. (Numeric Expected)
106 97 61 Missing Argument
107 97 61 Invalid Message Unit Delimiter
108 97 61 Binary Block Checksum Error
109 97 61 Binary Block Byte Count Error
121 97 61 Illegal Hex Character
122 97 61 Unrecognized Argument Type
123 97 61 The Argument Is Too Large
124 97 61 Non-binary Arg. (Binary Or Hex Expected)
151 97 61 Illegal Response Value In Query
201 98 62 Remote Command Received When In Local Mode
202 98 62 Command Aborted – (RTL) Return To Local
203 98 62 I/O Deadlock Detected
205 98 62 Argument Out Of Range
206 98 62 Group Execute Trigger Ignored
Parity, Framing, and
Overrun Errors