Tektronix TDS7000 Series Programmer's Manual

TDS7000 Series GPIB Programmer Online Guide

Printable version 1.0

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

Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (c)(1) and (2) of the Commercial Computer Software – Restricted Rights clause at FAR

52.227-19, as applicable. Tektronix products are covered by U.S. and foreign patents, issued and pending. Information in this

documentation supercedes that in all previously published material. Specifications and price change privileges reserved.

Tektronix, Inc. P.O. Box 500, Beaverton, OR 97077 TEKTRONIX, TEK, and TEKPROBE are registered trademarks of Tektronix, Inc.

FrameScan is a trademark of Tektronix, Inc.

TDS7000 Series Programmer Online Guide

OLH0140, Version 01.00

Getting Started

Introduction

This programmer online guide provides you with the information you need to use GPIB commands for remotely controlling your instrument. With this information, you can write computer programs that will perform functions such as setting the front-panel controls, taking measurements, performing statistical calculations, and exporting data for use in other programs, such as spreadsheets.

The programmer guide is divided into the following major topics (books):

• Getting Started. This topic introduces you to the online help and provides basic information about setting up your instrument for remote control.

• Command Syntax. This topic provides an overview of the command syntax that you will use to communicate with the instrument and other general information about commands, such as how commands and queries are constructed, how to enter commands, constructed mnemonics, and argument types.

• Command Groups. This topic contains all the commands listed in functional groups. Each group consists of an overview of the commands in that group and a table that lists all the commands and queries for that group. You can click a command in the listing and a detailed description of the command will be displayed.

• Status and Events. This topic discusses the status and event reporting system for the GPIB interface. This system informs you of certain significant events that occur within the instrument. Topics that are discussed include registers, queues, event handling sequences, synchronization methods, and messages that the instrument may return, including error messages.

• Miscellaneous. This topic contains miscellaneous information, such as a list of reserved words, a table of the factory initialization (default) settings, and GPIB interface specifications that may be helpful when using GPIB commands to remotely control the instrument.

Setting Up Remote Communications

Before setting up your instrument for remote communications, you should familiarize yourself with the following GPIB requirements:

• A unique device address must be assigned to each device on the bus. No two devices can share the same device address.

• No more than 15 devices can be connected to any one line.

• One device should be connected for every 6 feet (2 meters) of cable used.

• No more than 65 feet (20 meters) of cable should be used to connect devices to a bus.

• At least two-thirds of the devices on the network should be powered on while using the network.

• Connect the devices on the network in a star or linear configuration. Do not use loop or parallel

configurations.

Connecting to the Instrument

Your instrument has a 24-pin GPIB connector on its rear panel. This connector has a D-type shell and conforms to IEEE Std 488.1–1987. Attach an IEEE Std 488.1–1987 GPIB cable to this connector and to your controller as shown in the following figure.

If necessary, the GPIB connectors can be stacked as shown in the figure below.

Setting the GPIB Address

To function correctly, your instrument must have a unique device address. The default settings for the GPIB configuration are:

• GPIB Address 1

• GPIB Mode GPIB Talk/Listen

To change either of the GPIB settings, do the following:

1. Select GPIB Configuration… from the Utilities menu.

2. Click the Configuration Talk/Listen button.

3. Change the GPIB Address to a unique address.

4. Click the Close button.

The instrument is set up for bi-directional communication with your controller.

Documentation

In addition to this TDS7000 Series Programmer Online Guide, the following documentation is included with this instrument.

User Manual. The User Manual has information about installing and operating the Oscilloscope. It also provides concepts and theories about using the oscilloscope that are not covered in the online help.

Quick Reference Guide. A quick reference guide provides basic information on connecting a signal to the oscilloscope and displaying the results.

TDS 7000 Series Online Help. This is an online help system that is integrated with the User Interface application that ships with this product.

Optional Service Manual. A service manual is available as an optional accessory; it includes procedures to service the oscilloscope to module levels. It also includes performance verification procedures so you can verify performance to advertised specifications.

Command Syntax

Syntax Overview

You can control the operations and functions of the instrument through the GPIB interface using commands and queries. The related topics listed below describe the syntax of these commands and queries. The topics also describe the conventions that the instrument uses to process them. See the Command Groups topic in the table of contents for a listing of the commands by command group or use the index to locate a specific command.

