Table of Contents
Advertisement
Figure 32-1
Error Messages
0
No error
-100
Command error
-101
Invalid character
-102
Syntax error
-103
Invalid separator
-104
Data type error
-105
GET not allowed
-108
Parameter not allowed
-109
Missing parameter
-112
Program mnemonic too long The header or character data element contains more than twelve characters.
-113
Undefined header
-121
Invalid character in number An invalid character for the data type being parsed was encountered. For example,
-123
Numeric overflow
-124
Too many digits
-128
Numeric data not allowed
-131
Invalid suffix
-138
Suffix not allowed
-141
Invalid character data
-144
Character data too long
-148
Character data not allowed A legal character data element was encountered where prohibited by the
-150
String data error
-151
Invalid string data
List of Error Messages
Figure 32-1 is a list of the error messages that are returned by the parser on
this oscilloscope.
The error queue is empty. Every error in the queue has been read (SYSTEM:ERROR?
query) or the queue was cleared by power-up or *CLS.
This is the generic syntax error used if the oscilloscope cannot detect more specific
errors.
A syntactic element contains a character that is invalid for that type.
An unrecognized command or data type was encountered.
The parser was expecting a separator and encountered an illegal character.
The parser recognized a data element different than one allowed. For example,
numeric or string data was expected but block data was received.
A Group Execute Trigger was received within a program message.
More parameters were received than expected for the header.
Fewer parameters were received than required for the header.
The header is syntactically correct, but it is undefined for the oscilloscope. For
example, *XYZ is not defined for the oscilloscope.
a "9" in octal data.
Number is too large or too small to be represented internally.
The mantissa of a decimal numeric data element contained more than 255 digits
excluding leading zeros.
A legal numeric data element was received, but the oscilloscope does not accept
one in this position for the header.
The suffix does not follow the syntax described in IEEE 488.2 or the suffix is
inappropriate for the oscilloscope.
A suffix was encountered after a numeric element that does not allow suffixes.
Either the character data element contains an invalid character or the particular
element received is not valid for the header.
oscilloscope.
This error can be generated when parsing a string data element. This particular
error message is used if the oscilloscope cannot detect a more specific error.
A string data element was expected, but was invalid for some reason. For example,
an END message was received before the terminal quote character.
Error Messages
List of Error Messages
32-9
Advertisement
Table of Contents
