4-32 Chapter4
Troubleshooting
–199 to –100: Command Errors
–114 Header suffix out of range
The value of a header suffix attached to a program
mnemonic makes the header invalid.
–161 Invalid block data
A block data element was expected, but was invalid (see
IEEE 488.2, 7.7.6.2). For example, an END message was
received before the end length was satisfied.
–101 Invalid character
A syntactic command contains a character which is
invalid for that type. For example, a header containing
an ampersand, such as “SETUP&”. This error might be
used in place of error numbers –114, –121, –141 and
some others.
–141 Invalid character data
Either the character data element contains an invalid
character or the particular element received is not valid
for the header.
–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.
–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.
–103 Invalid separator
The parser was expecting a separator and encountered
an illegal character. For example, the semicolon was
omitted after a program message unit.
To Next Page
Loading...
Need help?
General
