Rigol DSA1030, User Manual

Page: 231 / 287

Troubleshooting RIGOL
User’s Guide for DSA1000 Series 5-9
accept one in this position for the header.
-130 Suffix error.
This error, as well as errors -131 through -139, are generated when
parsing a suffix. This particular error message should be used if the
device cannot detect a more specific error.
-131 Invalid suffix.
The suffix does not follow the syntax described in IEEE 488.2, 7.7.3.2,
or the suffix is inappropriate for this device.
-134 Suffix too long.
The suffix contained more than 12 characters (see IEEE 488.2, 7.7.3.4).
-138 Suffix not allowed.
A suffix was encountered after a numeric element which does not allow
suffixes.
-140 Character data error.
This error, as well as errors -141 through -149, are generated when
parsing a character data element. This particular error message should
be used if the device cannot detect a more specific error.
-141 Invalid character data.
Either the character data element contains an invalid character or the
particular element received is not valid for the header.
-144 Character data too long.
The character data element contains more than twelve characters (see
IEEE 488.2, 7.7.1.4).
-148 Character data not allowed.
A legal character data element was encountered where prohibited by
the device.
-150 String data error.
This error, as well as errors -151 through -159, are generated when
parsing a string data element. This particular error message should be
used if the device cannot detect a more specific error.
-151 Invalid string data.
A string data element was expected, but was invalid for some reason
(see IEEE 488.2, 7.7.5.2); for example, an END message was received
before the terminal quote character.
-158 String data not allowed.
A string data element was encountered but was not allowed by the
device at this point in parsing.
-160 Block data error.