169
Chapter 6 Error Messages
Execution Errors
4
6
-161 Invalid block data
For a definite-length block, the number of types of data sent does not
match the number of bytes that you specified in the block header
-168 Block data not allowed
Data was sent to the instrument in SCPI definite length block format but
this command does not accept this format.
-178 Expression data not allowed
A channel list was received but is not allowed for this command.
Example:
SYST:CTYPE? (@100)
-222 Data out of range
A numeric parameter value is outside the valid range for this command.
Example:
ARM:COUNT -3
-223 Too much data
A character string was received but could not be executed because the
string length was more than 13 characters. This error can be generated
by the DIAGnostic:DISPlay command.
-224 Illegal parameter value
A discrete parameter was received which was not a valid choice for this
command. You may have used an invalid parameter choice.
Example:
TRIG:SOURCE ALARM (ALARM is not a valid choice)
-310 System error
A firmware defect has been found. This is not a fatal error but you should
contact your nearest Agilent Technologies Service Center (see page 8) if
this error is reported.
-350 Queue overflow
The error queue is full because more than 10 errors have occurred. No
additional errors are stored until you remove errors from the queue. The
error queue is cleared by the *CLS (clear status) command or when power
is cycled. The errors are also cleared when you read the queue.
-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 bus Device Clear.
To Next Page
Loading...
Need help?
General