Filter
Top Products
Execution errors
Error
Number
Error Description description/explanation/examples
–200
Execution error This is the generic syntax error for devices that can
-
not detect more specific errors. This code indicates
only that an Execution Error as defined in
IEEE-488.2, 11.5.1.1.5 has occurred.
–210
Trigger error
–211
Trigger ignored
Indicates that a GET, ∗TRG, or triggering signal was
received and recognized by the counter but was ig
-
nored because of counter timing considerations; for
example, the counter was not ready to respond.
–212
Arm ignored Indicates that an arming signal was received and
recognized by the counter but was ignored.
–213
Init ignored Indicates that a request for a measurement initiation
was ignored because another measurement was al-
ready in progress.
–214
Trigger deadlock Indicates that the trigger source for the initiation of a
measurement is set to GET and subsequent mea-
surement query is received. The measurement can-
not be started until a GET is received, but the GET
would cause an INTERRUPTED error.
–215
Arm deadlock Indicates that the arm source for the initiation of a
measurement is set to GET and subsequent mea-
surement query is received. The measurement can-
not be started until a GET is received, but the GET
would cause an INTERRUPTED error.
–220
Parameter error Indicates that a program-data-element related error
occurred. This error message is used when the
counter cannot detect the more specific errors –221
to –229.
–221
Settings conflict Indicates that a legal program data element was
parsed but could not be executed due to the current
counter state (see IEEE-488.2, 6.4.5.3 and
11.5.1.1.5.)
Settings conflict;
PUD memory is
protected
Settings conflict; in
-
valid combination of
channel and function
Error Messages
Error Code -200 to -221 8-7