Service manual

Appendix C 231
Error messages
Order of Alphabet
C. Error Messages
-161 Invalid block data
Block data was expected but given 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, “MEAS
IRIM,” an ampersand (&) is inserted by mistake, like “MEAS&IRIM.”
-141 Invalid character data
There are invalid characters in a character data element or the received parameter is not
valid. For example, though a correct program message was “MEAS LSR,” a wrong
program message, “MEAS LSD,” was received.
-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.
154 INVALID DATE
You attempted to specify the date of the built-in clock using the DATE key or the
SETCDATE command, but the date was out of range and, as a result, the setting you
attempted to execute became invalid. The settable range is: 1900 to 2099 for year, 1 to 12
for month, and 1 to 31 for day. Also, you cannot specify a date that does not exist actually.
Specify correct date 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.
112 INVALID FILE NAME
When the recall command (RECD <string>) or the re-save command (RESAVD <string>)
was executed, a string that indicated a file name was not followed by a necessary extension
and, as a result, the command was ignored. Add a required extension, and then perform
recall or re-save. This message occurs, for example, when you attempt to execute the recall
or re-save command without adding an extension (“.STA”, “.DAT”, “.TXT”) to a file
name. Also, it does when you attempt to execute re-save of a graphics file without adding
an extension (“.TIF”).
-103 Invalid separator
The parser (syntax analysis program) expected a separator, but a character other than a
separator was sent. For example, though the correct way is using “;” to separate 2 sent
program messages like “MEAS IRIM;FMT LOGY”, a semicolon (;) to separate the program
messages is missing, like “MEAS IRIM FMT LOGY”.
-151 Invalid string data
Character string data was expected but given 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 it is inappropriate for
the 4294A.