Not all commands require the complexity of the full command path. For example, the
Status? command doesn’t have a Node or Subnode.
Some commands allow for reading and writing data and some commands are Read Only.
To indicate a read function, a question mark (?) is placed at the end of the command path.
For example, a write command to change the load resistance to 100.5 ohms would be
“CONFigure:LOAD:VALue 100.5<cr>”, where <cr> indicates a carriage-return. For
example, a mArms read command would be “READ:MArms?<cr>”, which would return a
value of “xxx.x<cr><lf>” where <cr> is a carriage-return and <lf> is a linefeed.
Lowercase letters indicate the long-form of the command (for example,
CONFigure:INPut:RANGe?) and can be omitted for simplification. Uppercase letters
indicate the abbreviated, or short-form, of the commands and must be included (for
example, CONF:INP:RANG?).
All commands sent to the unit are terminated with a Carriage Return.
NOTE: Commands can be entered in either upper or lowercase or a mixture of the two,
uppercase and lowercase. Commands sent to the ESU –2050 are not case sensitive.
Upper and lower cases are only used when documenting the commands.
Parameter Form
The PARAMETER FORM column indicates the number and order of parameters in a
command and their legal values. Parameter formats are listed in angle brackets (<>) while
string parameters are simply listed.
Square brackets ([]) are used to enclose one or more parameters that are optional.
The vertical bar (|) can be read as “or” and is used to separate alternative parameter
options.
The query form of a command is generated by appending a question mark (?) to the last
keyword. However, not all commands have a query form, and some commands exist only
in the query form. The COMMENTS column is used to indicate this.
Comments
The COMMENTS column indicates any notes.
Komentarze do niniejszej Instrukcji