Filter
Top Products
Appendix A Error Messages
List of Errors
A-8 Operating and Programming Guide
.
-178 Expression data not allowed Expression data was encountered but was not allowed by the Receiver at this point
in parsing.
-200 Execution error This is the generic syntax error if the Receiver cannot detect more specific errors.
-220 Parameter error Indicates that a program data element error occurred. This error is used when the
Receiver cannot detect more specific errors.
-221 Settings conflict Indicates that a legal program data element was parsed but could not be executed
due to the current Receiver state.
-222 Data out of range Indicates that a legal program data element was parsed but could not be executed
because the interpreted value is outside the legal range defined by the Receiver.
-223 Too much data Indicates that a legal program data element of block, expression, or string type was
received that contained more data than the Receiver could handle due to memory or
related receiver-specific requirements.
-224 Illegal parameter value Used where exact value, from a list of possible values, was expected (but not
received).
-230 Data corrupt or stale No valid data available.
-240 Hardware error Indicates that a legal program command or query could not be executed because of
a hardware problem in the Receiver.
-241 Hardware missing Indicates that a legal program command or query could not be executed because of
missing Receiver hardware.
-300 Device-specific error This is the generic device-dependent error.
-310 System error Indicates that a system error occurred.
-311 Memory error Occurs on EEPROM write failure.
-315 Configuration memory lost Could happen on powerup or preset if a nonvolatile memory problem is detected.
-321 Out of memory Indicates that the Receiver has detected that insufficient memory is available.
-330 Self-test failed Indicates at least one failure occurred when *TST? or :DIAG:TEST? was executed.
-350 Queue overflow An error occurred but was not recorded because the error queue is full.
-360 Communication error This is the generic communication error for devices that cannot detect the more
specific errors described for errors -361 through -363.
-361 Parity error in program
message
Parity bit not correct when data received for example, on a serial port.
-362 Framing error in program
message
A stop bit was not detected when data was received. For example, on a serial port
(for example, a baud rate mismatch).
-363 Input buffer overrun Software or hardware input buffer on serial port overflows with data caused by
improper or nonexistent pacing.
-440 Query UNTERMINATED
after indefinite response
Indicates that a query was received in the same program message after a query
requesting an indefinite response (e.g., *IDN? or :PTIM:TCOD? or :SYST:STAT?).
Table A-2. Error Messages (Continued)
Number Error String Cause