BNC 1105 Universal Counter - Manual (Page 91)

91 91 91 91
7.2 Execution Errors
-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 when 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 Setting 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.
-224 Illegal parameter value
Used where exact value, from a list of possible values, was expected.
-230 Data corrupt or stale
No valid data available. New measurement started but not completed.
-240 Hardware error
Indicates that a legal program command or query could not be executed because of
a hardware problem in the Counter.
-241 Hardware missing
Indicates that a legal program command or query could not be executed because of