AMETEK M130 - Manual (Page 54)

IEEE 488.2 and SCPI Command Operation Sorensen Ethernet Option
3-4 M130/131 Programming Manual
3.2.4 O
PERATION
S
TATUS AND
Q
UESTIONABLE
S
TATUS
R
EGISTERS
The Operation Status and Questionable Status Registers will always return 0
when queried. The Operation Status Enable and Questionable Status Enable
Registers can be programmed and queried to allow SCPI compatibility but have
no effect on the Operation Status and Questionable Status Registers.
3.2.5 E
RROR
/E
VENT
Q
UEUE
The supply maintains an Error/Event Queue as defined by SCPI. The queue
holds up to 10 error events.
To view the error events, use the SYSTem:ERRor? Query command, which
reads in a First In/First Out (FIFO) manner. The read operation removes the
entry from the queue. The *CLS command clears all entries from the queue.
The following error codes are defined in the SCPI 1995.0 specification and are
supported by the M130. Error codes are in the range of [-32768, 32767]. SCPI
reserves the negative error codes and 0, while error codes greater than 0 are
device-specific errors.
Table 3-4 SCPI Error Codes
Error Code Description
208 Isolation relay must open first
An attempt to change the state of the polarity relay was made while the
isolation relay was closed. First open the isolation relay; then change the
state of the polarity relay.
207 Voltage sign mismatched polarity relay state
The algebraic sign on the voltage of a voltage programming command,
such as SOUR:VOLT , did not match the state of the polarity relay,
so the voltage command was ignored. For example, if the polarity relay is
in the positive voltage position (normal output voltage position), the
command SOUR:VOLT –5 will cause this error. Conversely, if the polarity
relay is in the negative voltage position (inverted output voltage position),
the command SOUR:VOLT 5 will cause this error.
Note that programming Over Voltage Protection with a mismatched
algebraic sign also can cause this error.
206 No channels setup to trigger
An attempt was made to trigger the M130 using the TRIG:TYPE <1|2|3>
command when there are no armed trigger settings. This error is not
generated when the GET is received, even when there are no armed
trigger settings.
205 GPIB or Ethernet GET not allowed during message
The GPIB or Ethernet G(roup) E(xecute) T(rigger) multiline command was
errantly generated by the system computer while or very shortly after a
message is or was sent. Give a few milliseconds after a message is sent
before attempting a GET; and never send a GET during a message
transfer over the GPIB or Ethernet.