User`s guide
Table Of Contents
- Legal Notices
- Safety Notices
- In this Book
- Contents
- Quick Reference
- Installation
- Operating the Power Supply Locally
- Operating the Power Supply Remotely
- Language Reference
- SCPI Command Summary
- Calibration Commands
- Measure Commands
- Output Commands
- Source Commands
- [SOURce:]CURRent[:LEVel][:IMMediate][:AMPLitude]
|MIN|MAX [SOURce:]CURRent[:LEVel][:IMMediate][:AMPLitude]? [MIN|MAX][SOURce:]CURRent[:LEVel]:TRIGgered[:AMPLitude] |MIN|MAX [SOURce:]CURRent[:LEVel]:TRIGgered[:AMPLitude]? [MIN|MAX] - [SOURce:]CURRent:PROTection:STATe ON|OFF[SOURce:]CURRent:PROTection:STATe?
- [SOURce:]VOLTage[:LEVel][:IMMediate][:AMPLitude]
|MIN|MAX [SOURce:]VOLTage[:LEVel][:IMMediate][:AMPLitude]? [MIN|MAX][SOURce:]VOLTage[:LEVel]:TRIGgered[:AMPLitude] |MIN|MAX [SOURce:]VOLTage[:LEVel]:TRIGgered[:AMPLitude]? [MIN|MAX] - [SOURce:]VOLTage:LIMit:LOW
|MIN|MAX [SOURce:]VOLTage:LIMit:LOW? [MIN|MAX] - [SOURce:]VOLTage:PROTection:LEVel
|MIN|MAX[SOURce:]VOLTage:PROTection:LEVel? [MIN|MAX]
- [SOURce:]CURRent[:LEVel][:IMMediate][:AMPLitude]
- Status Commands
- STATus:PRESet
- STATus:OPERation[:EVENt]?
- STATus:OPERation:CONDition?
- STATus:OPERation:ENABle
STATus:OPERation:ENABle? - STATus:OPERation:NTR
STATus:OPERation:PTR STATus:OPERation:NTR? STATus:OPERation:PTR? - STATus:QUEStionable[:EVENt]?
- STATus:QUEStionable:CONDition?
- STATus:QUEStionable:ENABle
STATus:QUEStionable:ENABle? - STATus:QUEStionable:NTR
STATus:QUEStionable:PTR STATus:QUEStionable:NTR? STATus:QUEStionable:PTR? - *CLS
- *ESE*ESE?
- *ESR?
- *OPC*OPC?
- *SRE*SRE?
- *STB?
- *WAI
- System Commands
- Trigger Commands
- Programming Examples
- Specifications
- Verification and Calibration
- Verification
- Equipment Required
- Measurement Techniques
- Constant Voltage Tests
- Constant Current Tests
- Test Record Form – Agilent N5741A and N5761A
- Test Record Form – Agilent N5742A and N5762A
- Test Record Form – Agilent N5743A and N5763A
- Test Record Form – Agilent N5744A and N5764A
- Test Record Form – Agilent N5745A and N5765A
- Test Record Form – Agilent N5746A and N5766A
- Test Record Form – Agilent N5747A and N5767A
- Test Record Form – Agilent N5748A and N5768A
- Test Record Form – Agilent N5749A and N5769A
- Test Record Form – Agilent N5750A and N5770A
- Test Record Form – Agilent N5751A and N5771A
- Test Record Form – Agilent N5752A and N5772A
- Calibration
- Verification
- Service
- Compatibility
- Index
- Declaration of Conformity
4 Operating the Power Supply Remotely
58 Series N5700 User’s Guide
SCPI Commands – an Introduction
SCPI (Standard Commands for Programmable Instruments) is an
ASCII-based instrument command language designed for test and
measurement instruments. SCPI commands are based on a
hierarchical structure, also known as a tree system. In this system,
associated commands are grouped together under a common node or
root, thus forming subsystems. Subsystem commands perform
specific power supply functions. A portion of the SOURce subsystem
is shown below to illustrate the tree system.
[SOURce:]
CURRent
[:LEVel]
[:IMMediate] <NRf+>
:TRIGgered <NRf+>
:PROTection
:STATe <Bool>
SOURce is the root keyword of the command, CURRent is a second-
level keyword, LEVel and PROTection are third-level keywords, and
IMMediate, TRIGgered and STATe are fourth-level keywords. Colons
(:) separate higher-level from lower-level keywords.
Syntax
The following command syntax is used in this manual:
Square Brackets [ ] Items within square brackets are optional. The representation [SOURce:]VOLTage
means that SOURce: may be omitted.
Angle brackets < > Items within angle brackets are parameter descriptions. For example, <NR1>
indicates a specific form of numerical data.
Vertical bar | Vertical bars separate alternative parameters. For example, VOLT | CURR indicates
that either "VOLT" or "CURR" can be used as a parameter.
The syntax characters cannot be included in the command string.
Multiple Commands in a Message
Multiple SCPI commands can be combined and sent as a single
message with one message terminator. There are two important
considerations when sending several commands within a single
message:
Use a semicolon (;) to separate commands within a message.
There is an implied path that affects how commands are
interpreted by the power supply.
The command path can be thought of as a string that gets inserted
before each keyword within a message. For the first command in a
message, the path is a null string. For each subsequent command the
path is defined as the characters that make up the keywords of the