Tektronix TPS2000, TDS2MM, TDS2MEM, TDS2CMA, TDS2CM User Manual

...

Programmer Manual

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.

www.tektronix.com

Copyright © Tektronix. All rights reserved. Licensed software products are owned by Tektronix or its subsidiaries or suppliers, and are protected by national copyright laws and international treaty provisions.

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:

H In North America, call 1-800-833-9200. H Worldwide, visit www.tektronix.com to find contacts in your area.

Preface vii............................................

Related Documents vii..................................

Conventions xi........................................

Getting Started

Getting Started 1--1.....................................

Syntax and Commands

Command Syntax 2--1...................................

Command and Query Structure 2--2.........................

Command Entry 2--6.....................................

Constructed Mnemonics 2--9..............................

Argument Types 2--11.....................................

Command Groups 2--15..................................

Acquisition Commands 2--15...............................

Calibration and Diagnostic Commands 2--16...................

Cursor Commands 2--17...................................

Display Commands 2--18..................................

File System Commands (TDS2MEM Module, TDS1000B,

TDS2000B, and TPS2000 Only) 2--19....................

Hard Copy Commands 2--20...............................

Horizontal Commands 2--21................................

Math Commands 2--22....................................

Measurement Commands 2--23.............................

Miscellaneous Commands 2--25.............................

PictBridge Commands (TDS1000B and TDS2000B Only) 2--27...

Power and Battery-Related Commands (TPS2000 Only) 2--28.....

Power Measurement (TPS2000 with TPS2PWR1 Power

Analysis Application Key Installed Only) 2--28.............

RS-232 Commands 2--32..................................

Save and Recall Commands 2--32...........................

Status and Error Commands 2--33...........................

Trigger Commands 2--34..................................

Vertical Commands 2--36..................................

Waveform Commands 2--37................................

Waveform Data Formats 2--40..............................

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Table of Contents

Waveform Data Record 2--42...............................

Waveform Data Locations and Memory Allocation 2--42.........

Waveform Preamble 2--43.................................

Scaling Waveform Data 2--43...............................

Transferring Waveform Data 2--43...........................

Command Descriptions 2--45..............................

Status and Events

Status and Events 3--1...................................

Registers 3--1...........................................

Status Registers 3--1..................................

Enable Registers 3--4..................................

The Enable Registers and the *PSC Command 3--6.........

Queues 3--6............................................

The Output Queue 3--6................................

The Event Queue 3--7.................................

Event Handling Sequence 3--8.............................

Synchronization Methods 3--10.............................

Using the *WAI Command 3--11.........................

Using the BUSY Query 3--13............................

Using the *OPC Set Command 3--14......................

Using the *OPC? Query 3--16............................

Messages 3--17..........................................

Programming Examples

Programming Examples 4--1.............................

Appendices

Appendix A: ASCII Code Chart A--1.......................

Appendix B: Factory Setup B--1...........................

TDS1000B and TDS2000B Series Oscilloscopes B--1...........

TPS2000 Series Oscilloscopes B--3.........................

TDS1000 and TDS2000 Series Oscilloscopes B--5.............

TDS210 and TDS220 Oscilloscopes B--6.....................

TDS224 Oscilloscopes B--8................................

Glossary and Index

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

List of Figures

Figure 2--1: Command message elements 2--4...............

Figure 2--2: Block Argument example 2--14..................

Figure 3--1: The Standard Event Status Register (SESR) 3--2..

Figure 3--2: The Status Byte Register (SBR) 3--3.............

Figure 3--3: The Device Event Status Enable Register

(DESER) 3--5.......................................

Figure 3--4: The Event Status Enable Register (ESER) 3--5....

Figure 3--5: The Service Request Enable Register (SRER) 3--5.

Figure 3--6: Status and event handling process 3--9...........

Figure 3--7: Command processing without using

synchronization 3--11..................................

Figure 3--8: Processing sequence with synchronization 3--11....

Table of Contents

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

iii

Table of Contents

List of Tables

Table 1--1: Communications ports and functions 1--1........

Table 1--2: Oscilloscope, extension module, and

adapter compatibility 1--2............................

Table 2--1: Oscilloscope communication protocol 2--1........

Table 2--2: BNF notation 2--2............................

Table 2--3: Command message elements 2--3................

Table 2--4: Comparison of Header Off and Header

On responses 2--5....................................

Table 2--5: Types of numeric arguments 2--11................

Table 2--6: Oscilloscope handling of incorrect

numeric arguments 2--12..............................

Table 2--7: Parts of a block argument 2--13..................

Table 2--8: Acquisition commands 2--15.....................

Table 2--9: Calibration and Diagnostic commands 2--16.......

Table 2--10: Cursor commands 2--17.......................

Table 2--11: Display commands 2--18.......................

Table 2--12: File System commands 2--19...................

Table 2--13: Hard Copy commands 2--20....................

Table 2--14: Horizontal commands 2--21....................

