Model 2601B-PULSE System SourceMeter Instrument Reference Manual Section 10: Instrument programming
2601B-PULSE-901-01A April 2020 10-3
Commands that cannot be used in scripts
Though the instrument accepts the following commands, you cannot use these commands in scripts.
Commands that cannot be used in scripts
IEEE Std 488.2 common commands
abort
endflash
endscript
flash
loadscript
loadandrunscript
password
restoreglobals
*CLS
*ESE
*ESE?
*ESR?
*IDN?
*OPC
*OPC?
*RST
*SRE
*SRE?
*STB?
*TRG
*TST?
*WAI
Manage scripts
This section describes how to create scripts by sending commands over the remote interface.
Tools for managing scripts
To manage scripts, you can send messages to the instrument, use your own development tool or
program, or use Keithley Instruments Test Script Builder (TSB) software. TSB software is a
programming tool that you can download from the Product Support web page
(tek.com/product-support). You can use it to create, modify, debug, and store Test Script Processor
(TSP
®
) scripting engine scripts. For more information about using the TSB software, see Using Test
Script Builder (TSB) (on page 10-31).
If you are using TSB to create scripts, you do not need to use the commands loadscript or
loadandrunscript and endscript.
Create and load a script
You create scripts by loading them into the runtime environment of the instrument. You can load a
script as a named script or as the anonymous script.
Once a script is loaded into the instrument, you can execute it remotely or from the front panel.
Anonymous scripts
If a script is created with the loadscript or loadandrunscript command with no name defined,
it is called the anonymous script. There can only be one anonymous script in the runtime environment.
If another anonymous script is loaded into the runtime environment, it replaces the existing
anonymous script.
To Next Page
Loading...
Need help?
General
