Loading ...
Loading ...
Loading ...
Chapter 4 Troubleshooting&Message RIGOL
User’s Guide for DSA700 Series
4-11
-130 Suffix error.
This error, as well as errors -131 to -139, is generated when parsing a
suffix. This error message is always used when 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 to -149, is generated when parsing a
character data element. This error message should be used if the
device cannot detect a more specific error.
-141 Invalid character data.
The command header is invalid when the character data element
contains an invalid character or a particular character.
-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 used in a position prohibited by the
device.
-150 String data error.
This error, as well as errors -151 to -159, is generated when parsing a
string data element. This error message is always used when 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 legal string data element was encountered but was not allowed by
the device at this point in parsing.
Loading ...
Loading ...
Loading ...