Error Codes GPIB Error Strings
260 Agilent 8163A/B, 8164A/B & 8166A/B Mainframes, Fifth Edition
Standard -150 “String data erro r”
[This error, as well as errors -151 through -159, are generated when pars-
ing a string data element. This error message is used when the device can-
not detect a more specific error.]
Standard -151 “Invalid string data”
[A string data e lemen t was e xpect ed, bu t was i nvali d for s ome re ason (see
IEEE 488.2, 7.7.5.2); for e xampl e, an E ND mes sage w as re ceived befo re the
terminal quote character.]
Standard -158 “String data not al lowed”
[A string data element was encou ntered but was not allow ed by the de-
vice at this point in parsing.]
Standard -161 “Invalid block data”
[A block data element was expected, but was invalid for some reason (see
IEEE 488.2, 7.7.6.2); for e xampl e, an E ND mes sage w as re ceived befo re the
length was satisfied.]
Standard -168 “Block data not allowed”
[A legal block data element was encountered but was not allowed by the
device at this point in parsi ng.]
Standard -170 “Expression error”
[This error, as well as errors -171 through -179, are generated when pars-
ing an expression data ele ment. This particula r error message is used
when the device cannot detect a more sp ecific error.]
Standard -171 “Invalid expression”
[The expression data element was invalid (see IEEE 488.2, 7.7.7.2); for ex-
ample, unmatched parentheses or an illegal character.]
Standard -178 “Expression data not allowed”
[A legal expression data was en countered but was not al lowed by the de-
vice at this point in parsing.]
Standard -181 “Invalid outside macro definition”
[Indicates that a m acro parameter placeholder ($ <number) was encoun-
tered outside of a macro definition.]
Standard -183 “Invalid inside macro definition”
[Indicates that the program mess age unit seque nce, sent wit h a *DDT or
*DMC command, is syntacticall y invalid (see IEEE 48 8.2, 10.7.6.3).]
Table18 Overview for Supported Strings
New/Old/Standard
Error
Number String