TDS200, TDS1000/TDS2000,
TDS1000B/TDS2000B, and
TPS2000 Series Digital Oscilloscopes
071-1075-04
This document supports:
S TPS2000 Series instruments, any version.
S TDS1000B and TDS2000B Series instruments,
any version.
S TDS2CM or TDS2CMA, any version, when
used in TDS1000 or TDS2000 Series instruments,
any version.
S TDS2MEM any version, when used in most
TDS1000 or TDS2000 Series instruments (except
TDS1001 and TDS2004 models), any version.
S TDS2CM, TDS2CMA, or TDS2MM any
version, when used in a TDS224 instrument, any
version.
S TDS2CM or TDS2CMA version CMV:v1.04
and above, or TDS2MM any version, when used
in TDS210 and TDS220 instruments with
FV:v1.09 and above.
Tektronix products are covered by U.S. and foreign patents, issued and
pending. Information in this publication supercedes that in all previously
published material. Specifications and price change privileges reserved.
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
OpenChoice® is a registered trademark of Tektronix Inc.
Tektronix is an authorized licensee of the CompactFlash® trademark.
PictBridge is a trademark of the Standard of Camera & Imaging Products
Association CIPA DC-001-2003 Digital Photo Solutions for Imaging Devices.
Contacting Tektronix
Tektronix, Inc.
14200 SW Karl Braun Drive
P.O. Box 500
Beaverton, OR 97077
USA
For product information, sales, service, and technical support:
HIn North America, call 1-800-833-9200.
HWorldwide, visit www.tektronix.com to find contacts in your area.
This programmer manual provides information on how to remotely
operate your TDS200, TDS1000/TDS2000, TDS1000B/TDS2000B,
or TPS2000 series oscilloscope. You can use communication ports
and protocols, such as for the RS-232, the General Purpose Interface
Bus (GPIB), or Universal Serial Bus (USB) standards, to remotely
control and operate your oscilloscope.
Related Documents
Each series of oscilloscopes has a different set of documentation.
TPS2000 Series Manuals
For general operation, refer to the TPS2000 Series Digital Storage
Oscilloscope User Manual, a standard accessory.
For information on the TPS2PWR1 Power Analysis Application,
refer to the TPS2PWR1 Power Analysis Application User Manual,an
optional accessory available in eleven languages.
LanguageTDS2PWR1 user manual part number
English071-1452-XX
French071-1453-XX
Italian071-1454-XX
German071-1455-XX
Spanish071-1456-XX
Japanese071-1457-XX
Portuguese071-1458-XX
Simplified Chinese071-1459-XX
Traditional Chinese 071-1460-XX
Korean071-1461-XX
Russian071-1462-XX
viii
TDS1000B and TDS2000B Series Manuals
For general operation, refer to the TDS1000B and TDS2000B Series
Digital Storage Oscilloscope User Manual, a standard accessory.
For general operation, and information on the TDS2CMA Communications module, refer to the TDS1000 and TDS2000 Serie s DigitalStorage Oscilloscope User Manual, a standard accessory.
LanguageTDS1000/TDS2000 user manual part number
English071-1064-XX
French071-1065-XX
Italian071-1066-XX
German071-1067-XX
Spanish071-1068-XX
Japanese071-1069-XX
Portuguese071-1070-XX
Simplified Chinese071-1071-XX
Traditional Chinese 071-1072-XX
Korean071-1073-XX
Russian071-1074-XX
For information on the TDS2MEM Storage Memory and Communications module, refer to the TDS2MEM Storage Memory andCommunications Module User Manual (071--1262--XX), an optional
accessory that includes all eleven langua ges.
For general operation, refer to the TDS200 Series Digital Real-Time
Oscilloscope User Manual, a standard accessory.
LanguageTDS200 series user manual part number
English071-0398-XX
French071-0400-XX
Italian071-0401-XX
German071-0402-XX
Spanish071-0399-XX
Japanese071-0405-XX
Portuguese071-0403-XX
Simplified Chinese071-0406-XX
Traditional Chinese 071-0407-XX
Korean071-0408-XX
Russian071-0404-XX
For information on the TDS2CMA Communications module, or
TDS2MM Math Measurements module, refer to the TDS200 SeriesExtension Modules Instructions Manual (071-0409-XX), a standard
accessory for extension modules in English only.
This manual contains information on how to remotely control and
operate your oscilloscope through communications protocol and
commands.
NOTE. For TDS1000B and TDS2000B series, you need to install the
PC Communications software from the CD that came with the
oscilloscope on a PC before
Device port to the PC. Refer to the TDS1000B and TDS2000B user
manual for installation information.
For all products, you need to connect an appropriate cable between
the communications port on your oscilloscope and your PC.
The next table describes where the communications port is located
on an extension module or oscilloscope, and the function of the port.
Table 1- 1: Communications ports and functions
SeriesPort locationPort function
you connect the oscilloscope USB
TDS200TDS2CM, TDS2CMA, or TDS2CMAX
Communications, TDS2MM Math
TDS1000/
TDS2000*
TDS1000B/
TDS2000B{
TPS2000Back of oscilloscopeRS-232, Centronics
*TDS1001 and TDS2004 are not compatible with the TDS2MEM module.
{Install the PC Communications software from the CD that came wi th the
oscilloscope first; refer to your TDS1000B and TDS2000B user manual for
information on installing the software. After the software is installed, then
connect the oscilloscope to a PC.
Refer to your oscilloscope user manual (Tektronix part numbers
listed on page v) for information on how to install, test, and
configure your oscilloscope and module.
NOTE. The firmware for the TDS1000B, TDS2000B, and TPS2000
series oscilloscopes includes communications, math, and storage
memory functions.
Table 1- 2:
Oscilloscope, extension module, and adapter compatibility
TDS2CM,TDS2CMA
Series
TDS200YesYesNoNo
TDS1000 or
TDS2000
TDS1000B or
TDS2000B
TPS2000{
*
TDS1001 and TDS2004 models are not compatible with the TDS2MEM module.
{RS-232 included in the oscilloscope firmware.
or TDS2CMAX
YesNoYes*No
NoNoNoYes
NoNoNoNo
TDS2MMTDS2MEM
TEK-USB-488
NOTE. If you use GPIB with the TDS1000B or TDS2000B series, you
can set a unique GPIB address for the oscilloscope through the
UTILITY " Options " GPIB Setup option.
You can control the oscilloscope through the GPIB, RS-232, or USB
interface using a large group of commands and queries.
This section describes the syntax these commands and queries use
and the conventions the oscilloscope uses to process them. The
commands and queries themselves are listed in the CommandDescriptions section.
Table 2- 1:
Model or optionGPIBRS-232USB
TDS2CM, TDS2CMA, TDS2CMAX YesYesNo
TDS2MMYesYesNo
TDS2MEMNoYesNo
TDS1000 or TDS2000Yes*
TDS1000B or TDS2000B
TPS2000NoYesNo
*
{Function available with a TDS2MEM module.
}Function available with a TEK-USB-488 adapter.
You transmit commands to the oscilloscope using the enhanced
American Standard Code for Information Interchange (ASCII)
character encoding. Appendix A contains a chart of the ASCII
character set.
Oscilloscope communication protocol
Yes*{
Yes}
Function available with a TDS2CM, TDS2CMA, or TDS2CMAX
module.
The Backus Naur Form (BNF) notation is used in this manual to
describe commands and queries. Table 2--2 lists the BNF notation.
Table 2- 2: BNF notation
SymbolMeaning
<>
::=Is defined as
|Exclusive OR
Defined element
{}
[]
...Previous element(s) may be
()
Group; one element is required
Optional; can be omitted
repeated
Comment
Command and Query Structure
Commands consist of set commands and query commands (usually
simply called commands and queries). Commands change oscilloscope settings or perform a specific action. Queries cause the
oscilloscope to return data and information a bout its status.
Most commands have both a set form and a query form. The query
form of the command is the same as the set form except that it ends
with a question mark. For example, the set command ACQuire:MODe
has a query form ACQuire:MODe?. Not all commands have both a set
and a query form; some commands are set only and some are query
only.
A few commands do both a set and query action. For example, the
*CAL? command runs a self-calibration program on the oscilloscope,
then returns the result of the calibration.
2- 2
A command message is a command or query name, followed by any
information the oscilloscope needs to execute the command or query.
Command messages consist of five different element types.
Table 2--3 lists and describes the five element types.
Table 2- 3: Command message elements
SymbolMeaning
<Header>
The basic command name. If the header ends with
a question mark, the command is a query. The
header may begin with a colon (:) character; if the
command is concatenated with other commands the
beginning colon is required. The beginning colon
can never be used with command headers
beginning with a star (*).
Command Syntax
<Mnemonic>
<Argument>
<Comma>
<Space>
A header subfunction. Some command headers
have only one mnemonic. If a command header has
multiple mnemonics, they are always separated
from each other by a colon (:) character.
A quantity, quality, restriction, or limit associated with
the header. Not all commands have an argument,
while other commands have multiple arguments.
Arguments are separated from the header by a
<Space>. Arguments are separated from each
other by a <Comma>.
A single comma between arguments of multiple-argument commands. It may optionally have white
space characters before and after the comma.
A white space character between command header
and argument. It may optionally consist of multiple
white space characters.
A command header is made up of one or more mnemonics arranged
in a hierarchical or tree structure. The first mnemonic is the base or
root of the tree and each subsequent mnemonic is a level or branch
off of the previous one. Commands at a higher level in the tree may
affect those at a lower level. The leading colon (:) always returns
you to the base of the command tree.
Queries
Queries cause the oscilloscope to return information about its status
or settings. Queries have the structure:
You can specify a query command at any level within the command
tree unless otherwise noted. These branch queries return information
about all the mnemonics below the specified branch or level.
For example, MEASUrement:MEAS<x>:UNIts? returns the measurement units, while MEASUrement:MEAS<x>:TYPe? returns the
measurement type selected for the measurement, and MEASUre-ment:MEAS<x>? returns all the measurement parameters for the
specified measurement.
Headers in Query Responses
You can control whether the oscilloscope returns headers as part of
the query response. Use the HEADer command to control this feature.
If header is on, the oscilloscope returns command headers as part of
the query and formats the query response as a valid set com mand.
When header is off, the oscilloscope sends back only the values in
the response. This format can make it easier to parse and extra ct the
information from the response.
Table 2--4 shows the difference in responses.
Table 2- 4: Comparison of Header Off and Header On responses
QueryHeader Off responseHeader On response
ACQuire:NUMAVg?64:ACQUIRE:NUMAVG 64
CHx1:COUPling?DC:CH1:COUPLING DC
Clearing the Output Queue
To clear the output queue and reset the oscilloscope to accept a new
command or query, send a Device Clear (DCL) from a GPIB host.
From an RS-232 host, send a break signal. The RS-232 interface
responds by returning the ASCII string “DCL.”
From a USB host, send an INITIATE_CLEAR followed by a
CHECK_CLEAR_STATUS. The USB interface responds to
CHECK_CLEAR_STATUS with STATUS_SUCCESS when it is
finished clearing the output queue.
Follow these general rules when entering commands:
H Enter commands in upper or lower case.
H You can precede any command with white space characters.
White space characters include any combination of the ASCII
control characters 00 through 09 and 0B through 20 hexadecimal
(0 through 9 and 11 through 32 decimal).
H The oscilloscope ignores commands that consists of just a
combination of white space characters and line feeds.
Abbreviating Commands
You can abbreviate many oscilloscope commands. These abbreviations are shown in capital letters in the command listing in the
Command Groups sectiononpage2--15andCommand Descriptions
section on page 2-- 45. For example, the command ACQuire:NUMAvg
can be entered simply as ACQ:NUMA or acq:numa.
If you use the HEADer command to have command headers included
as part of query responses, you can also control whether the returne d
headers are abbreviated or are full-length using the VERBose
command.
2- 6
Concatenating Commands
You can concatenate any combination of set commands and queries
using a semicolon (;). The oscilloscope executes concatenated
commands in the order received. When concatenating commands
and queries you must follow these rules:
H Completely different headers must be separated by both a
semicolon and by the beginning colon on all commands but the
first. For example, the commands TRIGger:MODe NORMal and
ACQuire:NUMAVg 16 can be concatenated into a single
H If concatenated commands have headers that differ by only the
last mnemonic, you can abbreviate the second command and
eliminate the beginning colon. For example, the commands
ACQuire:MODe AVErage and ACQuire:NUMAVg 16 could be
concatenated into a single command:
ACQuire:MODe AVErage; NUMAVg 16
The longer version works equally well:
ACQuire:MODe AVErage;:ACQuire:NUMAVg 16
H Never precede a star (*) command with a colon or semicolon:
ACQuire:MODe AVErage;*TRG
The oscilloscope processes commands that follow the star
command as if the star command was not there, so:
ACQuire:MODe AVErage;*TRG;NUMAVg 16
sets the acquisition mode to average and sets acquisition
averaging to 16. The *TRG command is ignored.
H When you concatenate queries, the responses to all queries are
combined into a single response message. For example, if
channel 1 coupling is set to DC and the bandwidth is set to
20 MHz, the concatenated query:
CH1:COUPling?;BANdwidth?
returns :CH1:COUPLING DC;:CH1:BANDWIDTH ON if header is on,
or DC;ON if header is off.
H You can concatenate set commands and queries in the same
message. For example:
ACQuire:MODe AVErage;NUMAVg?;STATE?
is a valid message that sets the acquisition mode to average,
queries the number of acquisitions for averaging, and then
queries the acquisition state. The oscilloscope executes
concatenated commands and queries in the order it receives
them.
H Any query that returns arbitrary data, such as ID?, must be the
last query when part of a concatenated command. If the que ry i s
not last, the oscilloscope generates event message 440.
Here are some INVALID concatenation examples:
H CH1:COUPling DC;ACQuire:NUMAVg 16
(missing colon before ACQuire)
H CH1:COUPling DC;:BANDwidth ON
(invalid colon before BANDwidth)
H CH1:COUPling DC;:*TRG
(invalid colon before a star (*) command)
H HORizontal:MAIn:POSition 0;MAIn:SCAle 1E–13
(levels of mnemonics are different—either remove the second
occurrence of MAIn:, or put :HORizontal: in front of
MAIN:SCAle)
Message Terminators
This manual uses the term <EOM> (End of message) to represent a
message terminator.
2- 8
GPIB End of Message (EOM) Terminators. GPIB EOM terminators can
be the END message (EOI asserted concurrently with the last data
byte), the ASCII code for line feed (LF) sent as the last data byte, or
both. The oscilloscope always terminates messages with LF and EOI.
White space is allowed before the terminator; for example, CR LF is
acceptable.
USB End of Message (EOM) Terminators. The EOM bit must be set in
the USB header of the last transfer of a command message. See the
USB Test and Measurement Class Specification (USBTMC) section
3.2.1 for details. The oscilloscope terminates messages by setting
the EOM bit in the USB header of the last transfer of a message to
the host (USBTMC Specification section 3.3.1), and by terminating
messages with a LF. White space is allowed before the terminator;
for example, CR LF is acceptable.
RS-232 End of Message Terminators. RS-232 EOM terminators can be a
CR (carriage return), LF (line feed), CRLF (carriage return followed
by a line feed), or LFCR (line feed followed by a carriage return).
When receiving, the oscilloscope accepts all four combinations as
valid input message terminators regardless of the currently selected
terminator. When a combination of multiple characters is selected
(CRLF or LFCR), the oscilloscope interprets the first character as the
terminator and the second character as a null command.
Constructed Mnemonics
Some header mnemonics specify one of a range of mnemonics. For
example, a channel mnemonic could be CH2. You can use these
mnemonics in the command just as you do any other mnemonic. For
example, there is a CH1:VOLts command and there is also a
CH2:VOLts command. In the command descriptions, this list of
choices is abbreviated CH<x>.
Channel Mnemonics
Commands specify the channel to use as a mnemonic in the header.
Command Syntax
SymbolMeaning
CH<x>2-channel models: A channel specifier; <x> is 1 or 2.
4-channel models: A channel specifier; <x> is 1, 2,
3, or 4.
Reference Waveform Mnemonics
Commands can specify the reference waveform to use as a
mnemonic in the header.
SymbolMeaning
REF<x>2-channel models: A reference waveform specifier;
<x> is A or B.
4-channel models: A reference waveform specifier;
In some commands you can specify a waveform without regard to its
type: channel waveform, math waveform, or reference waveform.
The “y” is the same as “x” in Reference Waveform Mnemonics.
SymbolMeaning
<wfm>Can be CH<x>, MATH, or REF<y>
Cursor Position Mnemonic
When the oscilloscope displays cursors, commands may specify
which cursor of the pair to use.
SymbolMeaning
POSITION<x>
A cursor selector; <x> is 1 or 2.
2- 10
Measurement Specifier Mnemonics
Commands can specify which measurement to set or query as a
mnemonic in the header. The oscilloscope can display up to four
(TDS200) or five (TDS1000, TDS2000, TDS1000B, TDS2000B, and
TPS2000) automated measurements.
SymbolMeaning
MEAS<x>A measurement specifier; <x> is 1--4 (TDS200)
or 1--5 (TDS1000, TDS2000, TDS1000B,
TDS2000B, and TPS2000).
A command argument can be in one of several forms. The individual
descriptions of each command tell which argument types to use with
that command.
Numeric Arguments
Many oscilloscope commands require numeric arguments. Table 2 --5
lists the three types of numeric argument.
Table 2- 5: Types of numeric arguments
SymbolMeaning
<NR1>Signed integer value
<NR2>Floating point value without an exponent
<NR3>Floating point value with an exponent
The syntax shown is the data format that the oscilloscope returns in
response to a query. This format is also the preferre d format when
sending a command to the oscilloscope.
Command Syntax
When you enter an incorrect numeric argument, the oscilloscope
automatically forces the numeric argument to a correct value.
Table 2-- 6 lists how the oscilloscope handles incorrect numeric
arguments.
Table 2- 6: Oscilloscope handling of incorrect numeric arguments
Argument valueOscilloscope response
Numeric argument is
less than lowest correct
value for that command
Sets the specified command to the lowest correct
value and executes the command
Numeric argument is
greater than the highest
correct value for that
command
Numeric value is between two correct values
Sets the specified command to the highest correct
value and executes the command
Rounds the entered value to the nearest correct
value and executes the command
Quoted String Arguments
Some commands accept or return data in the form of a quoted string,
which is simply a group of ASCII characters enclosed by single
quotes (’) or double quotes (”). For example:
”this is a quoted string”
SymbolMeaning
<QString>Quoted string of ASCII text
Follow these rules when you use quoted strings:
1. A quoted string can include any character defined in the 7-bit
ASCII character set. Refer to Appe ndix A.
2. Use the same type of quote character to open and close the string:
2- 12
”this is a valid string”
3. You can mix quotation marks within a string as long as you
<NZDig> specifies the number of <Dig> elements that follow. Taken
together, the <Dig> elements form a decimal integer that specifies
how many <DChar> elements follow.
#0 means that the <Block> is an indefinite length block. The
<terminator> ends the block. You should not use indefinite length
blocks with RS-232, because there is no way to include a <termina-tor> character as a <DChar> character.
Thefirstoccurrenceofa<terminator> character signals the end of
the block and any subsequent <DChar> characters will be interpreted
as a syntax error. With the GPIB, the EOI line signals the last byte.
With the USB, the EOM bit signals the last byte.
This section lists the commands organized by functional group. The
Command Descriptions section, starting on page 2--45, lists all
commands alphabetically.
The oscilloscope GPIB, USB, and RS-232 interfaces conform to
Tektronix standard codes and formats except where noted. The GPIB
interface also conforms to IEEE Std 488.2–1987 except where noted.
The USB interface also conforms to USB Test and Measurement
Class, Subclass USB488 Specification, except where noted.
Acquisition Commands
Acquisition commands affect the acquisition of waveforms. These
commands control mode, averaging, and single-waveform
acquisition. Table 2--8 lists and describes Acquisition commands.
Table 2- 8: Acquisition commands
HeaderDescription
ACQuire?Return acquisition parameters
ACQuire:MODeSet or query the acquisition mode
ACQuire:NUMACq?Return the # of acquisitions obtained
ACQuire:NUMAVgSet or query the number of acquisitions
for average
ACQuire:STATEStart or stop the acquisition system
ACQuire:STOPAfterSet or query the acquisition control
Calibration and Diagnostic commands let you initiate the oscilloscope self-calibration routines and examine the results of diagnostic
tests. Table 2--9 lists and describes Calibration and Diagnostic
commands.
Table 2- 9: Calibration and Diagnostic commands
HeaderDescription
*CAL?Perform an internal self-calibration and
return result status
CALibrate:ABOrtStop an in-progress factory calibration
CALibrate:CONTINUEPerform the next step in the factory
calibration sequence
CALibrate:FACtoryInitialize the factory calibration sequence
CALibrate:INTERNALPerform an internal self-calibration
CALibrate:STATUS?Return PASS or FAIL status of the last
self- or factory-calibration operation
2- 16
DIAg:RESUlt:FLAG?Return diagnostic tests status
DIAg:RESUlt:LOG?Return diagnostic test sequence results
CURSor:VBArs:UNItsSet or query the vertical cursors to time
or frequency
CURSor:VBArs:VDELTa?
(TDS1000B, TDS2000B, and
TPS2000 only)
Display Commands
Display commands let you change the graticule style, displayed
contrast, and alter other display attributes. Table 2--11 lists and
describes Display commands.
Table 2- 11: Display commands
HeaderDescription
DISplay?Return display settings
DISplay:BRIGHTness
(TPS2000 only)
DISplay:CONTRastSet or query the LCD display contrast
DISplay:FORMatSet or query the YT or XY display
DISplay:INVert
(not available on the TDS200,
accepted as a legal command on
theTDS2000B and TPS2000 but
has no effect on these models)
DISplay:PERSistenceSet or query the accumulate time
Return the vertical distance between
cursors
Set or query the LCD display brightness
Set or query the normal or inverted
monochrome display
2- 18
DISplay:STYleSet or query the waveform display style
(TDS2MEM Module, TDS1000B, TDS2000B, and TPS2000 Only)
File system commands perform file management tasks on the
CompactFlash (CF) card of TPS2000 oscilloscopes, and TDS models
with a TDS2MEM module; and on USB flash drives of TDS1000B
and TDS2000B oscilloscopes. Table 2--12 lists these commands.
Table 2- 12: File System commands
HeaderDescription
FILESystem?Return the current working directory (CWD) and
CF card or USB flash drive free space values
FILESystem:CWDSet or query the current CF card or USB flash
drive directory
FILESystem:DELEteDelete specified file on the CF card or USB flash
drive
FILESystem:DIR?Return a list of files in current CF card or USB
flash drive directory
FILESystem:FORMatFormat the CF card or USB flash drive
FILESystem:FREESpace?Return free space on the CF card or USB flash
drive
FILESystem:MKDirCreate a new directory on the CF card or USB
flash drive
FILESystem:RENameAssign new name to specified file on the CF
Use the following conventions when specifying file paths and file
names::
H The default folder (directory) is A:\.
H File and folder names have a maximum of 11 characters; eight
characters,followedbyaperiod,followedbyuptothree
characters. This format is referred to as 8.3 naming.
H Wild card characters (*, %, ?) are not valid characters in file or
path names.
H Lists the Windows-generated short file and folder names for long
file or folder names created on PC Windows operating systems.
Hard Copy Commands
The hard copy commands let you control the format of hard copy
output, and the starting and stopping of hard copies. Table 2--13 lists
and describes Hard Copy commands. :
2- 20
NOTE. TDS1000B and TDS2000B oscilloscopes include PictBridge
commands to provide additional control of the hard copy format.
Refer to page 2--27 for information on the PictBridge commands.
Table 2- 13: Hard Copy commands
HeaderDescription
HARDCopyStart or terminate hard copy
HARDCopy:BUTTON
(TDS2MEM, TDS1000B,
TDS2000B, and TPS2000 only)
HARDCopy:FORMatSet or query the hard copy output format
Set or query the hard copy button
function
For TDS1000B, TDS2000B, and
TPS2000, set or query the PRINT button
HARDCopy:INKSaver
(TDS1000, TDS2000, TDS2000B,
and TPS2000 only)
HARDCopy:LAYoutSet or query the hard copy orientation
HARDCopy:PORTSet or query the hard copy port for
Horizontal Commands
Horizontal commands control the time bases of the oscilloscope. You
can set the position and time per division of both the main and
window time bases. You can substitute SECdiv for SCAle in all
appropriate horizontal commands. This provides program compatibility with previous Tektronix digitizing oscilloscopes. Table 2-- 14
lists and describes Horizontal commands.
Command Groups
Set or query the hard copy ink saver
option
output: RS232, GPIB, Centronics, or
USB
Table 2- 14: Horizontal commands
HeaderDescription
HORizontal?Return horizontal settings
HORizontal:DELay?Return all settings for the window time
base
HORizontal:DELay:POSitionPosition window
HORizontal:DELay:SCAleSet or query the window time base
time/division
HORizontal:DELay:SECdivSame as HORizontal:DELay:SCAle
HORizontal:MAIn?Return the main time base time/division
HORizontal:MAIn:POSitionSet or query the main time base trigger
MATH:FFT:HORizontal:SCAle
(TDS200 with a TDS2MM module, TDS1000,
TDS2000, TDS1000B, TDS2000B, and
TPS2000 only)
Set or query the FFT horizontal zoom factor
Command Groups
MATH:FFT:VERtical:POSition
(TDS200 with a TDS2MM module, TDS1000,
TDS2000, TDS1000B, TDS2000B, and
TPS2000 only)
MATH:FFT:VERtical:SCAle
(TDS200 with a TDS2MM module, TDS1000,
TDS2000, TDS1000B, TDS2000B, and
TPS2000 only)
MATH:VERtical?Return all math vertical
MATH:VERtical:POSition
(TDS1000B, TDS2000B, and TPS2000 only)
MATH:VERtical:SCAle
(TDS1000B, TDS2000B, and TPS2000 only)
Measurement Commands
Measurement commands control the automated measurement
system. The oscilloscope can display up to four (TDS200) or five
(TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000)
automated measurements. In the commands, these measurement
readouts are named MEAS<x>, where <x> can be 1, 2, 3, or 4 (or 5
for TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000).
Set or query the FFT vertical
display position
Set or query the FFT vertical
zoom factor
waveform parameters
Set or query the math waveform display position
Set or query the math waveform display scale
The best method for taking measurements over the computer
interface is to use the MEASUREMENT:IMMED commands and
queries. The immediate measurement has no front-panel equivalent,
and the oscilloscope never displays immediate measurements.
Because they are computed only when they are requested, immediate
measurements slow the waveform update rate less than displayed
measurements.
Use the VALue? query to obtain measurement results of either
displayed or immediate measurements.
Several measurement commands set and query measurement
parameters. You can assign some parameters, such as waveform
sources, differently for each measurement readout.
Table 2--16 lists and describes Measurement commands.
Miscellaneous commands are a group of commands that do not fit
into any other category.
Several commands and queries are common to all 488.2–1987
devices on the GPIB or USB bus, and the device on the RS-232
interface. These commands and queries are defined by IEEE Std.
488.2–1987 and Tektronix Standard Codes and Formats 1989 and
begin with an asterisk (*) character. Table 2 --17 lists and describes
Miscellaneous commands.
Command Groups
ment
Table 2- 17: Miscellaneous commands
HeaderDescription
AUTORange?
(TDS1000B, TDS2000B, and
TPS2000 only)
AUTORange:SETTings
(TDS1000B, TDS2000B, and
TPS2000 only)
AUTORange:STATE
(TDS1000B, TDS2000B, and
TPS2000 only)
AUTOSetAutomatic oscilloscope setup
AUTOSet: ENABLE
(TDS1000B and TDS2000B only)
Return all autorange parameters
Set or query the which parameters
autorange can adjust
Set or query the autorange to on or off
Allows educators to disable or enable the
Autorange and Autoset functions.*
AUTOSet: ENABLE can be manually set from the Service Diag
menu. To access the service diagnostics menu, refer to the
TDS1000B and TDS2000B series service manual.
PictBridge Commands (TDS1000B and TDS2000B Only)
The PictBridge commands let you control the format of the hard
copy on the PictBridge compatible printer. Table 2 --13 lists and
describes PictBridge commands. :
NOTE. The HARDCopy:BUTTON, HARDCopy:INKSaver, and
HARDCopy:LAYOUT commands apply to the TDS1000B and
TDS2000B oscilloscopes. Refer to page 2--20 for more information.
Table 2- 18: PictBridge commands
HeaderDescription
PICTBridge:DEFSet the next six options to default
PICTBridge:PAPERSIZESet or query the paper size
PICTBridge:IMAGESIZESet or query the image size
PICTBridge:PAPERTYPESet or query the paper type
PICTBridge:PRINTQUALSet or query the print quality
RS-232 commands allow you to set or query the parameters that
control the RS-232 port. Table 2--21 lists and describes RS-232
commands.
Table 2- 21: RS-232 commands
HeaderDescription
RS232?Query RS232 parameters
RS232:BAUdSet or query the baud rate
RS232:HARDFlaggingSet or query the hard flagging
RS232:PARitySet or query the parity type
RS232:SOFTFlaggingSet or query the soft flagging
RS232:TRANsmit:TERMinatorSet or query the end-of-line terminator
Refer to Table 2--1 on page 2--1 for a list of products that are
compatible with RS-232.
Save and Recall Commands
Save and Recall commands allow you to store and retrieve internal
waveforms and settings. When you “save a setting,” you save most
of the settings of the oscilloscope. When you then “recall a setting,”
the oscilloscope restores itself to the state it was in when you saved
that setting.
To display a saved waveform, use the SELect:<wfm> command
described on page 2--197. Table 2--22 lists and describes Save and
Recall commands.
SAVe:IMAge
(TDS2MEM, TDS1000B,
TDS2000B, and TPS2000 only)
SAVe:IMAge:FILEFormat
(TDS2MEM, TDS1000B,
TDS2000B, and TPS2000 only)
SAVe:SETUpSave oscilloscope setting
SAVe:WAVEformSave waveform
Status and Error Commands
Status and error commands let you determine the status of the
oscilloscope and control events.
Several commands and queries are common to all devices on the
GPIB or USB bus. These commands and queries are defined by
IEEE Std. 488.2–1987 and Tek Standard Codes and Formats 1989,
and begin with an asterisk (*) character. Table 2 --23 lists and
describes Status and Error commands.
*ESR?Return standard event status register; this is the usual
EVENT?Return event code
EVMsg?Return event message
EVQty?Return number of events in queue
*OPCSet or query the operation complete
*PSCSet or query the power-on status clear
*SRESet or query the service request enable
*STB?Read status byte
*WAIWait to continue
way to determine whether a set command executed
without error
T rigger Commands
Trigger commands control all aspects of oscilloscope triggering.
The three types of triggers are edge, pulse width, and video. Edge
triggering is the default type. Edge triggering lets you acquire a
waveform when the signal passes through a voltage level of your
choosing. Pulse width triggering lets you trigger on normal or
aberrant pulses. Video triggering adds the capability of triggering on
video fields and lines. Table 2--24 lists and describes Trigger
commands.
TRIGger:MAIn:TYPeSet or query the main trigger type
TRIGger:MAIn:VIDeo?Query video trigger parameters
TRIGger:MAIn:VIDeo:LINE
(TDS1000, TDS2000, TDS1000B,
TDS2000B, and TPS2000 only)
TRIGger:MAIn:VIDeo:POLaritySet or query the video trigger polarity
TRIGger:MAIn:VIDeo:SOUrceSet or query the video trigger source
TRIGger:MAIn:VIDeo:STANdard
(TDS1000, TDS2000, TDS1000B,
TDS2000B, and TPS2000 only)
TRIGger:MAIn:VIDeo:SYNCSet or query the video trigger sync
TRIGger:STATE?Return trigger system status
Vertical Commands
Vertical commands control the attributes of the channels. The
SELect:<wfm> command also displays a specified waveform or
removes it from the display. Table 2--25 lists and describes Vertical
commands.
Table 2- 25: Vertical commands
HeaderDescription
CH<x>?Return vertical parameters
Set or query the video trigger line
Set or query the video trigger
standard
2- 36
CH<x>:BANdwidthSet or query the channel bandwidth
CH<x>:COUPlingSet or query the channel coupling
CH<x>:CURRENTPRObe
(TDS1000B, TDS2000B, and
TPS2000 only)
Set or query the scale settings for current
probes
All oscilloscope, firmware version,
and module combinations except
TDS210 and TDS220 with firmware
below V 2.00 and a TDS2CMA
communications module.
CH<x>:POSitionSet or query the channel position
CH<x>:PRObeSet or query the channel probe parame-
CH<x>:SCAleSet or query the channel volts/div
CH<x>:VOLtsSame as CH<x>:SCAle
)
Set or query the channel invert
ters
CH<x>:YUNit
(TDS1000B, TDS2000B, and
TPS2000 only)
SELect?Controls the display of waveforms
SELect:<wfm>Set or query the waveform display state
Waveform Commands
Waveform commands let you transfer waveform data points to and
from the oscilloscope. Waveform data points are a collection of
values that define a waveform. One data value usually re presents one
data point in the waveform record. When working with peak-detect
waveforms, each data value is either the min or max of a min/max
pair. Before you can transfer waveform data, you must specify t he
data format and waveform locations.
Table 2-- 26 lists and describes Waveform commands. Refer to the
text following this table for more information about waveform
commands.
WFMPre:<wfm>:YMUltSet or query the vertical scale factor
WFMPre:<wfm>:YOFfSet or query the vertical position
WFMPre:<wfm>:YUNitSet or query the vertical units
WFMPre:<wfm>:YZEro?
(TDS200 with TDS2MM module,
TDS1000, TDS2000, TDS1000B,
TDS2000B, and TPS2000 only)
Set or query the waveform conversion
factor
Waveform Data Formats
Internally, the oscilloscope uses one 8-bit data byte to represent each
waveform data point, regardless of the acquisition mode.
The DATa:WIDth command lets you specify the number of bytes per
data point when transferring data to and from an oscilloscope. This
provides compatibility with other digitizing oscilloscopes.
When DATa:WIDth is set to two:
H If sending data, the oscilloscope multiplies each point by 256; the
most significant byte then has meaningful data and the least
significant byte is 0
H If receiving data, the oscilloscope truncates the data (divides by
256) and saves the most significant byte
NOTE. The oscilloscopes uses these methods to handle waveforms
transmitted in ASCII or binary format.
The oscilloscope can transfer waveform data in either ASCII or
binary format. Use the DATa:ENCdg command to specify one of the
following formats:
H ASCII data is represented by signed integer values. The range of
values depends on the byte width specified. One-byte-wide data
ranges from –128 to 127. Two-byte-wide data ranges from
–32768 to 32767.
Each data value requires two to seven characters. This includes
one character for the minus sign if the value is negative, one to
five ASCII characters for the waveform value, and a comma to
separate data points.
An example of an ASCII waveform data string follows:
H Binary data can be represented by signed integer or positive
integer values. The range of the values depends on the byte width
specified.
Table 2--27 lists the ranges for one- and two-byte-wide data.
Table 2- 27: Binary data ranges
Byte widthSigned integer rangePositive integer range
1–128 to 1270to255
2–32,768 to 32,7670 to 65,535
The defined binary formats also specify the order in which the bytes
are transferred giving a total of four binary formats: RIBinary,
RPBinary, SRIbinary, and SRPbinary.
RIBinary is signed integer where the most significant byte is
transferred first, and RPBinary is positive integer where the most
significant byte is transferred first. SRIbinary and SRPbinary
correspond to RIBinary and RPBinary respectively but use a
swapped byte order where the least significant byte is transferred
first. The byte order is ignored when DATa:WIDth is set to 1.
Waveform Data Record
You can transfer multiple points for each waveform record. You can
transfer a portion of the waveform or you can transfer the en tire
record. The DATa:STARt and DATa:STOP commands let you
specify the first and last data points of the waveform record.
When transferring data into the oscilloscope you must specify the
location of the first data point within the waveform record. For
example, when DATa:STARt is set to 1, data points will be stored
starting with the first point in the record, and when DATa:STARt is
set to 500, data will be stored starting at the 500
The oscilloscope ignores DATa:STOP when reading in data as the
oscilloscope will stop reading data when there is no more data to
read or when it has reached 2500 data points.
th
point in the record.
2- 42
You must specify the first and last data points in the waveform
record when transferring data from the oscilloscope to an external
device. Setting DATa:STARt to 1 and DATa:STOP to 2500 always
sends the entire waveform, regardless of the acquisition mode.
Waveform Data Locations and Memory Allocation
The DATa:SOUrce command specifies the location of the data when
transferring waveforms from the oscilloscope. You can transfer one
waveform at a time.
You can transfer only one waveform into the oscilloscope at a time.
Each waveform is stored in one of two stored waveform locat ions for
2-channel models or one of four stored waveform locations for
4-channel models. You specify the stored waveform location with
the DATa:DESTination command.
NOTE. The oscilloscope stores waveforms that are ≤2500 data points
long. The oscilloscope truncates waveforms longer than 2500 data
points.
Waveform Preamble
Each waveform that is transferred has an associated waveform
preamble that contains information such as the horizontal scale,
vertical scale, and other settings in place when the waveform was
created. Refer to the WFMPre commands on page 2--244 for more
information about the waveform preamble.
Scaling Waveform Data
Once you transfer the waveform data to the controller, you can
convert the data points into voltage values for analysis using
information from the waveform preamble.
Transferring Waveform Data
Data transfer times depend on data format, data width, and the speed
of the controller. Refer to Programming Examples on page 4--1.
From the Oscilloscope. To transfer waveforms from the oscilloscope to
an external controller, follow these steps:
1. Use the DATa:SOUrce command to select the waveform source.
2. Use the DATa:ENCdg command to specify the waveform data
format.
3. Use the DATa:WIDth command to specify the number of bytes
per data point.
4. Use the DATa:STARt and DATa:STOP commands to specify the
portion of the waveform that you want to transfer.
5. Use the WFMPRe? command to transfer waveform preamble
information.
6. Use the CURVe? command to transfer waveform data.
Commands either set or query oscilloscope values. Some commands
both set and query, some only set, and some only query.
Manual Conventions
This manual uses the following conventions:
H No query form exists for commands identified as “Set Only”
H A question mark (?) appended to the command and “Query
Only” indicates query-only commands
H Fully spells out headers, mnemonics, and arguments with the
minimal spelling shown in upper case; for example, to use the
abbreviated form of the ACQuire:MODe command, just type
ACQ:MOD
H Syntax of some commands varies, depending on the model of
oscilloscope and extension module you use; differences are noted
H Command descriptions list specific oscilloscopes series (and
module) when commands are valid for only those products
NOTE. While Trigger View is active (when you push the TRIG VIEW
button on the front panel), the oscilloscope ignores the set form of
most commands. If you send a command at this time, the oscilloscope
generates execution error 221 (Settings conflict).
Sets or queries the oscilloscope acquisition mode. This affects all
live waveforms and is equivalent to setting the Mode option in the
Acquire menu.
Waveforms are the displayed data point values taken from
acquisition intervals. Each acquisition interval represents a time
duration that is determined by the horizontal scale (time per
division).
2- 46
The oscilloscope sampling system can operate at a rate greater than
that indicated by the horizontal scale. Therefore, an acquisition
interval can include more than one sample.
The acquisition mode, which you set using this ACQuire:MODe
command, determines how the final value of the acquisition interval
is generated from the many data samples.
SAMple specifies that the displayed data point value is the first
sampled value that was taken during the acquisition interval. The
waveform data has 8 bits of precision in all acquisition modes. You
can request 16 bit data with a CURVe? query, but the lower-order
8 bits of data will be zero. SAMple is the default mode.
PEAKdetect specifies the display of the high-low range of the
samples taken from a single waveform acquisition. The oscilloscope
displays the high-low range as a vertical range that extends from the
highest to the lowest value sampled during the acquisition interval.
PEAKdetect mode can reveal the presence of aliasing.
AVErage specifies averaging mode, where the resulting waveform
shows an average of SAMple data points from several separate
waveform acquisitions. The number of waveform acquisitions that
go into making up the average waveform is set or queried using the
ACQuire:NUMAVg command.
Examples
ACQuire:MODe PEAKdetect
Displays a vertical area representing the range of the highest to
lowest value of the acquired signal.
ACQuire:MODe?
Might return SAMPLE.
Related Commands
WFMPre:PT_Fmt
ACQuire:NUMACq? (Query Only)
Indicates the number of acquisitions that have taken place since
starting oscilloscope acquisition. The maximum number of
acquisitions that can be counted is 2
when you change most Acquisition, Horizontal, Vertical, or Trigger
arguments that affect the waveform except for the following:
H Changing the trigger level or trigger holdoff when in Sample or
NOTE. Any change made when in Average mode aborts the
acquisition and resets ACQuire:NUMACq to zero.
H TDS200: changing the vertical position does not reset the value
H TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000
series: if the Trigger mode is set to Auto, and the Horizontal
Scale is 10 ms/div or slower, changing the vertical position does
not reset the value
NOTE. In Scan mode, ACQuire:NUMACq? always returns zero.
Group
Acquisition
Syntax
ACQuire:NUMACq?
Returns
<NR1>
Examples
ACQuire:NUMACq?
Might return 350, indicating that 350 acquisitions took place since
an ACQuire:STATE RUN command was executed.
ACQuire:NUMAVg
Sets the number of oscilloscope waveform acquisitions that make up
an averaged waveform. This command is equivalent to setting the
Averages option in the Acquire menu.
<NR1> is the number of waveform acquisitions. Correct values are 4,
16, 64,and128.
Examples
ACQuire:NUMAVg 16
This specifies that an averaged waveform will show the result of
combining 16 separately acquired waveforms.
ACQuire:NUMAVg?
Might return 64, indicating that there are 64 acquisitions specified
for averaging.
ACQuire:STATE
Command Descriptions
Starts or stops oscilloscope acquisitions. This command is the
equivalent of pressing the front-panel RUN/STOP button. If
ACQuire:STOPAfter is set to SEQuence, other signal events may
also stop acquisition.
NOTE. The best way to determine when a single sequence acquisition
is complete is to use *OPC? rather than ACQuire:STATE?. For more
information on the *OPC? command, refer to page 2--169.
ON | RUN | <NR1> ≠ 0 starts acquisition and display of waveforms. If
the command was issued in the middle of an acquisition sequence
(for instance averaging), RUN restarts the sequence, discarding any
data accumulated before the STOP. It also resets the number of
acquisitions.
Examples
ACQuire:STATE RUN
Starts acquisition of waveform data and resets the number of
acquisitions count (NUMACq) to zero.
ACQuire:STATE?
Returns 0 or 1, depending on whether or not the acquisition system is
running.
Related Commands
*OPC?
ACQuire:STOPAfter
Tells the oscilloscope when to stop taking acquisitions.
Group
Acquisition
Syntax
ACQuire:STOPAfter { RUNSTop | SEQuence}
ACQuire:STOPAfter?
Arguments
RUNSTop specifies that the run and stop states should be determined
by pressing the front-panel RUN/STOP button or issuing the
ACQuire:STATE command.
SEQuence specifies “single sequence” operation, where the
oscilloscope stops after it has acquired enough waveforms to satisfy
the conditions of the acquisition mode. For example, if the
acquisition mode is set to sample, the oscilloscope stops after
digitizing a waveform from a single trigger event. However, if the
acquisition mode is set to average 64 waveforms, then the oscilloscope stops only after acquiring all 64 waveforms.
The ACQuire:STATE command and the front-panel RUN/STOP
button also stop acquisitions when the oscilloscope is in single
sequence mode.
Examples
ACQuire:STOPAfter RUNSTop
Sets the oscilloscope to stop the acquisition when you press the
front-panel RUN/STOP button.
ACQuire:STOPAfter?
Might return SEQUENCE.
ALLEv? (Query Only)
Causes the oscilloscope to return all events and their messages, and
removes the returned events from the Event Queue. The me ssages
are separated by commas. Use the *ESR? query to enable the events
to be returned. For a complete discussion of how to use these
registers, refer to page 3--1. This command is similar to repeatedly
sending *EVMsg? queries to the oscilloscope.
<Command> is the command that caused the error and may be
returned when a command error is detected by the oscilloscope. As
much of the command is returned as possible without exceeding the
60 character limit of the <Message> and <Command> strings
combined. The command string is right-justified.
Examples
ALLEv?
Might return the following string:
:ALLEV 2225,“Measurement error, No waveform to measure;
”,420,“Query UNTERMINATED; ”
Causes the oscilloscope to adjust its vertical, horizontal, and trigger
controls to display a stable waveform. This command is equivalent
to pushing the front-panel AUTOSET button.
For a detailed description of the Autoset function, refer to the user
manual for your oscilloscope.
Group
Miscellaneous
Syntax
AUTOSet EXECute
Arguments
EXECute invokes Autoset.
AUTOSet:ENABLE
(TDS1000B and TDS2000B Series Only)
Command Descriptions
Allows educators to disable or enable the Autorange and Autoset
functions. The function can be manually set from the Service Diag
menu. To access the menu, refer to the TDS1000B and TDS2000B
series service manual.
Group
Miscellaneous
AUTOSet:SIGNAL? (Query Only)
(TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000 Series
Only)
Returns the type of signal discovered by the most recent execution of
Autoset.
Might return { LEVEL | SINE | SQUARE | VIDPAL | VIDNTSC |
OTHER | NONe }
LEVEL if the oscilloscope discovered a DC level.
SINE if the oscilloscope discovered a sine-like waveform.
SQUARE if the oscilloscope discovered a square-like waveform.
VIDPAL if the oscilloscope discovered a PAL or SECAM standard
video signal.
VIDNTSC if the oscilloscope discovered an NTSC standard video
signal.
OTHER if the oscilloscope was unable to classify the signal.
NONE if the AUTOSET menu is not displayed.
AUTOSet:VIEW
(TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000 Series
Only)
If the current menu is not the Autoset menu, or if the view is not
valid for the detected waveform, the set command causes the
oscilloscope to generate error 221 (Settings conflict).
Group
Miscellaneous
Syntax
AUTOSet:VIEW { MULTICYcle | SINGLECYcle | FFT |
RISINGedge | FALLINGedge | FIELD | ODD | EVEN | LINE |
LINENum | DCLIne | DEFault | NONE }
MULTICYcle displays a sine or square wave of several cycles. Default
for sine-like and square-like signals.
SINGLECYcle displays a sine or square wave of approximately one
cycle.
FFT displays the FFT of a sine wave.
RISING displays the rising edge of a square wave.
FALLING displays the falling edge of a square wave.
FIELD displays a video signal synchronized on all fields. This is the
default for video signals.
ODD displays a video signal synchronized on odd fields.
EVEN displays a video signal synchronized on even fields.
LINE displays a video signal synchronized on all lines.
LINENum displays a video signal synchronized on the specified line
number.
DCLIne returns a query response when the oscilloscope finds a DC
level.
DEFault returns a query response when the oscilloscope cannot
determine the signal type.
NONE returns a query response when the AUTOSET menu is not
displayed. Set is ignored.
Examples
AUTOSet:VIEW EVEN
The oscilloscope will display video signals synchronized on even
fields when operated in autoset mode.
BUSY? (Query Only)
Returns the status of the oscilloscope. This command allows you to
synchronize the operation of the oscilloscope with your application
program. Refer to Synchronization Methods on page 3--10 for more
information.
0 when the oscilloscope is not busy processing any of the commands
listed in Table 2--30 (*OPC) on page 2--170.
1 when the oscilloscope is busy processing one of the commands
listed in Table 2--30 (*OPC) on page 2--170.
Examples
BUSY?
Might return 1, indicating that the oscilloscope is busy.
Related Commands
*OPC, *WAI
*CAL? (Query Only)
Performs an internal self-calibration and returns its status. This is
equivalent to selecting the Do Self Cal option in the Utility menu.
Although *CAL? is a query command, it does perform an action.
NOTE. The self-calibration can take several minutes to complete.
During this time, the oscilloscope does not execute any commands.
Disconnect all signals from the oscilloscope before performing an
internal self-calibration.
0 indicates that the self-calibration completed without any errors
detected.
Any value other than zero indicates that the self-calibration did not
complete successfully or completed with errors.
Examples
*CAL?
Performs a self-calibration and might return 0 to indicate that it
completed successfully.
Related Commands
CALibrate:INTERNAL
CALibrate:ABOrt (Set Only)
Command Descriptions
NOTE. You should only use this command in a qualified service
environment. For more information about the factory calibration
sequence, refer to the service manual for your oscilloscope.
Aborts the factory calibration process. When you abort the factory
calibration, the oscilloscope restores the calibration settings to the
previous factory calibration constants stored in non-volatile memory.
Stops the in-process factory calibration procedure.
CALibrate:CONTINUE (Set Only)
NOTE. You should only use this command in a qualified service
environment. For more information about the factory calibration
sequence, refer to the service manual for your oscilloscope.
Performs the next step in the factory calibration operation.
Group
Calibration and Diagnostic
Syntax
CALibrate:CONTINUE
Examples
CALibrate:CONTINUE
Performs the next step in the factory calibration operation.
CALibrate:FACtory (Set Only)
NOTE. You should only use this command in a qualified service
environment. For more information about the factory calibration
sequence, refer to the service manual for your oscilloscope.
Starts the oscilloscope’s internal factory calibration operation. The
calibration operation consists of a sequence of steps. You send the
CALibrate:CONTINUE command to advance to the next calibration
step. The calibration program automatically sets up the oscilloscope
for each calibration step. Use the CALibrate:ABOrt command to
abort the factory calibration.
Returns the status of the last calibration operation performed (either
self- or factory-calibration) since power up.
Group
Calibration and Diagnostic
Syntax
CALibrate:STATUS?
Returns
PASS indicates that the oscilloscope completed the last calibration
operation without detecting any errors.
FAIL indicates that the oscilloscope detected errors during the last
calibration operation, or that no calibration operations have been
performed since power up.
Examples
CALibrate:STATUS?
Might return CALIBRATE:STATUS FAIL, if the oscilloscope failed the
last calibration operation.
CH<x>? (Query Only)
Returns the current oscilloscope vertical settings. The value of <x>
can vary from 1 through 4 for 4-channel instruments or 1 through 2
for 2-channel instruments.
Because CH<x>:SCAle and CH<x>:VOLts are identical, only
CH<x>:SCAle is returned.
Sets or queries the bandwidth setting of the specified oscilloscope
channel. The value of <x> can vary from 1 through 4 for 4-channel
instruments or 1 through 2 for 2-channel instruments.
This command is equivalent to setting the BW Limit option in the
Vertical menu.
Command Descriptions
Group
Vertical
Syntax
CH<x>:BANdwidth { ON | OFF }
CH<x>:BANdwidth?
Arguments
ON sets the channel bandwidth to 20 MHz.
OFF sets the channel bandwidth to the full bandwidth of the
oscilloscope.
In most acquisition modes, full bandwidth is 60 MHz, 100 MHz, or
200 MHz (depending on the oscilloscope model). There are
exceptions.
TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000 Series
At vertical scales from 2.00 to 4.99 mV/div (sensitivity at the BNC;
that is, after the probe factor is removed), the full bandwidth is
20 MHz.
TDS200 Series
At vertical scales of 5 mV/div or less (sensitivity at the BNC; that is,
after the probe factor is removed), the full bandwidth is 20 MHz.
When the acquisition mode is Peak Detect, and the vertical scale at
the BNC is 10 mV/div or less, the full bandwidth is also 20 MHz.
Examples
CH2:BANDWIDth ON
Sets the bandwidth of channel 2 to 20 MHz.
CH1:BANDWIDth?
Might return OFF. This indicates there is no bandwidth limiting on
channel 1.
CH<x>:COUPling
Sets or queries the input attenuator coupling setting of the specified
oscilloscope channel. The value of <x> can vary from 1 through 4
for 4-channel instruments or 1 through 2 for 2-channel instruments.
This command is equivalent to setting the Coupling option in the
Vertical menu.
Group
Vertical
Syntax
CH<x>:COUPling { AC | DC | GND }
CH<x>:COUPling?
Arguments
AC sets the specified oscilloscope channel to AC coupling.
DC sets the specified oscilloscope channel to DC coupling.
GND sets the specified oscilloscope channel to ground. Only a flat
ground-level waveform is displayed.
Examples
CH1:COUPlING AC
This establishes AC coupling on channel 1.
CH2:COUPlING?
Might return DC. Indicating that channel 2 is set to DC coupling.
CH<x>:CURRENTPRObe
(TDS1000B, TDS2000B, and TPS2000 Series Only)
Sets or queries the scale factor of the specified channel for current
probes. The value of <x> can vary from 1 through 4 for 4-channel
instruments or 1 through 2 for 2-channel instruments.
You can issue this command when CH<x>:YUNit <QString> is set
to V. However, this command only affects the readouts when
CH<x>:YUNit <QString> is set to A.
Command Descriptions
Group
Vertical
Syntax
CH<x>:CURRENTPRObe { 0.2|1|2|5|10|50|100|
1000 }
CH<x>:CURRENTPRObe?
Arguments
0.2 sets the specified oscilloscope channel to 0.2X attenuation.
1 sets the specified oscilloscope channel to 1X attenuation.
2 sets the specified oscilloscope channel to 2X attenuation.
5 sets the specified oscilloscope channel to 5X attenuation.
10 sets the specified oscilloscope channel to 10X attenuation.
50 sets the specified oscilloscope channel to 50X attenuation.
100 sets the specified oscilloscope channel to 100X attenuation.
1000 sets the specified oscilloscope channel to 1000X attenuation.
Returns
<NR1>
Examples
CH2:CURRENTPRObe 1000
This sets channel 2 to 1000X attenuation.
CH1:CURRENTPRObe?
Might return 10.
CH<x>:INVert
2- 66
NOTE. You can NOT use this command with a TDS210 or TDS220
oscilloscope with firmware below V 2.00 and a TDS2CMA
(or TDS2CM) communications module.
Sets or queries the inversion state of the specified oscilloscope
channel. The value of <x> can vary from 1 through 4 for 4-channel
instruments or 1 through 2 for 2-channel instruments.
This command is equivalent to setting the Invert option in the
Vertical channel menus.
OFF sets the specified oscilloscope channel to non-inverted.
Examples
CH1:INVert ON
Inverts the signal on channel 1.
CH2:INVert?
Might return OFF, indicating that channel 2 is not inverted.
CH<x>:POSition
Sets or queries the vertical position of the specified oscilloscope
channel. The value of <x> can vary from 1 through 4 for 4-channel
instruments or 1 through 2 for 2-channel instruments.
The position voltage value is applied to the signal before digitization. This command is equivalent to adjusting the front-panel
VERTICAL POSITION knob.
Command Descriptions
Group
Vertical
Syntax
CH<x>:POSition <NR3>
CH<x>:POSition?
Arguments
<NR3> is the position in divisions from the center graticule.
Table 2-- 28 lists the vertical position ranges using a 1X probe.
Table 2- 28: Vertical position ranges using a 1X probe
CH<x>:SCAlePosition range
2mV/div±1000 divs
5mV/div±400 divs
10 mV/div±200 divs
20 mV/div±100 divs
50 mV/div±40 divs
100 mV/div±20 divs
200 mV/div±10 divs
500 mV/div±100 divs
1V/div±50 divs
2V/div±25 divs
5V/div±10 divs
Examples
CH2:POSition 1.32E0
Positions the channel 2 input signal 1.32 divisions above the center
of the display.
CH1:POSition?
Might return –1.32E0, indicating that the current position of channel
1 is at –1.32 divisions.
CH<x>:PRObe
Sets or queries the attenuation factor of the specified channel or
voltage probes. The value of <x> can vary from 1 through 4 for
4-channel instruments or 1 through 2 for 2-channel instruments.
1 sets the specified oscilloscope channel to 1X attenuation.
10 sets the specified oscilloscope channel to 10X attenuation.
20 sets the specified oscilloscope channel to 20X attenuation.
(TDS1000B, TDS2000B, and TPS2000 series only)
50 sets the specified oscilloscope channel to 50X attenuation.
(TDS1000B, TDS2000B, and TPS2000 series only)
100 sets the specified oscilloscope channel to 100X attenuation.
500 sets the specified oscilloscope channel to 500X attenuation.
(TDS1000B, TDS2000B, and TPS2000 series only)
1000 sets the specified oscilloscope channel to 1000X attenuation.
Returns
<NR1>
Examples
CH2:PRObe 1000
Sets channel 2 to 1000X attenuation.
CH1:PRObe?
Might return CH1:PROBE 10
CH<x>:SCAle
Sets or queries the vertical gain of the specified oscilloscope
channel. The value of <x> can vary from 1 through 4 for 4-channel
instruments or 1 through 2 for 2-channel instruments.
This command is equivalent to adjusting the front-panel VOLTS/
DIV knob.
<NR3> is the gain, in volts or amps per division. For example, the
voltage range is 5 V/div to 2 mV/div when using a 1X voltage probe.
Examples
CH1:SCAle 100E–3
Sets the channel 1 gain to 100 mV/div.
CH2:SCAle?
Might return 1.0E0, indicating that the current V/div setting of
channel 2 is 1 V/div.
Related Commands
CH1:VOLts
CH<x>:VOLts
Sets or queries the vertical gain of the specified channel. The value
of <x> can vary from 1 through 4 for 4-channel instruments or 1
through 2 for 2-channel instruments.
This command is identical to the CH<x>:SCAle command and is
included for compatibility purposes. Only CH<x>:SCAle is returned
in response to a CH<x>? query.
Sets or queries the units of the specified channel. The value of <x>
can vary from 1 through 4 for 4-channel instruments or 1 through 2
for 2-channel instruments.
Group
Vertical
Syntax
CH<x>:YUNit <QString>
CH<x>:YUNit?
Arguments
<QString> is either “V” for volts or “A” for amps. This is equivalent
to setting the probe to Voltage or Current in the probe front-panel
menu. This command is case insensitive.
Examples
CH2:YUNIT?
Command Descriptions
Might return CH2:YUNIT “V”, indicating that the channel 2 units are
volts.
*CLS (Set Only)
The *CLS command clears the following oscilloscope status data
structures:
H The Event Queue
H The Standard Event Status Register (SESR)
H The Status Byte Register (except the MAV bit described on
If the *CLS command immediately follows an <EOI>, the Output
Queue and MAV bit (Status Byte Register bit 4) are also cleared.
MAV indicates information is in the output queue. The device clear
(DCL) GPIB control message and the USBTMC INITIATE_CLEAR
control message will clear the output queue and also MAV.
*CLS does not clear the output queue or MAV. *CLS can suppress a
service request that is to be generated by an *OPC command. This
will happen if a hard copy output or single sequence acquisition
operation is still being processed when the *CLS command is
executed.
Refer to Registers on page 3--1 for more information.
Selects and displays the oscilloscope cursor type. Cursors are
attached to the waveform selected by CURSor:SELect:SOUrce. This
command is equivalent to setting the Type option in the Cursor
menu. Setting the function to anything other than OFF causes the
Cursor menu to be displayed.
NOTE. Setting the display format to XY removes the cursors. Sending
the CURSor:FUNCtion command when the display format is XY
causes the oscilloscope to generate event 221 (Settings conflict) and
leaves the display in XY format.
Command Descriptions
Group
Cursor
Syntax
CURSor:FUNCtion { HBArs | OFF | VBArs }
CURSor:FUNCtion?
Arguments
HBArs specifies horizontal bar cursors that measure the vertical units
in volts, amps, divisions, or decibels.
OFF removes cursors from the display.
VBArs specifies vertical bar cursors that measure time or frequency.
Might return 5.08E0 for the difference between the two cursors.
CURSor:HBArs:POSITION<x>
Positions a horizontal bar cursor. The value of <x> can vary from 1
through 2.
NOTE. If Trigger View is active, the query form returns 9.9E37 and
generates event 221 (Settings conflict).
Command Descriptions
Group
Cursor
Syntax
CURSor:HBArs:POSITION<x> <NR3>
CURSor:HBArs:POSITION<x>?
Arguments
<NR3> specifies the horizontal bar cursor position, relative to ground
(in volts when the units are volts and amps when the units are amps),
relative to the center of the screen (in divs when units are divisions),
or relative to 1 V RMS (in decibels when the source is an FFT math
waveform), for the waveform specified by the CURSor:SELect:SOUrce command.
The cursor position is limited to the graticule whenever an attempt is
made to move it outside the graticule.
VOLTSSQUARED indicates volts squared (V*V) as the unit of measure.
(TDS1000B, TDS2000B, and TPS2000 series only)
AMPSSQUARED indicates amps squared (A*A) as the unit of measure.
(TDS1000B, TDS2000B, and TPS2000 series only)
VOLTSAMPS indicates voltage times current (V*A) as the unit of
measure. (TDS1000B, TDS2000B, and TPS2000 series only)
NOTE. Unknown units are represented by ”?” in the oscilloscope
readouts.
Examples
CURSor:HBArs:UNIts?
Might return CURSOR:HBARS:UNITS VOLTS.
CURSor:SELect:SOUrce
Command Descriptions
Sets or queries the waveform that is the source of the vertical and
horizontal scale factors used in determining cursor values. This
command is equivalent to setting the Source option in the Cursor
menu.
Group
Cursor
Syntax
CURSor:SELect:SOUrce <wfm>
CURSor:SELect:SOUrce?
Arguments
<wfm> specifies the waveform data source on which cursor
measurements will be taken.
Returns the time or frequency difference between the two vertical
bar cursors. The units (seconds or Hertz) are specified by the
CURSor:VBArs:UNIts command. If the cursor source is an FFT
math waveform, CURSor:VBArs:DELTa is always in Hertz,
regardless of the value set by CURSor:VBArs:UNIts.
NOTE. If Trigger View is active, this query returns 9.9E37 and
generates event 221 (Settings conflict).
Might return 8.92E–1, indicating that the time difference between
the vertical bar cursors is 0.892 seconds.
CURSor:VBArs:HDEL Ta? (Query Only)
(TDS1000B, TDS2000B, and TPS2000 Series Only)
Returns the time or frequency difference between the two vertical
bar cursors. The units (seconds or Hertz) are specified by the
CURSor:VBArs:UNIts command. If the cursor source is an FFT
math waveform, CURSor:VBArs:DELTa is always in Hertz,
regardless of the value set by CURSor:VBArs:UNIts.
Command Descriptions
The command is identical to the CURSor:VBArs:DELTa? query. It is
included for compatibility with the TDS3000 series.
NOTE. If Trigger View is active, this query returns 9.9E37 and
generates event 221 (Settings conflict).