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 publication supercedes
that in all previously published material. Specifications and price change privileges reserved.
Tektronix Japan, Ltd., Shinagawa Intercity Building B 6th Floor, 2-15-2 Konan, Minato-ku, Tokyo 108-6106 Japan
Tektronix, Inc., P.O. Box 500, Beaverton, OR 97077
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
Windows and Windows 98 are trademarks of Microsoft Corporation.
Hardware Warranty
Tektronix warrants that the products that it manufactures and sells will be free from defects in materials and workmanship
for a period of one (1) year from the date of shipment. If a product proves defective during this warranty period, Tektronix,
at its option, either will repair the defective product without charge for parts and labor, or will provide a replacement in
exchange for the defective product.
In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the
warranty period and make suitable arrangements for the performance of service. Customer shall be responsible for
packaging and shipping the defective product to the service center designated by Tektronix, with shipping charges prepaid.
Tektronix shall pay for the return of the product to Customer if the shipment is to a location within the country in which the
Tektronix service center is located. Customer shall be responsible for paying all shipping charges, duties, taxes, and any
other charges for products returned to any other locations.
This warranty shall not apply to any defect, failure or damage caused by improper use or improper or inadequate
maintenance and care. Tektronix shall not be obligated to furnish service under this warranty a) to repair damage resulting
from attempts by personnel other than Tektronix representatives to install, repair or service the product; b) to repair
damage resulting from improper use or connection to incompatible equipment; c) to repair any damage or malfunction
caused by the use of non-Tektronix supplies; or d) to service a product that has been modified or integrated with other
products when the effect of such modification or integration increases the time or difficulty of servicing the product.
THIS WARRANTY IS GIVEN BY TEKTRONIX IN LIEU OF ANY OTHER WARRANTIES, EXPRESS OR
IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. TEKTRONIX’ RESPONSIBILITY TO
REPAIR OR REPLACE DEFECTIVE PRODUCTS IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO
THE CUSTOMER FOR BREACH OF THIS WARRANTY. TEKTRONIX AND ITS VENDORS WILL NOT BE
LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IRRESPECTIVE
OF WHETHER TEKTRONIX OR THE VENDOR HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH
DAMAGES.
Software Warranty
Tektronix warrants that the media on which this software product is furnished and the encoding of the programs on the
media will be free from defects in materials and workmanship for a period of three (3) months from the date of shipment.
If a medium or encoding proves defective during the warranty period, Tektronix will provide a replacement in exchange
for the defective medium. Except as to the media on which this software product is furnished, this software product is
provided “as is” without warranty of any kind, either express or implied. Tektronix does not warrant that the functions
contained in this software product will meet Customer’s requirements or that the operation of the programs will be
uninterrupted or error–free.
In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the
warranty period. If Tektronix is unable to provide a replacement that is free from defects in materials and workmanship
within a reasonable time thereafter, Customer may terminate the license for this software product and return this software
product and any associated materials for credit or refund.
THIS WARRANTY IS GIVEN BY TEKTRONIX IN LIEU OF ANY OTHER WARRANTIES, EXPRESS OR
IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. TEKTRONIX’ RESPONSIBILITY TO
REPLACE DEFECTIVE MEDIA OR REFUND CUSTOMER’S PAYMENT IS THE SOLE AND EXCLUSIVE
REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF THIS WARRANTY. TEKTRONIX AND ITS
VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES IRRESPECTIVE OF WHETHER TEKTRONIX OR THE VENDOR HAS ADVANCE NOTICE OF
THE POSSIBILITY OF SUCH DAMAGES.
This programmer manual is for the WCA230A and WCA280A Portable Wireless
Communication Analyzers. It provides information on operating your analyzer
using the General Purpose Interface Bus (GPIB).
This manual is composed of the following sections:
HGetting Started outlines how to use the GPIB interface.
HSyntax and Commands defines the syntax used in command descriptions,
presents a list of all command subsystems, and presents detailed descriptions
of all programming commands.
HStatus and Events describes how the status and Events Reporting system
operates and presents a list of all system errors.
HProgramming Examples describes some example analyzer programs.
HAppendices provides additional information including character charts, GPIB
interface specification, and factory initialization settings.
Related Manual
WCA230A and WCA280A User Manual
(Standard accessory; Tektronix part number 071-1253-XX)
Describes how to install the analyzer and how to work with the menus and
details the functions.
Difference between WCA230A and WCA280A
WCA230A and WCA280A have the same functions except for their measurement frequency ranges:
WCA230ADC to 3 GHz. . . . . . . . .
WCA280ADC to 8 GHz. . . . . . . . .
Unless otherwise noted, descriptions in this manual apply to both.
WCA230A & WCA280A Programmer Manual
ix
Preface
x
WCA230A & WCA280A Programmer Manual
Getting Started
Getting Started
You can write computer programs that remotely set the analyzer front panel
controls or that take measurements and read those measurements for further
analysis or storage.
To help you get started with programming the analyzer, this section includes the
following sections:
HOverview of the Manual
Summarizes the type of programming information contained in each major
section of this manual.
HConnecting the Interface
Describes how to physically connect the analyzer to a controller.
HUsing GPIB Ports
Describes how to use the GPIB port.
HSetting the GPIB Parameters from the Front Panel
Describes how to set the GPIB parameters from the front panel.
WCA230A & WCA280A Programmer Manual
1-1
Getting Started
Overview of the Manual
The information contained in each major section of this manual is described
below.
Syntax and Commands
:CALCulate Commands
:TRIGger
:ABORt Commands
IEEE Common Commands
*CAL?
*CLS
*ESE
*ESR
*IDN?
*OPC
Section 2, Syntax and Commands, describes the structure and content of the
messages your program sends to the analyzer. Figure 1–1 shows command parts
as described in the Command Syntax subsection.
Command parts
Header
Comma
:MMEMory:COPYFILE1,FILE2
Mnemonics
Figure 1-1: Command parts
Section 2 also describes the effect of each command and provides examples of
how you might use it. The Command Groups section provides lists by functional
areas. The IEEE Common Commands and the subsequent sections arrange
commands alphabetically (Figure 1–2).
ArgumentsSpace
:CALCulate:MARKer:X
:CALCulate:MARKer:AOFF
S
A
E
:CALCulate:DLINe
S
A
Syntax: . . .
E
Arguments:
Examples: . . .
Commands grouped in functional areasCommands listed alphabetically
Figure 1-2: Functional groupings and an alphabetical list of commands
1-2
WCA230A & WCA280A Programmer Manual
Getting Started
Status and Events
The program may request information from the analyzer. The analyzer provides
information in the form of status and error messages. Figure 1–3 illustrates the
basic operation of this system.
Section 3, Status and Events, describes how to get status or event information
from the program and details the event and error messages.
Your program requests
status and event reports.
Controller
The analyzer sends status and event reports.
WCA230A/WCA280A
GPIB cable
Figure 1-3: EventĆdriven program
Programming Examples
Section 4, Programming Examples, includes Visual C++ source code as well as
sample programs for running macro programs.
Figure 1-4: Sample program (Visual C++ source code)
WCA230A & WCA280A Programmer Manual
1-3
Getting Started
Connecting the Interface
The analyzer has a 24-pin GPIB connector on its rear panel, as shown in
Figure 1–5. This connector has a D-type shell and conforms to IEEE Std
488.1–1987.
Attach an IEEE Std 488.1-1987 GPIB cable (Tektronix part number
012-0991-00) to this connector.
GPIB connector
1-4
Figure 1-5: GPIB connector (rear panel)
Appendix B: GPIB Interface Specifications gives more information on the GPIB
configuration of the analyzer.
For the other interfaces, refer to the WCA230A and WCA280A User Manual.
WCA230A & WCA280A Programmer Manual
Using the GPIB Port
Getting Started
The analyzer has Talker/Listener functions through which it can communicate
with other devices, as well as the external controller, located on the bus.
GPIB
ControllerUsing the analyzer as a talker or listener
Figure 1-6: GPIB connection
GPIB Requirements
Observe these rules when you use your analyzer with a GPIB network:
HAssign a unique device address to each device on the bus. No two devices
can share the same device address.
HDo not connect more than 15 devices to any one bus.
HConnect one device for every 2 meters (6 feet) of cable used.
HDo not use more than 20 meters (65 feet) of cable to connect devices to a
bus.
HTurn on at least two-thirds of the devices on the network while using the
network.
HConnect the devices on the network in a star or linear configuration as shown
in Figure 1–7. Do not use loop or parallel configurations.
GPIB Device
GPIB Device
GPIB Device
GPIB Device
GPIB Device
GPIB Device
Figure 1-7: Typical GPIB network configurations
WCA230A & WCA280A Programmer Manual
GPIB Device
1-5
Getting Started
Setting the GPIB Parameters from the Front Panel
Set the GPIB parameters as required for the bus configuration. Once you have set
the parameters, you can control the analyzer through the GPIB interface.
1. Press the SYSTEM key in the UTILITY block.
SYSTEM key
2. Press the Remote Setup... side key.
3. Press the Remote Interface side key to select On.
4. Press the side key GPIB Setup...→ GPIB Address and set the address
using either the general purpose knob or the numeric keypad.
The range is 0 to 30 (factory default setting: 1).
NOTE. The GPIB address cannot be initialized with *RST command.
Remote Setup menu
Remote Interface
Selects whether the connection
between the analyzer and GPIB
is turned on or off.
GPIB Setup...
Sets the GPIB parameters
such as address.
1-6
Figure 1-8: Setting the GPIB parameters
WCA230A & WCA280A Programmer Manual
Getting Started
To disconnect the analyzer from the bus:
HPress the Remote Interface side key to select Off.
When the analyzer is disconnected from the bus, all the communication
processes with the controller are interrupted.
WCA230A & WCA280A Programmer Manual
1-7
Getting Started
1-8
WCA230A & WCA280A Programmer Manual
Syntax and Commands
Command Syntax
This section contains information on the Standard Commands for Programmable
Instruments (SCPI) and IEEE 488.2 Common Commands you can use to
program your WCA230A/WCA280A analyzer. The information is organized in
the following subsections:
HBackus-Naur Form Definition
HSCPI Commands and Queries
HIEEE 488.2 Common Commands
HConstructed Mnemonics
BackusĆNaur Form Definition
This manual may describe commands and queries using the Backus-Naur Form
(BNF) notation. Table 2–1 defines the standard BNF symbols:
Table 2-1: BNF symbols and meanings
SymbolMeaning
<ą>Defined element
::=Is defined as
|Exclusive OR
{ą}Group; one element is required
[ą]Optional; can be omitted
.ă.Ă.Previous element(s) may be repeated
(ą)Comment
WCA230A & WCA280A Programmer Manual
2-1
Command Syntax
SCPI Commands and Queries
SCPI is a standard created by a consortium that provides guidelines for remote
programming of instruments. These guidelines provide a consistent programming environment for instrument control and data transfer. This environment
uses defined programming messages, instrument responses, and data format
across all SCPI instruments, regardless of manufacturer. The analyzer uses a
command language based on the SCPI standard.
The SCPI language is based on a hierarchical or tree structure (see Figure 2–1)
that represents a subsystem. The top level of the tree is the root node; it is
followed by one or more lower-level nodes.
TRIGger
SEQuence
POLarity
SOURceLEVel
Root node
LowerĆlevel nodes
Figure 2-1: Example of SCPI subsystem hierarchy tree
You can create commands and queries from these subsystem hierarchy trees.
Commands specify actions for the instrument to perform. Queries return
measurement data and information about parameter settings.
2-2
WCA230A & WCA280A Programmer Manual
Command Syntax
Creating Commands
Creating Queries
Query Responses
SCPI commands are created by stringing together the nodes of a subsystem
hierarchy and separating each node by a colon.
In Figure 2–1, TRIGger is the root node and SEQuence, LEVel, POLarity, and
SOURce are lower-level nodes. To create a SCPI command, start with the root
node TRIGger and move down the tree structure adding nodes until you reach
the end of a branch. Most commands and some queries have parameters; you
must include a value for these parameters. If you specify a parameter value that
is out of range, the parameter will be set to a default value. The command
descriptions, which start on page 2–35, list the valid values for all parameters.
For example, TRIGger:SEQuence:SOURce EXT is a valid SCPI command
created from the hierarchy tree in Figure 2–1.
To create a query, start at the root node of a tree structure, move down to the end
of a branch, and add a question mark. TRIGger:SEQuence:SOURce? is an
example of a valid SCPI query using the hierarchy tree in Figure 2–1.
The query causes the analyzer to return information about its status or settings.
When a query is sent to the analyzer, only the values are returned. When the
returned value is a mnemonic, it is noted in abbreviated format, as shown in
Table 2–2.
Table 2-2: Query response examples
QueryResponse
:DISPlay:OVIew:SGRam:X:SPAN?10.0E+6
:SENSe:AVERage:TYPE?RMS
A few queries also initiate an operation action before returning information. For
example, the *CAL? query runs a calibration.
WCA230A & WCA280A Programmer Manual
2-3
Command Syntax
Parameter Types
Every parameter in the command and query descriptions is of a specified type.
The parameters are enclosed in brackets, such as <value>. The parameter type is
listed after the parameter and is enclosed in parentheses, for example, (discrete).
Some parameter types are defined specifically for the WCA200 Series command
set and some are defined by ANSI/IEEE 488.2-1987 (refer to Table 2–3).
Table 2-3: Parameter types used in syntax descriptions
Parameter typeDescriptionExample
arbitrary block
booleanBoolean numbers or valuesON or 1; OFF or 0
discreteA list of specific valuesMIN, MAX, UP, DOWN
binaryBinary numbers#B0110
octalOctal numbers#Q57, #Q3
hexadecimal
2,3
NR1
1
A specified length of arbitrary data#512234xxxxx . . .
where 5 indicates that the followĆ
ing 5 digits (12234) specify the
length of the data in bytes;
xxxxx ... indicates the data
2
Hexadecimal numbers
#HAA, #H1
(0-9, A, B, C, D, E, F)
numericIntegers0, 1, 15, -1
NR22numericDecimal numbers1.2, 3.141516, -6.5
NR32numericFloating point numbers3.1415E-9, -16.1E5
NRf2numericFlexible decimal number that may
be type NR1, NR2 or NR3
4
string
Alphanumeric characters
See NR1, NR2, and NR3 examĆ
ples
Testing 1, 2, 3"
(must be within quotation marks)
1
Defined in ANSI/IEEE 488.2 as Definite Length Arbitrary Block Response Data."
2
An ANSI/IEEE 488.2-1992Ćdefined parameter type.
3
Some commands and queries will accept an octal or hexadecimal value even though
the parameter type is defined as NR1.
4
Defined in ANSI/IEEE 488.2 as String Response Data."
2-4
WCA230A & WCA280A Programmer Manual
Command Syntax
SCPIĆdefined Parameters. In addition to the ANSI/IEEE 488.2-1987-defined
parameters, WCA200 Series support the following SCPI-defined parameters.
H<NRf> for boolean
OFF|ON|0|1|<NRf>
You can use <NRf> for boolean parameter. The values other than zero (OFF)
are regarded as one (ON).
HMAXimum and MINimum for numeric parameters
You can use MAXimum and MINimum for the numeric parameter <NRf>.
The following example sets the trigger level to the maximum (100%).
:TRIGger[:SEQuence]:LEVel:IF MAXimum
The commands that have numeric parameters support the following query:
<header>? { MAXimum | MINimum }
The query command returns the maximum or minimum acceptable value for
the command. For example,
:TRIGger[:SEQuence]:LEVel:IF? MAXimum
returns 100 indicating the maximum trigger level is 100%.
HUP and DOWN for numeric parameters
The [:SENse]:FREQuency:CENTer command (refer to page 2–259) supports
UP and DOWN for the numeric parameters. The increment/decrement of
UP/DOWN is determined by one of these commands:
The Line Feed (LF) character (ASCII 10), and all characters in the range of
ASCII 127-255 are defined as special characters. These characters are used in
arbitrary block arguments only; using these characters in other parts of any
command yields unpredictable results.
You can abbreviate most SCPI commands, queries, and parameters to an
accepted short form. This manual shows these short forms as a combination of
upper and lower case letters. The upper case letters indicate the accepted short
form of a command. As shown in Figure 2–2, you can create a short form by
using only the upper case letters. The accepted short form and the long form are
equivalent and request the same action of the instrument.
Long form of a command
Accepted short form of a
command and parameter
ulate3:MARKer:Y 50
:CALC
Minimum information needed for
accepted short form
CALC3:MARK:Y 50
Figure 2-2: Example of abbreviating a command
NOTE. The numeric suffix of a command or query may be included in either the
long form or short form; the analyzer will default to “1” if no suffix is used. In
Figure 2–2, the “3” of “CALC3” indicates that the command is directed to
View 3.
2-6
WCA230A & WCA280A Programmer Manual
Loading...
+ 400 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.