Backus-Naur Form Notation

This documentation describes the commands and queries using Backus-Naur Form (BNF) notation. Refer to the following table for the symbols that are used.

Symbols for Backus-Naur Form

Symbol Meaning

< > Defined element ::= Is defined as | Exclusive OR { } Group; one element is required [ ] Optional; can be omitted . . . Previous element( s) may b e repeated ( ) Comment

Command and Query Structure

Commands consist of set commands and query com man ds (usu ally call ed commands and queries). Commands modify instrument settings or tell the instrument to perform a specific action. Queries cause the instrument to return data and status information.

Most commands have both a set form and a query form. The query form of the command differs from the set form by its question mark on the end. 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 have set only and some have query only.

Messages

A command message is a command or query name followed by any information the instrument needs to execute the command or query. Command messages may contain five element types, defined in the following table.

Command and Message Elements

Symbol Meaning

<Header> This is 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. Never use the beginning colon with command headers beginning with a star (*).

<Mnemonic> This is a header subfunction. Some

command headers have only one mnemonic. If a command header has multiple mnemonics, a colon (:) character always separates them from each other.

<Argument> This is a quantity, quality, restrictijon, or limit

associated with the header. Some commands have no arguments while others have multiple arguments. A <space> separates arguments from the header. A <comma> separates arguments from each other.

<Comma A single comma is used between arguments

of multiple-argument commands. Optionally, there may be white space characters before and after the comma.

<Space> A white space character is used between a

command header and the related argument. Optionally, a white space may consist of multiple white space characters.

Commands

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

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

A command header consists 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 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 instrument to return status or setting information. Queries have the structure:

• [:]<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. For example, HIStogram:STATistics:STDdev? returns the standard deviation of the histogram, while HIStogram:STATistics? returns all the histogram statistics, and HIStogram? returns all the histogram parameters.

Headers

You can control whether the instrument returns headers as part of the query response. Use the HEADer command to control this feature. If header is on, the query response returns command headers, then formats itself as a valid set command. When header is off, the response includes only the values. This may make it easier to parse and extract the information from the response. The table below shows the difference in responses.

Comparison of Header Off and Header On Responses

Query Header Off Header On

TIME? "14:30:00" :TIME "14:30:00" ACQuire:NUMAVg? 100 :ACQUIRE:NUMAVG 100

Command Entry

Rules

The following rules apply when entering commands:

• You can enter commands in upper or lower case.

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

• The instrument ignores commands consisting of any combination of white space characters and line

feeds.

Abbreviating

You can abbreviate many instrument commands. Each command in this documentation shows the abbreviations in capitals. For example, you can enter the command ACQuire:NUMAvg simply as ACQ:NUMA or acq:numa.

Abbreviation rules may change over time as new instrument models are introduced. Thus, for the most robust code, use the full spelling.

If you use the HEADer command to have command headers included as part of query responses, you can further control whether the returned headers are abbreviated or are full-length with the VERBose command.

Concatenating

You can concatenate any combination of set commands and queries using a semicolon (;). The instrument executes concatenated commands in the order received.

When concatenating commands and queries, you must follow these rules: 1 Separate completely different headers by a semicolon and by the beginning colon on all commands

except the first one. For example, the commands TRIGger:MODe NORMal and ACQuire:NUMAVg 10, can be concatenated into the following single command:

TRIGger:MODe NORMal;:ACQuire:NUMAVg 10

2 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, you can concatenate the

commands ACQuire:MODe ENVelope and ACQuire:NUMAVg 10 into a single command: ACQuire:MODe ENVelope; NUMAVg 10 The longer version works equally well: ACQuire:MODe ENVelope;:ACQuire:NUMAVg 10

3 Never precede a star (*) command with a colon:

ACQuire:MODe ENVelope;*OPC Any commands that follow will be processed as if the star command was not there so the commands,

ACQuire:MODe ENVelope;*OPC;NUMAVg 10 will set the acquisition mode to envelope and set the number of acquisitions for averaging to 10.

4 When you concatenate queries, the responses to all the queries are concatenated into a single

response message. For example, if the display background color is white and the display foreground

