HP 53131A/132A 225 MHz Programming Manual page 318

Number Error String
-151 Invalid string data
-158 String data not allowed
-160 Block data error
-161 Invalid block data
-168 Block data not allowed
-170 Expression error
-171 Invalid expression
-178 Expression data not allowed
-181 Invalid outside macro definition
-183 Invalid inside macro definition
-200 Execution error
-210 Trigger error
-211 Trigger ignored
-213 Init ignored
-220 Parameter error
-221 Settings conflict
-222 Data out of range
-223 Too much data
Chapter 5 Errors
Error Types
Table 5-2. Errors (Continued)
Cause
A string data element was expected but was invalid for some reason.
For example, an END message was received before the terminal
quote character.
A string data element was encountered but was not allowed by the
Counter at this point in parsing.
This error can be generated when parsing a block data element.
This particular error message is used if the Counter cannot detect a
more specific error.
A block data element was expected, but it was not allowed by the
Counter at this point in parsing.
A legal block data element was encountered but was not allowed by
the Counter at this point in parsing.
This error can be generated when parsing an expression data
element. It is used if the Counter cannot detect a more specific error.
The expression data element was invalid (see IEEE 488.2).
For example, unmatched parentheses or an illegal character.
Expression data was encountered but was not allowed by the Counter
at this point in parsing.
Indicates that a macro parameter placeholder ($<number>) was
encountered outside of a macro definition.
Indicates that the program message unit sequence, sent with a *DMC
command, is syntactically invalid.
This is the generic syntax error if the Counter cannot detect more
specific errors. This code indicates only that an Execution Error has
occurred.
Used if the Counter cannot detect a more specific error from the :INIT,
:TRIG, or :ABOR subsystems.
Indicates that a GET or *TRG was received and recognized by the
Counter but was ignored.
Indicates that a request for a measurement initiation was ignored as
another measurement was in progress.
Indicates that a program data element related error occurred. This
error is used when the Counter cannot detect more specific errors.
Indicates that a legal program data element was parsed but could not
be executed due to the current Counter state.
Indicates that a legal program data element was parsed but could not
be executed because the interpreted value is outside the legal range
defined by the Counter. Typically, the value is clipped to legal limit.
Indicates that a legal program data element of block, expression,
or string type was received that contained more data than the Counter
could handle due to memory or related Counter-specific requirements.
5-8 Programming Guide