Filter
Top Products
Digitizers Error Messages 147Appendix C
-221 Settings conflict You tried to set a pretrigger count that exceeds the sample count -1.
Or, you enabled one of the internal triggers as the source for a
particular channel such as channel 2 (TRIG:SOUR INT2) and then
tried to enable one of the limit checking features on channel 2
(CALC2:LIM:UPP:STAT ON).
-222 Data out of range A numeric parameter value is outside the valid range for the command.
Example: digitizer is on the 1V range and you send TRIG:LEV -3
-224 Illegal parameter
value
A discrete parameter was received which was not a valid choice for
the command. You may have used an invalid parameter choice.
Examples: CAL:SOUR TTLT2 (TTLT2 is not a valid choice) or
SAMP:COUN ON (ON is not a valid choice).
-230 Data corrupt or stale NOT USED
-231 Data questionable NOT USED
-240 Hardware error This can occur if the instrument fails at power on.
-241 Hardware missing Usually is a result of sending a legal E1564A command to an E1563A.
An example is CAL:DAC:VOLT, which is only legal for an E1564A.
-300 Device-specific error NOT USED
-311 Memory error NOT USED
-312 PUD memory lost NOT USED
-313 Calibration memory
lost
NOT USED
-330 Self-test failed The digitizer's complete self-test failed from the remote interface
(*TST?). In addition to this error, more specific self-test errors are also
reported. See also “Self-Test Errors” following this section.
-350 Too many errors The error queue is full because more than 20 errors have occurred.
No additional errors are stored until you remove errors from the queue.
The error queue is cleared when power has been off, or after a *CLS
(clear status) command has been executed.
-410 Query
INTERRUPTED
A command was received which sends data to the output buffer, but
the output buffer contained data from a previous command (the
previous data is not overwritten). The output buffer is cleared when
power has been off or after a *RST (reset) has been executed.
-420 Query
UNTERMINATED
The digitizer was addressed to talk (i.e., to send data over the
interface) but a command has not been received which sends data
to the output buffer. For example, you may have executed a
SAMPle:COUNt <
count
> (which does not generate data) and then
attempted an ENTER statement to read data from the remote interface.
-430 Query
DEADLOCKED
A command was received which generates too much data to fit in the
output buffer and the input buffer is also full. Command execution
continues but all data is lost.
Number Title Description