color is black, the concatenated query DISplay:COLor:BACKGround?;FOREGround? will return the

following. If the header is on: :DISPLAY:COLOR:BACKGROUND 7;:DISPLAY:COLOR:FOREGROUND 0 If the header is off: 7;0

5 Set commands and queries may be concatenated in the same message. For example,

ACQuire:MODe SAMple;NUMAVg?;STATE? is a valid message that sets the acquisition mode to sample. The message then queries the

number of acquisitions for averaging and the acquisition state. Concatenated commands and queries are executed in the order received.

Here are some invalid concatenations:

• DISPlay:STYle:NORMal;ACQuire:NUMAVg 10 (no colon before ACQuire)

• DISPlay:COLor:CURSor1 1;:CURSor2 5 (extra colon before CURSor2; use DISPlay:COLor:CURSor1 1:CURSor2 5 instead)

• DISPlay:STYle:NORMal;:*OPC (colon before a star (*) command)

• DISPlay:COLor:CURSor1 1;COLor:CURSor2 5 (levels of the mnemonics are different; either remove the second use of COLor or place :DISPlay: in front of COLor:CURSor2 5)

Terminating

This documentation uses <EOM> (End of message) to represent a message terminator.

End of Mess age Terminat or

Symbol Meaning

<EOM> Message terminat or

The end-of-message terminator may 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 instrument always terminates messages with LF and EOI. It allows white space before the terminator. For example, it allows CR LF.

Clearing the Instrument

You can clear the Output Queue and reset the instrument to accept a new command or query by using the selected Device Clear (DCL) GPIB function. Refer to your GPIB library documentation for further details about the selected Device Clear operation.

Argument Types

Numeric

Many instrument commands require numeric arguments. The syntax shows the format that the instrument returns in response to a query. This is also the preferred format when sending the command to the instrument though any of the formats will be accepted. This documentation represents these arguments as follows:

Numeric Arguments

Symbol Meaning

<NR1> Signed integ er val ue <NR2> Floating point value without an exponent <NR3> Float ing point va lue with an exponent

Most numeric arguments will be automatically forced to a valid setting, either by rounding or truncating, when an invalid number is input unless otherwise noted in the command description.

Quoted String

