Chapter 5 Errors
Error Types
5-8 Programming Guide
Table 5-2. Errors (Continued)
Number Error String Cause
-151
-158
-160
-161
-168
-170
-171
-178
-181
-183
-200
-210
-211
-213
-220
-221
-222
-223
Invalid string data
String data not allowed
Block data error
Invalid block data
Block data not allowed
Expression error
Invalid expression
Expression data not allowed
Invalid outside macro definition
Invalid inside macro definition
Execution error
Trigger error
Trigger ignored
Init ignored
Parameter error
Settings conflict
Data out of range
Too much data
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.
