Specifications

8-4
SCPI Messages
Command Errors [-199, -100]
-105 GET not allowed
A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7).
-108 Parameter not allowed
More parameters were received than expected for the header; for example, the *EMC
common command only accepts one parameter, so receiving *EMC 0,1 is not allowed.
-109 Missing parameter
Fewer parameters were received than required for the header; for example, the *EMC
common command requires one parameter, so receiving *EMC is not allowed.
-110 Command header error
An error was detected in the header. This error message should be used when the device
cannot detect the more specific errors described for errors -111 through -119.
-111 Header separator error
A character which is not a legal header separator was encountered while parsing the
header; for example, no white space followed the header, thus *GMC“MACRO” is an
error.
-112 Program mnemonic too long
The header contains more that twelve characters (see IEEE 488.2, 7.6.1.4.1).
-113 Undefined header
The header is syntactically correct, but it is undefined by this specific device; for example,
*XYZ is not defined for any device.
-114 Header suffix out of range
Indicates that a nonheader character has been encountered in what the parser expects is a
header element.
-120 Numeric data error
This error, as well as errors -121 through -129, are generated when parsing a data element
which appears to be numeric, including the nondecimal numeric types. This particular
error message should be used if the device cannot detect a more specific error.
-121 Invalid character in number
An invalid character for the data type being parsed was encountered; for example, an
alpha in a decimal numeric or a “9” in octal data.