SCPI-Based Errors
386 FTB-500
–210 “Trigger error” -----
–211 “Trigger ignored” Indicates that a GET, *TRG, or triggering signal was
received and recognized by the device but was
ignored because of device timing considerations;
for example, the device was not ready to respond.
Note: a DT0 device always ignores GET and treats
*TRG as a Command Error.
–212 “Arm ignored” Indicates that an arming signal was received and
recognized by the device but was ignored.
–213 “Init ignored” Indicates that a request for a measurement
initiation was ignored as another measurement
was already in progress.
–214 “Trigger deadlock” Indicates that the trigger source for the initiation of
a measurement is set to GET and subsequent
measurement query is received. The
measurement cannot 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
measurement query is received. The
measurement cannot 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 should be used
when the device cannot detect the more specific
errors described for errors –221 through –229.
–221 “Settings conflict” Indicates that a legal program data element was
parsed but could not be executed due to the
current device state (see IEEE 488.2, 6.4.5.3 and
11.5.1.1.5).
Error
Number
Description Probable Cause
To Next Page
Loading...
