TSP-Net
The TSP-Net
®
library allows the 2600B to control LAN-enabled devices directly through its LAN port.
This enables the 2600B to communicate directly with a device that is not TSP
®
enabled without the
use of a controlling computer.
TSP-Net capabilities
The TSP-Net library permits the 2600B to control a remote instrument through the LAN port for both
Test Script Processor (TSP
®
) and non-TSP instruments. Using TSP-Net library methods, you can
transfer string data to and from a remote instrument, transfer and format data into Lua variables, and
clear input buffers. The TSP-Net library is only accessible using commands from a remote command
interface.
You can use TSP-Net commands to communicate with any ethernet-enabled instrument. However,
specific TSP-Net commands exist for TSP-enabled instruments to allow for support of features unique
to the TSP scripting engine. These features include script downloads, reading buffer access, wait
completion, and handling of TSP scripting engine prompts.
Using TSP-Net commands with TSP-enabled instruments, a 2600B can download a script to another
TSP-enabled instrument and have both instruments run scripts independently. The 2600B can read
the data from the remote instrument and either manipulate the data or send the data to a different
remote instrument on the LAN. You can simultaneously connect to a maximum of 32 devices using
standard TCP/IP networking techniques through the LAN port of the 2600B.
Using TSP-Net with any ethernet-enabled instrument
Refer to TSP command reference (on page 9-1) for details about the commands presented in
this section.
The 2600B LAN port is auto-sensing (Auto-MDIX), so you can use either a LAN crossover cable or a
LAN straight-through cable to connect directly from the 2600B to an ethernet device or to a hub.
To set up communication to a remote ethernet-enabled instrument that is TSP
®
enabled:
1. Send the following command to configure TSP-Net to send an abort command when a
connection to a TSP instrument is established:
tspnet.tsp.abortonconnect = 1
If the scripts are allowed to run, the connection is made, but the remote instrument may be busy.
To Next Page
Loading...
Need help?
General
