|
-100 Command error
|
This event bit (Bit 5) indicates a syntax error, or a semantic error, or a GET command was entered, see IEEE 488.2, 11.5.1.1.4.
|
|
-101 Invalid character
|
Indicates a syntactic elements contains a character which is invalid for that type.
|
|
-102 Syntax error
|
Indicates that an unrecognized command or data type was encountered. For example, a string was received when the device does not accept strings.
|
|
-103 Invalid separator
|
The parser was expecting a separator and encountered an illegal character. For example, the semicolon was omitted after a program message unit.
|
|
-104 Data type error
|
The parser recognized a data element different than one allowed. For example, numeric or string data was expected but block data was encountered.
|
|
-105 Get not allowed
|
Indicates a Group Execute Trigger was received within a program message. Correct the program so that the GET does not occur within the program code.
|
|
-108 Parameter not allowed
|
Indicates that more parameters were received than expected for the header. For example, *ESE common command only accepts one parameter, so *ESE 0,1 is not allowed.
|
|
-109 Missing parameter
|
Indicates that less parameters were received than required for the header. For example, *ESE requires one parameter, *ESE is not allowed.
|
|
-110 Command header error
|
Indicates an error was detected in the header. This error is used when the device cannot detect the more specific errors -111 through -119.
|
|
-111 Header separator error
|
Indicates that a character that is not a legal header separator was encountered while parsing the header.
|
|
-112 Program mnemonic too long
|
Indicates that the header contains more that twelve characters, see IEEE 488.2, 7.6.1.4.1.
|
|
-
- 113 Undefined header
-
- 113 Undefined header
|
-
Indicates the header is syntactically correct, but it is undefined for this specific device. For example, `XYZ' is not defined for any device.
-
Attempt to set value of the GPS RF Generator Frequency or Frequency 2 will result in this error
|
|
-114 Header suffix out of range
|
Indicates the value of a header suffix attached to a program mnemonic makes the header invalid.
|
|
-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 non-decimal numeric types. This particular error is used if the device cannot detect a more specific error.
|
|
-121 Invalid character in number
|
Indicates 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
|
Indicates the magnitude of an exponent was greater than 32000, see IEEE 488.2, 7.7.2.4.1.
|
|
-124 Too many digits
|
Indicates 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
|
Indicates that a legal numeric data element was received, but the device does not 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 is used if the device cannot detect a more specific error.
|
|
-131 Invalid suffix
|
Indicates 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
|
Indicates the suffix contain more than 12 characters, see IEEE 488.2, 7.7.3.4.
|
|
-138 Suffix not allowed
|
Indicates that a suffix was encountered after a numeric element that 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 is used if the device cannot detect a more specific error.
|
|
-141 Invalid character data
|
Indicates that the character data element contains an invalid character or the particular element received is not valid for the header.
|
|
-144 Character data too long
|
Indicates the character data element contains more than twelve characters, see IEEE 488.2, 7.7.1.4.
|
|
-148 Character not allowed
|
Indicates 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 is used if the device cannot detect a more specific error.
|
|
-151 Invalid string data
|
Indicates that a string data element was expected, but was invalid, 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
|
Indicates that a string data element was encountered but was not allowed by the device at this point in parsing.
|
|
-160 Block data error
|
This error, as well as errors -161 through -169, are generated when parsing a block data element. This particular error message is used if the device cannot detect a more specific error.
|
|
-161 Invalid block data
|
Indicates a block data element was expected, but was invalid, see IEEE 488.2, 7.7.6.2. For example, and END message was received before the end length was satisfied.
|
|
-168 Block data not allowed
|
Indicates a legal block data element was encountered, but not allowed by the device at this point in parsing.
|
|
-170 Expression error
|
This error, as well as errors -171 through -179, are generated when parsing an expression data element. This particular error message is used if the device cannot detect a more specific error.
|
|
-171 Invalid expression
|
Indicates the expression data element was invalid, see IEEE 488.2, 7.7.7.2. For example, unmatched parentheses or an illegal character.
|
|
-178 Expression data not allowed
|
Indicates a legal expression data was encountered, but was not allowed by the device at this point in parsing.
|
|
-180 Macro error
|
This error, as well as error -181 through -189, are generated when defining a macro or execution a macro. This particular error message is used if the device cannot detect a more specific error.
|
|
-181 Invalid output macro definition
|
Indicates that a macro parameter place holder was encountered outside of a macro definition.
|
|
-183 Invalid inside macro definition
|
Indicates that the program message unit sequence, sent with a *DDT or a *DMC command, is syntactically invalid, see IEEE 488.2, 10.7.6.3.
|
|
-184 Macro parameter error
|
Indicates that a command inside the macro definition had the wrong number or type of parameters.
|