EXFO FTB-500 (Window XP) - Manual (Page 372)

SCPI-Based Errors
362 FTB-500
–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 reason (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 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 was
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 was encountered but was
not allowed by the device at this point in parsing.
Error
Number
Description Probable Cause