This section summarizes the mandatory subset of IEEE 488.2 commands required for any SCPI compliant instrument.
Common command |
Description |
Clears all status data structures |
|
Programs the Standard Event Status Enable register bits |
|
Reads the Standard Event Status Register |
|
Returns the UNIQUE identification of the PSU |
|
Operation Complete Command used for program synchronization |
|
Recalls the PSU state stored in the specified storage location |
|
Reset PSU to the initial state |
|
Stores the current PSU state in the specified storage location |
|
Enables bits in the Status Byte enable register. |
|
Reads the Status Byte register |
|
Generates a software trigger |
|
Returns Self-Test results |
|
Waits until all pending commands are completed |
Syntax |
*CLS |
Description |
Clear Status Command. This command clears all status data structures in the PSU:
The corresponding condition and enable registers are unaffected. If *CLS immediately follows a program message terminator (<NL>), then the output queue and the MAV bit are also cleared. |
Return |
None |
Related Commands |
*ESR? STATus:OPERation[:EVENt] STATus:OPERation:INSTrument[:EVENt] STATus:OPERation:INSTrument:ISUMmary[<n>][:EVENt] STATus:QUEStionable[:EVENt] STATus:QUEStionable:INSTrument[:EVENt] STATus:QUEStionable:INSTrument:ISUMmary[<n>][:EVENt] SYSTem:ERRor |
Syntax |
*ESE {<value>} *ESE? |
|||
Description |
Standard Event Status Enable Command. This command sets the Standard Event Status Enable register bits in the PSU. Those settings determine which events of the Standard Event Status Event register (see *ESR?) are allowed to set the ESB (Event Summary Bit) of the Status Byte register. A 1 in the bit position enables the corresponding event. All of the enabled events of the Standard Event Status Event Register are logically ORed sets the Event Summary Bit (ESB) of the Status Byte Register. A STATus:PRESet command does not clear the bits in the Status Byte register. See also Section 3.1 in this document. |
|||
Parameters |
Name |
Type |
Range |
Default |
|
<value> |
NR1 |
0 – 255 (A decimal value which corresponds to the binary-weighted sum of the bits in the register. See also table in Section 3.1). |
– |
Return |
The query reads the enable register and returns a decimal value which corresponds to the binary-weighted sum of all bits set in the register. |
|||
Usage example |
To enable bit 2 (decimal value = 4), bit 3 (decimal value = 8), and bit 7 (decimal value = 128), the corresponding decimal value would be 140 (4 + 8 + 128): *ESE 140 Read value of the Standard Event Status Enable register: *ESE? 140 |
|||
Errors |
-200,"Execution error" |
|||
Related Commands |
*CLS *ESR *RST STATus:PRESet |
Syntax |
*ESR? |
Description |
Standard Event Status Register (see Section 3.2) Query. Reading the Standard Event Status Event register clears it. |
Return |
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register. |
Usage example |
If ERRor (bit 2) is set: ESR? 4 |
Syntax |
*IDN? |
Description |
Identification query for the UNIQUE identification of the PSU. (see also IEEE 488.2 10.14). |
Return |
The following system parameters will be displayed: <vendor>, <model>, <serial number>, <firmware>. The <model> include information about the CPU in use in brackets and could be Due or Simulator. More information about the simulator can be found in Section 9. |
Usage example |
*IDN? Envox,EEZ H24005 (Due),CS17001,v1.1 |
Syntax |
*OPC *OPC? |
Description |
Operation Complete Command. The command is mainly used for program synchronization. It causes the PSU to set the OPC bit (bit 0) of the Standard Event Status register when the PSU has completed all pending operations *OPC. Pending operations are complete when:
Query whether the current operation is completed and the query returns 1. See also IEEE 488.2 Section 12.5 – 12.8. |
Return |
Query causes the PSU to place a 1 in the output buffer when all pending operations are completed. *OPC? does not suspend processing of commands. |
Usage example |
*OPC? 1 if current operation is not completed: *OPC? 0 |
Syntax |
*RCL {<profile>} |
|||
Description |
This command recalls the PSU state stored in the specified storage location. The PSU has ten storage locations in non-volatile memory to store PSU states. It is not possible to recall the PSU state from a storage location that is empty or was deleted (Error 400 will be generated). When the firmware is started for the first time, storage locations 1 through 9 are empty (location 0 has the power-on state).
The PSU uses location 0 to automatically save the state of the PSU at power down. |
|||
Parameters |
Name |
Type |
Range |
Default |
|
<profile> |
NR1 |
0 – 9 |
– |
Return |
None |
|||
Usage example |
*RCL 2 |
|||
Errors |
||||
Related Commands |
*SAV MEMory:STATe:DELete MEMory:STATe:RECall:AUTO MEMory:STATe:RECall:SELect SYSTem:POWer |
Syntax |
*RST |
Description |
Reset Command. Restores the PSU to its initial state (as predefined in the PSU firmware, see Section 8.2) and clears the error queue. The reset command does NOT affect calibration data, nor any of saved configuration profiles (0 to 9). When *RST is issued, all outputs are set to OFF, and voltage and current are programmed to 0. The power up sequence is started. All SPI peripherals are reinitialize except the controller if an active Ethernet connection exists. |
Return |
None |
Usage example |
*RST MEMory:RECall:AUTO SYSTem:POWer |
Related Commands |
*RST *SAV MEMory:STATe:CATalog? |
Syntax |
*SAV {<profile>} |
|||
Description |
This command stores the current instrument state in the specified storage location. Any state previously stored in the same location is overwritten without generating any errors. The PSU has nine storage locations in non-volatile memory which are available to the user for storing PSU states. The following channel and system parameters are stored in the non-volatile memory:
Users can assign an arbitrary name to each of locations 1 through 9 using the MEMory:STATe:NAME command.
A reset (*RST command) does not affect the configurations stored in memory. Once a state is stored, it remains constant until it is overwritten using this command or specifically deleted using the MEMory:STATe:DELete command.
The PSU uses location 0 to automatically hold the state of the PSU at power down. |
|||
Parameters |
Name |
Type |
Range |
Default |
<profile> |
NR1 |
1 – 9 |
– |
|
Return |
None |
|||
Usage example |
*SAV 2 |
|||
Related Commands |
*RCL *RST MEMory:STATe:CATalog? MEMory:STATe:NAME MEMory:STATe:DELete |
Syntax |
*SRE {<value>} *SRE? |
|||
Description |
Enable bits in the Status Byte enable register (see Section 3.2). |
|||
Parameters |
Name |
Type |
Range |
Default |
|
<value> |
NR1 |
0 – 255 (A decimal value which corresponds to the binary-weighted sum of the bits in the register. See also table in Section 3.1). |
– |
Return |
Query the Status Byte enable register. The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits set in the enable register. |
|||
Usage example |
*SRE 32 |
|||
Related Commands |
*STB |
Syntax |
*STB? |
Description |
Read Status Byte Query. This query reads the Status Byte register (see Section 3.2), which contains the status summary bits and the Output Queue MAV bit. The Status Byte is a read-only register and its bits are not cleared when it is read.
A serial poll also returns the value of the Status Byte register, except that bit 6 returns Request for Service (RQS) instead of Master Status Summary (MSS). A serial poll clears RQS, but not MSS. When the MSS bit is set, the PSU has one or more reasons for requesting service. |
Return |
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register. |
Usage example |
If OPER (bit 7) is set: *STB? 128 |
Related Commands |
*SRE |
Syntax |
*TRG |
Description |
This command generates a trigger to the trigger subsystem which has selected a bus (software) trigger as its source (TRIGger[:SEQuence]:SOURce BUS). |
Return |
None |
Usage example |
Generate a trigger operation after 5 seconds: TRIG:SOUR BUS TRIG:DEL 5 INIT *TRG |
Errors |
-211, "Trigger ignored" 304,"Incompatible transient modes" 307,"List lengths are not equivalent" |
Related Commands |
*WAI ABORt INITiate TRIGger[:SEQuence]:DELay TRIGger[:SEQuence]:SOURce |
Syntax |
*TST? |
Description |
Self-Test Query. The self-test query causes an internal self-test, and places a response into the Output Queue indicating whether or not the PSU completed the self-test without detected errors.
Note: All all terminal connections must be removed while the internal self-test is being performed.
If an active Ethernet connection exists, testing of the Ethernet controller will be skipped. You can use DIAGnostic[:INFOrmation]:TEST? for to produce a detailed report of the latest self-test.
If a fan is installed, and not running, this command will start it for the short time to obtain speed information. |
Return |
0 or 1 depends of the self-test results. See also DIAGnostic[:INFOrmation]:TEST?. |
Usage example |
If all tests passed: *TST? 0 If one or more tests failed: *TST? 1 |
Related Commands |
DIAGnostic[:INFOrmation]:TEST? SYSTem:BEEP:STATe |
Syntax |
*WAI |
Description |
Not implemented yet
The Wait-to-Continue Command causes the PSU to wait until all pending commands are completed before executing any other commands.
Pending operations are as defined under the *OPC command. |
Return |
None |
Usage example |
For example, the *WAI command can be used to make a voltage measurement after an OUTPut ON command has completed: OUTPut ON;*WAI;:MEASure:VOLTage? |
Related Commands |
*OPC |