![background image](http://html2.mh-extra.com/html/keithley/system-sourcemeter-2601b/system-sourcemeter-2601b_reference-manual_4009934345.webp)
Series 2600B System SourceMeter® Instrument Reference Manual
Section 7: TSP command reference
2600BS-901-01 Rev. B / May 2013
7-5
1.
Instrument command name
. Indicates the beginning of the command description. It is followed
by a brief description of what the command does.
2.
Type of command
. Commands can be functions, attributes, or constants. If the command is an
attribute, it can be read-only (R), read-write (RW), or write-only (W). For detail on commands, see
Introduction to TSP operation
(on page 5-1).
3.
TSP-Link accessible
.
Yes
or
No
; indicates whether or not the command can accessed through a
TSP-Link network.
4.
Affected by
. Commands or actions that have a direct effect on this command.
•
LAN restore defaults
•
Recall setup
•
Instrument reset:
This command is reset when
reset()
,
localnode.reset()
, or
*RST
is sent.
1.
Where saved
. Indicates where the command settings reside once they are used on an
instrument. Options include:
•
Not saved:
Command is not saved anywhere and must be typed each time you use it.
•
Nonvolatile memory:
Storage area in the instrument where information is saved when the instrument
is turned off.
•
Saved setup:
Command is saved as part of the saved setup.
1.
Default value:
Lists the default value or constant for the command. The parameter values are
defined in the Usage or Details sections of the command description.
Command usage
The Usage section of the remote command listing shows how to properly structure the command.
Each line in the Usage section is a separate variation of the command usage; all possible command
usage options are shown here.
Figure 123: Command usage section
1
Structure of command usage:
Shows how the parts of the command should be organized. If a
parameter is shown to the left of the command, it is the return when you print the command.
Information to the right are the parameters or other items you need to enter.
2.
User-supplied parameters:
Indicated by italics. For example, for the function
beeper.beep(
duration, frequency
)
, replace
duration
with the number of seconds and
frequency
with the frequency of the tone.
beeper.beep(2, 2400)
generates a two-second,
2400 Hz tone.
Some commands have optional parameters. If there are optional parameters, they must be
entered in the order presented in the Usage section. You cannot leave out any parameters that
precede the optional parameter. Optional parameters are shown as separate lines in usage,
presented in the required order with each valid permutation of the optional parameters.
For example:
printbuffer
(
startIndex
,
endIndex
,
buffer1
)
printbuffer
(
startIndex
,
endIndex
,
buffer1
,
buffer2
)
Summary of Contents for System SourceMeter 2601B
Page 841: ......