Program Messages - Keithley SourceMeter 2790 Reference Manual

Hide thumbs Also See for SourceMeter 2790:
Table of Contents

Advertisement

10-14
klqb

Program messages

A program message is made up of one or more command words sent by the computer to
the instrument. Each common command is a three letter acronym preceded by an
asterisk (*). SCPI commands are categorized in the STATus subsystem and are used to
explain how command words are structured to formulate program messages.
STATus
:OPERation
:ENABle?
:PRESet
Single command messages
The above command structure has three levels. The first level is made up of the root com-
mand (STATus) and serves as a path. The second level is made up of another path
(:OPERation) and a command (:PRESet). The third path is made up of one command for
the :OPERation path. The three commands in this structure can be executed by sending
three separate program messages as follows:
stat:oper:enab <NRf>
stat:oper:enab?
stat:pres
In each of the above program messages, the path pointer starts at the root command (stat)
and moves down the command levels until the command is executed.
Multiple command messages
You can send multiple command messages in the same program message as long as they
are separated by semicolons (;). The following is an example showing two commands in
one program message:
stat:oper; stat:oper:enab <NRf>
If the command contains a question mark (?; query) or a non-optional number
included in the command word, you must include it in the short-form version.
Example:
:delay? = :del?
Command words or characters that are enclosed in brackets ([ ]) are optional and
need not be included in the program message.
For fastest response to commands, always use short forms.
:ENABle <NRf>
Model 2790 SourceMeter
Path (Root)
Path
Command and parameter
Query command
Command
®
Switch System Reference Manual

Advertisement

Table of Contents
loading

Table of Contents