xx
MSO3000 and DPO3000 Series
ZZZ
Digital Phosphor Oscilloscopes
Programmer Manual
*P077030102*
077-0301-02
xx
MSO3000 and DPO3000 Series
ZZZ
Digital Phosphor Oscilloscopes
Programmer Manual
Revision C
www.tektronix.com
077-0301-02
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
supersedes that in all previously published material. Specifications and price change privileges reserved.
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
Contacting
Tektronix, Inc.
14150 SW Karl Braun Drive
P.O . Bo x 50
Beaverton, OR 97077
USA
For product information, sales, service, and technical support:
In North America, call 1-800-833-9200.
Worl d wi
Tektronix
0
de, visit www.tektronix.com to find contacts in your area.
Table of Contents
Getting Started .. ... .. . .. . .. ... .. . .. ... ... .. . .. . .. ... ... .. . .. ... ... .. . .. ... ... .. . .. . .. ... ... .. . .. ... ... .. . .. ... ... . 1-1
Instrument Functionality Updates that Impact the Programmatic Command Set . .. . .. . .. ... ... ... .. 1-1
Setting Up Remote Communications Hardware . ... .. . .. . .. ... ... .. . .. . .. ... ... .. . .. . .. ... ... ... .. . .. ... 1-2
Ethernet .................................................................................................. 1-2
USB....................................................................................................... 1-2
GPIB...................................................................................................... 1-4
Setting Up Remote Communications Software . ... ... .. . .. . .. ... ... .. . .. . .. ... ... .. . .. ... ... ... .. . .. ... . 1-5
Using VISA..................... .................................. ................................ ....... 1-5
Using e*Scope.......................... .................................. ............................... 1-6
Using a Socket Server .................................................................................. 1-7
Command Syntax...................................... ................................ ........................... 2-1
Command and Query Structure ............................................................................ 2-1
Clearing the oscilloscope .. ... .. . .. ... ... .. . .. . .. ... ... .. . .. . .. ... ... .. . .. ... ... .. . .. ... ... .. . .. . .. ... ... .. . 2-3
Command Entry.............................................................................................. 2-3
Constructed Mnemonics .................................................................................... 2-5
Argument Types................... .................................. ................................ ......... 2-7
Command Groups .............................................................................................. 2-11
Acquisition Command Group . . .. . .. ... ... .. . .. ... ... .. . .. ... ... .. . .. . .. ... ... .. . .. ... ... .. . .. ... ... .. . .. 2-11
Alias Command Group............................. ................................ ....................... 2-12
Bus Command Group ..................................................................................... 2-13
Calibration and Diagnostic Command Group .......................................................... 2-17
Configuration Command Group.......................................................................... 2-17
Cursor Command Group..... .................................. ................................ ........... 2-21
Display Command Group................................................................................. 2-22
Ethernet Command Group................................................................................ 2-23
File System Command Group............... ................................ ............................. 2-24
Hard Copy Command Group.......................... .................................. ................. 2-25
Horizontal Command Group .. ................................ .................................. ......... 2-27
Mark Command Group................. .................................. ................................ . 2-27
Math Command Group....................... ................................ ............................. 2-29
Measurement Command Group..................... ................................ ..................... 2-30
Miscellaneous Command Group......................................................................... 2-33
PictBridge Command Group .. ................................ .................................. ......... 2-35
Power Command Group ................. ................................ ................................. 2-35
Save and Recall Command Group ....................................................................... 2-43
Search Command Group..... ................................ .................................. ........... 2-45
Status and Error Command Group.................. ................................ ..................... 2-56
Trigger Command Group .................. ................................ ............................... 2-57
Vertical Command Group........ .................................. ................................ ....... 2-75
MSO3000 and DPO3000 Series Programmer Manual i
Table of Contents
Waveform Trans
Zoom Command Group.......................... ................................ ......................... 2-91
Commands Listed in Alphabetical Order. ................................ ................................ ... 2-93
Status and Events ................................................................................................. 3-1
Registers ......... ................................ .................................. ........................... 3-1
Queues ........................................................................................................ 3-4
Event Handl
Synchronization Methods............ .................................. ................................ ..... 3-7
Appendix A: Character Set ..................................................................................... A-1
Appendix B: Reserved Words.................................................................................. B-1
Appendix C: Programming Example.......................................................................... C-1
Appendix D: Waveform Transfer (WFMOutpre and CURVe Query) Examples ......................... D-1
Example
Example 2: Digital Waveform (Channels DO-D15).................................................... D-3
Example 3: The Digital Collection with 4 Bytes Per Point and MagniVu Off....................... D-5
Example 4: The Digital Collection with 8 Bytes Per Point and MagniVu Off....................... D-7
Example 5: The Digital Collection with 4 Bytes Per Point and MagniVu On ..................... D-10
Example 6: The Digital Collection with 8 Bytes Per Point and MagniVu On ..................... D-12
ndix E: Search and Trigger Command Sequence Examples...... ................................ .... E-1
Appe
Example 1: Single Threshold Edge Search ...................... ................................ ........ E-1
Example 2: Single Threshold Edge Trigger ....................... ................................ ...... E-2
Example 3: Dual Threshold Runt Search .... ................................ ............................ E-2
Example 4: Single Threshold Logic Search on Three Waveforms.................................... E-3
Index
1: Analog Waveform (Channels 1–4) ....................... ................................ .. D-1
fer Command Group ................................................................... 2-78
ing Sequence................................................................................... 3-5
ii MSO3000 and DPO3000 Series Programmer Manual
Getting Started
This manual explains the use of commands for remotely controlling your
oscilloscope. With this information, you can write computer programs to
perform func
tions, such as setting the front-panel controls, taking measurements,
performing statistical calculations, and exporting data for use in other programs.
You can use these commands with these oscilloscope models:
MSO3054, MSO3034, MSO3032, MSO3014, MSO3012 , DPO3054, DPO3052,
DPO3034, DPO3032, DPO3014, DPO3012
Instrument Function
ality Updates that Impact the Programmatic Command Set
The following lists some of the instrument functionality updates that impact
the p rogrammatic command set, along with links to some of the corresponding
commands:
Feature Use these commands
Support for the MIL-STD-1553 bus (requires the DPO3AERO
application module)
Support for the FlexRay bus (requires the DPO3FLEX
application module)
Ability to trigger and search on pulse width r anges
Support for timeout trigger and search TRIGger:A:TYPe, SEARCH:SEARCH<x>:TRIGger:A:TYPe
Ability to query instrument configuration settings
Ability to turn waveform display persistence off or on DISplay:PERSistence OFF
Support for choosing the number of waveforms included in an
envelope for envelope acquisition mode
Ability to import .CSV w aveform files RECAll:WAVEform
Support for socket server interface
Ability to select solid graticule
Ability to transfer licenses between modules and oscilloscope APPLication:LICENSE:SLOT<x>:LOCation?, APPLication:
Ability to press and hold front panel buttons (only the Cursors
button is currently supported)
(See page 2-13,
(See page 2-57,
(See page 2-45,
(See page 2-13,
(See page 2-57,
(See page 2-45,
TRIGger:A:PULSEWidth:WHEn, TRIGger:A:PULSEWidth:
LOWLimit, TRIGger:A:PULSEWidth:HIGHLimit
SEARCH:SEARCH<x>:TRIGger:A:PULSEWidth:WHEn,
SEARCH:SEARCH<x>:TRIGger:A:PULSEWidth:HIGHLimit,
SEARCH:SEARCH<x>:TRIGger:A:PULSEWidth:LOWLimit
(See page 2-17,
ACQuire:NUMEnv
(See page 1-2,
Hardware
DISplay:GRAticule
LICENSE:SLOT<x>:TRANSFER, APPLication:LICENSE:
SLOT<x>:TYPe?
FPAnel:HOLD
Bus Command Group.)
Trigger Command Group.)
Search Command Group.)
Bus Command Group.)
Trigger Command Group.)
Search Command Group.)
Configuration Command Group.)
Setting Up Remote Communications
.)
MSO3000 and DPO3000 Series Programmer Manual 1-1
Getting Started
Setting Up Rem
Ethernet
ote Communications Hardware
You can remotely communicate between your oscilloscope and PC via Ethernet,
USB, GPIB, or v ia a socket server.
If you are using Ethernet, start by connecting an appropriate Ethernet cable to the
Ethernet port (RJ-45 connector) on the rear panel of your oscilloscope. This
connects the oscilloscope to a 10/100 Base-T local area network.
To change the Ethernet settings on your oscilloscope, do the following:
USB
1. On the front panel, push Utility.
2. Push Utility Page.
3. Select I/O with the Multipurpose knob.
4. Push
5. On the side menu, if you are on a DHCP Ethernet network and using a through
6. If you are using a cross-over cable, set DHCP/BOOTP to Off, and push
If you are using USB, start by connecting the appropriate USB cable to the USB
2.0 high-speed (HS) device port on the rear panel of your oscilloscope. This
ort requires that the cable connected from the port to the host computer meets
p
the USB 2.0 specification for high speed connections. Typically, such cables
should be 3 feet or shorter in length, but this is determined by the quality of the
cable and, with higher quality cables, this length can be extended. (It is also
dependent upon the drive capability of the host USB port to which the instrument
is connected.) The use of high quality short cables is recommended to avoid USB
connection problems.
Ethernet Network Settings.
le, set DHCP/BOOTP to On.
cab
ange Instrument Settings to set a hard coded IP address.
Ch
1-2 MSO3000 and DPO3000 Series Programmer Manual
Getting Started
With USB, the system automatically configures itself. To verify that the USB is
enabled:
1. On the front panel, push Utility.
2. Push Utility Page.
3. Select I/O with the Multipurpose knob.
4. Push USB/Computer, and verify that USB is enabled.
5. If USB is disabled, push Connect to computer on the side menu.
After connection, the host, with appropriate software, can list the oscilloscope as a
USB device with the following parameters.
Table 1-1: USB Device Parameters
Parameter Value
Manufacturer ID 0x0699 (decimal 1689)
Product ID
Serial number Serial number
Manufacturer description
Interface description “USBTMC-USB488”
0x0410 (decimal 1040) DPO3012
0x0411 (decimal 1041) DPO3014
0x0412 (decimal 1042) DPO3032
0x0413 (decimal 1043) DPO3034
0x0414 (decimal 1044) DPO3052
0x0415 (decimal 1045) DPO3054
0x0420 (decimal 1056) MSO3012
0x0421 (decimal 1057) MSO3014
0x0422 (decimal 1058) MSO3032
0x0423 (decimal 1059) MSO3034
0x0425 (decimal 1061) MSO3054
“Tektronix”
MSO3000 and DPO3000 Series Programmer Manual 1-3
Getting Started
GPIB
To u se GPI B , s t a
rt by connecting an appropriate USB cable to the USB 2.0
high-speed device port on the rear panel of your oscilloscope. Connect the other
end to the TEK-USB-488 Adapter host port. Then connect a GPIB cable from the
TEK-USB-488 Adapter to your PC.
Supply power to the Adapter in either of these two ways:
1. Use the optional 5 V
power adapter connected to the 5 VDCpower input
DC
on the Adapter.
2. Use an appropriate USB cable connected to a powered USB host port on your
PC and the Device port on the TEK-USB-488 Adapter.
The oscilloscope has a USB 2.0 high-speed device port to control the oscilloscope
through USBTMC or GPIB with a TEK-USB-488 Adapter. The USBTMC
protocol allows USB devices to communicate using IEEE488 style messages.
This lets you run your GPIB software applications on USB hardware.
Before setting up the oscilloscope for remote communication using the electronic
(physical) GPIB interface, 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 a ny 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.
To function correctly, your oscilloscope must have a unique device address. The
default setting for the GPIB configuration is GPIB Address 1.
1-4 MSO3000 and DPO3000 Series Programmer Manual
Getting Started
To chan g e the GP
1. On the front panel, push Utility.
2. Push Utility Page.
3. Select I/O with the Multipurpose knob.
4. Push GPIB.
5. Enter the GPIB address on the side menu, using the multipurpose knob. This
will set the GPIB address on an attached TEK-USB-488 Adapter.
The oscilloscope is now set up for bidirectional communication with your
controller.
IB address settings, do the following:
Setting Up Remote Communications Software
Connect your oscilloscope directly to a computer to let the PC analyze your data,
collect screen images, or to control the oscilloscope using a program of your own
creation. Three ways to connect your oscilloscope to a computer are through the
VISA drivers, the e*Scope Web-enabled tools, or via a socket server.
Using
VISA
VISA lets you use your MS-Windows computer to acquire data from your
oscilloscope for use in an analysis package that runs on your PC, such as
Microsoft Excel, National Instruments LabVIEW, Tektronix OpenChoice Desktop
ware, or your own custom software. You can use a common communications
soft
connection, such as USB, Ethernet, or GPIB, to connect the computer to the
oscilloscope.
To set up VISA communications between your oscilloscope and a computer:
MSO3000 and DPO3000 Series Programmer Manual 1-5
Getting Started
1. Load the VISA dr
as OpenChoice Desktop. You will find the drivers and OpenChoice Desktop
software on the appropriate CD that comes with your oscilloscope or at the
Tektronix software finder Web page (www.tektronix.com).
2. Connect the oscilloscope to your computer with the appropriate USB or
Ethernet cable. You will find the drivers and OpenChoice Desktop software
on the appropriate CD that comes with your oscilloscope or at the Tektronix
software fi nder Web page (www.tektronix.com/downloads).
3. On the front panel, push Utility.
4. Push Utility Page on the lower menu.
5. Turn multipurpose knob a and select I/O.
6. If you are using USB, the system sets itself up automatically for you, if USB is
enabled. Check USB on the lower menu to be sure that USB is enabled. If it is
not enabled, push USB. Then push Connect to Computer on the side menu.
7. To use Ethernet, push Ethernet Network Settings on the lower menu. Use
the side menu buttons to adjust your network settings, as needed. For more
information, see the e*Scope setup information below.
8. If you want to change socket server parameters, push Socket Server and enter
new values through the resulting side menu.
ivers on your computer. Also, load your application, such
Quick Tips
Using e*Scope
9. If you are using GPIB, push GPIB. Enter the GPIB address on the side menu,
using multipurpose knob a.
10. Run your application software on your computer.
Your oscilloscope shipped with a CD containing a variety of Windows-based
software tools for efficient connectivity between your oscilloscope and your
computer. These include toolbars that speed connectivity with Microsoft
Excel a nd Word. There are also two standalone acquisition programs called
NI LabVIEW SignalExpress™, Tektronix Edition and Tektronix OpenChoice
esktop.
D
The rear-panel USB 2.0 device port is the correct USB port for computer
connectivity. Use the rear- and front-panel USB 2.0 host ports to connect
your oscilloscope to USB flash drives, printers and keyboards. Use the USB
Device port to connect your oscilloscope to a PC or a PictBridge printer.
With e*Scope, you can use a web browser on your computer to send and receive
commands using any connected MSO/DPO3000 Series oscilloscope. To set up
e*Scope communications between your oscilloscope and a Web browser running
onaremotecomputer:
1-6 MSO3000 and DPO3000 Series Programmer Manual
Getting Started
1. Connect the osc
Ethernet cable.
2. On the front panel, push Utility.
3. Push Utility P age on the lower menu.
4. Turn multipurpose knob a and select I/O.
5. Push Ethernet Network Settings.
6. Push Change Instrument Settings to display and change the instrument
setup on your oscilloscope. Optional: enter an Instrument IP address if
you’d like to manually configure it.
7. Push Test Connection to check if your oscilloscope can find an attached
network.
8. Start y our browser on your remote computer. In the browser address line,
enter the host name, a dot, and the domain name together. Alternatively, just
enter the IP address of the instrument. Either way, you should then see the
e*Scope page on your Web browser on your computer screen.
9. ClickontheDatatabonthee*Scopepage.UnderTalk/Listen, you may enter
and send commands to the connected oscilloscope.
illoscope to your computer network with an appropriate
Using a Socket Server
ket server provides two-way communication over an Internet Protocol-based
Asoc
computer network. You can use your oscilloscope’s socket server feature to let
your oscilloscope talk to a remote-terminal device or computer.
To set up and use a socket server between your oscilloscope and a remote terminal
or computer:
1. Connect the oscilloscope to your computer network with an appropriate
Ethernet cable.
2. Push Utility.
3. Push Utility Page.
4. Turn multipurpose knob a and select I/O.
5. Push Socket Server.
6. On the resulting Socket Server side menu, push the top entry to highlight
Enabled.
7. Choose whether the protocol should be None or Term i na l . A communication
session run by a human at a keyboard typically uses a terminal protocol.
An automated session might h andle its own communications without using
such a protocol.
8. If required, change the port number by rotating multipurpose knob a.
9. If required, press OK to set the new port number.
MSO3000 and DPO3000 Series Programmer Manual 1-7
Getting Started
10. After setting u
p the socket server parameters, you can now have the computer
talk to the oscilloscope. If you are running an MS Windows PC, you could
run its default client with its command-like interface. One way to do this is
by typing “
Telnet ” in the Run window. The Telnet window will open on
the PC.
NOTE. On MS Windows 7, you must first enable Telnet for it to work.
11. Start a terminal session between your computer and your oscilloscope by
typing in an open command with the oscilloscope's LAN a ddress and port #.
You can obtain the LAN address by pushing the Ethernet Network
Settings bottom menu item and then Change Instrument Settings on the
ng side menu.
resulti
You can obtain the port number by pushing the Socket Server bottom
menu ite
For example, if the oscilloscope IP address was
port # w
m and viewing the Current Port side menu item.
123.45.67.89 and the
as the default of
4000, you could open a session by writing into
the MS Windows Telnet screen:
o 123.
45.67.89 4000
12. You can now type in a standard query, as found in the programmer manual,
as
such
*idn?
The Telnet session window will respond by displaying a character string
cribing your instrument.
des
You can type in more queries and view more results on this Telnet session
ndow. You can find the syntax for relevant queries and related status
wi
codes in other sections of this manual.
NOTE. Do not use the computer’s backspace key during an MS Windows' Telnet
session with the oscilloscope.
Socket Server Terminal Protocol Mode Commands. Following are Tektronix
Instrument Control Terminal Session Control commands:
!t <timeout> : set the response timeout in milliseconds.
!d : send device clear to the instrument.
!r : read response from instrument.
!h : print this usage info.
1-8 MSO3000 and DPO3000 Series Programmer Manual
Getting Started
Documentation
NOTE. Commands
read automatically.
The followin
site at www.tektronix.com/downloads:
MSO3000 and
and operating the oscilloscope.
Getting St
from your oscilloscope into any one of several available analysis tools.
MSO3000 a
and a performance verification procedure.
TekV ISA
implementation of the VISA Application Programming Interface (API). TekVISA
is industry-compliant software for writing interoperable oscilloscope drivers in a
variety of Application Development Environments (ADEs).
arted with OpenChoice ™ Solutions Manual. Options for getting data
nd DPO3000 Series Technical Reference. Oscilloscope specifications
Programmer Manual. Description of TekVISA, the Tektronix
containing a ? are treated as queries, and the responses are
g documents are available for download on the Manuals Finder Web
DPO3000SeriesUserManual. Information about installing
MSO3000 and DPO3000 Series Programmer Manual 1-9
Getting Started
1-10 MSO3000 and DPO3000 Series Programmer Manual
Command Syntax
You can control the operations and functions of the oscilloscope through the
Ethernet port or the USB 2.0 device port using commands and queries. The
related topi
The topics also describe the conventions that the oscilloscope uses to process
them. See the Command Groups topic in the table of contents for a listing o f the
commands by command group, or use the index to locate a specific command.
cs listed below describe the syntax of these commands and queries.
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.
Table 2-1: Symbols for Backus-Naur Form
Symbol Meaning
<>
=
| Exclusive OR
{ } Group; one element is required
[]
.. .
( ) Comment
Command and Query Structure
mmands consist of set commands and query commands (usually called
Co
commands and queries). Commands modify oscilloscope settings or tell the
oscilloscope to perform a specific action. Queries cause the oscilloscope to return
data and status information.
Defined element
Is defined as
Optional; can be omitted
Previous element(s) may be repeated
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 at the end. For example,
the set command
commands have both a set and a query form. Some commands have set only and
some have query only.
Messages
MSO3000 and DPO3000 Series Programmer Manual 2-1
A command message is a command or query name followed by any information
the oscilloscope needs to execute the command or query. Command messages
may c ontain five element type s, defined in the following table.
ACQuire:MODe has a query form ACQuire:MODe?.Notall
Command Syntax
Commands
Table 2-2: Comm
Symbol Meaning
<Header>
<Mnemonic>
<Argument
<Comma> A single c
<Space>
Comman
>
ds cause the oscilloscope to perform a specific function or change one of
and Message Elements
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
(:) characte
the beginning colon is required. Never use the beginning colon with
command headers beginning with a star (*).
This is a header subfunction. Some command headers have only one
mnemonic. I
character always separates them from each other.
This is a qu
Some commands have no arguments while others have multiple
arguments. A <space> separates arguments from the header. A
<comma> se
commands. Optionally, there may be white space characters before
and after the comma.
A white space character is used between a command header and the
related argument. Optionally, a white space may consist of multiple
white sp
r. If the command is concatenated with other commands,
f a command header has multiple mnemonics, a colon (:)
antity, quality, restriction, or limit associated with the header.
parates arguments from each other.
omma is used between arguments of multiple-argument
ace characters.
the settings. Commands have the structure:
eader>[<Space><Argument>[<Comma> <Argument >]...]
[:]<H
A command header consists of one or more mnemonics arranged in a hierarchical
ee structure. The first mnemonic is the base or root of the tree and each
or tr
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.
2-2 MSO3000 and DPO3000 Series Programmer Manual
Command Syntax
Queries
Headers
Queries cause t
have the structure:
[:]<Header>
[:]<Header>[<Space><Argument> [<Comma><Argu ment>]...]
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.
Use the HEADer command to control whether the oscilloscope returns headers as
part of the query response. 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.
Table 2-3: Comparison of Header Off and Header On R esponses
Query Header Off Header On
TIME?
ACQuire:NUMAVg?
he oscilloscope to return status or setting information. Queries
14:30:00 :TIME “14:30:00”
100
:ACQUIRE:NUMAVG 100
Clearing the oscilloscope
You can clear the Output Queue and reset the oscilloscope to accept a new
command or query by using the selected Device Clear (DCL) function.
Command Entry
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 oscilloscope ignores commands consisting of any combination of white
space characters and line feeds.
MSO3000 and DPO3000 Series Programmer Manual 2-3
Command Syntax
Abbreviating
Concatenating
You can abbrevi
ate many oscilloscope commands. Each command in this
documentation shows the minimum acceptable 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 oscilloscope 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.
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:
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 ACQ uire:NUMAVg 8, can be concatenated
into the following single command:
TRIGger:MODe NORMal;:ACQuire:NUMAVg 8
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 8 into a single command:
ACQuire:MODe ENVelope; NUMAVg 8
The longer version works equally well:
ACQuire:MODe ENVelope;:ACQuire:NUMAVg 8
3. Never precede a star (*) command with a colon:
ACQuire:STATE 1;*OPC
Any commands that follow will be processed as if the star command was
not there so the commands,
ACQuire:MODe ENVel
ope;*OPC;NUMAVg 8
will set the acquisition mode to envelope and set the number of acquisitions
for averaging to 8.
4. When you concatenate queries, the responses to all the queries are
concatenated into a single response message. For example, if the display
graticule is set to Full and the display style is set to dotsonly, the concatenated
query
DISplay:GRAticule?;STYle:DOTsonly? will return the following.
Iftheheaderison:
DISPLAY:GRATICULE FULL;:DISPLAY:STYLE:DOT SONLY 1
2-4 MSO3000 and DPO3000 Series Programmer Manual
Command Syntax
If the header is
FULL;1
off:
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 comma nds and queries are executed in the order received.
Here are some invalid concatenations:
DISPlay:STYle:NORMal;ACQuire:NUMAVg 8 (no colon before ACQuire)
DISPlay:GRAticule FULL;:DOTSONLY OFF (extra colon before
DOTSonly. You could use DISPlay:DOTsonly OFF instead)
DISPlay:GRAticule FULL;:*TRG (colon before a star (*) command)
MATH:HORizontal:SCAle 1.0e-1;HORizontal:P OSition 5.0el
(levels of the mnemonics are different; either remove the second use of
HORizontal: or place :MATH in front of HORizontal:POSition)
Terminating
This documentation uses <EOM> (End of Message) to represent a message
terminator.
Table 2-4: End of Message Terminator
Symbol Meaning
<EOM>
Th
concurrently with the last data byte). The last data byte may be an ASCII line
feed (LF) character.
This oscilloscope does not support ASCII LF only message termination. The
oscilloscope always terminates outgoing messages with LF and EOI.
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>.
Message terminator
e end-of-message terminator must be the END message (EOI asserte d
MSO3000 and DPO3000 Series Programmer Manual 2-5
Command Syntax
Math Spe
Cursor Position
Mnemonics
cifier Mnemonics
When cursors ar
e displayed, commands may specify which cursor of the pair to
use.
Table 2-5: Channel Mnemonics
Symbol Meaning
CH<x> A channel specifier; <x> is 1 through 4.
Table 2-6: Cursor Mnemonics
Symbol Meaning
CURSOR<x>
POSITION<x>
HPOS<x>
A cursor selector; <x> is either 1 or 2.
A cursor selector; <x> is either 1 or 2.
A cursor selector; <x> is either 1 or 2.
Commands can specify the mathematical waveform to use as a mnemonic in
the header.
Table 2-7: Math Specifier Mnemonics
Symbol Meaning
Math<x>
A math waveform specifier; <x> is 1.
Measurement Specifier
Mnemonics
hannel Mnemonics
C
Reference Waveform
Mnemonics
Commands can specify which measurement to set or query as a mnemonic in the
header. Up to four automated measurements may be displayed.
Table 2-8: Measurement Specifier Mnemonics
Symbol Meaning
MEAS<x> A measurement specifier; <x> is 1 through 4.
Commands specify the channel to use as a mnemonic in the header.
Commands can specify the reference waveform to use as a mnemonic in the
header.
Table 2-9: Reference Waveform Mnemonics
Symbol Meaning
REF<x>
A reference waveform specifier; <x> is 1, 2, 3, or 4 for 4-channel
oscilloscopes and 1 or 2 for 2-channel oscilloscopes.
2-6 MSO3000 and DPO3000 Series Programmer Manual
Argument Types
Command Syntax
Commands use arguments such as enumeration, numeric, quoted string and block.
Each of these arguments are listed in detail below.
Enumeration
Numeric
Enter these arguments as unquoted text words. Like key words, enumeration
arguments follow the same convention where the portion indicated in uppercase is
required and that in lowercase is optional.
For example:
Many osci
SAVe:WAVEform:FILEFormat INTERNal
lloscope commands require numeric arguments. The syntax shows
the format that the oscilloscope returns in response to a query. This is also the
preferred format when sending the command to the oscilloscope though any of
the formats will be accepted. This documentation represents these arguments as
described below.
Table 2-10: Numeric Arguments
Symbol Meaning
<NR1>
<NR2> Floating point value without an exponent
<NR3> Floating point value with an exponent
<bin>
Signed integer value
Digital data in binary format
Most numeric arguments will be automatically forced to a valid setting, by either
rounding or truncating, when an invalid number is input, unless otherwise noted
the command description.
in
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
"). The following is an example of a quoted string:
(
string"
. This documentation represents these arguments as follows:
"This is a quoted
Table 2-11: Quoted String Argument
Symbol Meaning
<QString> Quoted string of ASCII text
MSO3000 and DPO3000 Series Programmer Manual 2-7
Command Syntax
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 ty
example:
2. You can mix q
previous rule. For example:
3. You c an i nc l
example:
4. Strings ca
pe of quote character to open and close the string. For
"this is a valid string".
uotation marks within a string as long as you follow the
"this is an 'acceptabl e' string ".
ude a quote character within a string by repeating the quote. For
"here is a "" mark".
n have upper or lower case characters.
5. If you use a GPIB network, you cannot terminate a quoted string with the
END messa
ge before the closing delimiter.
6. A carriage return or line feed embedded in a quoted string does not terminate
the s tri
ng. The return is treated as another character in the string.
7. The maximum length of a quoted string returned from a query is 1000
ters.
charac
Here are some invalid strings:
"Invalid string argument' (quotes are not of the same type)
Block
"test<EOI>" (termination character is embedded in the string)
Several oscilloscope commands use a block argument form, as defined in the
table below.
Table 2 -12: Block Argument
Symbol Meaning
<NZDig>
<Dig>
<DChar> A character with the hexadecimal equivalent of 00 through FF (0
<Block>
A nonzero digit character i n the range of 1–9
A digit character, in the range of 0–9
through 255 decimal)
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 <NZDig> and <Dig> elements form a decimal integer that specifies how
many <DChar> elements follow.
2-8 MSO3000 and DPO3000 Series Programmer Manual
Command Syntax
MSO3000 and DPO3000 Series Programmer Manual 2-9
Command Syntax
2-10 MSO3000 and DPO3000 Series Programmer Manual
Command Groups
This manual lists the MSO/DPO3000 Series IEEE488.2 commands in two ways.
First, it presents them by functional groups. Then, it lists them alphabetically. The
functional g
command. (See page 2-93, Commands Listed in Alphabetical Order.)
Acquisition Command Group
Use the commands in the Acquisition Command Group to set up the modes and
functions that control how the oscilloscope acquires signals input to the channels,
and processes them into waveforms.
Using the commands in this group, you can do the following:
Start and stop acquisitions.
roup list starts below. The alphabetical list provides detail on each
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.
Control acquisition of channel waveforms.
Set acquisition parameters.
Table 2-13: Acquisition Commands
Command Description
ACQuire?
ACQuire:MAGnivu Sets or returns the MagniVu feature
ACQuire:MAXSamplerate?
ACQuire:MODe Sets or returns the acquisition mode
ACQuire:NUMACq? Returns the number of acquisitions that have
ACQuire:NUMAVg Sets or returns the number of acquisitions for
ACQuire:NUMEnv This command controls the number of
ACQuire:STATE Starts or stops the acquisition system
ACQuire:STOPAfter Sets or returns whether the acquisition is
Returns the acquisition parameters
Returns the maximum real-time sample rate
occurred
an averaged waveform
envelopes (when acquisition mode has been
set to ENVelope using ACQuire:MODe). The
number of envelopes can be set from 1 to
2000 in increments of 1, or to INFInite.
continuous or single sequence
MSO3000 and DPO3000 Series Programmer Manual 2-11
Command Groups
Alias Command
Group
Use the Alias commands to define new commands as a sequence of standard
commands. You may find this useful when repeatedly using the same commands
to perform ce
rtain tasks like setting up measurements.
Aliases are similar to macros but do not include the capability to substitute
parameters
into alias bodies. The alias mechanism obeys the following rules:
The alias name must consist of a valid IEEE488.2 message unit, which may
not appear
in a message preceded by a colon, comma, or a command or query
program header.
The a lias
name may not appear in a message followed by a colon, comma,
or question mark.
An alias
name must be distinct from any keyword or keyword short form.
An alias name cannot be redefined without first b eing deleted using one of
as deletion functions.
the ali
Alias names do not appear in response messages.
2-14: Alias Commands
Table
Command Description
s
ALIa
ALIas:CATalog? Returns a list of the currently defined alias
ALIas:DEFine
ALIas:DELEte
ALIas:DELEte:ALL Deletes all existing aliases
ALIas:DELEte[:NAMe]
ALIas[:STATE] Sets or returns the alias state
Sets or returns the alias state
labels
Assigns a sequence of program messages
n alias label
to a
moves a specified alias
Re
Removes a specified alias
2-12 MSO3000 and DPO3000 Series Programmer Manual
Command Groups
Bus Command Gr
oup
Use the Bus commands when working with serial or parallel bus measurements.
Install the DPO3EMBD application module when working with I2CorSPI
bus signals.
Install the DPO3AUTO module when working with CAN or LIN bus signals.
Install the DPO3COMP module when working with RS-232, RS-422,
RS-485, and UART bus signals.
Install the DPO3AUDIO module when working with I2S, Left Justified (LJ),
Right Justified (RJ), and TDM bus signals.
Install the DPO3AERO module when working with MIL-STD-1553 bus
signals.
Install the DPO3FLEX module when working with FlexRay bus signals.
NOTE. Parallel bus trigger and analysis functionality is included standard with
the MSO Series.
NOTE.
The Search Command Group and the Trigger Command Group also
contain bus-related commands.
Table2-15:BusCommands
Commands Description
BUS Returns the parameters for each bus
BUS:B<x>:AUDio:BITDelay Sets or returns the number of delay bits for
the AUDIO bus
BUS:B<x>:AUDio:BITOrder Sets or returns the bit order for the AUDIO
bus
BUS:B<x>:AUDio:CHANnel:SIZe Sets or returns the number of bits per
channel for the AUDIO bus
BUS:B<x>:AUDio:CLOCk:POLarity Sets or returns the clock polarity for the
AUDIO bus
BUS:B<x>:AUDio:CLOCk:SOUrce Sets or returns the clock source waveform
for the AUDIO bus
BUS:B<x>:AUDio:DATa:POLarity Sets or returns the data polarity for the
AUDIO bus
BUS:B<x>:AUDio:DATa:SIZe Sets or returns the number of bits per word
for the AUDIO bus
BUS:B<x>:AUDio:DATa:SOUrce Sets or returns the data source waveform for
the AUDIO bus
MSO3000 and DPO3000 Series Programmer Manual 2-13
Command Groups
Table2-15: BusCommands(cont.)
Commands Description
BUS:B<x>:AUDio:DISplay:FORMat Sets or returns the display format for the
AUDIO bus
BUS:B<x>:AUDio:FRAME:SIZe Sets or returns the number of channels in
each frame for the AUDIO bus
BUS:B<x>:AUDio:FRAMESync:POLarity Sets or returns the frame sync polarity for
the AUDIO bus
BUS:B<x>:AUDio:FRAMESync:SOUrce Sets or returns the frame sync source
waveform for the AUDIO bus
BUS:B<x>:AUDio:TYPe Sets or returns the audio format (type) for
the AUDIO bus
BUS:B<x>:AUDio:WORDSel:POLarity Sets or returns the word select polarity for
the AUDIO bus
BUS:B<x>:AUDio:WORDSel:SOUrce Sets or returns the word s elect source
waveform for the AUDIO bus
BUS:B<x>:CAN:BITRate Sets or returns the bit rate for the CAN bus
BUS:B<x>:CAN:PRObe Sets or returns the probing method used to
probe the C AN bus
BUS:B<x>:CAN:SAMPLEpoint Sets or returns the sample point (in %) to
sample during each bit period
BUS:B<x>:CAN:SOUrce Sets or returns the CAN data source
BUS:B<x>:DISplay:FORMAt Sets the display format for the numerical
information in the specified bus waveform
BUS:B<x>:DISplay:TYPe Sets the display type for the specified bus
BUS:B<x>:FLEXray:BITRate This command specifies the bit rate for
FlexRay
BUS:B<x>:FLEXray:CHannel This command specifies the FlexRay ID
format
BUS:B<x>:FLEXray:SIGnal Specifies which FlexRay standard to use:
BDIFFBP, BM or TXRX.
BUS:B<x>:FLEXray:SOUrce This command specifies the FlexRay data
source
BUS:B<x>:I2C:ADDRess:RWINClude Sets and returns whether the read/write bit is
included in the address
BUS:B<x>:I2C{:CLOCK|:SCLK}:SOUrce Sets or returns the I2C SCLK source
BUS:B<x>:I2C{:DATA|:SD ATA}:SOUrce Sets or returns the I2C SDATA source
BUS:B<x>:LABel Sets or returns the waveform label for the
specified bus
BUS:B<x>:LIN:BITRate Sets or returns the bit rate for LIN
BUS:B<x>:LIN:IDFORmat Sets or returns the LIN ID format
BUS:B<x>:LIN:POLARity Sets or returns the LIN polarity
2-14 MSO3000 and DPO3000 Series Programmer Manual
Loading...