Rubidium™ MG362x1A SeriesLow-Noise RF/Microwave SignalGenerators : Error Messages : Command Errors
 
Command Errors
An <error code> in the range [–199, –100] indicates that an IEEE 488.2 syntax error has been detected by the instrument’s parser. The occurrence of any error in this class should cause the command error bit (bit 5) in the standard event status register to be set. One of the following events has occurred:
• An IEEE 488.2 syntax error has been detected by the parser. That is, a controller-to-device message is received which is in violation of the IEEE 488.2 standard. Possible violations include a data element which violates the device listening formats or whose type is unacceptable to the device
• An unrecognized header was received. Unrecognized headers include incorrect device-specific headers and incorrect or unimplemented IEEE 488.2 common commands
• A Group Execute Trigger (GET) was entered into the input buffer inside of an IEEE 488.2<PROGRAM MESSAGE>
Events that generate command errors shall not generate execution errors, device-specific errors, or query errors; see the other error definitions in this chapter.
Command Errors (1 of 4)
Error Code
Error Description [description/explanation/examples]
11
EEPROM read/write error
EEPROM read and/or write failed
10
Hardware communication error
Failed to communicate with device hardware.
2
Option mismatch
Operation failed due to option mismatch.
1
Model mismatch
Operation failed due to option mismatch.
0
No error
The queue is completely empty. Every error/event in the queue has been read or the queue was purposely cleared by power-on, *CLS, etc.
-100
Command error
-101
Invalid character
A syntactic element contains a character which is invalid for that type.
–102
“Syntax error”
An unrecognized command or data type was encountered.
–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”
A Group Execute Trigger was received within a program message (see IEEE 488.2, 7.7).
–108
“Parameter not allowed”
More parameters were received than expected for the header.
–109
“Missing parameter”
Fewer parameters were received than required for the header.
–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.
–111
“Header Separator Error”
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 than 12 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.
–114
“Header suffix out of range”
The value of the numeric 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 the nondecimal 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 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 12 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 reasons (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.
–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 should be used if the device cannot detect a more specific error.
–161
“Invalid block data”
A block data element was expected, but invalid for some reason (see IEEE 488.2, 7.7.6.2); for example, an END message was received before the length was satisfied.
–168
“Block data not allowed”
A legal block data element was encountered but was 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 should be used if the device cannot detect a more specific error.
–171
“Invalid expression”
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”
A legal expression data element was encountered but was not allowed by the device at this point in parsing.
–180
“Macro error”
This error, as well as errors –181 through –189, are generated when defining a macro or executing a macro. This particular error message should be used if the device cannot detect a more specific error.
–181
“Invalid outside macro definition”
Indicates that a macro parameter placeholder ($<number) was encountered outside of a macro definition.
–183
“Invalid inside macro definition”
Indicates that the program message unit sequence, sent with a *DDT or *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.