Table of Contents
Advertisement
legal input range or is otherwise inconsistent with the device's capabilities.
• A valid program message could not be properly executed due to some device condition.
Execution errors shall be reported by the device after rounding and expression evaluation opera-
tions have taken place. Rounding a numeric data element, for example, shall not be reported as
an execution error. Events that generate execution errors shall not generate Command Errors,
device-specific errors, or Query Errors; see the other error definitions in this section.
Table 5-2. Execution Errors (1 of 3)
Error Number
Error Description [description/explanation/examples]
–200
desc = "Execution error"
help = ""
[This is the generic syntax error for devices that cannot detect more specific errors.
This code indicates only that an Execution Error as defined in IEEE 488.2,
11.5.1.1.5 has occurred.]
–213
desc = "INIT:IMM command ignored"
help = "An initiate immediate remote command was received. The instrument was
in continuous sweep mode when the command was received. The remote
command is ignored unless the instrument is in single sweep mode. To select single
sweep mode use the INIT:CONT OFF command."
–221
desc = "Settings Conflict Error"
help = "A request was made but the instrument settings resulting from the request
are in conflict with each other."
[Indicates that a legal program data element was parsed but could not be executed
due to the current device state (see IEEE 488.2, 6.4.5.3 and 11.5.1.1.5.)]
–222
desc = "Data out of range"
help = "A numeric value was entered which is outside the legal range of values for
the parameter. The name of the parameter is listed at the end of the error
message."
[Indicates that a legal program data element was parsed but could not be executed
because the interpreted value was outside the legal range as defined by the device
(see IEEE 488.2, 11.5.1.1.5.)]
Status Listings
SCPI-Defined Errors
5-11
Advertisement
Table of Contents
