This particular error message is used if the device cannot detect a more specific error. Suffix - This error, as well as errors -131 through -139, are generated when parsing a suffix. 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. 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. For example, an alpha in a decimal numeric or a "9" in octal data.Įxponent too large - Indicates the magnitude of an exponent was greater than 32000, see IEEE 488.2, 7.7.2.4.1. Invalid character in number - Indicates an invalid character for the data type being parsed was encountered. Numeric data - This error, as well as errors Header suffix out of range - Indicates the value of a header suffix attached to a program mnemonic makes the header invalid. For example, *XYZ is not defined for any device. Undefined header - Indicates the header is syntactically correct, but it is undefined for this specific device. Program mnemonic too long - Indicates that the header contains more that twelve characters, see IEEE 488.2, 7.6.1.4.1. Header separator - Indicates that a character that is not a legal header separator was encountered while parsing the header. This error is used when the device cannot detect the more specific errors -111 through -119. For example, *ESE requires one parameter, *ESE is not allowed.Ĭommand header - Indicates an error was detected in the header. Missing parameter - Indicates that less parameters were received than required for the header. For example, *ESE common command only accepts one parameter, so *ESE 0,1 is not allowed. Parameter not allowed - Indicates that more parameters were received than expected for the header.
Correct the program so that the GET does not occur within the program code.
GET not allowed - Indicates a Group Execute Trigger was received within a program message. For example, numeric or string data was expected but block data was encountered. For example, the semicolon was omitted after a program message unit.ĭata type -The parser recognized a data element different than one allowed. Invalid separator - The parser was expecting a separator and encountered an illegal character. For example, a string was received when the device does not accept strings. Syntax - Indicates that an unrecognized command or data type was encountered. Invalid character - Indicates a syntactic elements contains a character which is invalid for that type. When one of these errors is generated, the command error bit in the event status register is set.Ĭommand - 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. 300 to -399 SCPI Specified Device-Specific ErrorsĪ command error indicates that the test set's GPIB parser has detected an IEEE 488.2 syntax error.