A.4 *ese? — standard event status enable query, A.5 *esr? — event status register query, A.6 *idn? — identification query – KEPCO ATE-DMG SERIES User Manual

Page 66: A.7 *opc — operation complete command, A.8 *opc? — operation complete query

Advertising
background image

A-2

ATE-DMG 042314

A.4

*ESE? — STANDARD EVENT STATUS ENABLE QUERY

*ESE?

Syntax:

*ESE?

Return value: Integer> value per Table A-2.

Description: Returns the mask stored in the Standard Event Status Enable Register. Contents of Standard

Event Status Enable register (*ESE) determine which bits of Standard Event Status register (*ESR)
are enabled, allowing them to be summarized in the Status Byte register (*STB). All of the enabled
events of the Standard Event Status Enable Register are logically ORed to cause ESB (bit 5) of the
Status Byte Register to be set (1 = set = enable function, 0 = reset = disable function). (See example,
Figure A-1.)

A.5

*ESR? — EVENT STATUS REGISTER QUERY

*ESR?

Syntax:

*ESR?
Return value: <integer> (Value = contents of Event Status register as defined in Table A-2.)

Description: Causes the power supply to return the contents of the Standard Event Status register. After it

has been read, the register is cleared. The Standard Event Status register bit configuration is
defined in Table A-2 (1 = set, 0 = reset). The error bits listed in Table A-2 are also related to error
codes produced during parsing of messages and to errors in the power supply. (See example, Figure
A-1.)

A.6

*IDN? — IDENTIFICATION QUERY

*IDN?

Syntax:

*IDN?
Return value: Character string

Description: Identifies the instrument. This query requests identification. The power supply returns a string

which contains the manufacturer name, the model, the serial number and the firmware level. The
character string contains the following fields: <Manufacturer>, <Model>, <Serial Number>, <Firmware
revision> where: <Manufacturer> = KEPCO, <Model> = ATE-V V - AA (V V is Vmax, AA is Imax, e.g.
100-10 or 6-100), <Serial Number> = MM,DD,YY-SSS (MM - month, DD - day, YY - year, SSS - serial
number in that day) <Firmware revision>=n.m (n.m revision, e.g, 1.0) (See example, Figure A-1.)

A.7

*OPC — OPERATION COMPLETE COMMAND

*OPC

Syntax:

*OPC

Description: Causes power supply to set status bit 0 (Operation Complete) when pending operations are

complete This command sets Standard Event Status Register bit 0 (see Table A-2) to “1” when all pre-
vious commands have been executed and changes in output level have been completed. This com-
mand does not prevent processing of subsequent commands, but bit 0 will not be set until all pending
operations are completed. (1 = set = enable function, 0 = reset = disable function). (See example, Fig-
ure A-1.) As an example, the controller sends command(s), then sends *OPC. If controller then sends
*ESR?, the power supply responds with either a “0” (if the power supply is busy executing the pro-
grammed commands), or a “1” (if the previously programmed commands are complete). (See exam-
ple, Figure A-1.)

A.8

*OPC? — OPERATION COMPLETE QUERY

*OPC?

Syntax:

*OPC?
Return value: <1> (ASCII) placed in output queue when power supply has completed operation.

Description: Indicates when pending operations have been completed.When all pending operations are com-

plete (all previous commands have been executed and changes in output level have been completed)
a “1” is placed in the Output Queue. Subsequent commands are inhibited until the pending operations
are completed. *OPC? is intended to be used at the end of a command line so that the application pro-
gram can monitor the bus for data until it receives the “1” from the power supply Output Queue. (See
example, Figure A-1.)

Advertising