RIGOL Troubleshooting
5-8 User’s Guide for DSA1000 Series
-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.
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 for this specific
device; for example, *XYZ is not defined for any device.
Header suffix out of range.
The value of a numeric suffix attached to a program mnemonic, see
Syntax and Style section 6.2.5.2, making the header invalid.
-115 Unexpected number of parameters.
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).
-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
non-decimal 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.
-123 Exponent too large.
The magnitude of the exponent was larger than 32000 (see IEEE
488.2,7.7.2.4.1).
-124 Too many digits.
The mantissa of a decimal numeric data element contained more than
255 digits excluding leading zeros (see IEEE 488.2, 7.7.2.4.1).
-128 Numeric data not allowed.
A legal numeric data element was received, but the device does not