Fluke 9500B - Page 206

8-A2 Appendix A to Section 8: 9500B Maintenance — Error Reporting Subsystem
Final Width = 215mm
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
9500B 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"
-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"
8.A.2.2 Recoverable Errors (Contd.)
8.A.2.2.4 Execution Errors (EXE)
(Remote operation only)
Execution Error Generation
An Execution Error is generated if a received
command cannot be executed due to it being
incompatible with the current device state, or
because it attempts to command parameters
which are out-of-limits.
In remote operation, the EXE bit (4) is set true
in the Standard-defined Event Status Byte, and
the error code number is appended to the Error
queue.
Execution Error Reporting
The error is reported by the mechanisms
described earlier in Section 6, Sub-section 6.5,
which deals with status reporting.
The Execution Error numbers are given below,
with their associated descriptions.
-220,"Parameter error"
-221,"Settings conflict"
-222,"Data out of range"
-223,"Too much data"
-224,“Illegal parameter value”
-241,“Hardware missing”
-258,"Media protected"
8.A.2.2.5 Query Errors (QYE)
(Remote operation only)
Query Error Generation
A Query Error is generated when the controller
fails to follow the Message Exchange Control
Protocol as follows:
• DEADLOCK State
The device has been asked to buffer more
data than it has room to store; the Output
Queue is full, blocking the Response
Formatter, Execution Control and Parser;
the Input Buffer is full, and the controller
is waiting to send more data bytes to the
device.
• UNTERMINATED Action
The controller attemps to read a Response
Message from the device without first
having sent a complete Query Message,
including the Program Message
Terminator.
• INTERRUPTED Action
The device is interrupted by a new Program
Message before it finishes sending a
Response Message.
Query Error Reporting
The QYE bit (2) is set true in the Standard-
defined Event Status Byte, and the error code
number is appended to the Error queue. The
error is reported by the mechanisms described
earlier in Section 6, Sub-section 6.5, which
deals with status reporting.
The specific reason for a query error must be
determined by inspection of the command
program. No error codes are provided from
within the 9500B.
8.A.2.2.6 Device-Dependent Errors
(DDE)
A Device-Dependent Error is generated if the
device detects an internal operating fault (eg.
during self-test). The DDE bit (3) is set true in
the Standard-defined Event Status Byte, and
the error code number is appended to the Error
queue. The error description appears on the
display, remaining visible until the next key-
press or remote command.
Errors are reported by the mechanisms
described earlier in Section 6, Sub-section 6.5,
which deals with status reporting.