Section 6: Instrument programming
Models 707B and 708B Switching Matrix Reference Manual
6-4
707B-901-01 Rev. A / August 2010
Tools for managing scripts
To manage scripts, you can send messages to the instrument, use your own development tool or
program, use the Keithley Test Script Builder Integrated Development Environment (TSB IDE), or use
TSB Embedded.
The TSB IDE is a programming tool that is included on the product CD. You can use it to create,
modify, debug, and store TSP scripts. For information on using the TSB IDE, see
TSB Embedded is a tool with a reduced set of features from the complete Keithley TSB IDE. TSB
Embedded has both script-building functionality and console functionality (single line ICL commands).
It is accessed from an Internet browser.
Create and load a script
When you create a script, you can create it as the anonymous script or as a named script.
Once a script is created and loaded into the instrument, you can execute it either 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.
a
Named scripts
A named script is a script with a unique name. You can have as many named scripts as needed in the
instrument (within the limits of the memory available to the runtime environment). When a named
script is created and loaded into the runtime environment with the
loadscript
or
loadandrunscript
commands, a global variable with the same name is created to reference the
script.
Key points regarding named scripts:
•
If you send a new script with the same name as an existing script, the existing script becomes an
unnamed script, which in effect removes the existing script if there are no other variables that
reference it.
•
Sending revised scripts with different names will not remove previously sent scripts.
•
Named scripts are stored in the runtime environment. Therefore, they are lost when the
instrument is turned off unless you also save them to nonvolatile memory. See
(on page 6-9).