In this section:
Introduction to TSP operation ................................................. 13-1
Fundamentals of scripting for TSP ......................................... 13-4
Fundamentals of programming for TSP ............................... 13-12
Test Script Builder (TSB) ..................................................... 13-31
Suggestions for increasing the available memory ................ 13-41
About TSP Commands ........................................................ 13-41
Introduction to TSP operation
Instruments that are enabled for Test Script Processor (TSP
®
) 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 when using any other instrument.
Unlike conventional instruments, TSP-enabled instruments can execute automated test sequences
independently, without an external controller. You can load a series of TSP commands into the
instrument using a remote computer or the front-panel port with a USB flash drive. You can 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.
Constants and enumerated types are commands that represent fixed values.
Section 13
Introduction to TSP commands