
In this section:
Introduction to TSP operation ................................................... 5-1
About TSP commands ............................................................. 5-3
Factory scripts ........................................................................ 5-18
Introduction to TSP operation
Instruments that are Test Script Processor (TSP
®
) enabled operate like conventional instruments by
responding to a sequence of commands sent by the controller. You can send individual commands to
the TSP-enabled instrument the same way you would using any other instrument.
Unlike conventional instruments, TSP-enabled instruments can execute automated test sequences
independently, without a controller. You can load a series of TSP commands into the instrument and
store these commands as a script that can be run later by sending a single command message to the
instrument.
You do not have to choose between using “conventional” control or “script” control. You can combine
these forms of instrument control in the way that works best for your test application.
Controlling the instrument by sending individual command messages
The simplest method of controlling an instrument through the communication interface is to send it a
message that contains remote commands. You can use a test program that resides on a computer
(the controller) to sequence the actions of the instrument.
TSP commands can be function-based or attribute-based. Function-based commands are commands
that control actions or activities. Attribute-based commands define characteristics of an instrument
feature or operation.
Functions
Function-based commands control actions or activities. For example, waiting for all overlapped
commands to complete is a function. A function-based command is not always directly related to
instrument operation. For example, the
eventlog.clear()
function clears the event log.
Each function consists of a function name followed by a set of parentheses ( ). Only include
information in the parentheses if the function takes a parameter. If the function takes one or more
parameters, they are placed between the parentheses and separated by commas.
Example 1
beeper.beep(0.5, 2400)
delay(0.250)
beeper.beep(0.5, 2400)
Emit a double-beep at 2400 Hz. The sequence is
0.5 s on, 0.25 s off, 0.5 s on.
Section 5
Introduction to TSP operation
Summary of Contents for 2657A
Page 3: ......