Some commands accept or return data in the form of a quoted string, which is simply a group of ASCII characters enclosed by a single quote (') or double quote ("). For example: "this is a quoted string". This documentation represents these arguments as follows:

Quoted String Argument

Symbol Meaning

<QString> Quoted string of ASCII text

A quoted string can include any character defined in the 7-bit ASCII character set. Follow these rules when you use quoted strings:

1 Use the same type of quote character to open and close the string. For example: "this is a valid

string".

2 You can mix quotation marks within a string as long as you follow the previous rule. For example, "this

is an 'acceptable' string".

3 You can include a quote character within a string simply by repeating the quote. For example: "here is

a "" mark". 4 Strings can have upper or lower case characters. 5 If you use a GPIB network, you cannot terminate a quoted string with the END message before the

closing delimiter. 6 A carriage return or line feed embedded in a quoted string does not terminate the string, but is treated

as just another character in the string. 7 The maximum length of a quoted string returned from a query is 1000 characters.

Here are some invalid strings: * "Invalid string argument' (quotes are not of the same type) * "test<EOI>" (termination character is embedded in the string)

Block

Several instrument commands use a block argument form (see the following table).

Block Arguments

Symbol Meaning

<NZDig> A nonzero digit character in the range of 1–9 <Dig> A digit character, in the range of 0–9 <DChar>

A character with the hexadecimal equivalent of 00 through FF (0 through 255 decimal)

<Block> A block of data bytes defined as:

<Block> ::= {#<NZDig><Dig>[<Dig>...][<DChar>...] |#0[<DChar>...]<terminator>}

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

Constructed Mnemonics

Some header mnemonics specify one of a range of mnemonics. For example, a channel mnemonic can be CH1, CH2, CH3, or CH4. You use these mnemonics in the command just as you do any other mnemonic. For example, there is a CH1:POSition command, and there is also a CH2:POSition command. In the command descriptions, this list of choices is abbreviated as CH<x>.

Cursor Position Mnemonics

When cursors are displayed, commands may specify which cursor of the pair to use.

Cursor Mnemonics

Symbol Meaning

CURSOR<x> A cu r sor s elector; <x> is eith er 1 or 2. POSITION<x> A curs or select or; <x> is ei ther 1 or 2. HPOS<x> A cursor selector; <x> is eith er 1 or 2.

Math Specifier Mnemonics

Commands can specify the mathematical waveform to use as a mnemonic in the header.

Math Specifier Mnemonics

Symbol Meaning

MATH<x> A math waveform specifier; <x> is 1 through 4.

Measurement Specifier Mnemonics

Commands can specify which measurement to set or query as a mnemonic in the header. Up to eight automated measurements may be displayed.

Measurement Specifier Mnemonics

Symbol Meaning

MEAS<x> A measurement specifier; <x> is 1 through 8.

Channel Mnemonics

Commands specify the channel to use as a mnemonic in the header.

Channel Mnemonics

Symbol Meaning

CH<x> A channel specifier; <x> is 1 through 4.

Reference Waveform Mnemonics

Commands can specify the reference waveform to use as a mnemonic in the header.

Reference Waveform Mnemonics

Symbol Meaning

REF<x> A reference waveform specifier; <x> is 1 through 4.

Commands

Acquisition Command Group

Acquisition Overview

You use the commands in the Acquisition Command Group to set up the modes and functions that control how the instrument acquires the signals you input to the channels and processes them into waveforms.

Using these commands for acquiring waveforms, you can do the following:

• Start and stop acquisitions.

• Control whether each waveform is simply acquired, averaged, or enveloped over successive

acquisitions of that waveform.

• Set the controls or conditions that start and stop acquisitions.

• Determine the action the system takes upon completing an acquisition, such as saving all waveforms

and taking a measurement when the acquisition is stopped.

• Control acquisition of acquired channel waveforms.

• Set acquisition parameters.

Acquisition Commands

Command

ACQuire? Returns acquisition parameters ACQuire:MODe? Returns acquisition mode ACQuire:MODe Sets acquisition mode ACQuire:NUMACq? Returns the number of

ACQuire:NUMAVg? Returns number of acquisitions

ACQuire:NUMAVg

ACQuireNUMEnv?

ACQuire:NUMEnv Sets number of acquisitions for

ACQuire:REPEt? Returns whether repetitive signal

ACQuire:REPEt Enables or disables repetitive

ACQuire:STATE? Returns acquisition state ACQuire:STATE Starts or stops acquisitions ACQuire:STOPAfter? Returns whether the acquisition

ACQuire:STOPAfter Sets whether the acquisition is

FASTAcq? Returns the Fast Acquisition state FASTAcq:STATE? Returns the Fast Acquisition state FASTAcq:STATE Enables or disables Fast

Description

acquisitions that have occurred

for an averaged waveform Sets number of acquisitions for

an averaged waveform Returns number of acquisitions

for envelope waveform

envelope waveform

acquisition mode on

signal acquisition mode

is continuous or single sequence

continuous or single sequence

Acquisition mode

ACQuire:MODe

Description

This command sets or queries the acquisition mode of the oscilloscope. This affects all live waveforms. This command is equivalent to selecting Horizontal/Acquisition from the Horiz/Acq menu and then choosing the desired mode from the Acquisition Mode group box.

Waveforms are the displayed data point values taken from acquisition intervals. Each acquisition interval represents a time duration set by the horizontal scale (time per division). The oscilloscope sampling system always samples at the maximum rate and so an acquisition interval may 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.

Group

Acquisition

Related Commands

ACQuire:NUMAVg (see page 23), ACQuire:NUMenv (see pa ge 2 4), CURVe? (see page 467)

Syntax 1

ACQuire:MODe{SAMple|PEAKdetect|HIRes|AVErage|ENVelope}

Syntax 2

ACQuire:MODe?

Arguments

• SAMple

Specifies that the displayed data point value is simply the first sampled value that is taken during the acquisition interval. In sample mode, all waveform data has 8 bits of precision. You can request 16 bit

SAMple

data with a CURVe? query but the lower-order 8 bits of data will be zero. For more information about the CURVe query, see page 467.

is the default mode.

• PEAKdetect

Specifies the display of high-low range of the samples taken from a single waveform acquisition. The high-low range is displayed as a vertical column that extends from the highest to the lowest value sampled during the acquisition interval.

PEAKdetect

mode can reveal the presence of aliasing or

narrow spikes.

• HIRes

Specifies Hi Res mode where the displayed data point value is the average of all the samples taken during the acquisition interval. This is a form of averaging, where the average comes from a single waveform acquisition. The number of samples taken during the acquisition interval determines the number of data values that compose the average.

• AVErage

Specifies averaging mode, in which the resulting waveform shows an average of SAMple data points from several separate waveform acquisitions. The oscilloscope processes the number of waveforms you specify into the acquired waveform, creating a running exponential average of the input signal. The number of waveform acquisitions that go into making up the average waveform is set or queried using the ACQuire:NUMAVg command. For more information about the ACQuire:NUMACg command, see page 23.

• ENVelope

Specifies envelope mode, where the resulting waveform shows the PEAKdetect range of data points from several separate waveform acquisitions. The number of waveform acquisitions that go into making up the envelope waveform is set or queried using the ACQuire:NUMENv command. For more information about the ACQuire:NUMENv command, see page 24.

Example 1

ACQuire:MODe ENVelope

Sets the acquisition mode to display a waveform that is an envelope of many individual waveform acquisitions.

Example 2

ACQuire:MODe?

This command might return

:ACQuire:MODe AVERAGE

, indicating that the displayed waveform is the

average of the specified number of waveform acquisitions.

ACQuire:NUMACq?

Description

This query-only command returns the number of waveform acquisitions that have occurred since starting acquisition with the ACQuire:STATE RUN command. This value is reset to zero when any acquisition, horizontal, or vertical arguments that affect the waveform are changed. The maximum number of acquisitions that can be counted is 2 This is the same value that displays in the upper center of the screen when the acquisition system is stopped.

Note: In FastFrame or InstaVu modes, the oscilloscope updates the acquisition count in groups of counts.

Group

Acquisition

Related Commands

ACQuire:STATE (see page 26)

Syntax

ACQuire:NUMACq?

Example

ACQuire:NUMACq?

This command might return :ACQUIRE:NUMACQ 350, indicating that 350 acquisitions have occurred since executing the ACQuire:STATE RUN command.

–1. The oscilloscope stops counting when this number is reached.

ACQuire:NUMAVg

Description

This command sets or queries the number of waveform acquisitions that make up an averaged waveform. Use the ACQuire:MODe command to enable the Average mode. Sending this command is equivalent to selecting Horizontal/Acquisition Setup from the Horiz/Acq menu, selecting the Acquisition tab, and then choosing Average from the Acquisition Mode group box. Then enter the desired number of waveforms that will be used to make up an averaged waveform in the # of Wfms box.

Group

Acquisition

Related Commands

ACQuire:MODe (see page 20)

Syntax 1

ACQuire:NUMAVg <NRf>

Syntax 2

ACQuire:NUMAVg?

Arguments

• NRf

This is the number of waveform acquisitions to average.

Example 1

ACQuire:NUMAVg 10

This command specifies that 10 waveform averages will be performed before exponential averaging starts.

Example 2

ACQuire:NUMAVg?

This command might return averaging.

:ACQUIRE:NUMAVG 75

, indicating that there are 75 acquisitions specified for

ACQuire:NUMEnv

Description

This command sets or queries the number of waveform acquisitions that make up an envelope waveform. Sending this command is equivalent to setting the Envelope count in the Acquisition Mode side menu.

Group

Acquisition

Syntax 1

ACQuire:NUMEnv {<NRf> | INFInite}

Syntax 2

ACQuire:NUMEnv?

Arguments

• NRf

This is the number of waveform acquisitions to be enveloped.

Example 1

ACQuire:NUMenv 10

This command specifies that an enveloped waveform will show the result of combining 10 separately acquired waveforms.

Example 2

ACQuire:NUMenv?

This command might return enveloped waveforms.

:ACQUIRE:NUMENV 0

, indicating that acq uisitions are acquired infinitely for

ACQuire:REPEt

Description

This command sets or queries whether repetitive mode is on or off. This is equivalent to setting Equivalent Time Auto/Off in the Acquisition control window. When the oscilloscope is in real-time operation, this setting has no effect.

The ACQuire:REPet command specifies the behavior of the acquisition system during equivalent-time operation. When repetitive mode is on, the acquisition system will continue to acquire waveform data until the waveform record is filled with acquired data. When repetitive mode is off, horizontal scale and record length settings will be restricted to those settings that will be achievable with real-time acquisition.

Group

Acquisition

Syntax 1

ACQuire:REPEt {OFF|ON|<NR1>}

Syntax 2

ACQuire:REPEt?

Arguments

• OFF

This argument disables repetitive mode.

• ON

This argument enables repetitive mode.

• NR1

A 0 disables repetitive mode ; any other value enables repetitive mode.

Example 1

ACQUIRE:REPEt 1

This command enables repetitive mode.

Example 2

ACQuire:REPEt?

This query might return :ACQUIRE:REPET OFF, indicating that repetitive mode is disabled.

ACQuire:STATE

Description

This command starts or stops acquisitions. When state is set to ON or RUN, a new acquisition will be started. If the last acquisition was a single acquisition sequence, a new single sequence acquisition will be started. If the last acquisition was continuous, a new continuous acquisition will be started.

If RUN is issued in the middle of completing a single sequence acquisition (for examples, averaging or enveloping), the acquisition sequence is restarted, and any accumulated data is discarded. Also, the oscilloscope resets the number of acquisitions. If the RUN argument is issued while in continuous mode, a reset occurs and acquired data continues to acquire.

Sending this command is equivalent to pressing the front-panel RUN/STOP button.

Group

Acquisition

Related Commands

ACQuire:STOPAfter (see page 27)

Syntax 1

ACQuire:STATE{OFF|ON|RUN|STOP|<NR1>}

Syntax 2

ACQuire:STATE?

Arguments

• OFF

This argument stops acquisitions.

• STOP

This argument stops acquisitions.

• ON

This argument starts acquisitions.

• RUN

This argument starts acquisitions.

• NR1

0 stops acquisitions; any other value starts acquisitions.

Example 1

ACQuire:STATE RUN

This command starts the acquisition of waveform data and resets the count of the number of acquisitions.

Example 2

ACQuire:STATE?

This query might return

:ACQUIRE:STATE 0

, indicating that the acquisition is stopped

ACQuire:STOPAfter

Description

This command sets or queries whether the oscilloscope continually acquires acquisitions or acquires a single sequence. This command is equivalent to pressing SINGLE from the front-panel.

Group

Acquisition

Related Commands

ACQuire:STATE (see page 26), ACQuire:REPEt (see page 25)

Syntax 1

ACQuire:STOPAfter {RUNSTop|SEQuence}

Syntax 2

ACQuire:STOPAfter?

Arguments

• RUNSTop

Specifies that the oscilloscope will continually acquire data, if ACQuire:STATE is turned on.

• SEQuence

Specifies that the next acquisition will be a single-sequence acquisition.

Example 1

ACQuire:STOPAfter RUNSTOP

This command sets the oscilloscope to continually acquire data.

Example 2

ACQuire:STOPAfter?

This query might return oscilloscope makes will be of the single-sequence type.

:ACQUIRE:STOPAFTER SEQUENCE

, indicating that the next acquisition the

ACQuire?

Description

This query-only command returns the following current acquisition parameters:

• Stop after

• Acquisition state

• Mode

• Number of envelopes

• Number of averages

• Repetitive signals

Group

Acquisition

Related Commands

ACQuire:MODe (see page 20), ACQuire:NUMACq (see page 22), ACQuire:NUMAVg (see page 23), ACQuire:NUMenv (see page 24), ACQuire:REPEt (see page 25), ACQuire:STATE ( see page 26), ACQuire:STOPAfter (see page 27)

Syntax

ACQuire?

Example

ACQuire?

This query might return the following string for the current acquisition parameters:

:ACQUIRE:STOPAFTER RUNSTOP;STATE 1;MODE SAMPLE;NUMENV 10;NUMAVG 16;REPET ON

+ 546 hidden pages

Tektronix TDS7000 Series Programmer's Manual

Specifications and Main Features

Frequently Asked Questions

User Manual