HP 132A, 53131A Error Types, Table 5-2.Errors (Continued)

Chapter 5 Errors

Error Types

Table 5-2. Errors (Continued)

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