Error Codes GPIB Error Strings
258 Agilent 8163A/B, 8164A/B & 8166A/B Mainframes, Fifth Edition
GPIB Error Strings
Error strings in the range -100 to -183 are defined by the SCPI standard,
downloadable from: http://www.scpiconsortium.org/scpistandard.htm
String descriptions taken from this standard (VERSION 1999.0 May, 1999),
whether in whole or in part, are enclosed by [ ].
Table 18 Overview for Supported Strings
New/Old/Standard
Error
Number String
Note:
Error strings in the range -100 to -183 are defined by the SCPI standard,
downloadable from: http://www.scpiconsortium.org/scpistandard.htm
String descriptions taken from this standard (VERSION 1999.0 May, 1999),
whether in whole or in part, are enclosed by [ ] in this table.
-100 to -199 Command Errors
Standard -100
"Command Error"
[This is the generic syntax error used when a more specific error cannot be
detected. This code indicates only that a Command Error as defined in IEEE
488.2,11.5.1.1.4 has occurred.]
Standard -101
"Invalid character"
[A syntactic element contains a character which is invalid for that type; for
example, a header containing an ampersand, SETUP&. This error might be
used in place of error -114 and perhaps some others.]
Standard -102
"Syntax error"
[An unrecognized command or data type was encountered; for example, a
string was received when the device does not accept strings.]
Standard -103
"Invalid separator"
[The parser was expecting a separator and encountered an illegal charac-
ter; for example, the semicolon was omitted after a program message unit]
Standard -104
"Data type error"
[The parser recognized a data element different than one allowed; for ex-
ample,numeric or string data was expected but block data was encoun-
tered.]
Standard -105 "GET not allowed"
[A Group Execute Trigger was received within a program message (see
IEEE488.2, 7.7).]
Standard -108 "Parameter not allowed"
[More parameters were received than expected for the header]
To Next Page
Loading...
