Chapter 5 Error Messages
Execution Errors
116
-221 Settings conflict
Indicates that a legal program data element was parsed but could not be executed due
to the current device state.
-222 Data out of range
A numeric parameter value is outside the valid range for the command.
Example: TRIG:DEL -3
-223 Too much data
A character string was received but could not be executed because the string length
was more than 40 characters. This error can be generated by the
CALibration:STRing command.
-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.
Example: DISP:STAT XYZ (XYZ is not a valid choice).
-330 Self-test failed
The power supply’s complete self-test failed from the remote interface (*TST?
command). In addition to this error, more specific self-test errors are also reported.
See also ‘‘Self-Test Errors’’, starting on
page 118.
-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) command
has been executed.
-420 Query UNTERMINATED
The power supply 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 an APPLy command (which does not generate data) and then
attempted an ENTER statement to read data from the remote interface.
-430 Query DEADLOCKED
To Next Page
Loading...
Need help?
General
