Tektronix TSO820, TSO8C17, TSO8C18 Programmer

xx
8 Series Sampling
ZZZ
Oscilloscope Programmer Manual
This document supports software release
1.0
www.tek.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 supersedes that in all previously published material. Specifications and price change privileges reserved.
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
TekVISA is a trademark of Tektronix, Inc.
Contacting Tektronix
Tektronix, Inc. 14150 SW Karl Braun Drive P.O. B o x 5 0 0 Beaverto USA
For product information, sales, service, and technical support:
n, OR 97077
In North America, call 1-800-833-9200. Worldwide, visit www.tek.com to find contacts in your area.
Table of Contents
Preface.............................................................................................................. iii
Getting Started
Getting Started ..... . ..... ..... . ..... . ..... . .... . . .... . ..... . ...................................................... 1-1
Syntax and Commands
Command syntax ................................................................................................. 2-1
Command a
ClearingtheInstrument ..................................................................................... 2-3
Command entry .............................................................................................. 2-4
Constructed mnemonics..................................................................................... 2-6
Argument types .............................................................................................. 2-7
Command Groups and Descriptions.......................................................................... 2-11
Status and Events
nd Query structure............................................................................. 2-1
Status and Events................................................................................................. 3-1
Synchronization Methods................................................................................... 3-2
Messages...................................................................................................... 3-7
Commands Index
TSO8 Series Programmer Manual i
Table of Contents
ii TSO8 Series Programmer Manual
Preface
This programmer manual provides you with the information required to use SCPI programmatic commands (PI) to remotely control a Tektronix TSO820 Sampling Oscilloscop
e through LAN connection.
TSO8 Series Programmer Manual iii
Preface
iv TSO8 Series Programmer Manual
Getting Started
This programmer manual provides you with the information required to use PI commands to remotely control your instrument. With this information, you can write comput provided by the User Interface.
er programs that will perform virtually all the same functions as
The program
Syntax and Commands. This section provides an overview of the command syntax use about commands, such as how commands and queries are constructed, how to enter commands, constructed mnemonics, and argument types.
Commands. This section contains all the commands and related arguments, returns, and examples. Commands are listed by group.
Status and Events. This section discusses the status and event reporting system for the GPIB interfaces. This system informs you of certain significant events that occur within the instrument. Topics discussed include registers, queues, event handling sequences, synchronization methods, and messages that the instrument may return, including error messages.
mer manual is divided into the following major sections:
d to communicate with the instrument and other general information
TSO8 Series Programmer Manual 1-1
Getting Started
1-2 TSO8 Series Programmer Manual
Command syntax
You can control the operations and functions of the instrument through the LAN interface using commands and queries. The related topics listed below 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.
syntax of these commands and queries. The topics also describe the
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 instrument settings or tell the instrument to perform a specific action. Queries cause the instrument to return data and status information.
Dened element
Is dened 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 on 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
TSO8 Series Programmer Manual 2-1
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.
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 instrument 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 TSO8 Series Programmer Manual
Command syntax
Queries
Headers
Queries cause t
he instrument to return status or setting information. Queries
have the structure:
[:]<Header>?
[:]<Header>?[<Space><Argument> [<Coma><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 sp
ecified 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.
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
shows the difference in responses.
below
Table 2-3: Comparison of Header Off and Header On Responses
Query Header Off Header On
TIME?
ACQuire:NUMAVg?
"14:30:00" :TIME"14:30:00"
100
:ACQUIRE:NUMAVG 100
Clearing the Instrument
You can clear the Output Queue and reset TSOVu 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.
TSO8 Series Programmer Manual 2-3
Command syntax
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 instrument ignores commands consisting of any combination of white space characters and line feeds.
Abbreviating
atenating
Conc
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:NUMAVG or acq:numavg.
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.
You can concatenate any combination of set commands and queries using a semicolon (;). The instrument executes concatenated commands in the order received.
2-4 TSO8 Series Programmer Manual
Command syntax
When concatena
ting commands and queries, you must follow these rules:
Separate completely different headers by a semicolon and by the beginning colon on all co
TRIGger:SOUrce FREerun and ACQuire:NUMAVg 10,canbe
mmands except the first one. For example, the commands
concatenated into the following single command:
TRIGger:SOUrce FREerun;:ACQuire:NUMAVg 10
If concaten
ated 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 AVERage
and ACQuire:NUMAVg 10 into a single command:
ACQuire:MODe AVERage; NUMAVg 10
The longer version works equally well:
ACQuire
:MODe AVERage;:ACQuire:NUMAVg 10
Never precede a star (*) command with a colon:
ACQuire:MODe AVERage;*OPC
Any commands that follow will be processed as if the star command was not there so the commands,
ACQuire:MODe AVERage;*OPC;NUMAVg 10 will
set the acquisition mode to envelope and set the number of acquisitions for
aging to 10.
aver
When you concatenate queries, the responses to all the queries are
catenated into a single response message. For example, if the Acquire
con mode is set to sample and state is set to on, the concatenated query
:ACQuire:MODe?;STATE? will return the following.
If the header is on:
CQuire:MODe SAMple :ACQuire:STATE ON
:A
If the header is off:
SAMple;ON
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:MODE TILE;ACQuire:NUMAVg 10 (no colon before ACQuire)
TSO8 Series Programmer Manual 2-5
Command syntax
Terminating
DISPLAY:REF1 1 1;REF2 0
DISplay:MODE TILE;:*OPC (colon before a star (*) command)
CURSOR:VIEW1:VBARS:POSITION1 21E-9;VBARS:POSITION2 3.45E-6
instead)
1;:REF2 0
(extra colon before REF2; use DISPLAY:REF1
(levels of the mnemonics are different; either remove the second use of VBARS or place
:CURSOR:VIEW1: in front of VBARS:POSITION2 3.45E-6)
This documentation uses <EOM> (End of message) to represent a message terminator.
Table 2-4: E nd of Message Terminator
Symbol Meaning
<EOM>
Message terminator
The end-of-message terminator must be the END message (EOI asserted concurrently with the last data byte). The last data byte may be an ASCII linefeed (LF) character.
This instrument does not support ASCII LF only message termination. The instrument always terminates outgoing messages with LF and EOI. It allows white space before the terminator. For example,
CR LF.
Constructed mnemonics
Some header mnemonics specify one of a range of mnemonics. A channel mnemonic has to be M<n>{A|B}, where <n> is the module number and {A|B} is the channel name of the module. You use these mnemonics in the command just as you do any other mnemonic. For example, there is a M1A:POSITION command, and there is also a M1B:POSITION command.
Cursor Position
Mnemonics
Measurement specier
mnemonics
When cursors are displayed, commands may specify which cursor of the pair to use.
Table 2-5: Cursor Mnemonics
Symbol Meaning
CURSOR<n>
POSITION<n>
HPOS<n>
Commands can specify which measurement to set or query as a mnemonic in the header. Up to 32 automated measurements may be displayed in the system. The displayed measurements are specified in this way:
A cursor selector; <n> is either 1 or 2.
A cursor selector; <n> is either 1 or 2.
A cursor selector; <n> is either 1 or 2.
2-6 TSO8 Series Programmer Manual
Command syntax
Channel mnemonics
Refere
nce waveform
mnemonics
Table 2-6: Meas
Symbol Meaning
MEAS<n> A measurement specier; <n> is 1 through 32.
SOURCE<n> A waveform specier; <n> is either 1 (Source 1 waveform) or 2 (Source
REFLevel<n>
GATE<n> A gate spec
Commands
urement specier mnemonics
2 waveform).
A waveform specier for reference level measurements; <n> is either 1 (Source 1 wa
veform) or 2 (Source 2 waveform).
ier; <n> is either 1 (Gate 1) or 2 (Gate 2).
specify the channel to use as a mnemonic in the header.
Table 2-7: Channel mnemonics
Symbol Meaning
M<n>{A|B} A channel specier; <n> is 1 to 4.
Commands can specify the reference waveform to use as a mnemonic in the header.
Argument types
Num
eric
Table 2-8: Reference waveform mnemonics
Symbol Meaning
REF<n>
A reference waveform specier; <n> is 1 through 8.
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
ill be accepted. This documentation represents these arguments as follows:
w
Table 2-9: Numeric arguments
Symbol Meaning
<NR1>
<NR2> Floating point value without an exponent
<NR3> Floating point value with an exponent
Signed integer value
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.
TSO8 Series Programmer Manual 2-7
Command syntax
Quoted String
Some commands a
ccept 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-10: Quoted String Argument
Symbol Meaning
<QString> Quoted string of AS CII 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 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.
Block
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)
Several instrument commands use a block argument form (see the foll
owing table).
Table 2-11: Block Argument
bol
Sym
<NZDig>
<Dig>
Char>
<D
Block>
<
ning
Mea
nzero digit character in the range of 1–9
Ano
igit character, in the range of 0–9
Ad
haracter with the hexadecimal equivalent of 00 through FF (0
Ac
through 255 decimal)
A block of data bytes dened as: <Block> ::=
{#<NZDig><Dig>[<Dig>...][<DChar>...]
#0[<DChar>...]<terminator>}
|
2-8 TSO8 Series Programmer Manual
Command syntax
<NZDig> specifi the <NZDig> and <Dig> elements form a decimal integer that specifies how many <DChar> elements follow.
es the number of <Dig> elements that follow. Taken together,
TSO8 Series Programmer Manual 2-9
Command syntax
2-10 TSO8 Series Programmer Manual
Command Groups and Descriptions
TSO8 Series Programmer Manual 2-11
Acquisition Command Group
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 all waveforms are simply acquired and averaged.
Set the controls or conditions that start and stop acquisitions.
Get data on acquired waveforms and histograms.
Get acquisition parameters.
Clear all acquired data.
Quire:STOPAfter:CONDition
AC
ACQuire:
1.
ACQ
Wfms
STOPAfter:
UNT
CO
2. AVGComp
ACQuire:STATE \{ OFF | ON | RUN | STOP | <NR1> }*
ACQuire:NUMAVg
RUN/STOP button on the right side of TSOVu
ACQuire:MODe { SAMple | AVERage }
1. SAMple
2. AVERage
ACQuire:NUMAVg
Acquisition Mode in “Acquisition Menu”
smaller than Stop
ACQuire:CURRentcount:ACQWfms
After Count
ACQuire:DATA:CLEar
Clear acquisition data, but not setup
ACQuire:MODe
Description This command sets or queries the acquisition mode of the instrument, which determines how the final value of the acquisition interval is generated from the many data samples. The instrument applies the specified mode globally to all channel waveforms that it acquires. The three, mutually exclusive acquisition modes are:
Sample: Use Sample mode to see the signal in its purest form with no post processing. This is the default mode.
TSO8 Series Programmer Manual 1
Average: Use Average mode to reduce the apparent noise in the signal to reveal fundamental waveform behavior.
Syntax ACQuire:MODe { SAMple | AVERage } ACQuire:MODe?
Related Commands ACQuire:NUMAVg
Arguments
SAMple specifies sample mode, in which the displayed data point value is simply the sampled value that was taken during the acquisition interval. There is no post processing of acquired samples; the instrument overwrites waveforms at each new acquisition cycle. SAMple is the default acquisition mode.
AVERage specifies averaging mode, in which the resulting waveform shows an average of SAMple data points from several consecutive waveform acquisitions. The instrument processes the number of waveforms you specify into the acquired waveform, creating a running back-weighted 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.
Returns ACQUIRE:MODE? might return ACQUIRE:MODE AVERAGE, indicating that the displayed waveform is the average of the specified number of waveform acquisitions.
Examples ACQUIRE:MODE AVERage sets the acquisition mode to display a waveform that is an average of SAMple data points from several consecutive waveform acquisitions.
ACQuire:STATE
Description This command starts or stops acquisitions or queries whether the acquisition is running or stopped.
Syntax ACQuire:STATE { OFF | ON | RUN | STOP | 1 | 0 } ACQuire:STATE?
Arguments
OFF stops acquisitions.
STOP stops acquisitions.
ON starts acquisitions.
RUN starts acquisitions.
0 stops acquisitions.
1 starts acquisitions.
Returns ACQUIRE:STATE? might return ACQUIRE:STATE 1, indicating that the acquisition system is running.
Examples ACQUIRE:STATE RUN starts acquisition of waveform data.
ACQuire:CURRentcount:ACQWfms?
TSO8 Series Programmer Manual 2
Description This query only command returns the current count value of acquired waveforms. The target value of this count is set by the ACQuire:STOPAfter:COUNt command (in conjunction with the ACQuire:STOPAfter:CONDition command). The instrument then counts up to this value. When the count reaches (or exceeds) the value, acquisition stops, and the specified StopAfter action is enabled.
Syntax ACQuire:CURRentcount:ACQWfms?
Related Commands
ACQuire:STOPAfter:COUNt
ACQuire:STOPAfter:CONDition
Arguments Query only command has no arguments.
Returns NR1 is the current count value of acquired waveforms.
Examples ACQUIRE:CURRENTCOUNT:ACQWFMS? might return ACQUIRE:CURRENTCOUNT:ACQWFMS 20, indicating that currently 20 waveforms have been acquired.
ACQuire:STOPAfter:MODe
Description This command tells the instrument when to stop taking acquisitions. The query form of this command returns the StopAfter mode. Syntax ACQuire:STOPAfter:MODe { RUNSTop | CONDition } ACQuire:STOPAfter:MODe?
Related Commands ACQuire:STOPAfter:CONDition ACQuire:STATE
Arguments
RUNSTop specifies that the run and stop state is determined by the RUN/STOP button of the application.
CONDition specifies that the run and stop state of the system is determined by a set a qualifiers specified by the StopAfter Condition. These sub-states are further described in the ACQuire:STOPAfter:CONDition section. (The instrument can still be stopped unconditionally by pressing the RUN/STOP button of the application or by sending the ACQuire:STATEcommand.)
Examples
ACQUIRE:STOPAFTER:MODE RUNSTOP sets the instrument to run or stop acquisitions when the user presses the RUN/STOP button of the application or the user sends the ACQuire:STATE command.
ACQUIRE:STOPAFTER:MODE? might return ACQUIRE:STOPAFTER:MODE CONDITION, indicating that the run and stop state of the system is determined by a set of qualifiers specified by the StopAfter condition.
ACQuire:STOPAfter:CONDition
TSO8 Series Programmer Manual 3
Description This command sets or queries the StopAfter condition. The StopAfter condition qualifies a stop condition for the acquisition system. Only one StopAfter condition can be active at a given time. Each StopAfter condition identifies, directly or indirectly, a specific data element or operation such that all mutually exclusive conditions are unique and unambiguous. This command allows you to specify the condition on which to stop acquiring. The condition is valid when the ACQuire:STOPAfter:MODE is set to CONDition.
Syntax ACQuire:STOPAfter:CONDition { ACQWfms | AVGComp } ACQuire:STOPAfter:CONDition?
Related Commands ACQuire:STOPAfter:COUNt ACQuire:NUMAVg
Arguments
ACQWfms sets the instrument to stop acquiring after some specified number of raw acquisition cycles. This setting tells the instrument to count the number of MainTime base sweeps (Mag sweeps are not counted independently) and stop acquisition after the specified number of acquisitions has been reached. Use the ACQuire:STOPAfter:COUNt command to set the target number of waveforms.
AVGComp sets the instrument to stop acquisition after the number of waveforms specified by the ACQuire:NUMAVg command have been acquired and averaged.
Examples ACQUIRE:STOPAFTER:CONDITION ACQWFMS sets the instrument to stop acquiring after some specified number of raw acquisition cycles. ACQUIRE:STOPAFTER:CONDITION? might return ACQUIRE:STOPAFTER:CONDITION ACQWFMS
ACQuire:STOPAfter:COUNt
Description This command sets or queries the target StopAfter count for the condition specified by the ACQuire:STOPAfter:CONDition command. The current count for the condition must be equal to or greater than this value before acquisitions are stopped and a StopAfter action is enabled. The state of the numeric StopAfter count for each condition is kept individually so that you do not need to re-enter a count when switching between conditions. Use the appropriate ACQuire:CURRentcount command to get the current count for a condition.
Syntax ACQuire:STOPAfter:COUNt <NR1> ACQuire:STOPAfter:COUNt?
Related Commands ACQuire:STOPAfter:MODe ACQuire:STOPAfter:CONDition ACQuire:CURRentcount:ACQWfms?
Arguments NR1 is the count value that must be reached (or exceeded) before the acquisitions stop and StopAfter action can occur.
Examples
ACQUIRE:STOPAFTER:COUNT 12 sets the StopAfter count for the specified condition to 12.
TSO8 Series Programmer Manual 4
ACQUIRE:STOPAFTER:COUNT? might return ACQuire:STOPAfter:COUNt 5, indicating that the total count for the specified condition is 5.
ACQuire:NUMAVg
Description This command sets or queries the number of waveform acquisitions that makeup an averaged waveform. Use the ACQuire:MODe command to enable the Average mode.
Syntax ACQuire:NUMAVg <NR1> ACQuire:NUMAVg?
Related Commands ACQuire:MODe
ACQuire:STOPAfter:CONDition
Arguments NR1 is the number of consecutive waveform acquisitions (from 2 to 4,096) used for averaging.
Examples
ACQUIRE:NUMAVG 10 specifies that an averaged waveform will show the result of combining 10 separately acquired waveforms.
ACQUIRE:NUMAVG? might return ACQUIRE:NUMAVG 75, indicating that there are 75 acquisitions specified for averaging.
ACQuire:DATa:CLEar
Description This command (no query form) causes an acquisition reset and clears all acquired data and clears the display. When a clear data occurs, it has the following effects:
When Acquisition is Running the current waveform data is replaced by the waveform data of the next acquisition cycle when it is available.
Counts. Resets all counts, including number of acquired waveforms, acquisition and average counts, conditional stop counts.
Measurement statistics. Measurement statistics are reset.
Histogram data and statistics. The data and all statistics will be cleared immediately.
Syntax ACQuire:DATa:CLEar
Examples ACQUIRE:DATA:CLEAR causes an acquisition reset and clears all acquired data.
Compensation Command Group
The compensation commands provide information about the current state of the compensation for the mainframe and all installed module channels, means to invoke compensation functions, and management of compensation storage memory locations.
TSO8 Series Programmer Manual 5
COMPensate:M[n]{A|B}
Description This command (no query form) compensates the module channel for DC variances. Volatile run-time compensation data for compensated channels are saved into their respective nonvolatile user memories.
Warning: Before proceeding, please save your setup.
For Mainframe SPC (Signal Path Compensation):
1. Disconnect or disable signals to mainframe’s Clock Prescale Input. For Module SPC (Signal Path Compensation):
1. Leave any trigger/clock signal connected to the mainframe’s Clock Prescale Input.
2. Disconnect or disable signals from sampling modules Inputs.
3. Terminate all unused electrical inputs with a 50 Ohms terminator and cover the unused optical modules inputs with dust covers.
Syntax
COMPensate:M[n]{A|B}
Examples
COMPENSATE:M1A performs the compensation routines for channel A on module 1.
COMPensate:MAInframe
Description This command (no query form) compensates the mainframe for DC variances. Volatile run-time compensation data for compensated mainframes are saved into their respective nonvolatile user memories.
Warning: Before proceeding, please save your setup.
For Mainframe SPC (Signal Path Compensation):
2. Disconnect or disable signals to mainframe’s Clock Prescale Input.
For Module SPC (Signal Path Compensation):
4. Leave any trigger/clock signal connected to the mainframe’s Clock Prescale Input.
5. Disconnect or disable signals from sampling modules Inputs.
6. Terminate all unused electrical inputs with a 50 Ohms terminator and cover the unused optical modules inputs with dust covers.
Syntax
COMPensate:MAInframe
Examples
COMPENSATE:MAINFRAME performs the compensation routines for channel A on module 1.
COMPensate:DATE:M[n]{A|B}?
Description This is a query only command that returns the date and the time of the current in-use (that is, run-time) compensation data for the module channel.
Syntax COMPensate:DATE:M[n]{A|B}?
TSO8 Series Programmer Manual 6
Returns <QString> Date and the time of the current in-use compensation data
Examples COMPENSATE:DATE:M1A? might return COMPENSATE:DATE:M1A "10/15/2019 7:55:01 AM"
COMPensate:DATE:MAInframe?
Description This is a query only command that returns the date and the time of the current in-use (that is, run-time) compensation data for the mainframe.
Syntax COMPensate:DATE:MAInframe?
Returns <QString> Date and the time of the current in-use (that is, run-time) compensation data for the mainframe.
Examples COMPENSATE:DATE:MAINFRAME? might return COMPENSATE:DATE:MAINFRAME "12/23/1973 1:13:34 AM"
COMPensate:RESults?
Description This is a query only command that returns an abbreviated status about the results of the last compensation execution. Any result other than PASS generally indicates a failure. For a more detailed message about the results of the last compensation execution, use the COMPensate:RESults:VERBose? query.
Syntax COMPensate:RESults?
Returns <QString>
Examples COMPENSATE:RESULTS? might return COMPENSATE:RESULTS "PASS", indicating that the compensation was successful.
COMPensate:STATus:M[n]{A|B}?
Description This is a query only command that returns the current compensation status for the module channel.
Syntax COMPensate:STATus:M[n]{A|B}?
Returns Enum. Possible responses are DEFaults, WARMup, FAIL, PASS, and COMPReq.
TSO8 Series Programmer Manual 7
Examples COMPENSATE:STATUS:M1A? might return COMPENSATE:STATUS:M1A COMPREQ, indicating that the warm-up period for the instrument has elapsed, but the current compensation temperature delta is greater than desired, or that the specified module has been moved to a different module compartment since last compensated. In either case, the instrument should be compensated again.
COMPensate:STATus:MAInframe?
Description This is a query only command that returns the current compensation status for the mainframe.
Syntax COMPensate:STATus:MAInframe?
Returns Enum. Possible responses are DEFaults, WARMup, FAIL, PASS, and COMPReq.
Examples COMPENSATE:STATUS:MAINFRAME? might return COMPENSATE:STATUS:MAINFRAME PASS, indicating that the current compensation data should allow the instrument to meet operating specifications.
COMPensate:TEMPerature:M[n]{A|B}?
Description This query only command returns the difference (in °C) between the current temperature of the module channel and the associated temperature currently residing in the in-use run-time compensation memory.
Syntax COMPensate:TEMPerature:M[n]{A|B}?
Returns NR3
Examples COMPENSATE:TEMPERATURE:M1A? might return COMPENSATE:TEMPERATURE:M1A 1.5
COMPensate:TEMPerature:MAInframe?
Description This query only command returns the difference (in °C) between the current temperature of the mainframe and the associated temperature currently residing in the in-use run-time compensation memory.
Syntax COMPensate:TEMPerature:MAInframe?
Returns NR3
Examples COMPENSATE:TEMPERATURE:MAINFRAME? might return COMPENSATE:TEMPERATURE:MAINFRAME 2.7.
TSO8 Series Programmer Manual 8
Calibration Command Group
The calibration commands provide information about the current state of the calibration for the mainframe and all resident sampling-module channels.
CALibration:TEMPerature:MAInframe?
Description
This query only command returns the difference (in °C) between the current temperature of the mainframe and the associated temperature currently residing in the in-use run-time calibration memory.
Syntax CALibration:TEMPerature:MAInframe?
Returns NR3
Examples CALiBRATION:TEMPERATURE:MAINFRAME? might return CALiBRATION:TEMPERATURE:MAINFRAME 2.7.
CALibration:TEMPerature:M[n]{A|B}?
Description
This query only command returns the difference (in °C) between the current temperature of the module channel and the associated temperature currently residing in the in-use run-time calibration memory.
Syntax CALibration:TEMPerature:M[n]{A|B}?
Returns NR3
Examples CALiBRATION:TEMPERATURE:M1A? might return CALiBRATION:TEMPERATURE:M1A 1.5
CALibration:STATus:M[n]{A|B}?
Description
This is a query only command that returns the current calibration status for the module channel.
Syntax CALibration:STATus:M[n]{A|B}?
Returns Enum. Possible responses are FAIL or PASS.
Examples CALiBRATION:STATUS:M1A? might return CALiBRATION:STATUS:M1A PASS indicates the calibration test has passed.
CALibration:STATus:MAInframe?
Description
This is a query only command that returns the current calibration status for the mainframe.
TSO8 Series Programmer Manual 9
Syntax CALibration:STATus:MAInframe?
Returns Enum. Possible responses are FAIL and PASS
Examples CALiBRATION:STATUS:MAINFRAME? might return CALiBRATION:STATUS:MAINFRAME PASS, indicating that the current calibration data should allow the instrument to meet operating specifications.
CALIbration:DATE:M[n]{A|B}?
Description This is a query only command that returns the date and the time of the current in-use (that is, run-time) calibration data for the module channel.
Syntax CALIbration:DATE:M[n]{A|B}?
Returns <QString> Date and the time of the current in-use calibration data
Examples CALIBRATION:DATE:M1A? might return :CALIBRATION:DATE:M1A "12/23/1973 1:13:34 AM"
CALIbration:DATE:MAInframe?
Description This is a query only command that returns the date and the time of the current in-use (that is, run-time) calibration data for the mainframe.
Syntax CALIbration:DATE:MAInframe?
Returns <QString> Date and the time of the current in-use (that is, run-time) calibration data for the mainframe.
Examples CALIBRATION:DATE:MAINFRAME? might return :CALIBRATION:DATE:MAINFRAME "12/23/1973 1:13:34 AM"
Cursor Command Group
Use the commands in the Cursor Command Group to control the cursor display and readout. You can use these commands to control the setups for cursor 1 and cursor 2, such as waveform source, cursor position, and cursor color. You can also use the commands to select one of the following cursor functions:
Off. Shuts off the display of all cursors.
Vertical Bars. Displays vertical bar cursors, which provide traditional horizontal unit readouts for
Cursor 1 (bar1), Cursor 2 (bar2), the delta between them, and 1/delta (results in frequency when the horizontal unit is time).
Horizontal Bars. Displays horizontal bar cursors, which provide traditional vertical unit readouts for Cursor 1 (bar1), Cursor 2 (bar2), and the delta between them.
TSO8 Series Programmer Manual 10
Waveform. Displays waveform cursors, which provide horizontal and vertical unit readouts for Cursor 1 (bar1), Cursor 2 (bar2), the delta between them, and 1/delta (results in frequency when the horizontal unit is time).
CURSor[:VIEW[x]]:CURSor[x]:SOUrce
Description This command sets or queries which waveform is associated with the specified cursor. The optional [:VIEW[x]] argument specifies which waveform view's cursors to manipulate. The cursor is specified by x in the :CURSor[x] portion of the command, which can be 1 or 2.
Syntax :CURSor[:VIEW[x]]:CURSor[x]:SOUrce { M[n]{A|B} | REF[x] } :CURSor[:VIEW[x]]:CURSor[x]:SOUrce?
Arguments
M[n]{A|B} specifies a live waveform to use as the source for the specified cursor.
REF[x] specifies a reference waveform to use as the source for the specified cursor.
Returns The waveform that is associated with the specified cursor.
Examples
:CURSOR:CURSOR2:SOURCE M1B associates cursor 2 in the default waveform view with the module 1 channel B waveform.
:CURSOR:VIEW2:CURSOR1:SOURCE? might return :CURSOR:VIEW2:CURSOR1:SOURCE
REF5, indicating that in waveform view 2, cursor 1 is associated with the Ref 5 waveform.
CURSor[:VIEW[x]]:FUNCtion
Description This command sets or queries cursor type. The optional [:VIEW[x]] argument specifies which waveform view's cursors to manipulate.
Syntax :CURSor[:VIEW[x]]:FUNCtion { WAVEform | VBArs | HBArs | VHBars } :CURSor[:VIEW[x]]:FUNCtion?
Arguments
WAVEform enables waveform cursors, which provide both vertical and horizontal unit readouts but are constrained to valid data points of the selected waveform.
VBArs enables vertical bar cursors, which provide horizontal unit readouts.
HBArs enables horizontal bar cursors, which provide vertical unit readouts.
VHBars enables vertical and horizontal bar cursors, which provide their respective unit readouts.
Returns The current cursor type
Examples
:CURSOR:VIEW3:FUNCTION VBARS enables the vertical bar type cursors in waveform view 3.
:CURSOR:FUNCTION? might return :CURSOR:FUNCTION WAVEFORM, indicating that the
waveform type cursors are enabled in the default waveform view.
TSO8 Series Programmer Manual 11
Loading...
+ 97 hidden pages