Agilent Technologies Twelfth 4287A RF LCR Operation Manual page 323

Table of Contents

Advertisement

-224
Illegal parameter value
The value of the parameter is illegal.
-213
Init ignored
Another measurement was being executed and the measurement start request (:INIT
command) was ignored.
-161
Invalid block data
Block data was expected but the sent block data was invalid for some reasons. (Refer to
IEEE488.2,7.7.6.2.) For example, the END message was received before the length of the
block data was reached.
-101
Invalid character
Invalid characters exist in the program message string. For example, for a correct program
message, ":CALC:PAR1:FORM LS", an ampersand (&) is inserted by mistake as
":CALC:PAR1:FORM&LS".
-121
Invalid character in number
An invalid character for the data type of the syntax analysis target was received. For
example, alphabetical characters exist in a decimal value, or "9" exits in octal data.
-171
Invalid expression
The equation data element is invalid. (Refer to IEEE488.2,7.7.7.2.) For example,
parentheses are not paired or a character violates the standard.
106
Invalid File Name
When executing the save/recall file command, a file name string was invalid. For example,
when executing the save command, no extension for the file was specified.
Specify a valid file name.
This error also occurs if the floppy disk has not been correctly inserted into the drive or the
disk is write-protected when you attempt to save a file onto it.
-103
Invalid separator
The parser (syntax analysis program) expected a separator, but a character other than a
separator was sent. For example, although the correct way is using ";" to separate two sent
program messages such as ":CALC:PAR1:FORM LS;*OPC?", the semicolon (;) needed to
separate the program messages is missing, as in ":CALC:PAR1:FORM LS *OPC?".
-151
Invalid string data
Character string data was expected but the sent string data was invalid for some reasons.
(Refer to IEEE488.2,7.7.5.2.) For example, the END message was received before the end
quotation mark character appeared.
-131
Invalid suffix
The suffix does not meet the syntax defined in IEEE488.2,7.7.3.2 or is inappropriate for
the 4287A.
Appendix F
Illegal parameter value
I
Error Messages
323

Advertisement

Table of Contents
loading

Table of Contents