Table 2--15: Math commands 2--22.........................

Table 2--16: Measurement commands 2--24..................

Table 2--17: Miscellaneous commands 2--25.................

Table 2--18: PictBridge commands (TDS1000B

and TDS2000B only) 2--27.............................

Table 2--19: Power and Battery-Related commands

(TPS2000 only) 2--28.................................

Table 2--20: Power Measurement commands

(TPS2000 with TPS2PWR1 only) 2--29..................

Table 2--21: RS-232 commands 2--32.......................

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Table of Contents

Table 2--22: Save and Recall commands 2--33................

Table 2--23: Status and Error commands 2--33...............

Table 2--24: Trigger commands 2--35.......................

Table 2--25: Vertical commands 2--36.......................

Table 2--26: Waveform commands 2--38....................

Table 2--27: Binary data ranges 2--41.......................

Table 2--28: V ertical position ranges using a 1X probe 2--68....

Table 2--29: DATa and WFMPre parameter settings 2--88.....

Table 2--30: Commands that generate an Operation

Complete message 2--170...............................

Table 2--31: Additional WFMPre commands 2--259............

Table 3--1: SESR bit functions 3--2........................

Table 3--2: SBR bit functions 3--4.........................

Table 3--3: No event messages 3--17........................

Table 3--4: Command error messages – CME bit 5 3--18.......

Table 3--5: Execution error messages – EXE bit 4 3--18........

Table 3--6: Device error messages – DDE bit 3 3--22..........

Table 3--7: System event messages 3--22.....................

Table 3--8: Execution warning messages – EXE Bit 4 3--23.....

Table 3--9: Internal warning messages 3--24.................

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Table of Contents

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Preface

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.

Conventions

Refer to the Command Syntax section of the Syntax and Commands chapter (page 2--1) for information about command conventions.

This manual uses the following convention:

Preface

H References to the TDS2CMA Communications Extension

Module include the TDS2CM and TDS2CMAX modules.

H Command descriptions list specific oscilloscopes series (and

module) when commands are valid for only those products

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Preface

xii

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Getting Started

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

Series Port location Port function

you connect the oscilloscope USB

TDS200 TDS2CM, TDS2CMA, or TDS2CMAX

Communications, TDS2MM Math

TDS1000/ TDS2000*

TDS1000B/ TDS2000B{

TPS2000 Back of oscilloscope RS-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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

TDS2CMA or TDS2CMAX

TDS2MEM Storage Memory and Communications

Back of oscilloscope USB Device

RS-232, Centronics, GPIB

RS-232, Centronics, CompactFlash

GPIB with a TEK-USB-488 adapter

1- 1

Getting Started

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

TDS200 Yes Yes No No

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

Yes No Yes* No

No No No Yes

No No No No

TDS2MM TDS2MEM

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.

1- 2

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Syntax and Commands

Command Syntax

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 Command Descriptions section.

Table 2- 1:

Model or option GPIB RS-232 USB

TDS2CM, TDS2CMA, TDS2CMAX Yes Yes No

TDS2MM Yes Yes No

TDS2MEM No Yes No

TDS1000 or TDS2000 Yes*

TDS1000B or TDS2000B

TPS2000 No Yes No

{ 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.

No Yes

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

2- 1

Command Syntax

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

Symbol Meaning

::= 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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Table 2--3 lists and describes the five element types.

Table 2- 3: Command message elements

Symbol Meaning

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

<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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

2- 3

Command Syntax

Figure 2--1 shows the five command message elements.

Header

SAVe:WAVEform CH1,REFA

Mnemonics Arguments

Comma

Space

Figure 2- 1: Command message elements

Commands

Commands cause the oscilloscope to perform a specific function or change one of its settings. Commands have the structure:

[:]<Header>[<Space><Argument>[<Comma><Argument>]...]

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:

2- 4

[:]<Header>?

[:]<Header>?[<Space><Argument>[<Comma><Argument>]...]

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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Command Syntax

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

Query Header Off response Header 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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

2- 5

Command Syntax

Command Entry

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

command:

TRIGger:MODe NORMal;:ACQuire:NUMAVg 16

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

Command Syntax

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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

2- 7

Command Syntax

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.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

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

Symbol Meaning

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.

Symbol Meaning

REF<x> 2-channel models: A reference waveform specifier;

<x> is A or B. 4-channel models: A reference waveform specifier;

<x>isA,B,C,orD.

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

2- 9

Command Syntax

Waveform Mnemonics

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.

Symbol Meaning

Cursor Position Mnemonic

When the oscilloscope displays cursors, commands may specify which cursor of the pair to use.

Symbol Meaning

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.

Symbol Meaning

MEAS<x> A measurement specifier; <x> is 1--4 (TDS200)

or 1--5 (TDS1000, TDS2000, TDS1000B, TDS2000B, and TPS2000).

TDS200, TDS1000/2000, TDS1000B/2000B, TPS2000 Programmer

+ 316 hidden pages