8-A2
Appendix A to Section 8: 9100 Maintenance — Error Reporting Subsystem
Final Width = 215mm
8.A.2.2
Recoverable Errors
8.A.2.2.1
Type of Errors
These consist of Command Errors, Execution Errors, Query
Errors and Device-Dependent Errors. Command, Query and
Execution Errors are generated due to incorrect remote
programming. Device-Dependent Errors can be generated by
manual as well as remote operation. Each of the reportable
errors is identified by a code number.
ALWAYS: record the total message content for possible use by the Service Center.
8.A.2.2.3
Command Errors (CME)
(Remote operation only)
Command Error Generation
A Command Error is generated when the remote command
does not conform, either to the device command syntax, or to
the IEEE 488.2 generic syntax. The CME bit (5) is set true in
the Standard-defined Event Status Byte, and the error code
number is appended to the Error Queue.
Command Error Reporting
The error is reported by the mechanisms described earlier in
Section 6, Sub-section 6.5, which deals with status reporting.
The Command Errors implemented in the 9100 are listed
below; their error numbers conform to those defined in the
SCPI Standard document:
-100,"Command error"
-101,"Invalid character"
-103,"Invalid separator"
-104,"Data type error"
-105,"GET not allowed"
-108,"Parameter not allowed"
-110,"Command header error"
-111,"Header separator error"
-113,"Undefined header"
-120,"Numeric data error"
-121,"Invalid character in number"
-123,"Exponent too large"
-124,"Too many digits"
-150,"String data error"
-160,"Block data error"
-161,"Invalid block data"
-178,"Expression data not allowed"
Note about the ERROR Queue (accessible via the IEEE-488 Interface)
The Error Queue is a sequential memory stack. Each reportable error has been given a listed number and explanatory message,
which are entered into the error queue as the error occurs. The queue is read destructively as a First-In/First-Out stack, using the
query command:SYSTem:ERRor? to obtain a code number and message.
Repeated use of the query:SYSTem:ERRor? will read successive Device-Dependent, Command and Execution errors until the
queue is empty, when the 'Empty' message (
0,"No error"
) will be returned.
It would be good practice to repeatedly read the Error Queue until the 'Empty' message is returned.
The common command
∗
CLS clears the queue.
8.A.2.2.2
Error Reporting
In response to a bus or a keyboard error, there are certain
categories of error reporting. Primarily, the error will be
reported to the original source of the error, but in some cases
will be reported to both local and remote operators. Locally,
the error will be displayed on the front-panel screen; remotely,
it will set the relevant ESR bit, and add the error to the Error
Queue.
