SCPI-Based Errors
Error
Description
Number
–110
"Command header
error"
–111
"Header separator
error"
–112
"Program mnemonic
too long"
–113
"Undefined header"
–114
"Header suffix out of
range"
–115
"Unexpected number
of parameters"
–120
"Numeric data error"
–121
"Invalid character in
number"
418
Probable Cause
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.
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.
The header contains more that twelve characters
(see IEEE 488.2, 7.6.1.4.1).
The header is syntactically correct, but it is
undefined for this specific device; for example,
*XYZ is not defined for any device.
The value of a numeric suffix attached to a
program mnemonic (see IEEE 488.2, Syntax and
Style section 6.2.5.2) makes the header invalid.
The number of parameters received does not
correspond to the number of parameters
expected. This is typically due an inconsistency
with the number of instruments in the selected
group (see section on
INSTrument:DEFine:GROup).
This error, as well as errors –121 through –129, are
generated when parsing a data element which
appears to be numeric, including the non-decimal
numeric types.This particular error message
should be used if the device cannot detect a more
specific error.
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.
FTB-500