User manual

Series 3700 System Switch/Multimeter Reference Manual Section 13: Instrument Control Library (ICL)
3700S-901-01 Rev. C / July 2008 13-5
TSP-LinkTM nodes
Each instrument or enclosure attached to the TSP-Link bus must be uniquely
identified. This identification is called a TSP-Link node number, and the
enclosures are called nodes. Each node must be assigned a unique node
number.
In relation to Test Script Processor (TSP
TM
), nodes look like tables. There is one
global table named node that contains all the actual nodes that are themselves
tables. An individual node is accessed as node[N] where N is the node number
assigned to the node. Each node has certain attributes that can be accessed as
elements of its associated table. These are listed as follows:
id: The node number assigned to the node.
model: The product model number string of the node.
revision: The product revision string of the node.
serialno: The product serial number string of the node.
There is also an entry for each logical instrument on the node (see Logical
instruments (on page 13-5)).
It is not necessary to know the node number of the node running a script. The
variable localnode is an alias for the node entry the script is running on. For
example, if a script is running on Node 5, the global variable localnode will be
an alias for node[5].
Logical instruments
You would normally refer to all instrumentation within one enclosure or node as
a single instrument. In the context of TSP
TM
and instrument control libraries, it is
useful to think of individual DMMs as instruments. To avoid confusion, DMMs
and other subdivisions of the instrumentation within an enclosure will be referred
to as "logical instruments."
Each logical instrument is given a unique identifier in a system. These identifiers
are used as part of all ICL function calls that control a given logical instrument. A
Series 3700 has the following logical instruments per enclosure:
beeper
display
format
slot
tsplink
bit
dmm
gpib
status
channel
eventlog
lan
timer
digio
errorqueue
scan
trigger