HP 53150A Series, Programming Manual

Page: 171 / 186

Chapter 5 Errors
Error Types
Programming Guide 5-9
5
Table 5-2. Errors (Continued)
Number Error String Cause
-131
-134
-138
-140
-141
-144
-148
-150
-151
-158
Invalid suffix
Suffix too long
Suffix not allowed
Character data error
Invalid character data
Character data too long
Character data not allowed
String data error
Invalid string data
String data not allowed
The suffix does not follow the syntax described in IEEE 488.2 or the
suffix is inappropriate for the Counter.
The suffix contained more than 12 characters.
A suffix was encountered after a numeric element that does not allow
suffixes.
This error can be generated when parsing a character data element.
This particular error message is used if the Counter cannot detect a
more specific error (errors -141 through -149).
The character data element contains an invalid character.
The character data element contains more than twelve characters.
A legal character data element was encountered where prohibited by the
Counter.
This error can be generated when parsing a string data element. This
particular error message is used if the Counter cannot detect a more
specific error.
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.
-160
-161
-168
-170
-171
-178
-181
-200
-210
Block data error
Invalid block data
Block data not allowed
Expression error
Invalid expression
Expression data not
allowed
Invalid outside macro
definition
Execution error
Trigger error
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 (errors -161 through -169).
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.
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.