Error Messages - Ametek California Instruments MX15 Series User Manual

10 . Error Messages

Any errors that occur during operation from either the front panel or the remote control interface
will result in error messages. Error messages are displayed in the upper lleft-hand corner of the
LCD display. They are also stored in the error message queue from which they can be queried
using the SYST:ERR? Query. The error queue has a finite depth. If more error messages are
generated than can be held in the queue, a queue overflow message will be put in the last
queue location. To empty the queue, use the error query until the No Error result is received.
Errors appearing on the LCD will generally remain visible until the user moves to another screen.
If multiple error messages are generated in succession, only the last message will be visible as
there is only space for one error message on the LCD display.
The same area of the display is also used to display status messages. While error messages
always have a negative error number, status messages have a positive number.
The table below displays a list of possible error and status messages along with their possible
cause and remedy.
Number
0
-100
-102
-103
-104
-108
-109
-110
-111
-112
-113
-120
-121
-123
-128
-168
-200
-201
MX15
Message String
"No error"
"Command error"
"Syntax error"
"Invalid separator"
"Data type error"
"Parameter not allowed"
"M issing parameter"
"Command header error"
"header separator error"
"Program mnemonic too
long"
"Undefined header"
"Numeric data error"
"Invalid character in
number"
"Exponent too large"
"Numeric data not
allowed"
"Block data not allowed"
"Execution error"
"Invalid while in local"
Cause
No errors in queue
Unable to complete requested
operation
Command syntax incorrect.
SCPI separator not recognized
Data type invalid.
One or more additional
parameters were received.
Too few parameters received for
requested operation
Command header incorrect
Invalid command separator
used.
Syntax error
Command not recognized error
Data received is not a number
Number received contains non-
numeric character(s)
Exponent in number exceeds
limits
Number received when number
is not allowed.
Block data was sent.
Command could not be
executed
Command issued but unit is not
in remote state
Remedy
Unit may be in a mode inconsistent
with request.
M isspelled or unsupported command
See SCPI section of programming
manual.
Check command for supported data
types
Check programming manual for
correct number of parameters
Check programming manual for
correct number of parameters
Check syntax of command.
Use semi-colon to separate command
headers
Check programming manual for
correct command syntax
Check programming manual for
correct command syntax
Check programming manual for
correct command syntax
Check programming manual for
correct command syntax
Check programming manual for
correct parameter range
Check programming manual for
correct command syntax
Check programming manual for
correct command syntax
Command may be inconsistent with
mode of operation such as
programming frequency when in DC
mode.
Put instrument in remote state before
issuing GPIB commands.
169