AMETEK M130 - Manual (Page 55)

Sorensen Ethernet Option IEEE 488.2 and SCPI Command Operation
M130/M131 Programming Manual 3-5
Error Code Description
204 GPIB or Ethernet IFC caused warm boot
This error relates to the GPIB or Ethernet IFC signal, and is available only
in association with a proprietary command.
203 Hardware watchdog warm boot
Caused by a hardware fault either in the power supply proper, or on the
M130. One possible explanation might be that the mains power to the
supply was interrupted for a short but sufficient time to cause the M130
processor to reset and re-boot. Also, it might be possible to generate this
error by a very momentary power-off through the front panel power switch.
202 Foreground watchdog warm boot
The internal firmware on the M130 found an internal error condition that
halted processing; to force resumption of processing, a warm boot is
required.
201 Unexpected warm boot
The M130 GPIB or Ethernet-side processor experienced a warm boot that
was unexpected, and it may indicate an internal crash of the M130
processor.
102 Incompatible unit type
This error is not used. It cannot occur.
101 Incompatible unit version
This slave does not support user defined initialization values nor ramping;
its firmware is too old a version to do so. Slave #n provides its firmware
version number as the last number on the response from the *IDN[n]?
query command.
100 Incompatibility error
This error is not used. It cannot occur.
0 No error
The error queue is empty.
-102 Syntax error
An unrecognized command or data type was encountered.
-108 Parameter not allowed
More arguments than expected were received.
-151 Invalid string data
Incorrect password. Manufacturer, model, or serial number string was
more than 16 characters. Invalid mnemonic.
-161 Invalid block data
The expected number of data values was not received.
-200 Execution error
An error/event number in the range [-299,-200] indicates that an error has
been detected by the instruments execution control block. The occurrence
of any error in this class shall cause the execution error bit (bit 4) in the
Event Status Register to be set. An execution error can be the result of:
• A <program data> element out of range, such as programming 35 volts
in a 33 volt device.
• A command could not be executed due to the current condition of the
device.
-203 Command protected
Attempted to store calibration values to EEPROM without unlocking.