Programming instructions

124 Error Messages
-131 Invalid suffix
A suffix was incorrectly specified for a numeric parameter. You may have misspelled the
suffix.
-134 Suffix too long
A header suffix is the number that can be appended to the end of some command headers.
This error is generated if the header suffix contains more than 12 characters.
-138 Suffix not allowed
A suffix was received following a numeric parameter. You may have misspelled the
suffix.
-148 Character data not allowed
A discrete parameter was received but a character string or a numeric parameter was
expected. Check the list of parameters to verify that you have used a valid parameter type.
Examples:
ROUTE:CLOSE CH101 or DIAG:DISP TEXT123 (the string must be enclosed
in quotes)
-151 Invalid string data
An invalid character string was received. Check to see if you have enclosed the character
string in quotation marks and verify that the string contains valid ASCII characters.
Example:
DIAG:DISP ’TESTING (the ending quote is missing)
-158 String data not allowed
A character string was received but is not allowed for this command. Check the list of
parameters to verify that you have used a valid parameter type.
-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 12 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 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